Project wss sites migration to MOSS

[Sir Spoky]

I have the following Current Setup:
• Project server 2007 32 bit with WSS sites all on our server stand alone
again a SQL database server
• MOSS 2007 Farm (new). 2 WFE and 2 app servers

And want to achieve this:

• Project server 2007 32bit server not part of the MOSS farm
• MOSS 2007 64b farm hosting the project server WSS sites and have the
project server create future project sites on the MOSS farm


Based on the configuration above, does project need to be part of the MOSS
farm? Or can I just tell project where to host and create future sites on the
MOSS farm? I did not find any docs on this. Any idea?

 

[Jane Darnell]

Sir,

If I understand you correctly, you have two sets of users and licenses. One
set is for your MOSS installation, and one set is for project server. I
assume the project server set is a subset of the other MOSS2007 set.

As far as I can tell, you can publish your Project Server workspaces in your
MOSS farm without any problem, as long as the person publishing the site has
the proper permissions in the MOSS farm. The problem you will have if the
Project Server installation is not part of the MOSS farm, is that the PWA
permissions groups defined in the default Project Server installation are
unknown in the MOSS environment. This will create obvious problems for your
project server Risks, Issues, Documents, and Deliverables. Even if you
recreate the proper permission groups you may still have synchronization
issues. I have been meaning to test this specific scenario but haven't yet,
so I would appreciate it if you posted back here with your findings!

The other thing that you will need to keep in mind once you get it all up
and running, is that your default MOSS users will not be able to view the
project server Risks, Issues, Documents, and Deliverables unless you have set
up a non-PWA permissions group that you must then add manually to the various
workspaces (though you may be able to add this in to your project workspace
template as a customization). Basically you need to think about who needs
access to project data that is not already part of the project team and who
also doesn't need access to project server (for example, deliverables posted
in the workspace may be enough information for sales, so you don't need to
give sales access to the project plan in PWA).

good luck!
Jane

 

[Chandrashekhar Vyas]

Hi Jane,



I have a question here-



1. I have created a Top Level Web Site ( http://servername )

2. I Installed Project Server over MOSS 2007

3. I configured PWA and gave path as http://servername/PWA

4. Now I see Home/PWA tabs on the portal with the help of Site Settings Add
Links



What I am trying is Having a Top Level Web site which will have multiple Sub
Sites(Team Sites), and also a Project Web Access(SPSite). I could get that
structure anyhow - but I am not sure if this is the correct way to integrate
the Project Server with the MOSS2007. Also I am UINABLE to inherit the user
from Home Portal in the PWA sites.



Any help / suggestions in the direction will be really appreciated



Thanks

CV

 

[Jane Darnell]

Hi CV,
So far it looks like you are on the right track. You can setup the PWA site
to publish all workspaces under a <server>/PWA/Topsite where Topsite is a
high level site in MOSS. You cannnot have those workspaces inherit
permissions from MOSS, however, unless you create some special MOSS user
groups and include these in your default project workspace template.

In other words, what you want is logical and possible, but not with
out-of-the-box functionality.

The permission levels that come out of the box with Project Server are these:
1. Web Administrators (Microsoft Office Project Server) Users who have
Manage Windows SharePoint Services permission in Microsoft Office Project
Server.
2. Project Managers (Microsoft Office Project Server) Users who have
published this project or who have Save Project permission in Microsoft
Office Project Server.
3. Team members (Microsoft Office Project Server) Users who have
assignments in this project in Microsoft Office Project Server.
4. Readers (Microsoft Office Project Server) Users who have been added to
this project in Microsoft Office Project Server, but not assigned to tasks.

You can see these permission levels in any PWA workspace by clicking on
Site Settings > Permissions > Permission Levels

At the top of the screen you will see the sentence:
"This Web site has unique permission levels that are not inherited from the
parent Web site."

This is by design because the permissions are synched by Project Server. The
MS Project "Tools>Build team" function determines who gets (how much) access
to the workspace. If you want to set up another default readers group, do
this in MOSS and add them to the default workspace template. You can find the
link for extending the workspace on MSN.
good luck,
Jane