You've just navigated the labyrinth of installing Microsoft Project Server 2010. The software parts are in place, the initial setup is done, and you're probably breathing a sigh of relief. But here's the thing: installation is just the first act. The real magic, the ability to glean insights and make informed decisions, lies in the post-installation configuration. It's where you truly bring your Project Server environment to life.
Think of it like building a house. You've got the walls up, the roof on, but it's not livable until you wire the electricity, plumb the water, and connect everything so it works seamlessly. Project Server 2010 is much the same. You've created a Global Group for Report Authors, for instance, but until you connect that group to the Reporting Database, they can't actually do anything with it. This module, as the experts at MSProjectExperts detail in their book, is all about making those crucial connections.
One of the most significant steps is configuring Excel Services and PerformancePoint Services. Why? Because Project Server 2010 leans heavily on the SharePoint Server 2010 Report Center. This isn't just a place to dump reports; it's a dynamic hub driven by Excel Services. It's where your users will go to access dashboards and reports, whether they're automatically generated or custom-built to meet specific needs.
To make this reporting powerhouse truly accessible, you need to ensure your report authors can connect to the Project Server 2010 Reporting database from Excel 2010. This involves a few key steps. First, those report authors need to be members of the domain global group you set up earlier. Second, and critically, that group needs db_datareader rights on the reporting database. It sounds technical, and it is, but it's essential. The login must explicitly allow access to the database to pull schema information and, of course, the data itself. This is where you'll fire up SQL Server Management Studio, connect to your SQL Server instance, and start making those precise configurations.
Beyond reporting, there's also the matter of Secure Store Services for, well, reporting. And don't forget the foundational elements like installing the SQL Server Native Client and Analysis Management Objects. Tuning SQL Server for optimal performance is another vital piece of the puzzle, ensuring your system doesn't just work, but works well. Finally, verifying Project Server functionality and configuring SharePoint Service Applications ties it all together. It’s this intricate dance between different services that transforms a collection of installed software into a robust enterprise project management solution.
