System Administration

Once you have planned how you want to configure your enterprise environment, you will need to implement the decisions your team made. This chapter introduces how to use Project 2003's administrative functions to configure and manage Project 2003.

The system administrator has to take an active role in Project 2003 for a couple reasons. The administrator must establish a Project server's users, groups, and security levels. Also, all the views in Project Web Access have to be created by the administrator, and the administrator must give specific groups of users rights to display those views. Unless otherwise specified, all functions described in this chapter require administrative rights to the Project server.

The role of system administrator has several functions, and may be performed by one person or several people depending on how your organization wants to set up and manage your enterprise environment. An administrator may exist in the PMO and establish the settings according to PMO standards and processes. You may also have an administrator that sets up and manages the users, groups, security and other overall system features. This chapter will discuss all administrative functions, but will focus on the major administrative functions from a portfolio management aspect, as well as all items related to Project Professional setup.

For detailed information about establishing users, groups, features, and security, see "Customizing and Administering Microsoft Project Server" on the CD accompanying this book.

This chapter discusses the administration from two perspectives: what you need to do for and within Project Web Access and what you need to do for and within Project Professional.