Security for separate departments

[AmyB]

We have implemented MS Project Server 2003 at our institution for our IS and
Telecomm departments. We have other departments that want to start using MS
Project Pro and MS Project Web Access but they don't want to have to see our
projects and vice versa. One of them however needs to be the "Administrator"
of their projects.

If we are all on the same server instance - what is the easiest way to
segregrate their projects so that they don't see our projects and vice versa?
Can one of them still be set up such that they can see/edit all projects
within their department but still not have the same access as the IS/Telecom
Administrators that can now see and access ALL projects on our server?

Thank you!

Amy

 

[Dale Howard [MVP]]

Amy --

The simplest solution is to create a separate Project Server instance for
each department. This will allow users in each department to see their own
projects and resources, without being able to see the projects and resources
in other departments. You can create each instance using the EditSite tool,
available for free download at:

http://www.microsoft.com/downloads/...3e-54e1-40a9-9bb8-2dd293226b6f&DisplayLang=en

Any other solution would be much more complex, involving the use of custom
Groups and Categories. Hope this helps.

 

[AmyB]

Thank you for getting back to me so quickly! We'll try that and let you know!

Amy

 

[Dale Howard [MVP]]

Amy --

You are more than welcome, my friend!

 

[AmyB]

Ok - we downloaded the EditSite tool but when I try logging in as the
administrator - I keep getting the error:

You cannot be logged on because your security settings in Internet Explorer
do not allow per-session cookies. Enable per-session cookies, and try to log
on again. (5011)

But we are using IE6 and have enabled the Privacy setting "Ovveride
Automatic Cookie Settings" and "Always Allow Session Cookies". Have you see
this error before and any ideas of other ways to avoid it?

Thank you!

Amy

 

[Dale Howard [MVP]]

Amy --

I'm not a network guy, so you'll need to repost this question as a new
question and let the technical folks answer it. Hope this helps.

 

[Gary L. Chefetz [MVP]]

Amy,

You run the EditSite tool on the server, using a logon that is at least a
local administrator on the server or a domain admin.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[greg]

Amy --

The simplest solution is to create a separate Project Server instance for
each department. This will allow users in each department to see their own
projects and resources, without being able to see the projects and resources
in other departments. You can create each instance using the EditSite tool,
available for free download at:

http://www.microsoft.com/downloads/details.aspx?FamilyID=6dc2c83e-54e...

Any other solution would be much more complex, involving the use of custom
Groups and Categories. Hope this helps.











- Show quoted text -

Is there a Project Server 2007 version of this EditSite tool or is
there a better way to handle this scenario using PS2007?
Thanks

 

[Gary L. Chefetz [MVP]]

Greg:

There isn't a tool like it, I assume mostlby because you can easily perform
these actions through SharePoint Central Administration in 2007.
Provisioning a new site, for instance, is a breeze in 2007.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com