One problem that we have seen several times now is the issues of mixed skus in a farm. So the scenario is that a customer wants to make use of some of the features of Microsoft Office SharePoint Server 2007 (MOSS) as well as Microsoft Office Project Server 2007 (PS). The misconception is that you can add a "Project Server" to a farm that is an Office Server farm - so you just want one Project machine in your farm - just load Project Server on a machine and join the farm! WRONG! The way it works is that ALL servers in the farm need to have all the bits loaded for all the different server products. So if your farm has 2 application servers and 2 web front end servers then each of these needs to have the applicable installation (complete or web front end) for both MOSS and PS. You can then choose which services are running on which server - and you could have the MOSS services on one and the PS services on the other - but both applications need to be loaded on all servers. There is a new document which includes details of this mixed server installation available at http://go.microsoft.com/fwlink/?LinkId=79599. Page 105 onward gives details steps of the why and how you can get these server products working together.
Remember - it is not that Project needs anything from MOSS for it to work - but in a farm environment you just cannot have different servers with different sets of binaries. One other option would be to have Project Server in its own farm - but you would then lose some of the capabilities of MOSS to work with PS - particularly regarding search across project workspaces.
Technorati Tags: Project Server 2007
Hi Brian, thanks for the link to this document. Your explanation above does then beg the question about licencing. So assuming I have a 2 server farm for MOSS and PS2007, I need to load the bits for each on each server (total of 2 installs of MOSS and PS2007), but then only run the Project Server application on one of the servers. How many PS2007 Server licneces to I need to buy?
Great question Ben! I'm just seeking some clarification on that point - and will post back here when I have an answer.
Hope you're doing great. I'll be deploying Project Server 2007 integrated with MOSS 2007 whoch is already in place and I have 2 questions with regards to the large farm deployment scenario I'm gonna be implementing. First let me give a brief overview of the Servers Involved in my deployment:
Two Front-end Web Servers Running Web Application
One Application Server Running MS SharePoint Indexing Services
One Application Server Running MS SharePoint Query Services
Two Application Servers Running MS Project Server 2007 Services
VLAN 1 Serving Two Front End Web Servers
VLAN 2 Serving Four Application Servers
VLAN 3 Serving Database Servers in a Clustered Environment
1. Could you provide a list of the ports that are being used by Project Server 2007 web and application servers that need to opnened explicitly ?
I ask this because in a medium farm deployment I did recently we faced issues in the case of ports to be opened since due to firewall and VLAN scenario port blocking policies were in place. In PS 2003 we knew exactly which ports to have explicitly opened as we had documentation on it.
2. When you say "Install Office Project Server 2007 to all front-end Web and application servers in the farm" ALL servers would include the SPS query and index servers as they are also Application Servers or only the 2 web servers and application servers?
I would really appreciate you early response.
I will try and do a post shortly on ports it is really WSS so they may have some documents already. In brief they will be 80/443 for http, whatever SQL is using (but only from WFE/App Server) and SMB stuff between servers. Analysis Services ports will need to be available between the servers and AS as well as directly to clients. One tip - DON'T lock down during install if you can avoid it - lock down once everything is up and running.
You need to load the same bits on each type of server - so ALL WFE get ALL the WFE bits and ALL the App Servers get ALL the App server bits - then you can decide which services will be running on each.
Also note that although having multiple app servers gives scalability it does not by default give fault tolerance. If a server goes down it needs to be removed from the farm - the other servers will not know if has gone.
Hope this helps!
Can you shed some more light on your statement " One other option would be to have Project Server in its own farm - but you would then lose some of the capabilities of MOSS to work with PS - particularly regarding search across project workspaces." for me?
I am looking at deploying MOSS 2007 and need to figure out how it will work with Project 2007 as I plan my servers and farm(s).
Thanks for your question. As mentioned in my posting if you have a farm with MOSS and PS you need all the bits on all the servers, but can leave some of the services stopped on some servers. But there will still be a licensing implication. If you treat Project Server as it's own farm. So it has its own SharePoint Configuration database (which could be on the same SQL Server as the other MOSS farm's databases). In this case you could not use the proposals workflow in Project Server, you could not use Project Server web parts in pages on the MOSS farm, and you may have some other restrictions on some of the MOSS features that only work in the local farm. I think MOSS search should be OK - WSS search probably not.
I hope this helps and great to know you are thinking about this before deploying!
In your answer to Brian's question you said you would seek clarification on the licensing issue. Did you eve recieve that because I am lookign for the same answer
You do need a license for each server you load Project Server on - even if you are not running the services.
Thanks for this info....I find it quite appalling that you cannot connect an instance of project to an existing moss farm.
It goes against all the attributes of the term 'Farm'
I understand your frustration, but an instance of Project will be a farm in its own right - with its own config database - so not as straightforward as it seems.
Things to check: Check if the user has any other Front End Server, if yes then you will see the following