Deploying the Project Guide: Overview
After you create the main page, side panes, and scripts for a custom Project Guide, you need to deploy it to users. If the Project Guide is a prototype or deployed to a single user, then the work you've done so far is sufficient. If you're rolling the custom Project Guide out for a big organization, then deployment requires two more steps.
- Give users access to the Project Guide files.
- Configure Microsoft® Office Project 2003 to use the custom Project Guide for every user in the organization who needs it.
There are six ways to configure Project to use the custom Project Guide.
- Change the default Project Guide registry settings by using system policies. This is one way to deploy the Project Guide to a large user base. Changing the Project registry settings also makes it more difficult for end users to accidentally change the Project Guide settings. For more information on how to use system policies with Project settings, see the Microsoft Office Project 2003 Resource Kit.
- Deploying a Custom Project Guide shows five additional ways to configure Project through the object model, so that Project uses a different Project Guide XML content schema or main page.
For information on using other URL pages within Project, such as from a Web service, see Hosting Other Web Content in the Project Guide. For information on persisting Project Guide content between sessions, see Persisting the Project Guide's State.