There is a business case to keep Project Server out of the main corporate
MOSS farm. In the past year or so, Project Server admins may have been inclined
to apply the cumulative updates to address issues in Project Server more
frequently than they would have applied the cumulative updates for MOSS.
Since corproate intranets may be heavily customized or have high availability
requirements, a lot of folks have recommended keeping Project Server in its
own farm, and separate from the primary farm.
That doesn't mean that Project Server doesn't play well with MOSS though.
If they're on their own farm, i.e. I have my corporate intranet on one farm,
and Project Server/MOSS on another farm, then that's perfectly fine. In
that case, you may not even need MOSS on the Project Server farm, as you
can leverage many of the services in the corporate intranet to meet your
needs at a cheaper cost.
Boris Bazant released a white paper on the topic a month or two ago:
http://www.microsoft.com/downloads/...62-0e9d-4e8e-92b4-2e2bb64945b8&displaylang=en
- Andrew Lavinsky
Blog:
http://blogs.catapultsystems.com/epm