Admin doesn't have admin access in PS2007

[asadim]

I have my own Active Directory authenticated username on PS2007 which has
Admin and Full Control rights. I can access PWA and do my admin tasks from my
machine fine (on my machine I am logged in with my AD user to our domain).
One of our staff who also has admin rights had complained that she did not
have access to some features such as View Assignments for resources. I tried
logging in to PWA from her machine on which I wasn't logged in with my AD
user (she was logged in with her AD account, needless to say). I logged in
fine to PWA but many of the options were inaccessible to me too, as though I
no longer had admin rights! I went back to my own machine and logged into PWA
and everything was fine.

These permissions and security templates have been bugging me ever since I
strated using PS2007 and now seems like this problem has something to do with
them. Any help is greatly appreciated.

 

[Dale Howard [MVP]]

asadim --

Is the other administrator a member of any security Groups other than the
Administrators group in PWA? If so, remove her from all other Groups and
let us know if this resolves the problem.

 

[asadim]

I have tried that but no luck. Even Project Managers can't access some basic
functionalities such as View Assignments for a resource. I have made sure
that they have access to that feature but still they can't use it (it's
greyed out in PWA). Not only the PM's but even Admins can't (I mentioned this
situation in my initial post) -like I said only I can do admin tasks from a
machine that I'm logged into with my AD accout. So if I login to PWA from
another machine whose user is not me (i.e. I'm not logged in to the machine
with my AD account) it won't work either.

Please let me know if you need to know of any specific permissions. Thanks.

 

[Dale Howard [MVP]]

asadim --

When you click Server Settings - Project Web Access Permissions in PWA, are
all possible permissions set to Allow in the system? Let us know.

 

[asadim]

Yes they are.

 

[Dale Howard [MVP]]

asadim --

Then I'm fresh out of ideas. There is no reason that people should not be
able to access the features you describe. You might want to repost your
original question to see if anyone else might have some ideas for you.
Sorry I could not be of more help.

 

[mike.mahoney]

asadim --

Then I'm fresh out of ideas. There is no reason that people should not be
able to access the features you describe. You might want to repost your
original question to see if anyone else might have some ideas for you.
Sorry I could not be of more help.

--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultanthttp://www.msprojectexperts.comhttp://www.projectserverexperts.com
"We wrote the book on Project Server"







- Show quoted text -

asadim

There are two separate issues here; one is permission settings, and
clearly there is something different between the accounts you are
using; second is how PWA responds when you sign-in as another user on
a desktop which is already connnected to the network on a different
windows account. In my system adopting this approach I find the
signed-in user "inherits" many of the PWA attributes of the resident
user - don't know why have tried clearing out caches etc with no
conclusive result. It is improved hugely however if you set up forms
authentication (for test accounts). Doing this also provides a much
more practical environment for investigating permissioning.

regards

Mike