Remove Logon to Project Server access

[Pramraj]

I would like to Uncheck the checkbox 'Resource can Logon to Project Server'
for users who have left the organization. The objective is to change the user
account to an inactive resource and remove the windows account associated
with the resource.
However, the checkbox is greyed out after the user is created.
Can anyone suggest how I may go about doing this?

 

[Jonathan Sofer [MVP]]

Please specify if you are you using PS 2007 or PS 2003?

Generally you don't need to modify security settings for resources if you
inactivate them. Inactivating a resource is enough to prevent them from
ever entering the system. Same goes with removing the windows user account,
you don't need to do it.

I would recommend leaving the account in tact and simply setting the user
status to inactive. This way if the user ever comes back and assuming their
role hasn't changed drastically, all you would have to do is re-activate the
account and they will be back to status quo.

Jonathan

 

[Pramraj]

I am using PS 2007.
Thanks for the recommendation but it's not suitable for my organization.
In my organization, when a user leaves, the windows account is immediately
disabled. When you attempt to inactivate an account in Project Server, it
checks active directory to validate the account and hence returns an error
when I try to save the change from Active to Inactive. Since the User Logon
Account is a required field, I am forced to have a valid windows account
entered. The account now remains with a status of Active and with a windows
account which is not valid.
Hence the ideal solution will be for me to be able to Uncheck the "Resource
can Logon to Project Server" check box at which point the User Logon Account
is no longer required and I will be able to save the change and keep the
account as an Inactive Resource.
--
Regards,
Pramraj

Please specify if you are you using PS 2007 or PS 2003?

Generally you don't need to modify security settings for resources if you
inactivate them. Inactivating a resource is enough to prevent them from
ever entering the system. Same goes with removing the windows user account,
you don't need to do it.

I would recommend leaving the account in tact and simply setting the user
status to inactive. This way if the user ever comes back and assuming their
role hasn't changed drastically, all you would have to do is re-activate the
account and they will be back to status quo.

Jonathan

 

[Gary Chefetz]

Pramraj:

It's a stupid little bug that the checkbox is never available for editing
after initial setup. The workaround to saving the resource as inactive is to
change the authentication method to Forms authentication and enter any user
name, as the system does not validate non-Windows accounts during resource
editing.

I am using PS 2007.
Thanks for the recommendation but it's not suitable for my organization.
In my organization, when a user leaves, the windows account is immediately
disabled. When you attempt to inactivate an account in Project Server, it
checks active directory to validate the account and hence returns an error
when I try to save the change from Active to Inactive. Since the User
Logon
Account is a required field, I am forced to have a valid windows account
entered. The account now remains with a status of Active and with a
windows
account which is not valid.
Hence the ideal solution will be for me to be able to Uncheck the
"Resource
can Logon to Project Server" check box at which point the User Logon
Account
is no longer required and I will be able to save the change and keep the
account as an Inactive Resource.

 

[Pramraj]

Thanks Gary. Your workaround works fine.