Stop auto-creation of users

[Josh]

I am in a corporate environment that uses PWA. We have established our
resource pool and use it for all of our projects. However, silly users will
type in a resource instead of selecting from a dropdown within project. This
of course creates a user in Project Server by default with that "incorrect"
name. Can I restrict people from typing in an invalide or non-existing
username/resource? Thanks.

 

[Dale Howard [MVP]]

Josh --

To correct this situation, the Project Server administrator should do the
following:

1. Log into PWA with administrator permissions
2. Click Admin - Server Configuration
3. In the permissions grid, set all three permissions in the Account
Creation section to Deny
4. Click the Save Changes button

In the future, if your PM's insist on typing the names of resources in their
projects, they will see a Spooler error whenever they try to publish their
projects. Refer to the following link for the cause of and solution to the
Spooler error:

http://www.projectserverexperts.com/Shared Documents/UseLocalResource.htm

Hope this helps.

 

[Guest]

Hello Josh,

Yes, you can prevent this. Most of the server deployments I have participated
in
allow only administrators to create project server accounts or add new resources
to the enterprise resource pool. Presuming your organization has a dedicated
administrator, I generally recommend that you Deny all three of the following
global permissions at the server level:

Create Accounts when Requesting Status Reports
Create Accounts from Microsoft Office Project
Create Accounts when Delegating Tasks

To do this go to the Admin | Server Configuration page in project web access
(PWA) and check the Deny box for each of these global permissions.

Please note that this will prevent the use of local (non-enterprise) resources
on all enterprise projects.

For more information, search for these resources in the "Project Server 2003
Security Group Guide". This document can be downloaded from Microsoft
separately or as part of the Microsoft Office Project Server 2003 Resource Kit.

Bob Segrest, PMP
Microsoft Project Blackbelt

 

[mark.everett]

Josh -

Dale and Bob are correct and this is pretty standard. Bob mentioned
that this will prevent the use of local (non-enterprise) resources on
all enterprise projects. This is not entirely correct. Users can
still create Local Resources, but those local resources will not be
imported to Enterprise and, unless the Workgroup setting is changed to
"None" on the Resource Information Dialog, will cause a Spooler Error.


In addition to making these changes, it's a good idea to let your PM's
know the proper procedure.

Hope this helps.
Mark Everett | PMP
www.quantumpm.com