Installing Project Server can be a daunting task, not just the first time but even the third, fourth, or fifth time you attempt it, because there are numerous detailed steps and you must execute many of them manually. By taking the very structured approach I present in this chapter, and following each step and checkpoint in order, installing SharePoint Team Services (STS) and Project Server can be relatively quick and painless. Failure to adhere to these procedures can lead you to many hours of troubleshooting. Indeed, this is a strong warning, but I can’t overstate the pitfalls of installation.
In this chapter, I take you through the installation steps for deploying with Project Server, STS, and SQL Server on one box, as well as variances to deploying across two or three servers.
These instructions apply to an enterprise implementation and not to a workgroup implementation. I cover advanced scaling techniques as an addendum to the core installation process in a later chapter.
Instructions in this chapter are based on installing on the Windows 2000 Server family. These instructions don’t apply to beta or released to manufacturing (RTM) versions of Windows Server 2003. Look for potential service releases in the Microsoft Knowledge Base and TechNet Web sites for the latest information, and check the Apress Web site at http://www.apress.com/book/bookDisplay.html?bID=185 for updates to this book.
Project Server requires a domain to take advantage of all enterprise features. Installations outside of a domain security environment are problematic in a number of ways. STS requires Windows Integrated Authentication; therefore, you must provide at least a local logon for each user on the machine on which STS is running. Project Professional isn’t designed to talk to Project Server over the Internet. It’s very “chatty,” with the database making numerous data calls that return large record sets. This makes it clunky at low bandwidths and frame-relay networks.