Libros - Microsoft - Project Server 2003 Administrators Guide

Microsoft Office Project
Server 2003 Administrator’s Guide

Microsoft Office Project
Server 2003 Administrator’s Guide
Copyright
Information in this document, including URL and other Internet Web site references, is subject to
change without notice. Unless otherwise noted, the example companies, organizations, products,
domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and
no association with any real company, organization, product, domain name, e-mail address, logo,
person, place or event is intended or should be inferred. Complying with all applicable copyright
laws is the responsibility of the user. Without limiting the rights under copyright, no part of this
document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any
form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any
purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
 2003 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows NT, Analysis Services, Microsoft Office, Microsoft
Project, Portfolio Analyzer, Portfolio Modeler, Project Professional, Project Server, Project Web
Access, SharePoint Portal Server, Windows Server, and Windows SharePoint Services are either
registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries.
The names of actual companies and products mentioned herein may be the trademarks of their
respective owners.
Published: October 19, 2003
Updated: January 30, 2004
Applies To: Microsoft Office Project Server 2003, Microsoft Office Project Professional 2003,
Microsoft Office Project Web Access 2003
Author: James Scott
Editor: Kerry Landen; Laura Graham
Reviewed by: Project Product Development
Microsoft Office Project Server 2003 Administrator’s Guide i
Table of Contents
Introduction 1
Introduction .............................................................................. 1
Microsoft Office Project Server 2003 Online Books Series..................................... 1
What Will You Learn from this Book? ....................................................................... 2
Who Should Read this Book?.................................................................................... 2
How is this Book Structured? .................................................................................... 3
Revision History.......................................................................................................... 3
Chapter 1 5
Administering Project Server Using Project Web Access................ 5
Working in the Project Web Access Admin Center................................................... 7
Managing Users and Groups.............................................................................. 7
Managing Security .............................................................................................. 8
Managing Views .................................................................................................. 8
Configuring Project Server.................................................................................. 9
Managing Windows SharePoint Services ........................................................10
Managing Enterprise Features.........................................................................11
Customizing Project Web Access .....................................................................12
Cleaning Up Project Server Data......................................................................13
Understanding Project Server Security...................................................................14
Project Server Security .....................................................................................15
Users and Groups ......................................................................................17
Permissions................................................................................................18
Security Templates ....................................................................................18
Understanding Project Web Access Permissions...................................................19
When to Allow and Deny Project Web Access Permissions............................21
Understanding Active Directory Synchronization with Project Server...................21
Understanding Project Server 2003 Web Parts.....................................................22
Using the Default Project Server 2003 Web Parts .........................................23
Creating Custom Project Server 2003 Web Parts ..........................................23
Chapter 2 24
Managing Users and Groups ..................................................... 24
Managing Users .......................................................................................................24
Adding a User ....................................................................................................25
ii Microsoft Office Project Server 2003 Administrator’s Guide
Modifying a User ............................................................................................... 30

Deactivating or Reactivating a User ................................................................ 30
Merging Two User Accounts ............................................................................. 31
Managing Groups..................................................................................................... 32
Creating a Group............................................................................................... 34
Using a Portal Site with Project Web Access............................................ 37
Modifying a Group............................................................................................. 37
Deleting a Group............................................................................................... 38
Security Group Synchronization with Active Directory ........................................... 39
Synchronizing Project Server Groups with Active Directory............................ 40
Clearing the Active Directory Globally-Unique Identifier ................................. 43
Changing the Project Web Access Administrator Password.................................. 44
Chapter 3 45
Managing Security ................................................................... 45
Security Rules in Categories ................................................................................... 45
Importance of Resource Breakdown Structure in Defining Security ............. 46
Managing Categories............................................................................................... 47
Adding a Category............................................................................................. 49
Modifying a Category ........................................................................................ 54
Deleting a Custom Category............................................................................. 54
Security Templates .................................................................................................. 55
Adding a Security Template ............................................................................. 56
Modifying a Security Template......................................................................... 57
Deleting a Security Template ........................................................................... 59
User Authentication ................................................................................................. 60
Recommendations for Determining User Authentication............................... 62
Setting Authentication Options ........................................................................ 62
Chapter 4 65
Managing Views....................................................................... 65
About Views.............................................................................................................. 67
Using Versions in Project and Project Center Views ....................................... 68
Working with Project Views ..................................................................................... 68
Working with Project Center Views ......................................................................... 77
Working with Assignment Views.............................................................................. 81
Working with Resource Center Views ..................................................................... 85
Working with Portfolio Analyzer Views .................................................................... 88
Modifying, Copying, and Deleting Views ................................................................. 89
Making Views Available to Project Web Access Users........................................... 90
Getting Additional Views................................................................................... 91
Microsoft Office Project Server 2003 Administrator’s Guide iii
Chapter 5 93
Configuring Project Server........................................................ 93
Enterprise and Non-Enterprise Modes ...................................................................93
Running Project Server in Enterprise Mode ....................................................94
Running Project Server in Non-Enterprise Mode ............................................95
Enabling Enterprise Features...........................................................................96
Using Master Projects with Project Server ...............................................98
Allowing Projects to Use Local Base Calendars .....................................101
Enforcing a Single Currency ....................................................................101
Allowing Only Enterprise Projects to Be Published to Project Server....102
Synchronizing the Enterprise Resource Pool with Active Directory..............102
Selecting the Features Available to Users in Project Web Access ...............105
Specifying the Intranet or Extranet Addresses for Project Server................106
Menus.....................................................................................................................107
Adding a Custom Top-Link or Side-Pane Menu.............................................108
Modifying a Top-Link or Side-Pane Menu......................................................110
Deleting a Top-Link or Side-Pane Menu ........................................................111
Chapter 6 112
Managing Windows SharePoint Services...................................112
Windows SharePoint Services Collaboration Features........................................112
Collaborating with Documents .......................................................................113
Tracking Issues ...............................................................................................114
Identifying Risks..............................................................................................115
Using the Project Workspace .........................................................................117
Managing Windows SharePoint Services .............................................................118
Connecting to Windows SharePoint Services................................................119
Site Provisioning Settings...............................................................................121
Managing SharePoint Sites............................................................................125
Creating, Editing, and Deleting Windows SharePoint Services Sites ...126
Synchronizing Users, Permissions, and Other Information ...................127
Going to Windows SharePoint Services Site Administration.................128
Synchronizing Administrator Accounts ..........................................................130
Connecting to SharePoint Portal Server ........................................................131
Project Workspace Site Settings ...........................................................................133
Administration.................................................................................................135
Customization .................................................................................................136
Manage My Information .................................................................................140
Top-Level Site Administration................................................................................141
Users and Permissions...................................................................................142
Management and Statistics ...........................................................................143
Site Collection Galleries..................................................................................145
iv Microsoft Office Project Server 2003 Administrator’s Guide
Site Collection Administration........................................................................146

Central Administration...........................................................................................147
Virtual Server Configuration ...........................................................................148
Security Configuration ....................................................................................148
Server Configuration.......................................................................................151
Component Configuration ..............................................................................156
Chapter 7 159
Managing Enterprise Features ................................................ 159
Updating Resource Tables and OLAP Cubes........................................................159
Building the OLAP Cube and Updating Resource Availability.......................162
Updating Resource Availability.......................................................................164
Checking In Enterprise Projects ............................................................................165
Checking In Enterprise Resources........................................................................167
Using Versions........................................................................................................168
When to Use Project Versions........................................................................170
When to Use the Version Archived Option.....................................................171
Saving a Version of a Project .........................................................................171
Adding a Custom Version ...............................................................................172
Modifying a Custom Version...........................................................................172
Deleting a Custom Version.............................................................................173
Chapter 8 174
Customizing Project Web Access ..............................................174
Timesheet Tracking Settings.................................................................................174
Specifying the Default Tracking Settings for Project Plans ..........................176
Locking Down the Default Tracking Setting ...........................................176
Working with Managed Timesheet Periods...................................................177
Working with Non-Managed Timesheet Periods ...........................................180
Moving to Managed Timesheet Periods
from Non-Managed Timesheet Periods....................................................181
Define Current and Future Task Visibility ......................................................183
Gantt Chart Formats ..............................................................................................183
Grouping Formats ..................................................................................................185
Home Page Formats ..............................................................................................187
Links ................................................................................................................188
Content............................................................................................................189
Keyboard Shortcuts for the Home Page Formats Page................................190
Notifications and Reminders.................................................................................190
Microsoft Office Project Server 2003 Administrator’s Guide v
Chapter 9 194
Cleaning Up Project Server Data ..............................................194
Deleting Projects Using the Open from
Microsoft Office Project Server Dialog Box......................................................200
Chapter 10 203
Working with Portfolio Analyzer............................................... 203
Configuring Portfolio Analyzer ...............................................................................204
Creating Portfolio Analyzer Views..........................................................................208
Preparing to Create Portfolio Analyzer Views ................................................210
Using Multiple OLAP Cubes ............................................................................214
Add Users to Cube Database Roles in Analysis Services .............................216
Making Views Available to Project Web Access Users..................................216
Working with Portfolio Analyzer Views ..................................................................217
Saving Portfolio Analyzer Views as GIF Images.............................................218
Saving Portfolio Analyzer Views as Links in Project Web Access .................220
(Sample) Tracking Resource Workload by Skill Level...................................220
Appendix A 232
Additional Resources ............................................................. 232
Microsoft Office Project Server 2003 Online Books Series.................................232
Project Server-Related Web Sites .........................................................................232
Appendix B 234
Project Server Administrative Tools ......................................... 234
Delete Duplicate Projects Utility............................................................................234
Working with projects in the Project Server database..................................236
Deleting duplicate projects prior to upgrade.................................................236
Project Server Cleaner...........................................................................................237
Project Server Documentation ..............................................................................242
On the Project Server and Project Professional CDs ....................................242
Project Server Health Monitor...............................................................................242
Monitor Tab .....................................................................................................243
ViewDrop Tab ..................................................................................................244
PDS Info Tab ...................................................................................................245
Admin Tab .......................................................................................................246
Notify Tab ........................................................................................................247
Errors Tab........................................................................................................248
Project Renaming Utility ........................................................................................248
Installing the PDS Extension ..........................................................................249
Running the Application .................................................................................250
vi Microsoft Office Project Server 2003 Administrator’s Guide
Project Server SetTracing Utility............................................................................253

Running the SetTracing Utility........................................................................254
SmokeTest .............................................................................................................256
Running SmokeTest .......................................................................................257
Results Page ...................................................................................................259
Command Line Interface................................................................................260
Running SmokeTest as a Scheduled Task....................................................260
View Backup and Restore .....................................................................................260
ViewBackup.exe Command Line Parameters ...............................................261
View Effective Rights .............................................................................................262
Installing the PDS Effective Rights Extension ...............................................263
Installing the ASP page...................................................................................264
View Populator Utility .............................................................................................267
Using the View Populator Utility .....................................................................268
Appendix C 270
Project Server Permissions ..................................................... 270
Project Server Category Permissions....................................................................270
Adjust Actuals .................................................................................................270
Approve Timesheets for Resources ...............................................................271
Assign Resources............................................................................................271
Build Team on Project ....................................................................................272
Create New Task or Assignment ....................................................................272
Delete Project .................................................................................................272
Edit Enterprise Resource Data.......................................................................273
Open Project....................................................................................................273
Save Project ....................................................................................................273
See Enterprise Resource Data.......................................................................274
See Projects in Project Center .......................................................................274
See Projects in Project Views.........................................................................274
See Resource Assignments in Assignment Views ........................................274
View Risks, Issues, and Documents ..............................................................275
Project Server Global Permissions........................................................................275
About Microsoft Office Project Server 2003 .................................................275
Assign Resource to Project Team ..................................................................275
Assign To-Do List Tasks ..................................................................................276
Backup Global.................................................................................................276
Build Team on New Project ............................................................................276
Change Password ...........................................................................................277
Change Work Days..........................................................................................277
Check In My Projects ......................................................................................277
Clean Up Project Server Database ................................................................277
Connect to Project Server using Microsoft Project 2002 .............................278
Microsoft Office Project Server 2003 Administrator’s Guide vii
Create Accounts from Microsoft Office Project .............................................278

Create Accounts when Delegating Tasks ......................................................279
Create Accounts when Requesting Status Reports ......................................279
Create Administrative Projects.......................................................................279
Create and Manage To-Do List.......................................................................280
Customize Project Web Access ......................................................................280
Delegate Task .................................................................................................280
Go Offline from Project Web Access ..............................................................281
Hide Task from Timesheet .............................................................................281
Integration with External Timesheet System.................................................281
Log On .............................................................................................................282
Manage Enterprise Features..........................................................................282
Manage Rules .................................................................................................283
Manage Security .............................................................................................283
Manage Server Configuration ........................................................................283
Manage Status Report Requests...................................................................283
Manage Task Changes ...................................................................................284
Manage Users and Groups.............................................................................284
Manage Views.................................................................................................284
Manage Windows SharePoint Services .........................................................284
New Project .....................................................................................................285
New Project Task ............................................................................................285
New Resource .................................................................................................285
New Task Assignment ....................................................................................285
Open Project Template ...................................................................................286
Publish To-Do List to All Users........................................................................286
Publish / Update / Status ..............................................................................286
Read Enterprise Global...................................................................................287
Save Baseline .................................................................................................287
Save Enterprise Global ...................................................................................287
Save Project Template....................................................................................288
Set Personal Notifications..............................................................................288
Set Resource Notifications.............................................................................288
Submit Status Report .....................................................................................288
Timesheet Approval ........................................................................................289
User Defined ...................................................................................................289
View Adjust Actuals.........................................................................................289
View Assignments View ..................................................................................289
View Documents .............................................................................................290
View Home ......................................................................................................290
View Issues......................................................................................................290
View Models ....................................................................................................290
View Portfolio Analyzer ...................................................................................291
View Project Center.........................................................................................291
viii Microsoft Office Project Server 2003 Administrator’s Guide
View Project View ............................................................................................291

View Resource Allocation ...............................................................................291
View Resource Center ....................................................................................291
View Risks .......................................................................................................292
View Status Report List ..................................................................................292
View Timesheet...............................................................................................292
Project Server Organizational Permissions ..........................................................292
Appendix D 294
Project Server Default Settings ............................................... 294
Users.......................................................................................................................294
Administrator ..................................................................................................294
Groups ....................................................................................................................298
Administrators.................................................................................................298
Executives .......................................................................................................301
Portfolio Managers .........................................................................................305
Project Managers............................................................................................308
Resource Managers........................................................................................311
Team Leads.....................................................................................................315
Team Members...............................................................................................318
Categories ..............................................................................................................322
My Direct Reports ...........................................................................................322
My Organization ..............................................................................................322
My Projects......................................................................................................324
My Resources..................................................................................................325
My Tasks .........................................................................................................326
Organization ...........................................................................................................327
Appendix E 331
Project Server Spooler............................................................ 331
Activating the Project Server Spooler ...................................................................331
Using the Project Server Spooler Dialog Box........................................................332
Resolving Project Server Spooler Errors...............................................................333
Project Server Spooler Errors.........................................................................333
Generic error during database access or update ..................................334
Data corruption in Project Server Database ..........................................334
MSP_WEB_ADMIN table not initialized ..................................................334
Invalid Resource Name ...........................................................................335
Domain validation of Windows account failed.......................................335
Resource already exists ..........................................................................335
Windows authentication only..................................................................336
Project Server authentication only .........................................................336
All authentication types disallowed ........................................................336
Microsoft Office Project Server 2003 Administrator’s Guide ix
Manager not allowed to create a new account......................................336

Beta or evaluation version has expired..................................................337
Manager requires authentication for Publish operation .......................337
Insufficient manager permissions for Publish .......................................337
Windows account already exists.............................................................338
Session has expired ................................................................................338
Cannot create manager account from Project Professional .................338
Cannot publish master project ...............................................................339
Cannot publish non-enterprise resources..............................................339
Cannot publish non-enterprise projects on this server .........................339
Appendix F 341
Project Server Registry Settings, Services,
and Application Folders .......................................................341
Project Server Registry ..........................................................................................341
\CubeProcess .................................................................................................342
\OLE DB Provider............................................................................................342
\Services\Configuration .................................................................................343
\Configuration\Connector.......................................................................343
\Configuration\Views Notification ..........................................................343
\Configuration\SessionMgr ....................................................................344
\WebClientServer\Languages .......................................................................344
\WebClient Server\ProjectServer\Datasets..................................................345
\Datasets\Application.............................................................................345
\Datasets\EnterpriseDatabase ..............................................................346
\Datasets\STS .........................................................................................346
\Datasets\ViewsFileDrop........................................................................346
\Datasets\ViewsSchedulingDatabase ...................................................347
\WinProj ...................................................................................................347
\WebClient Server\ProjectServer\Services ..................................................347
Services ..................................................................................................................347
Project Server Session Mgr Service (PjSessionMgr).....................................348
Project Server Tracing Service (PjTraceSvc)..................................................349
Project Server Views Notification Service (PjViewNotify)..............................349
Project Server Scheduled Process Service (PjSchSvc) .................................349
Project Server Connector Service (PjConnectSvc) ........................................350
Folders....................................................................................................................350
\BIN\1033 ......................................................................................................351
\BIN\Connector ..............................................................................................351
\BIN\ViewDrop................................................................................................351
\Help\1033.....................................................................................................351
\IIS Virtual Root...............................................................................................352
Microsoft Office Project Server 2003 Administrator’s Guide 1
Introduction
The Microsoft Office Project Server 2003 Administrator’s Guide is designed to help your
organization understand the tasks involved with administering Microsoft® Office Project
Server 2003.
Send us your feedback. Please let us know what you think about the quality of this
content. If this text does not meet your needs, let us know how we can improve it. If this
text was helpful to you, let us know how it helped.
mailto:projdocs@microsoft.com?subject=Feedback: Microsoft Office Project Server 2003
Administrator’s Guide
Microsoft Office Project Server 2003 Online Books Series

The Microsoft® Office Project Server 2003 Online Books series documents the Microsoft
Enterprise Project Management (EPM) solution and provides a detailed reference for all
phases of deploying Project Server, including planning, installation, configuration, and
administration. Each book is designed to stand alone and can be referred to on an as-
needed basis. You can also read these books in the order listed below for a complete guide
to deploying Project Server 2003:
• Microsoft Office Project Server 2003 Configuration Planning Guide
http://go.microsoft.com/fwlink/?LinkID=20235
• Microsoft Office Project Server 2003 Disaster Recovery Guide
• Microsoft Office Project Server 2003 Installation Guide
• Microsoft Office Project Server 2003 Application Configuration Guide
• Microsoft Office Project Server 2003 Administrator’s Guide
A key part of deploying Project Server 2003 and the EPM solution it provides is proper
planning. These books will help your organization plan for deployment by explaining
Project Server 2003 in detail, highlighting the questions you should ask throughout the
planning phase, and providing a reference for the requirements during each phase of
deployment. These books are not intended to be a substitute for proper planning within
2 Microsoft Office Project Server 2003 Administrator’s Guide
your organization as to what your EPM solution should be. The Microsoft® Office Project
Server 2003 Online Books series will help you succeed in deploying your organization’s
project management solution.
What Will You Learn from this Book?

There are a number of important tasks that a Microsoft® Office Project Server 2003
administrator must manage in Microsoft Office Project Web Access 2003 in order for users
of Project Web Access and Microsoft Office Project Professional 2003 to access and
interact effectively with project data, including:
• Managing users and groups.
• Managing Project Server security.
• Managing Microsoft Windows® SharePoint™ Services settings that enable users of
Project Professional and Project Web Access to access Documents, Issues, and Risks.
• Managing enterprise features, including enabling or disabling enterprise and non-
enterprise modes, managing versions, and more.
• Customizing Project Web Access to fit the specific needs of your organization.
Who Should Read this Book?

This guide is designed to produce maximum benefits for the following professionals:
Project Server administrators
Those individuals who will have administrator privileges for Project Server and will
perform the duties required of the Project Server administrator.
Windows SharePoint Services administrators
Those individuals responsible for administering Windows SharePoint Services and
ensuring that Project Server and Windows SharePoint Services are always properly
synchronized and that the Documents, Issues, and Risks collaboration tools are
available.
Active Directory administrators
Those individuals responsible for setting up individual e-mail accounts and security
groups in the Active Directory® directory service that will be mapped to the Project
Server Enterprise Resource Pool and Project Server security groups.
Any member of your organization’s Project Server deployment planning team
Those individuals within your organization who will plan the deployment of Project
Server and who may need a better understanding of the day-to-day Project Server
administrative tasks that are available in Project Web Access.
How is this Book Structured?

This book has nine chapters and six appendices. You can review these chapters in any
order you need to; they are organized in the same manner in this book as they are
organized in Project Web Access. Appendix data is primarily reference data and lists.
• Introduction
• Chapter 1, Administering Project Server Using Project Web Access
• Chapter 2, Managing Users and Groups
• Chapter 3, Managing Security
• Chapter 4, Managing Views
• Chapter 5, Configuring Project Server
• Chapter 6, Managing Windows SharePoint Services
• Chapter 7, Managing Enterprise Features
• Chapter 8, Customizing Project Web Access
• Chapter 9, Cleaning Up Project Server Data
• Chapter 10, Working with Portfolio Analyzer
• Appendix A, Additional Resources
• Appendix B, Project Server Administrative Tools
• Appendix C, Project Server Permissions
• Appendix D, Project Server Default Settings
• Appendix E, Project Server Spooler
• Appendix F, Project Server Registry Settings, Services, and Application Folders
Revision History
The following table provides the revision history for this document.
Date Revision
October 2003 • Initial Publication.
January 2004 • Added information about Project Server

Web Parts to Chapter 1, Administering
Project Server Using Project Web Access.
• Added Chapter 10, Working with Portfolio
Analyzer.
• Moved information related to Portfolio
Analyzer in Chapter 4 to Chapter 10.
• Added information about Project Server
Date Revision
administrative tools to Appendix B,
Project Server Administrative Tools.
1
Administering Project Server Using
Project Web Access
Microsoft® Office Project Web Access 2003 is one of two interfaces that can be used to
work with and access information stored in Microsoft Office Project Server 2003. (The
other interface is Microsoft Office Project Professional 2003.) Project Web Access
provides specific access to Project Server information in the following areas:
• Home Allows quick access to Project Server information and helps users decide
which areas they need to visit first. For example, team members may learn they have
new tasks and will decide they need to go to the Tasks area to see them. What users see
in the Home area depends on the permissions they have in Project Server.
• Tasks Allows team members to view, edit, and update project task assignments that
have been made in Project Professional. Users can work with tasks in either a Gantt
Chart or a Timesheet view. Users can only see information that the Project Server
administrator has given them permission to see. In the Tasks area, users can perform
numerous activities regarding their tasks, such as viewing, creating, and delegating
tasks, and working times, such as transferring non-working time from their Microsoft
Outlook® Calendars and making updates.
• Project Allows users to view portfolios of projects or individual projects. Users can
see either summary information about multiple projects or detailed information about
individual projects. They can also create to-do lists, which are lists of tasks that are not
associated with a project.
• Resource Allows users to view, modify, and analyze information across projects and
assignments published to Project Server.
• Status Reports Allows project managers to request, collect, and consolidate text-
based status reports. A status report is simply a narrative description from team
members about progress related to project tasks. Team members are allowed to
respond to status reports and send their responses to their managers. Status reports
can be set up so that project managers receive both individual submissions and a
merged or compiled status report that groups responses per section into a single status
report.
• Updates Allows project managers to review updates to project tasks and to resource
working times sent to project managers from a resource’s Tasks area. Project managers
can also update project plans even after they have been published to the Project Server
database.
• Documents Allows users to easily manage project-related documents by viewing
them, uploading them, and linking them to tasks by using Project Web Access. Before
users can work with documents, a server running Microsoft Windows® SharePoint™
Services must be installed and configured properly for Project Server.
• Issues Allows users to track issues that arise throughout the project life cycle by
allowing users to view and submit issues. Tracking issues improves the efficiency and
effectiveness of project management because it enables communication about
problems and helps identify related action items that can be used to resolve the issue.
Before project managers can track issues, a server running Windows SharePoint
Services must be installed and configured properly for Project Server.
• Risks Allows users to track information that can have adverse affects on the project
life cycle by allowing users to report and identify risks to a project’s success. Before
project managers can track risks, a server running Windows SharePoint Services must
be installed and configured properly for Project Server.
• Admin For more information about the Project Web Access Admin center, see
Working in the Project Web Access Admin Center.
X To access Project Web Access from a Web page
1. Open Microsoft Internet Explorer.
2. Enter the Uniform Resource Locator (URL) for Project Server, for example:
http://<servername>/projectserver
X To access Project Web Access from the server running Project Server
1. Log on to the server running Project Server.
2. On the Start menu, point to All Programs, then Microsoft Office Project
Server 2003, and then select Configure Microsoft Office Project Server.
X To access Project Web Access from Project Professional
1. Start Project Professional and connect to Project Server.
2. On the Collaborate menu, select Project Center, Resource Center, Portfolio
Analyzer, Portfolio Modeler, Risks, Issues, or Documents.
Working in the Project Web Access Admin Center

The Project Web Access Admin center allows administrators to set defaults, define users
and groups, manage security for Project Web Access, and manage default settings for all
Project Professional and Project Web Access enterprise features. An administrator can
perform numerous activities, such as creating new users, setting permissions, creating or
modifying views, or enabling enterprise features.
Managing Users and Groups

The Manage Users and Groups section enables you to add or modify users and groups of
users, set security permissions and properties, and synchronize Project Server security
groups with the Active Directory® directory service.
The Users page in Project Web Access.

Note For more information about creating, modifying, and deleting users and groups, see Chapter
2, Managing Users and Groups in the Microsoft Office Project Server 2003 Administrator’s Guide.
Managing Security
The Manage Security section enables you to establish user account creation and
authentication preferences, set security permissions for collections of projects, resources,
and assignments; create and edit templates for security permissions; and specify the
minimum password length for Project Server authentication.
The Categories page in Project Web Access.

Note For more information about working with security categories and security templates, see
Chapter 3, Managing Security in the Microsoft Office Project Server 2003 Administrator’s Guide.
Managing Views
The Manage Views section provides a location to define Project, Project Center, Resource
Center, Assignment, and Portfolio Analyzer views.
The Specify Views page in Project Web Access.

Note For more information about working with Project, Project Center, Resource Center,
Assignment, and Portfolio Analyzer views, see Chapter 4, Managing Views in the Microsoft Office
Project Server 2003 Administrator’s Guide.
Configuring Project Server

The Server Configuration section is where you can decide whether to use Project Server in
enterprise or non-enterprise mode. If you select enterprise mode, then you can also
determine the scope of enterprise features that will be available to Project Server users. In
addition, you can add top-level and side-pane links to custom pages that enable you to
customize Project Web Access to provide access to information that is not included in
Project Server by default.
The Server configuration page in Project Web Access.

Note For more information about configuring enterprise and non-enterprise modes, or creating
custom menus in Project Web Access, see Chapter 5, Configuring Project Server in the Microsoft
Office Project Server 2003 Administrator’s Guide.
Managing Windows SharePoint Services

The Manage Windows SharePoint Services section is where you can specify the settings for
the server running Windows SharePoint Services that is used to store documents and track
issues and risks. In addition, you can link to Windows SharePoint Services administrative
pages, configure a Microsoft SharePoint Portal Server for use with Project Server, and
synchronize Project Server users with Windows SharePoint Services.
The Connect to SharePoint server page in Project Web Access.

Note For more information about connecting Project Server to Windows SharePoint Services and
managing Windows SharePoint Services itself, see Chapter 6, Managing Windows SharePoint
Services in the Microsoft Office Project Server 2003 Administrator’s Guide.
Managing Enterprise Features

The Manage Enterprise Features section is where members of your organization can go to
create and build the online analytical processing (OLAP) cube, create versions, and check
in checked-out enterprise projects and enterprise resources.
The Update resource tables and OLAP cube page in Project Web Access.
Note For more information about updating OLAP cubes, checking in enterprise projects and
enterprise resources, and managing project versions, see Chapter 7, Managing Enterprise Features
in the Microsoft Office Project Server 2003 Administrator’s Guide.
Customizing Project Web Access

The Customize Project Web Access section allows you to specify timesheet tracking
settings, create managed timesheet periods, customize Gantt Chart and Grouping format
displays, and configure default e-mail notification and reminder service messages.
The Tracking settings page in Project Web Access.

Note For more information about customizing Project Web Access features like timesheets, Gantt
Chart views, Grouping formats, the Project Web Access home page, as well as configuring e-mail
notifications and reminders, see Chapter 8, Customizing Project Web Access in the Microsoft Office
Cleaning Up Project Server Data

The Clean Up Project Server Database section allows you to delete task, resource, and
project data as a group or as associated with a particular resource.
The Clean up Project Server database page in Project Web Access.

Note For more information about deleting project task, resource, status report, and other related
data, see Chapter 9, Cleaning Up Project Server Data in the Microsoft Office Project Server 2003
Administrator’s Guide.
Understanding Project Server Security

Every person who has an interest in a project is a potential user of Project Server, whether
he or she is an active participant who makes changes to a project, such as a team member
or a project manager, or a more passive participant like a customer who is interested only in
a project’s delivery. Each of these individuals will require a user account to access the
information stored on Project Server. This user account will identify an individual when he
or she logs on to the server and will personalize the interface and data that is displayed and
that can be accessed by the user according to the permissions and categories assigned to
the user. The user permissions and categories govern what the user can see (in terms of
data) and do (in terms of functionality).
All Project Server users must have a user account. This can be either a Project Server user
account (user name and password) or a Windows authenticated user account. To gain
access to Project Server, users are required to log on through Project Web Access or
Project Professional. This process identifies and authenticates the person logging on against
the user accounts within Project Server and then uses the Project Server security model to
determine which areas the user has permission to view and access.
Project Server Security

Project Server security is modeled on Windows technology, which is centered around
granting users and groups access to objects and principals. Security features in Project
Server are designed to control and manage access to projects, resources, and reports stored
in the Project Server database, pages in Project Web Access, and features available in
Project Professional and Project Web Access. In addition, the security architecture makes it
easier to manage a large number of users and projects by allowing permissions to be
assigned to groups of users and unique categories. This greatly reduces the number of times
an administrator will have to update permissions in Project Web Access.
The following are elements of Project Server security:
• Security objects Items that can have actions carried out on them or contain data. In
Project Server, this includes categories that consist of collections of projects, resources,
assignments, and views.
• Security principals Rules that define access to security objects. In Project Server,
users and groups have rights, or permissions, over security objects. This allows them to
access or manipulate Project Server objects.
• Security templates Maps used for applying security principals to security objects,
allowing users and groups to access or manipulate Project Server objects. You can use
security templates to quickly apply predefined permission profiles to new or existing
users, groups, and categories. By applying security templates, you can easily standardize
the rights being applied according to the role being played.
• User Any person who accesses Project Server. To gain access, a user needs to be
authenticated by the server. Authentication can be via a Windows user account or by a
Project Server user account. Each user has a set of permissions associated with their
user account that determines the type of data they can access on the server. Users are
security principals.
• Group A collection of users that have similar information and functionality needs.
These users are usually aligned with the type of roles played within an organization.
Users can belong to multiple groups depending on the type of work they perform in
your organization. Groups are security principals.
• Permissions Rules that determine the actions a user can perform while using Project
Server. Global permissions provide rights over functionality within the server. Object
permissions are associated with categories. These permissions give users and groups
rights to perform actions on objects associated with a category. Permissions are applied
to a server (or organization), group, category, or a user. This means that a user’s actual
permissions will consist of the combination of all permissions the server has, the
groups the user belongs to, categories the user has access to, as well as permissions
granted directly to the user.
• Categories The collections of projects, resources, assignments, views, and models to
which users and groups in Project Server are granted access. Categories define the
scope of the information accessed, providing multiple types of access to data for
groups of users.
• Views Sets of data fields that can be displayed for the collections of projects,
assignments, and resources in a category. Views also define the format of the display,
for example the columns that are displayed, a grouping style, or a filter.
Uses for Security
Project Server security can be used effectively in many different ways. For example it can:
• Protect confidential data from other users There may be sensitive projects or data,
such as resource rates, that need to be protected. If information is being supplied
externally from the organization to clients, suppliers, or partners, there may be some
information or details that should not be disclosed.
• Secure data from malicious or accidental damage Project data is usually extremely
valuable. Ensuring that only the right users have access to that data and removing
functionality from those that don’t need it reduces the changes of accidental or
malicious loss of data.
• Provide data depending on the information needs and functionality
requirements of the user The Project Server security model can be configured to
personalize information so that users only see the data that is relevant to them, rather
than all data. For example, system performance can be improved when Project Server
security is used to narrow the amount of information that a group of users can see. In a
large deployment (or a deployment with large sets of data), every user is not required to
see every view or to access all pieces of data. A group of resources may only need to
see their own work, making the need to view project and portfolio data unnecessary.
• Enforce project management processes discipline within the organization
Assigning functionality to roles can help ensure (or relax) discipline around an
organization’s project management process. For example, resources can have the
options for adding, rejecting, and delegating tasks removed.
What a user sees in terms of data content and what he or she can do in terms of
performing actions or manipulating that data is governed by the relationship between the
user, the permissions the server has, the permissions the user has or the groups to which he
or she belongs, the categories to which he or she belongs, and the views of data within
those categories.
Because the things a user needs to see and do usually depend on the role he or she plays
within an organization, it makes sense to define groups, permission templates, and
categories in terms of the job he or she performs within the project management
environment of the organization. Some users have implied roles—for example, users who
publish project plans to Project Server are usually project managers. Groups can be defined
in terms of the roles they carry out—for example, team members, project managers,
executives, and those who have similar permissions assigned to them. These roles would
then map to the different categories, depending on the role’s information needs—that is,
team members usually only need access to tasks, so they belong to a task’s category.
This approach to security is reflected in the predefined groups, templates, and categories
that are created when Project Server is installed.
Users and Groups

Users and groups of users are what security in Project Server is built around. You should
define groups by identifying common needs based on the areas of Project Server (objects)
to which a single user would need access. Specifically, groups should be defined as users
who need to access the same set of data in the same way. For example, every project
manager in a particular division within your organization may need to be able to access all
of the projects managed within that division and to be able to open and save those
projects. Adding users and groups to security categories (including custom security
categories) allows you to associate security principals (users and groups) to a specific set of
security objects (projects, views, resources, etc.).
After you have defined your groups you can add users to the groups; users added to a
group will inherit the permissions assigned to that group. Defining access to Project Server
by group also keeps the overall number of security principals with direct permissions to
categories to a minimum, which simplifies administering Project Server security. Typically,
the membership of a group will change frequently, but the security requirements of a group
will change infrequently.
Users can belong to multiple groups depending on the jobs they perform or the
organization to which they belong. Project Server creates a number of default groups
during installation, each with a set of predefined categories and permissions assigned to
them:
• Administrators
• Executives
• Portfolio managers
• Project managers
• Resource managers
• Team leads
• Team members
Administrators usually assign user rights by adding a user account to one of the built-in
groups or by creating a new group and assigning specific user rights to that group.
Note For a complete list of Project Web Access global and category permissions, see Appendix C:
Project Server Permissions in the Microsoft Office Project Server 2003 Administrator’s Guide.
Permissions
Permissions can be set in a number of different places within the Project Server
administration menu. They are enabled and disabled by selecting the check boxes in the
Allow and Deny columns. Both columns function as an on/off switch, meaning that if the
check box is selected, permission is allowed or denied. If the Allow or Deny check boxes
are not enabled, the state is considered Not Allow. The Not Allow state will not prevent a
user from accessing the feature associated with the permission if they are granted
permission in some other way (for example, belonging to more than one security category,
one with the permission allowed, the other not allowed). If the permission is denied
anywhere, permission will be denied everywhere for a particular user or group.
Note The Deny check box is provided to enable the administrator to deny access to functionality by
overriding any other permission settings. Administrators should only select the Deny check box in
limited circumstances. Situations where using the Deny check box may be appropriate are when a
user outside the organization will be accessing Project Server (or for any other reason where all
functionality needs to be stopped); otherwise, the Deny check box should be used cautiously. The
administrator account is protected against its permissions being denied to prevent accidental
lockout.
In an organization where there are many users, setting up a large number of permissions on
an individual basis and administering those permissions can be an overwhelming task. To
make this easier, you can use the principle of groups to assign permissions to multiple users
with a single action. You should create the groups and define the set of permissions to
associate with the groups before assigning users to groups and groups to categories. This
should be a planned process; the day-to-day administration of users, groups, and categories
should be as simple as adding users to security groups or removing them. This approach
will help reduce the day-to-day activities and management processes required of your
Project Server administrator.
Security Templates
Security templates are a quick way to apply or reset predefined permission profiles to new
or existing users, groups, and categories. By applying security templates, the rights being
applied can easily be standardized according to the role. There are a number of predefined
templates created when Project Server is installed. These align with the predefined groups.
These security templates can be customized and/or new security templates created.
Creating custom security templates should be a process that your organization plans for.
For example, first determine the common usage patterns that are required in your
organization but which are not covered by the default security categories included with
Project Server. This will help identify the requirements for a custom security template.
Once the usage pattern is understood, next determine the combined patterns of data access
and the permission requirements that are needed by users when performing all of the
required tasks defined by the usage pattern. This becomes the definition of the security
category. The next step is to determine the set of projects, resources, views, etc., that the
users and groups assigned to the security category will need to be able to access. Then add
the users and groups to the custom security category; they will use the permissions defined
in the template and will have access to the projects, views, resources, etc., that are also
defined in the template.
Understanding Project Web Access Permissions

You can allow or deny permissions to individual Project Web Access users or groups of
Project Web Access users. You can use security templates to define sets of permissions and
then assign permissions to users and groups based on security templates. You can use
categories to define the specific projects, resources, and views to which you allow users and
groups various levels of access. You can also set permissions for Project Web Access
features to make them available or unavailable to the organization as a whole.
Permissions in Project Web Access work similarly to permissions in Microsoft Windows.

Users and groups are the security principals. Projects, resources, and views are the security
objects. Categories are collections of security objects. Use permissions to allow or deny
security principals access to security objects.
• Users Each individual user must be granted permission to view or access the data in a
particular area of Project Web Access, Project Server, or Project Professional. You can
grant permissions at the user level or you can assign users to groups (recommended)
and grant permissions at the group level. A single user can be a member of any number
of groups.
• Groups A group of users is simply a collection of individual users who are assigned
the same permissions. You can combine individual users who have common security
requirements into a single group to reduce the number of security principals that you
need to manage. For example, if your company employs contractors, you may want the
contractors to have a different set of permissions than regular team members.
Use security templates in combination with groups to make it easier to set permissions.
First, create a new security template, and then grant all users in the group permissions
based on the new security template.
• Project Web Access includes the following default groups:
• Administrator
• Executive
• Portfolio Manager
• Project Manager
• Resource Manager
• Team Lead
• Resource
A group may not be part of another group.
• Security Templates A security template is simply a predefined set of permissions.
Use security templates to simplify granting permissions to groups of users who need
access to the same data. Project Web Access includes the following default security
templates:
• Administrator
• Executive
• Portfolio Manager
• Project Manager
• Resource Manager
• Team Lead
• Resource
Note Changing the settings for a security template does not automatically apply the same
set of changes to each of the users and groups the template was applied to. A security
template is simply intended to be a starting point for assigning permissions to users and
groups.
• Categories A category is a collection of security objects. Create custom categories

when you need to provide new ways to access project, resource, and view data. Project
Web Access includes the following default categories:
• My Organization
• My Projects
• My Tasks
• Organization An organization is the complete collection of data that exists in a single
installation of Project Server. Setting permissions at the organization level allows you
to make features available or unavailable to all users of Project Web Access, Project
Server, or Project Professional, depending on the permission. If you allow or deny

permissions at the organizational level, all users within the organization will be affected
regardless of permissions set elsewhere.
Note Only one organization exists for each Project Server installation.
When to Allow and Deny Project Web Access Permissions

All Project Server permissions can be allowed or denied in Project Web Access:
• Allow must be selected in order for any users or member of a group to be able to
perform the actions associated with the permission.
• Deny should be used carefully. If a user is denied a specific permission, that user will
be denied for that permission regardless of any Allow settings he or she may have in
other groups. No permissions are set to Deny by default.
• Not Allow, while not strictly a permission, is a state that exists when neither Allow
nor Deny are selected for the same permission in the same group. If a user belongs to
more than one group that has the same permission set to Allow (but not Deny) in at
least one of the groups, then the user will be allowed to perform the actions associated
with the permission for all groups. In other words, if a user is allowed a permission in
one group or category, that user will be allowed that permission in all groups and
categories to which the user belongs.
One thing to consider when setting permissions is that Deny can be very limiting because
it will override allowed permissions in other areas. You may find that using Deny as little as
possible will make it easier to manage large groups of users.
Understanding Active Directory Synchronization with Project

Server
Active Directory is included as a standard feature of Windows 2000 Server or Microsoft
Windows Server™ 2003 that can be enabled after initial installation. A new feature of
Project Server 2003 is the ability to synchronize security groups in Active Directory with
security groups in Project Server, or to populate the Enterprise Resource Pool in Project
Server based on the users that belong to a mapped group in Active Directory.
Organizations in a position to take advantage of Active Directory will be able to greatly
simplify the security and resource management aspects of Project Server.
Note Project Server only supports one-way synchronization from Active Directory to Project Server.
The Active Directory Connector in Project Server 2003 facilitates synchronization of users
and groups from Active Directory to Project Server as long as the servers running Active
Directory and Project Server are working across trusted domains. This new component
makes calls to the Project Data Service (PDS) so that Active Directory data is written to the
Enterprise Resource Pool and security group membership information in the Project
Server database based on the presence and status of users in Active Directory (as compared
to the presence and status of users and groups in mapped security groups or users in the
Enterprise Resource Pool).
You should think about Active Directory synchronization with Project Server as two
separate features:
• Mapping Active Directory groups to Project Server security groups. Each security
group in Project Server can be mapped individually to Active Directory security
groups. All users and groups within the Active Directory security group that is mapped
to a Project Server security group will be added to the Project Server security group
during synchronization.
• Mapping an Active Directory group to the Project Server Enterprise Resource Pool.
When the Enterprise Resource Pool and Project Server security groups are configured to
be synchronized with a security group or group of security groups in Active Directory, you
can automate some of the most important steps in the process of creating users and getting
them associated with the right security groups in Project Server.
• For more information about synchronizing the Enterprise Resource Pool with Active
Directory, see the topic Synchronizing the Enterprise Resource Pool with Active
Directory in Chapter 5, Configuring Project Server of the Microsoft Office Project
Server 2003 Administrator’s Guide.
• For more information about synchronizing Project Server security groups with security
groups in Active Directory, see the topic Security Group Synchronization with
Active Directory in Chapter 2, Managing Users and Groups of the Microsoft Office
Understanding Project Server 2003 Web Parts

Project Server 2003 includes six custom Web Parts that allow users in your organization to
access task, project, views, and timesheet data that is stored in the Project Server database
while using Windows SharePoint Services and SharePoint Portal Server.
Note Project Server 2003 Web Parts do not work by default with SharePoint Portal Server. Some
customization is required in order to establish the connection between the Project Server Web
Parts on the server running SharePoint Portal Server to Project Server.
Using the Default Project Server 2003 Web Parts

Project Server 2003 Web Parts are based on the Content Editor Web Part in Windows
SharePoint Services. The default Project Server 2003 Web Parts have a dependency on the
customized Windows SharePoint Services template used by Project Web Access. They will
not work in SharePoint Portal Server unless the custom properties are modified to
recognize the Project Server database.
The following Web Parts are included with Project Server 2003:
• Project Timesheet Provides users a way to view and edit their Project Web Access
timesheet.
• Project Center Allows users to view the Project Center.
• Project Report Displays the project drill-down view for a project for which an active
Windows SharePoint Services site has been created. (This view is available in the
Project Workspace for a given project; this drill-down view appears in the Project
Workspace.)
• Project Manager Updates Enables project managers to view updates sent to them
by their project team members.
• Project Resource Assignments Allows project managers, resource managers, and
team leads to view the tasks to which their resources have been assigned.
• Project Portfolio Analyzer Allows executives, project managers, and resource
managers to analyze project data using the PivotChart and PivotTable available in
Portfolio Analyzer.
Creating Custom Project Server 2003 Web Parts

Project Web Access provides a browser-based client that allows team members, resource
managers, and other members of your organization to enter or view timesheet information
and view portfolio reports. You can create simple Project Server 2003 Web Parts for use in
SharePoint Portal Server that point to an existing page in Project Web Access.
The process for creating custom Project Server 2003 Web Parts is identical to the process
for creating custom Web Parts for Microsoft Project Server 2002 and as simple as
identifying the page in Project Web Access that you want to use as your Web Part, adding
URL options until the page has all the settings in Project Web Access that you want it to
have while running in Windows SharePoint Services or SharePoint Portal Server, and then
copying the URL into a Page Viewer Web Part.
Note For more information about creating custom Web Parts for use in SharePoint Portal Server,
see the Microsoft Office Project Server 2003 Software Development Kit (SDK) on MSDN:
2
Managing Users and Groups
Users and groups of users are what security in Microsoft® Office Project Server 2003 is
built around. You should define groups by identifying common needs based on the areas of
Project Server to which a single user would need access. For example, every user will need
to view his or her projects and tasks, but perhaps only project managers should be allowed
to create assignments. After you have defined your groups, you can add users to the
groups. Users added to groups will inherit the equivalent permissions assigned to the
groups. Defining access to Project Server by group also keeps the overall number of
security principals with direct permissions to categories to a minimum, which simplifies
administering Project Server security. Typically, the membership of a group will change
frequently; however, the security requirements of a group will rarely change.
Managing Users
Users can belong to one or more Project Server security groups, depending on the jobs
they perform or the organization in which they work. Project Server creates a single user
during installation: the Project Server administrator account.
The Users page in Project Web Access.

Administrators can add new individual users, modify existing users, deactivate resource
accounts, and merge user accounts together. Administrators can assign rights to users by
adding them to one of the built-in groups or by creating a custom group and assigning
them specific rights to the custom group.
Adding a User
Every user in Project Server and Microsoft Office Project Web Access 2003 must have a
user account created before he or she can log on and interact with project data. There are
two user types in Project Server: Microsoft Windows® authenticated users (domain
accounts) and Project Server users (user name and password accounts). Both Windows
authenticated users and Project Server users can be given access to any area of Project
Server, Project Web Access, or Microsoft Office Project Professional 2003; Windows user
accounts are required for the following enterprise features:
• Portfolio Analyzer
• Portfolio Modeler
• (Recommended) Windows SharePoint™ Services Documents, Issues, and
Risks Windows SharePoint Services requires Windows authentication for users to be
able to access the Documents, Issues, Risks areas of Project Web Access. Users with
Project Server user accounts may be able to access these pages, depending on your
configuration; however, only Windows authenticated users will be able to use every
feature in these areas.
• Membership in the Enterprise Resource Pool and Synchronization of the Project
Server Enterprise Resource Pool with a single Active Directory security group
The Project Server Enterprise Resource Pool must be created in Project Professional
and saved to Project Server, or created by synchronizing a group in Active Directory
with the Enterprise Resource Pool.
Note For more information about the Enterprise Resource Pool, see the topic
Synchronizing the Enterprise Resource Pool with Active Directory Chapter 5, Configuring
Project Server in the Microsoft Office Project Server 2003 Enterprise Configuration Guide.
• Synchronization of Project Server security groups with Active Directory security

groups Project Server security groups can be configured to security groups in Active
Directory so that when the users are added or removed in Active Directory, they are
removed from the Project Server security group during the next synchronization
between Active Directory and Project Server.
Note For more information about synchronizing users between an Active Directory security
group and the Enterprise Resource Pool, see the section Security Group Synchronization
with Active Directory in Chapter 2, Managing Users and Groups of the Microsoft Office
The Add User page in Project Web Access.

X To add a new user
1. In the Project Web Access Admin center, in the side pane under Actions, click
Manage users and groups.
2. In the side pane, under Add, modify, and delete, click Users.
3. On the Users page, click Add User.
4. On the Add User page, select an authentication method for this user.
• If you select Windows Authentication, complete the Windows User Account,
E-mail (optional), and User Name text boxes.
• If you select Project Server authentication, complete the User Account, E-

mail, Password, and Confirm Password text boxes. If the company e-mail
address has already been entered in the Company e-mail address field on the
Notifications and reminders page, and the user’s e-mail address is in the same
domain, you only need to enter the user’s e-mail address.
5. Under Groups: Select the groups in which the user is a member, select the groups
to which the user will belong and then either click Add or, to add the user to all
available groups, click Add All.
Users automatically inherit the permissions of any groups they belong to.
6. Under Categories: Select the category that can be accessed by this user, select the
categories the user can access, and then either click Add or, to add the user to all
available categories, click Add All.
For each category, set the permissions for the user within the category.
Note For more information about Project Server security categories, see the section
Managing Categories in Chapter 3, Managing Security of the Microsoft Office Project
7. You can set permissions manually for any category or you can apply a security template
containing predefined permission settings. To set permissions using a security
template, in the Selected categories list, select the category to which you want to
apply the template. Select the template to apply in the list next to the Set Permissions
with Template button, and then click Set Permissions with Template.
To set permissions manually in the Selected categories list, select the category to
which you want to apply permissions. In the Permissions list, click Allow or Deny
for each activity. In most cases, you only need to set permissions at the group level; use
category permissions for users with special needs that are not covered by a group’s
permissions.
Note For more information about Project Server category permissions, see Appendix C:
Project Server Permissions in the Microsoft Office Project Server 2003 Administrator’s
Guide.
8. Under Global Permissions: Set user’s global permission, select the global
permissions for the user. To set permissions using a security template, select the
template to apply in the list next to the Set Permissions with Template button, and
then click Set Permissions with Template.
Guide.
9. Click Save Changes.

Modifying a User
You can modify user account information for any user in the Project Server database. You
might want to do this, for example, if a resource name is changed or if a resource changes
roles in your organization.
X To modify information for a Project Web Access user
3. On the Users page, select the user you want to modify, and then click Modify User.
4. On the Modify User page, make any necessary changes.

Note For more information about clearing the Active Directory globally-unique identifier
(GUID), see the topic Clearing the Active Directory Globally-Unique Identifier in Chapter 2,
Managing Users and Groups of the Microsoft Office Project Server 2003 Administrator’s
Guide. For more information about modifying a user’s Account Status, see Deactivating or
Reactivating a User, also in Chapter 2.
Deactivating or Reactivating a User

At times, you may need to make user accounts unavailable in Project Server. When you
make a user account inactive, that user’s information and data will remain in the database,
but the user will be made unavailable for new assignments. In a sense, this user account is
frozen until it is reactivated.
Deactivating a user will inactivate the user’s account so that it can no longer be used to log
on to Project Server. Users will not be able to use this account while sending assignment
updates, requesting status reports, or delegating tasks.
Note User accounts, when deactivated, are not actually deleted from the Project Server database.
This is to ensure that any relationships that resource may have with project data can be preserved
in case they are needed later.
X To deactivate a user account

3. On the Users page, select the user account you want to deactivate, and then click
Deactivate User.
4. In the alert, click Yes to confirm that you want to deactivate the user.
X To reactivate a user account
3. On the Users page, select a user. Click Show Grid to view all users or just select a user
from the drop-down list. After you have selected the user to reactivate, click Modify
User.
4. On the Modify User page, in the Account Status list, select Active.
Merging Two User Accounts

You may find that two accounts have unintentionally been created for the same person. If
this occurs, you can combine the two accounts into a single user account. When you merge
two accounts, one account is kept in the Project Server database and the other account’s
information (tasks, assignments, and so on) is merged into the account you keep. You
should only merge user accounts if the accounts refer to the same person. This might
happen, for example, if more than one Project Server account is created for the same user
or if a Project Server user account is created for a user who already has a Windows
authenticated user account. If you try to merge user accounts that have been assigned the
same tasks or status reports, you could have data conflicts. Project Web Access will not
allow the merging of two user accounts that share or have conflicting task or status report
data. Security settings for the user account merged into another user account will be lost;
both user accounts will be assigned the security settings for the user account that remains
in the Project Server database.
Note This procedure should not be used with resources in the Enterprise Resource Pool.
X To merge two user accounts

3. Select the account that you want to keep, and then click Merge User Accounts.
4. Under Merge User Accounts, verify that the account on the left is the user account
you want to keep. If it is not, select a new user account from the list.
5. In the list on the right, select the user account you want to merge into this account.
This will create a single user account with all of the attributes of the user shown in the list
on the left, but with data from both user accounts. The user account on the right is deleted
permanently. Any non-project time entries for the deleted user are also deleted.
Managing Groups
A group is a collection of users who have the same security requirements in Project Web
Access. By adding users to groups, you can significantly reduce the amount of time spent
managing user permissions. Users automatically inherit the permissions of any group to
which they belong.
The Groups page in Project Web Access.

A Project Server installation creates seven default groups. The default groups
(Administrator, Project Managers, Executives, Resource Managers, Portfolio Managers,
Team Leads, and Team Members) are designed to be used together with the five default
categories (My Organization, My Projects, My Resources, My Direct Reports, and My

Tasks):
• Team Members group As projects are published to Project Server from Project
Professional, accounts are created on the server for any resources in the project plan
that are not already Project Server users. By default, the server adds any new resources
to the Team Members group, which is granted permissions to the My Tasks category.
The Team Members group is generally able to view and not edit data in the category.
The Team Members group is granted a number of global permissions that allow use of
the Project Web Access timesheet, status reports, and to-do list features.
Note Accounts created when projects are published to the Project Server database from
Project Professional are created as Project Server user accounts with blank passwords.
• Project Managers group Users are automatically added to the Project Managers
group when a Project Professional user publishes a project to the Project Server
database and when a Project Professional user creates a project manager account from
the Collaborate tab in the Options dialog box. The Project Managers group is granted
permissions to the My Projects category. The Project Managers group is able to view
and edit projects in the category. Project Managers are granted a number of global
permissions that allow creation of new projects, status reports, and to-do lists. They are
also granted limited permissions to the My Organization category.
• Resource Managers group The Resource Managers group is granted permissions to
the My Resources category.
• Executives group Users who require broad visibility of the projects and resources in
an organization can be added to the Executives group. This group can view any project
and any resource published to the server. Administrators must manually create user
accounts for users belonging to the Executives group. Only team members and project
manager accounts can be added automatically. The Executives group is granted
permissions to the My Organization category. The Executives group is granted global
permissions to view project and resource information in the Project Center, Resource
Center, Portfolio Analyzer, and Portfolio Modeler.
• Team Leads group This group can be used for users who do not manage projects
but need limited abilities to view and edit project information. This group is granted
permission to the My Projects category.
• Portfolio Managers group Users who manage the enterprise global template and
enterprise resource pool in an organization can be added to the Portfolio Managers
group. These users have broad ability to create and edit data, but cannot perform
Project Server administrative tasks like adding users or creating groups. Portfolio
Managers are able to view and edit all projects and resources in the organization. This
group is granted permission on the My Organization category.
• Administrators group This group is granted all available permissions in Project

Server and is granted permissions to the My Organization category.
Creating a Group
You can create custom security groups in Project Web Access to customize Project Server
security to better meet the security requirements of your own organization.
The Add Group page in Project Web Access.

X To add a group
2. In the side pane, under Add, modify, and delete, click Groups.
3. On the Groups page, click Add Group.
4. In the Group Name and Description box on the Add Group page, type a name and
description for the group.
5. In the Active Directory Group box, type the name of the associated Active Directory
group, if applicable.
Note For more information about using Active Directory to synchronize Project Server
security groups, see the topic Security Group Synchronization with Active Directory in
Chapter 2, Managing Users and Groups of the Microsoft Office Project Server 2003
6. Under Users: Select the users that belong to this group, in the Available users list,
select the names of the users who will belong to the group, and then click Add. To
select multiple users, hold down the CTRL key while making your selections. To add
all available users, click Add All.
7. Under Categories: Select the categories that can be accessed by members of this
group, in the Available categories list, select the categories the group can access, and
then click Add. To select multiple users, hold down the CTRL key while making your
selections. To add all available categories, click Add All.
8. You can set permissions manually for any category or you can apply a security template
containing predefined permission settings. To set permissions using a security
template, in the Selected categories list, select the category to which you want to
apply the template. Select the template to apply in the list next to the Set Permissions
with Template button, and then click Set Permissions with Template.
To set permissions manually in the Selected categories list, select the category to
which you want to apply permissions. In the Permissions list, click Allow or Deny
for each activity. In most cases, you only need to set permissions at the group level; use
category permissions for users with special needs that are not covered by a group’s
permissions.
Guide.
9. Under Global Permissions: Set user’s global permission, select the global
permissions for the group. To set permissions using a security template, select the
template to apply in the list next to the Set Permissions with Template button, and
then click Set Permissions with Template.
Guide.

Using a Portal Site with Project Web Access

You can add a portal site to Project Web Access. The portal site can be a server running
SharePoint Portal Server, a digital dashboard, or any other portal that your organization
wants to use. Portals can provide a single, easy-to-access location that can help team
members better track and manage project-related information, improve collaboration, and
provide for better long- and short-term analysis of project data.
X To specify the portal site for a Project Server security group
3. On the Groups page, click Add Group or Modify Group.
4. Under Digital Dashboard link, if necessary, enter the path to the portal site Uniform
Resource Locator (URL) for this group.
Modifying a Group
You can modify the information associated with any security group in Project Web Access.
In addition, all default Project Server security groups (Administrators, Executives, Portfolio
Managers, Project Managers, Resource Managers, Team Leads, and Team Members) do
not have an Active Directory security group associated with them by default. If you want to
use the Active Directory synchronization feature of Project Server, you must first map
Active Directory security groups to Project Server security groups. Identifying the Active
Directory group to which a Project Server security group will be synchronized is a separate
process for each Project Server security group; Project Server security groups do not need
to map to the same Active Directory security group.
The Modify Group page in Project Web Access.

X To modify a group in Project Web Access
3. On the Groups page, select the group you want to modify, and then click Modify
Group.
4. On the Modify Groups page, make any necessary changes to group membership and
category or permissions associations.
Deleting a Group
If you no longer need a custom security group, you can delete it. You should ensure that
there are no other users or groups dependent on this group before deleting it.
X To delete a group
3. On the Groups page, click a group in the Group Name column, and then click
Delete Group. You cannot delete Project Server predefined groups.
Security Group Synchronization with Active Directory

Any organization already using or planning to use Active Directory for network security
and Project Server as their primary project management application can take advantage of
the Active Directory synchronization feature. Synchronizing Active Directory with Project
Server security groups is really the process of mapping a security group in Active Directory
to a security group in Project Server. This may require the creation of groups in Active
Directory that are used exclusively for Project Server. You will need to determine the best
method to use for your organization when mapping users in Active Directory to Project
Server security groups.
Note Users accessing Project Server data from outside your organization’s firewall will require
Project Server authentication (and that Project Server be set to Mixed authentication mode). Active
Directory synchronization with Project Server security groups can only be performed for users with
Windows authentication. Accounts using Project Server authentication will not be affected during
this synchronization and will not be deactivated.
You can use the default security groups in Project Server or you can create custom groups
to represent the security and access needs of users in your organization. Once created, you
can assign those groups permissions to categories and views. In Project Server, users would
then be added to the groups and would inherit the group’s permission to the specific
categories and views. An administrator could then create custom groups in Active
Directory that map to Project Server security groups, and then add users to those groups in
Active Directory.
One approach that allows faster implementation of the Active Directory synchronization
feature is to create custom groups in Active Directory that map directly to the default
groups in Project Server. First, mimic the default Project Server group structure in Active
Directory, and then add users and groups. Then enable the Active Directory
synchronization feature for Project Server.
Because organizations may arrange their Active Directory groups in a way that does not
map to security groups in Project Server, an administrator needs to map Project Server
security groups to the appropriate Active Directory security groups and may need to create
specific Active Directory groups for this purpose. If these specific groups in Active
Directory contain other groups (such as organizational units), the administrator can simply
place resources in the core Active Directory group and have the new Active Directory
synchronization feature automatically map them to the correct Project Server security
groups.
Synchronizing Active Directory with Project Server security groups is a two-step process in
Project Web Access:
• Specifying the Active Directory security group for each Project Server security group
that you want to synchronize.
Note For more information about specifying the Active Directory group, see the topic
Modifying a Group in Chapter 2, Managing Users and Groups of the Microsoft Office Project
• Setting up the timing options for Active Directory synchronization.

Note For more information about specifying the Active Directory group, see the topic
Synchronizing Project Server Groups with Active Directory in Chapter 2, Managing Users and
Groups of the Microsoft Office Project Server 2003 Administrator’s Guide.
These two steps can be performed in any order, but actual synchronization will not take
place unless the Active Directory group specified in the Active Directory Group field on
the Modify Groups page matches a security group in Active Directory at the time of
synchronization.
Synchronizing Project Server Groups with Active Directory

You can configure Project Server to automatically synchronize Project Server 2003 security
groups with mapped Active Directory groups in Project Web Access.
What happens during synchronization of a Project Web Access security group?
The Active Directory connector to Project Server determines whether each user listed in
the security group in Active Directory that has been mapped to a Project Server security
group exists in the Project Server security group. If yes, no action is taken. If no, then the
user is automatically added to the Project Server security group. If a user is found in a
Project Server security group that does not have a corresponding member in the mapped
Active Directory security group, the user in the Project Server security group will be
deactivated.
You should ensure that you do not do the following before synchronizing Project Server
security groups with Active Directory:
• Internet Information Services (IIS) should not be reset while synchronization is in
progress. If IIS is reset during synchronization, the Project Server Scheduled Process
Service will stop immediately without any error handling.
The Project Server database will still show the processes as running and the user
interface will be disabled. You will need to restore the
MSP_WEB_ADMIN_AD.WADMIN_AD_GRP_UPDATE to 0 (from 1) in the
Project Server database, and then re-synchronize the Active Directory groups with
Project Server security groups.
• Enterprise features should not be disabled while synchronization is in progress.
• Only use the Update Now button when accessing Project Web Access from the
server running Project Server.
• The name entered in Project Web Access should match exactly the name of the Active
Directory group. For example, if the Active Directory group is “ac1ops ” then you
need to enter “ac1ops ” in Project Web Access (note the trailing space in both names
in this example). Entering a trailing space in Project Web Access when there isn’t one
in Active Directory will cause synchronization to fail.
• During a manual synchronization, if the page in Project Web Access where you specify
the synchronization information for Project Server is refreshed just before Active
Directory synchronization is started, then it will appear that the synchronization was
cancelled and has failed.
• If you are running Project Server on a computer that is on a domain using mixed mode
(compatible with user accounts that were created before Windows 2000 was available),
then be sure that the Active Directory group you are synchronizing to does not contain
any user accounts with empty user name or display name fields.
• The local system account that the Project Server Scheduled Process Service uses to run
Active Directory synchronization should have permission to read information from
Active Directory. If the user account associated with the Project Server Scheduled
Process Service does not have permission to read from Active Directory,
synchronization will fail.
• If the alias and user name in Active Directory do not match, for example “ac1ops” for
the alias and “AC1 Operations” for the user name, then you must specify the user
name for Active Directory synchronization to function properly with Project Server.
If you receive partial or total failures during Active Directory synchronization with Project
Server or the Enterprise Resource Pool, look in the Event Viewer to determine the specific
cause of the error. To open the Event Viewer, click Start, point to Administrative Tools,
and select Event Viewer.
X To specify the Active Directory security group for Project Server security groups
3. On the Groups page, select the group for which you want to specify the Active
Directory security group, and then click Modify Group.
4. On the Modify Group page, type the name of the Active Directory security group you
want to use in the Active Directory Group field.
For example, you can use the Active Directory group’s alias by itself or with the
domain in the form of domain\alias or alias@domain.
X To set regular synchronization of Project Server groups with Active Directory
2. Under Add, modify, and delete, click Groups.
3. On the Groups page, under Active Directory: Set the options for AD
synchronization, select Update every, specify the update frequencies you want to
use, and then select the date and time when you want updates to begin.
Note A user can only select Update Now when he or she is logged on locally to the Project
Server computer and has permission to read from Active Directory.
4. Click Save AD Options.

Note This synchronization setting applies to all groups that have a valid Active Directory security
group specified in the Active Directory Group field on the Add Group or Modify Group page in the
Admin area of Project Web Access.
X To remove regular synchronization of Project Server groups with Active Directory

synchronization, select Update only when specified and then do not click the
Update Now button.

Note Clicking Update Now will run Save AD Options automatically before synchronization.
X To manually set synchronization of Project Server groups with Active Directory

synchronization, select Update only when specified and then click the Update
Now button.
Clearing the Active Directory Globally-Unique Identifier

The Clear User AD GUID check box is only enabled on the Modify Users page for
Project Server users who use Windows authentication and only when the user has an
associated Active Directory Globally Unique Identifier (AD GUID). Clearing the AD
GUID will prevent any further updates from Active Directory for that particular user.
Note Clearing the AD GUID will not remove a resource from the Enterprise Resource Pool. If you
want to remove a resource from the Enterprise Resource Pool, you must either remove the resource
from the Active Directory group being used to synchronize to the Enterprise Resource Pool or you
must delete the user directly in the checked-out Enterprise Resource Pool using Project
Professional.
X To clear the Active Directory Globally Unique Identifier for a user

2. Under Add, modify, and delete, click Users.
3. On the Users page, select the user whose AD GUID you want to clear, and then click
Modify User.
4. On the Modify Users page, select Clear User AD GUID.
This option is only available for users who have a Windows user account and already
belong to a Project Server security group that has been synchronized with Active
Directory.
Changing the Project Web Access Administrator Password

Changing the administrator password from the default Project Server password to a strong
password will improve Project Server security. This should be one of the first things you do
after you have finished installing and configuring Project Server.
X To change the administrator password
2. Under Add, modify, and delete, click Users.
3. On the Users page, select Administrator, and then click Modify User.
4. On the Modify User page, click Reset Password.
5. In the Reset password dialog box, complete the New Password and Confirm
Password fields, and then click Save Changes.
Note The password must meet the minimum requirements for Project Server user
accounts, as specified under Password Length for Project Server Authentication in Project
Web Access. For more information about specifying the minimum password length, see the
topic User Authentication in Chapter 3, Managing Security of the Microsoft Office Project
6. On the Modify Users page, click Save Changes.

3
Managing Security
Categories are the collections of projects, resources, assignments, views, and models to
which users and groups in Project Server are granted access. Categories define which
collections of specific data (projects, assignments, resources, and views) that these users
and groups have access to. Categories allow the administrator to separate the data by scope
of the information accessed, and to filter data using security rules like Resource Breakdown
Structure (RBS) that can help organize and display data in specific ways.
Project Server creates five default categories during installation. These default categories are
designed to enable Project Server to provide the most common layer of security for a
hierarchical organization or matrix organization. You can only add users and groups to
categories directly. However, you can add projects and resources to categories manually by
choosing them from lists or you can use predefined filters (security rules) to automatically
add them to categories. Any user who has permission to a category is granted permission to
all of the projects and resources in the category.
Note For an introduction to Project Server security, see the topic Understanding Project Server
Security in Chapter 1, Administering Project Server Using Project Web Access of the Microsoft Office
Security Rules in Categories

Security rules are defined relationships between users, projects, resources, and models.
Security rules are used to determine what users can see in relation to the objects they have
been granted access to. Security rules are used to query the Project Server database to
determine the list of projects, resources, or models a particular user will be able to access.
The results of this query will be unique to each user. For example, if two project managers
belong to the My Projects security category, a security rule queries for all of the projects
that they manage so that each manager has access to only the projects that they created.
Security rules are used to automate the granting of access to three different types of
objects: projects, resources, and models.
Security rules allow you to filter resources and projects by:
• All of the projects they manage.
• All of the projects to which they are assigned.
• All of the projects assigned to resources they manage.
• All of the projects managed by resources that they manage.
• A project manager’s or resource manager’s own information.
• Information for all resources in projects that they manage.
• Information for all resources that they manage.
• A project manager’s or resource manager’s own models.
• Models created by resources that they manage.
Importance of Resource Breakdown Structure in Defining

Security
RBS is an Enterprise Resource Outline Code that is saved in the Enterprise Global
Template. It is typically used to define look-up table values based on the management
reporting structure of your organization, though it can be structured in other ways as well.
RBS plays a significant role in the definition of security in Project Web Access and Project
Server and it works best when used to provide an organizational rather than a location-
based structure. By specifying values for RBS for all resources in the Enterprise Resource
Pool, your organization can take advantage of the security rules that can be defined for
each security category.
The lookup table definition used to describe RBS is critical because security rules for
viewing projects and resources use the RBS to determine the access that is granted based
on security rules. When Project Server checks a resource’s position within the RBS, if the
object assigned to a resource falls below the level in the RBS to which the user is trying to
access, then access is granted.
The following security rules use RBS:
• (Projects) Allow users in this category to view all projects managed by resources
that they manage If a project is managed by a resource with an RBS code below the
category member in the RBS hierarchy, the category member will be able to see the
project in the Project Center in Project Web Access.
• (Projects) Allow users in this category to view all projects managed by resources
that they manage If a task in a project is assigned to a resource with an RBS code
below the category member in the RBS hierarchy, the category member will be able to
see the project in Project Center.
• (Resources) Allow users in this category to view information for all resources that
they manage If a resource has an RBS code assigned to it that is beneath the category
member in the RBS hierarchy, the category member will be able to view the resource
information.
• (Resources) Allow users in this category to view information for all resources in
projects that they manage If a project manager creates a project with ten resources
in it, then that project manager will be able view the information for those ten
resources.
• (Models) Allow users in this category to view models created by resources that
they manage If a model was created by a resource with an RBS code below (in the
same branch of the RBS tree) the user requesting access to the model, access will be
granted.
Note You will want to ensure that you have set up your organization’s RBS before adding users,
groups, and views to security categories in Project Web Access, outside of the default security
category settings that are included by default with Project Server. For more information about the
default security settings in Project Server, see Appendix D: Project Server Default Settings in the
Microsoft Office Project Server 2003 Administrator’s Guide.
Managing Categories
A Project Server installation creates five default security categories:
• My Tasks This category is intended for the individual team members who are
assigned to tasks in one or more enterprise projects. It grants users permission to view
Microsoft Windows® SharePoint™ Services Documents, Issues, and Risks, and
timesheets and status reports for the projects to which they are assigned.
• My Projects This category is intended for project managers. This category grants
project managers read and write access to project plans that they have created. By
default, project managers can view all enterprise resources.
• My Resources This category is intended for resource managers. This category uses a
security rule that is based on RBS and is only useful when RBS is defined.
• My Direct Reports This category is intended for resource managers who need to be
able to approve timesheets.
• My Organization This category is used to grant broad access to all information. This
category is intended for members of a Project Management Office (PMO), executives
in an organization, and other key users that require visibility to the entire organization.
Users in this category are by default granted permission to view projects and resources
throughout the organization.
The Categories page in Project Web Access.

Each of these default security categories has a set of predefined groups and permissions
assigned to them when Project Server is installed:
• Portfolio managers, administrators, and executives are assigned to the My Organization
category.
• Project managers, team leads, and resource managers are assigned to the My Projects
category.
• Team members are assigned to the My Tasks category.
• Resource managers are assigned to the My Resources category.
• Any user with direct reports is assigned to the My Direct Reports category.
Adding a Category
You can add a custom security category in Project Web Access to help create a security
structure in Project Server that closely maps to the way your own organization handles
user- and group-level security.
The Add Category page in Project Web Access.

X To add a category
Manage security.
2. In the side pane, under Security options, click Categories.
3. On the Categories page, click Add category.
4. On the Add Category page, under Category name and description, type the name
of the category and a description.
5. In the Available users and groups list, select the users and groups who will belong to
the security category, and then click Add.
Note While it is possible to grant permissions to individual users, it is recommended that

you grant permissions to users through groups whenever possible.
6. For each user or group, set the category permissions:
• To set category permissions using a security template, in the Users and groups
with permissions list, select a user or group. Select the template to apply from the
drop-down list next to the Set Permissions with Template button, and then
click Set Permissions with Template.
• To set category permissions manually, in the Users and groups with
permissions list, select a user or group. In the Permissions list, click Allow or
Deny for each permission.
7. Under Projects: Select the projects that users in this category can view, specify
the projects that users in this security category can view and the project views they can
use by selecting from the available projects and views or from options provided. All
projects selected will have the same set of views. There are three options:
• Select All current and future projects in the Project Server database to allow
users that have permissions to this category to see all current and future projects in
the Project Server database.
• Select Only the projects indicated below to choose specific projects that are
currently saved in the Project Server database.
• Select one or more security rules from the list of security rules. The rules Allow
users in this category to view all projects they manage and Allow users in
this category to view all projects in which they are a team member are driven
by who created the project and whether the user is a member of a project team.
The rules Allow users in this category to view all projects managed by
resources that they manage and Allow users in this category to view all
projects assigned to resources that they manage are both driven by RBS.
• Select the project views that will belong to this category. If project views are not
added to a security category, users who belong to that security category will not be
able to see any projects in the Project Center.
8. Under Resources: Select the resources whose information can/cannot be viewed

by users in this category, specify the resources whose information users in this
security category will be able to view and the assignment and Resource Center views
that they can use by selecting from the available resources and views or options
provided. There are three options:
• Select All current and future resources in the Project Server database to allow
users that have permissions to this category to see all current and future resources
in the Project Server database.
• Select Only the resources specified below to choose specific resources that are
currently saved in the Project Server database and whose assignments can or
cannot be viewed by users who belong to this category.
• Select one or more security rules from the list of security rules. The rules Allow
users in this category to view their own information and Allow users in this
category to view information for all resources in projects that they manage
are driven by who created the resource and whether the user is a member of a
project team.
The rules Allow users in this category to view information for all resources
that they manage and Allow users in this category to view information for all
resources that they manage directly are both driven by RBS.
• Select the Assignment views in this category. Users who belong to this category
will only be able to see Assignment views that have been added.
• Select the Resource Center views in this security category. If Resource Center
views are not added to a security category, users who belong to that security
category will not be able to see any resources in the Resource Center.
9. Under Project Center Views: Select views for displaying a portfolio of projects,
specify the Project Center views, Portfolio Analyzer views, and Portfolio Modeler
views that users in this security category will be able to view by selecting from the lists
of views and options provided.
• Select the Project Center views in this security category.
• Select the Portfolio Analyzer views in this security category.
• Specify the models that can be viewed. There are three options:
Select All current and future models in the Project Server database to allow
users that have permissions to this category to see all current and future models in
Select Only the models specified below to choose specific models that are
currently saved in the Project Server database.
Select one or more security rules from the list of security rules. The rule Allow
users in this category to view their own models is driven by who created the
model.
The rule Allow users in this category to view models created by resources
that they manage is driven by RBS.
Modifying a Category
You can modify the properties of any security category in Project Web Access, including
adding or removing groups, users, views, and more.
X To modify an existing category in Project Web Access
Manage security.
3. On the Categories page, select the category you want to modify, and then click
Modify Category.
4. On the Modify Category page, make the necessary changes.

Deleting a Custom Category

If you are no longer using a custom category, you can delete it. You cannot delete the
default Project Server categories. Before deleting a category, verify that all users and groups
associated with this category either no longer need access to the particular features and
functions to which this category granted them access, or that the users and groups have
been migrated to a new category that will continue to provide them access to the features
and functions in Project Server, Project Web Access, and Microsoft Office Project
Professional 2003 to which they need access.
X To delete a category
Manage security.
3. On the Categories page, select the category you want to delete, and then click Delete
Category.
4. Click OK in the alert dialog box to confirm deletion.
Security Templates
Security templates are a quick way to apply or reset predefined permission profiles to new
or existing users, groups, and categories. By applying security templates, the rights being
applied can easily be standardized according to the role. There are a number of predefined
templates created when Project Server is installed. These align with the predefined groups.
These security templates can be customized and/or new security templates created.
Creating custom security templates should be a process that your organization plans for.
For example, first determine the common usage patterns that are required in your
organization but not covered by the default security categories included with Project
Server. This will help identify the requirements for a custom security template. Once the
usage pattern is understood, next determine the combined patterns of data access and the
permission requirements that are needed by users when performing all of the required tasks
defined by the usage pattern. This becomes the definition of the security category. The next
step is to determine the set of projects, resources, views, etc., that the users and groups
assigned to the security category will need to be able to access. Then add the users and
groups to the custom security category; they will use the permissions defined in the
template and will have access to the projects, views, resources, etc., that are also defined in
the template.
The Security templates page in Project Web Access.
Adding a Security Template

You can group commonly used permissions into a security template and then assign
permissions to users, groups, and categories based on the permissions set in the security
template.
X To add a security template
Manage security.
2. In the side pane, under Security options, click Security templates.
3. On the Security templates page, click Add Template.
4. In the Add New Template dialog box, enter a name and a description for the security
template.
• To base this template on an existing template, select a template from the Copy
Template list. The new template is populated with the security permissions in the
existing template.
• To create a new security template without setting permissions, do not select a
security template in the Copy Template list. You will need to modify the template
before it can be used.
5. Click OK.
Modifying a Security Template

You can modify a security template in Project Web Access. In addition, any custom
security template not based on an existing security template will need to be set up for
permissions to the various available user roles.
The Modify Template page in Project Web Access.

X To modify a security template
Manage security.
2. In the side pane, under Security options, click Security templates.
3. On the Security template page, select the template, and then click Modify Template.
4. Under Template Name and Description, modify the template name and update the
description as needed.
5. Under Permissions: Select the permissions that you want this template to be
allowed or denied, for each activity, select the check box in the Allow column to
allow users to perform the activity, or the check box in the Deny column to prevent
users from performing this activity.
The permissions list is organized by user roles: Account Creation, Admin,

Collaboration, Enterprise Portfolio Management, General, Status Reports, Tasks, To-
Do List, Transactions, Views, and Workgroup.
• To allow or deny permissions for all the activities in a user role, select the check
box in the Allow or Deny column in the user role row. For example, select the
Allow check box in the Status Reports row to allow users to perform all the
activities associated with status reports.
• To allow or deny permissions for individual activities in a user role, select the
Allow or Deny check box for the activity. For example, select the Allow or Deny
check box in the Create Manager Accounts from Project row.
• Use the Features column to sort the views by user role.
Deleting a Security Template

You can delete any unused custom security template in Project Web Access. Custom
templates do not affect access to Project Server, Project Web Access, or Project
Professional; they are only the basis for custom security categories. Before deleting a
custom security template, you should make sure you will not need it later. Otherwise there
are no other associated risks with deleting a custom security template.
X To delete a security template
Manage security.
2. In the side pane, under Security options, click Security template.

3. On the Security template page, select the template you want to delete, and then click
Delete Template.
You cannot delete Project Server default security templates.
User Authentication
Project Server can authenticate users who have a Windows user account, a Project Server
user account, or both. By default, authentication for Project Server is set to Mixed, which
means both Windows and Project Server authentication methods are allowed. Users who
need to access information stored on servers running Windows SharePoint Services,
Microsoft SQL Server™ 2000, or Analysis Service will still require Windows
authentication.
The User authentication page in Project Web Access.

Windows authentication provides for better overall security than just Project Server
authentication or mixed authentication methods. Therefore, it is recommended that only
Windows authentication be used.
As an administrator, you can choose one of the following authentication options:

• Mixed Allows both Windows authentication and Project Server authentication.
However, a single authentication method must be specified for each user account.
Some users can be authenticated using Windows authentication while others can be
authenticated using Project Server authentication.
• Windows authentication only Permits only Windows authentication for all users.
This allows for the highest level of security in Project Server because all users must
authenticate to Project Server based on their Windows user accounts. If you select this
method, all Project Server authentications will be handled transparently for all users
who have accepted the Project Server End User Licensing Agreement (EULA) and
have downloaded the Project Web Access Microsoft ActiveX® controls (second-time
access).
• Project Server authentication only Permits Project Server authentication only for all
accounts. Project Web Access users must supply a user name and password each time
they log on to Project Web Access.
If you change authentication methods after creating Windows authenticated user accounts,
those Windows authenticated user accounts will be immediately deactivated.
Note For more information about deactivated user accounts, see the topic Deactivating or
Reactivating a User in Chapter 2, Managing Users and Groups of the Microsoft Office Project
Server 2003 Administrator’s Guide. For more information about changing the authentication
method for Project Server, see the topic User Authentication in Chapter 3, Managing Security of the
Windows SharePoint Services (Documents, Issues, and Risks) and Analysis Services
(Portfolio Analyzer and Portfolio Modeler) require Windows authentication. If Mixed
authentication is selected, you will have to take some extra steps to allow Project Server
users access to those features in Project Web Access.
Note The Project Web Access default administrator account is always a Project Server user
account. Your organization should ensure that there is at least one user with administrative
privileges that uses the same authentication method as defined on the User authentication page in
Project Web Access.
It is recommended that you configure Internet Information Services (IIS) to use Secure
Sockets Layer (SSL) for best security. If you do not configure IIS to use SSL, potentially
sensitive data will be sent in clear text between the clients and servers in your deployment.
Examples of this include:
• If you are using Project Server accounts, then user names and passwords are sent from
client to server in plain text.
• All information exposed through the Project Data Service (PDS) is transmitted in plain
text, including a SQL Server 2000 user name and password.
• Users of Project Web Access could transmit potentially sensitive company data
between client and server.
Recommendations for Determining User Authentication

Consider the following general security guidelines when determining whether to choose
Windows authentication only, Project Server authentication only, or Mixed
authentication:
• If all users accessing Project Server already have (or can have) a Windows domain
account, you should configure Project Server to accept only Windows authentication.
• If some users need to access Project Server from the Internet but do not have a
Windows account, use Mixed authentication, and consider setting up unique sets of
roles, permissions, and categories to separate internal access users from external access
users.
• Determine whether project managers will be allowed to create resources in Project
Server as they publish projects and assignments to the Project Server database. If
project managers are allowed to create their own resources, they should use Windows
authentication for all resources that have a Windows user account. This information
can be entered in the Windows User Account field in Project Professional.
When a Windows user account is specified for a resource and a workgroup message is
sent to that resource, the Windows user account is used to create the resource’s
account in Project Server. If a Windows user account has not been specified, then the
resource’s name is used to create a Project Server account for the new user.
• If your organization is using Windows SharePoint Services, you should support
Windows authentication for users who need to access the Documents, Risks, and
Issues features.
Setting Authentication Options

You can specify the authentication methods that users can use to log on to Project Web
Access: Windows authentication (domain name\user name), Project Server user accounts
(user account and password), or mixed (both Windows and Project Server authentication).
In addition, you can specify the length of Project Server user account passwords.
X To specify the user authentication type
Manage security.
2. In the side pane, under Security options, click User authentication.
3. On the User authentication page, under Specify how users should be

authenticated by Project Server, select the method you want users to use when
logging on to Project Web Access. Chose one of the following options:
• Mixed Users can be authenticated with Windows authentication using the user
account logon ID, or with Project Server authentication using a logon ID and
password entered by the user.
• Windows Authentication only Users can only use Windows authentication. All
Project Server authentication accounts will be deactivated. Deactivated Windows
authentication will remain disabled.
• Project Server authentication only Users can only use Project Server
authentication. All Windows authenticated user accounts will be deactivated.
Deactivated Project Server user accounts will remain disabled.
X To disable user authentication settings
1. Determine the user authentication method that your organization wants to use
(Mixed, Windows Authentication only, or Project Server authentication only) on
the User authentication page in the Admin center in Project Web Access.
2. On the server running Project Server, open the Registry Editor.

3. Create a DWORD Value at the following location in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\MS Project
\WebClient Server\ProjectServer\Datasets\Applications
Name the DWORD Value DisableAuthEdit and assign it a value of 1.

4. This will disable the options in Project Web Access:
X To set the Project Server password length

Manage security.
2. In the side pane, under Security options, click User authentication.
3. On the User authentication page, under Password Length for Project Server
Authentication, enter the minimum length for Project Server passwords in the
Minimum length that users must set their passwords to text box.
Changing this setting will not affect existing passwords; it will only affect password
creation when users change their passwords or create new passwords.

4
Managing Views
Microsoft® Office Project Web Access 2003 views contain all of the published
information about projects and resources in the Project Server database and can be used to
create Project, Project Center, Assignment, Resource Center, and Portfolio Analyzer views.
Views are simply live and interactive reports of project and resource information that is
stored in the Microsoft Office Project Server 2003 database. Views allow project team
members to see more than just the tasks, assignments, and projects that they are working
on. Views can also allow project and resource managers to communicate critical
information about their projects throughout their organization. For example, some views
allow team members to see information about just their projects. Other views can be used
to assist project and resource managers with keeping track of their project’s tasks, checking
to see which resources are available, and then matching the needs of their projects to the
skills of available resources.

Views are created in Project Web Access. Views provide a way of keeping project data
more secure, because permissions must be granted to users in order for them to see a
specific view. Often, the creation of views will fall on a core group of project management
and administrative individuals responsible for maintaining the integrity of Project Server
data within the larger organization.
Views can be accessed by users of Project Web Access and Project Professional in the
following areas:
• The Tasks, Projects, and Resources top-level menus in Project Web Access.
• The Project Center, Resource Center, and Portfolio Analyzer options in the
Collaborate menu in Project Professional.
When the Enterprise Resource Pool is populated with users, project managers can add
enterprise resources to their projects and then save the projects (with assignments) to the
Project Server database. Resource information (including skills and enterprise custom
fields), availability, and assignments can be viewed in Project Web Access. Views can be
defined by administrators (or any Project Web Access user with permission to create views)
and can then be added to categories in Project Web Access. Users belonging to the
category will be able to access all views added to that category.
About Views
After you have installed and configured Project Server and added users to the Enterprise
Resource Pool, most organizations will be ready to start letting users interact with Project
Server data from Project Professional and Project Web Access without a lot of additional
configuration. However, users who will want to create views will need to be granted
permission to do so.
Users must have the appropriate permissions to access the Manage views area of Project
Web Access in order to create new views. Users must also have the appropriate
permissions to access the Projects and Resources areas of Project Web Access in order to
access existing views.
On the Specify Views page in Project Web Access, all of the Project, Project Center,
Assignment, Resource Center, and Portfolio Analyzer views that are currently available will
be displayed. Each view has the following descriptive elements:
• View Name is the name of the view. This is the same as the Name field under View
name and description when adding or modifying a view.
• View Type is the type of view. There are five types of views: Project, Project Center,
Assignment, Resource Center, and Portfolio Analyzer.
• Project views provide task, assignment, or resource information specific to a single
project.
• Project Center views provide a portfolio view of projects. A Project Center view
can allow users to view all enterprise projects in the Project Server database, edit
some project-level Enterprise Outline Codes in the Project Center view, and allow
grouping and filtering on the Enterprise Outline Codes in the Project Center view.
• Assignment views display task assignments that have been made through Project
Web Access, including projects and tasks that resources are currently working on,
non-project time entered by resources, and other assignment data, including the
timephased breakdown of a resource’s work and actual work values.
• Resource Center views contain a list of resources that are part of the Enterprise
Resource Pool. They include a resource view that groups resources using various
Enterprise Resource Outline Codes (pulled directly from the Enterprise Resource
Pool in the Project Server database), a view that allows a user to edit some
resource-level properties like Location, Department, or Skills, and availability and
usage views for any selected resource.
• Portfolio Analyzer views take advantage of Microsoft Office Web Components to
display online analytical processing (OLAP) data stored in cubes in the Analysis
Services server. This combination of technology allows you to use PivotTable and
PivotChart features to display and manipulate project data. Setting up and using
Portfolio Analyzer involves some additional steps.
• View Description is the description of the view. This is the same as the Description
field under View name and description when adding or modifying a view.
Using Versions in Project and Project Center Views

Multiple versions of a project can be published to the Project Server database, and multiple
versions of a project can be made available in Project Center views. The Version field
should be added to Project Center views to indicate the version of a project that a user is
viewing. Even if only one project has been selected to view, it may still be useful to know
which version of the project is being viewed.
Note Assignment and Resource Center views can only display the Published versions of projects.
Working with Project Views

Project views display data within a specific project, including task, assignment, and resource
details. There are three primary views available for the Project Center:
• Tasks
• Resources
• Assignments
Project (Task), Project (Resource), and Project (Assignment) views can be accessed from
the following areas:
• In Project Web Access, click Projects in the top-level navigation. Select a project to
view. On the View A Project page, select a view from the Choose a view drop-down
list.
• In Project Professional, point to the Collaborate menu and then select Project
Center. Select a project to view. On the View A Project page, select a view from the
Choose a view drop-down list.
Creating Task views in Project Web Access.

X To add a Project Tasks view
Manage views.
2. On the Specify Views page, click Add View.
3. Under View Type, select Project.

4. Under View name and description, type the name of the view and a description in
the Name and Description text boxes.
Note Name is a required field.
5. Under Table: Select the type of information you want displayed in the view, click
Task. Allow the page to refresh with the updated list of fields.
6. Under Fields: Select the fields you want displayed in the view, in the Available
fields list, select the fields you want included in the view, and then click Add. To select
multiple fields, hold down the CTRL key while making your selections. Each field is set
to Automatically fit this field to width by default.
• If you want to increase the width for a field, select the name of the field in the
Displayed fields list, select the Field width option, and then type the field width.
• If you want to have Project Web Access automatically determine the width of the
field in the view, select Automatically fit this field to width.
• If you want to adjust the order of the fields in the view, you can select a field under
Displayed fields and then click Up or Down to change the field order.
7. Under Splitter-bar: Enter an offset (in pixels) for the splitter bar in the view,
enter the number of pixels from the left of the view display that you want the Gantt
Chart splitter to be displayed.
8. Under Gantt Chart Format: Specify the Gantt Chart format for this view, select
the type of Gantt Chart or custom Gantt Chart that you want to use to display
information. The Gantt Chart options available in this drop-down list include Gantt
Chart (Views), Detail Gantt (Views), Leveling Gantt, Tracking Gantt, Gantt
Chart (Project Center), Tracking (Project Center), and any of the eleven custom
Gantt Chart views that can be created in Project Web Access.
Note For more information about creating custom Gantt Chart views, see the topic Gantt
Chart Formats in Chapter 8, Customizing Project Web Access of the Microsoft Office Project
9. Under Grouping format: Specify the grouping format for this view, select the
grouping style or custom grouping style that you want to use to display this
information. The Grouping format options available in this drop-down list include
Timesheet, Views, and any of the nine custom Grouping format views that can be
created in Project Web Access.
Note For more information about creating custom grouping format views, see the topic
Grouping Formats in Chapter 8, Customizing Project Web Access of the Microsoft Office
10. Optionally, under Default Group, Sort (Optional): Specify the default group and
sort for the view. Options include the following:
• Group by You can group the view by a field in the Displayed fields list. Use the
Then by lists to refine the sort. For example, select Start for the Group by to first
sort by start date, and then select Task Name in the first Then by list to then be
able to sort the list by Task Name within the initial sorting by Start date.
• Sort by You can sort the view by any field in the Displayed fields list.
• Order Indicate whether you want to sort the view in Ascending or Descending
order.
11. Under Outline levels: Specify the number of outline levels displayed by default
in this view, indicate the level of drill-down detail the view will make available to users
who can view it. The outline levels options available in this drop-down list include any
or all of the ten custom outline levels.
12. Under Filter (Optional): Specify a filter to be applied to the view, set up filters by
selecting a field from the Field list (any field available within the type of view),
choosing an Operator, and setting a Value. You can establish relationships with other
filters by selecting And/Or.
• Use the percent symbol (%) in the Value field to represent a string of characters.
The percent symbol can also be included in a string. For example, if you wanted to
filter for any Microsoft application, you could enter Microsoft%. Any string that
begins with Microsoft would be included in the view.
• Use the underscore character (_) in the Value field to filter for a single wildcard
character in a string of characters. For example, if you wanted to filter for a
specific type of task (Training classes), you could enter Training _ Class and the
filter would return Training A Class, Training B Class, and so on.
Note You should not create filters that test for NA when that value is also associated with a
date, for example if Field is set to “Actual Start”, Operator is set to “Equals”, and Value is
set to “NA”. Testing for NA does not work and can create instability when the view itself is
used. If you want to test for no value, use NULL instead.
13. Under Categories (Optional): Select the categories that this view belongs to, add
the categories within which this view will be available. Under Available categories
select the categories and then click Add or Add All.
Note The only way to make Project Tasks views available to users of Project Web Access or
Project Professional is to add them to a category. This step is optional when creating a view
and can be done later by modifying the view or the category to which you want to add the
view.

X To add a Project Resources view
Manage views.

Resource. Allow the page to refresh with the updated list of fields.
sort by start date, and then select Resource Name in the first Then by list to
then be able to sort the list by Resource Name within the initial sorting by Start
date.
order.
the categories that this view will be available. Under Available categories, select the
categories and then click Add or Add All.
Note The only way to make Project Resource views available to users of Project Web
Access or Project Professional is to add them to a category. This step is optional when
creating a view, and can be done later by modifying the view or by modifying the category to
which you want to add the view.

X To add a Project Assignment view

Manage views.

Assignment. Allow the page to refresh with the updated list of fields.
Chart (Views), Detail Gantt (Views), Leveling Gantt, Tracking Gantt, and any of
the eleven custom Gantt Chart views that can be created in Project Web Access.
order.
the categories within which this view will be available. Under Available categories,
Note The only way to make Project Assignment views available to users of Project Web
Working with Project Center Views

Project Center is a view definition that supports enterprise-level features and allows
viewing of enterprise projects in Project Web Access and Project Professional. A Project
Center view can allow users to view all enterprise projects in the Project Server database,
edit some project-level Enterprise Outline Codes in the Project Center view, and allow
grouping and filtering on the Enterprise Outline Codes in the Project Center view.
Project Center views can be accessed from the following areas:
• In Project Web Access, click Projects in the top-level navigation.
• In Project Professional, point to the Collaborate menu and select Project Center.
Creating Project Center views in Project Web Access.

X To add a Project Center view
Manage views.
3. Under View Type, select Project Center.

Chart (Project Center), Tracking (Project Center), Gantt Chart (Views), Detail
Gantt (Views), Leveling Gantt, Tracking Gantt, and any of the eleven custom
Gantt Chart views that can be created in Project Web Access.
sort by start date, and then select Project Name in the first Then by list to then
be able to sort the list by Project Name within the initial sorting by Start date.
order.
Note The only way to make Project Center views available to users of Project Web Access
or Project Professional is to add them to a category. This step is optional when creating a
view, and can be done later by modifying the view or by modifying the category to which you
want to add the view.
Working with Assignment Views

Assignment views display task assignments that have been made through Project Web
Access, including projects and tasks that resources are currently working on, non-project
time entered by resources, and other assignment data, including the timephased breakdown
of a resource’s work and actual work values.
Creating Assignment views in Project Web Access.

X To add an Assignment view
Manage views.
3. On the Specify Views page, under View Type, select Assignment.

Note Selected fields are displayed in Assignment views only if a project manager includes
them in the fields published to Project Server. Project managers can include fields to
publish to Project Server with the Publish Fields command on the Customize sub-menu in
Project Professional. To use Publish Fields, point to Tools and then Customize, and then
select Published Fields. This action can only be fully completed when Project Professional is
connected to the Project Server database.
information. The Gantt Chart options available in this drop-down list include
Personal Gantt (Tasks) and four custom Assignment Information Gantt Chart views
that can be created in Project Web Access.
order.
Note The only way to make Assignment views available to users of Project Web Access or
Project Professional is to add them to a category. This step is optional when creating a view,
and can be done later by modifying the view or by modifying the category to which you want
to add the view.

Working with Resource Center Views

Resource Center views contain a list of resources that are part of the Enterprise Resource
Pool. These views include a view that groups resource using various Enterprise Resource
Outline Codes. These are pulled directly from the Enterprise Global Template in the
Project Server database, including Resource Breakdown Structure (RBS). This view allows
users to edit some resource-level properties like Location, Department, or Skills (if the user
has the View Resource Center category permission in Project Web Access) and
availability and usage views for any selected resource.
Creating Resource Center views in Project Web Access.

Resource Center views can be accessed from the following areas:
• In Project Web Access, click Resource in the top-level navigation.
• In Project Professional, point to the Collaborate menu and select Resource Center.
X To add a Resource Center view
Manage views.
3. On the Specify Views page, under View Type, select Resource Center.
Note Selected fields are displayed in Assignment Views only if a project manager includes
them in the fields published to Project Server. Project managers can include fields to
publish to Project Server with the Publish Fields command on the Customize sub-menu in
Project Professional. To use Publish Fields, point to Tools, and then Customize, and then
select Published Fields. This action can only be fully completed when Project Professional is
connected to the Project Server database.
sort by start date, and then select Resource Name in the first Then by list to
then be able to sort the list by Resource Name within the initial sorting by Start
date.
order.
Note The only way to make Resource Center views available to users of Project Web
11. Under RBS Filter (Optional): Filter resources to user’s RBS branch, select Filter
Resources to user’s RBS branch if you want to use RBS to determine which
resources are available in the view for a particular user. If RBS is defined in the
Enterprise Global Template, enabling this feature will limit the resources displayed in
the Resource Center view to just those managed by the current user. This is useful for
creating a view that is available to users who belong to the My Resources category.
Working with Portfolio Analyzer Views

Portfolio Analyzer takes advantage of Microsoft Office Web Components, which is a
collection of Microsoft ActiveX® components. Project uses two Office Web Components
(PivotTable and Chart) to access OLAP cube data stored in the Analysis Services database
(an Analysis Services database is created for each OLAP cube created in Project Web
Access). Users can interact with this data using fully interactive PivotTable and PivotChart
reports in Project Web Access and Project Professional. Users can sort, filter, add, or
modify data, expand and collapse details, and save their results for future reference.
Portfolio Analyzer views can be accessed from the following areas:
• In Project Web Access, click Projects in the top-level navigation, and then under
Actions, select Analyze projects in Portfolio Analyzer in the side pane or click
Resources, and then under Actions, select Analyze resources in Portfolio Analyzer.
• In Project Professional, point to the Collaborate menu, and then select Portfolio
Analyzer.
Note For more information about Portfolio Analyzer views, see Chapter 10, Working with Portfolio
Analyzer in the Microsoft Office Project Server 2003 Administrator’s Guide.
Modifying, Copying, and Deleting Views

The process for creating views is slightly different for each of the seven types of views. The
process for modifying, deleting, or copying views is generally the same until you get to the
actual page where you make modifications. That page is identical to the page you use when
adding the view. You should refer to the procedures that discuss how to add each view
type when making the actual modifications to each of the view types.
X To modify a Project, Project Center, Assignment, Resource Center, or Portfolio Analyzer view
Manage views.
2. On the Specify Views page, in the View Name column, select the view you want to
modify, and then click Modify View.
Note The view type cannot be modified. Once created, Project (Task), Project (Resource),
Project (Assignment), Project Center, Resource Center, Assignment, and Portfolio Analyzer
views must always remain the same view type as originally created.
3. Make any necessary changes. Refer to these topics for more information:
• Working with Project Views for Project (Tasks), Project (Resources), and Project
(Assignments) views
• Working with Project Center Views
• Working with Assignment Views
• Working with Resource Center Views
• Working with Portfolio Analyzer Views
X To copy a Project, Project Center, Assignment, Resource Center, or Portfolio Analyzer view
Manage views.
2. On the Specify Views page, in the View Name column, select the view you want to
make a copy of, and then click Copy View.
3. In the Copy View dialog box, type the name for the new view and then click OK.
4. Select the new view, click Modify View, and then complete the page. When you copy
a view, you are not only copying the specifics of the view, but also all of the other
attributes of that particular view. For example, if you copy a Project (Task) view, then
the copy will only make available the list of task fields. If you later attempt to modify
the view, you will only be able to make changes within the context of a Project (Task)
view.
X To delete a Project view
Manage views.
2. On the Specify Views page, select the view you want to delete, and then click Delete
View.
Note If you delete a view, users who belong to any category that allows users to see the
deleted view can no longer view the set of project data that was defined by the view.
Making Views Available to Project Web Access Users

Views only define the fields and formats available in a report. Views do not define the
resources or projects visible in the report. After a view is defined, the view must be added
to one or more categories in order for the view to be accessed by the Project Web Access
users who are also assigned to that category. Categories define the specific projects and
resources that a particular user will be able to see. By adding views to categories,
administrators can define the objects (projects and resources) and the properties of the
objects (views) available to any given user or group of users.
Note For more information about adding views to Project Server security categories, see the topic
Managing Categories in Chapter 3, Managing Security Categories of the Microsoft Office Project
X To add a view to a category

Manage security.
3. On the Categories page, select a category in the Category Name column, and then
click Modify Category.
4. Under the sections Projects: Select the projects that users in this category can
view, Resources: Select the resources whose information can/cannot be viewed
by users in this category, and Project Center Views: Select views for displaying a
portfolio of projects, select the view you want to make available to the selected
category, and then click Add.
Getting Additional Views

Before users in your organization can access custom views, you must make sure that the
views are available in Project Web Access. To update the list of available views with custom
Hypertext Markup Language (HTML) views, data access pages, and Active Server Pages
(ASP) pages, you must first add them to the \IIS Virtual Root\Views folders on the
computer running Project Server. After you have added the custom views to the correct
folders, you can then make them available for users to access in Project Web Access.
Note Project Server 2003 does not support incorporating data access page views that were
created in Microsoft Access or Microsoft Excel into Project Web Access.
X To update the list of available views

Manage views.
2. On the Specify Views page, click Get Additional Views.
Custom views can be added as long as they are stored in one of the following folders
under the Project Server root directory:
C:\Program Files\Microsoft Office Project Server 2003

\IIS Virtual Root\Views\<folderName>
• The ..\Views\Project folder contains Project views.

• The ..\Views\Portfolio folder contains Project Center views.
• The ..\Views\PortfolioAnalyzer folder contains Portfolio Analyzer views.
• The ..\Views\Assignment folder contains Assignment views.
• The ..\Views\ResourceCenter folder contains Resource Center views.
3. When finished, you will be notified that Project Server has been successfully updated.
All HTML, data access pages, and ASP pages found under the Views folders in the
Project Server virtual directory have been added to the list of available views in Project
Web Access.
5
Configuring Project Server
Microsoft® Office Project Server 2003 includes a standard set of features available to all
users of Project Server 2003, Microsoft Office Project Web Access 2003, and Microsoft
Office Project Professional 2003. This standard set of features is always enabled. Enterprise
features can be enabled or disabled and provide additional functionality. Some features
have dependencies on other enterprise features. Some are available as default items during
Project Server setup. Project Server configuration using Project Web Access is the area in
Project Server where your organization can specify the enterprise feature settings that users
in your organization will have available to them when using Project Server, Project Web
Access, and Project Professional as part of your organization’s Enterprise Project
Management (EPM) solution. In addition to configuring enterprise and non-enterprise
features, you can add custom top-level and side-pane menu items to help make Project
Web Access organization-specific.
Note Project Server also provides administrators the ability to enable or disable specific features
for all users of Project Server. Server-wide configuration is done on the Server configuration page in
Project Web Access.
Enterprise and Non-Enterprise Modes

Project Server is designed to support two different modes: enterprise and non-enterprise.
Enterprise features are a set of features in Project Server that are designed to take
advantage of several aspects of project management that could only be possible when using
a server application like Project Server. For example, the Enterprise Resource Pool and
Enterprise Global Template are stored in the Project Server database in order to provide
central availability for all users in your organization. Also, Portfolio Analyzer requires
Microsoft SQL Server™ 2000 Analysis Services.
Running Project Server in Enterprise Mode

In enterprise mode, Project Professional uses the Enterprise Global Template and
Enterprise Resource Pool. Users typically cannot be created as-needed by the project
manager. Project managers will be required to use Enterprise Calendars, as defined in the
Enterprise Global Template. In general, enterprise mode is used for organizations that
want to manage their projects together as a collection. Several Project Web Access features
are only available when Project Server is run in enterprise mode. Project Server in
enterprise mode is designed to provide users in your organization better ways to:
• Experience a common approach to project management by using consistent,
standardized data maintained in the Project Server database.
• Provide a way for your organization to standardize your project management approach
against a common set of rules, reports, and standards using Resource Breakdown
Structure (RBS), the Enterprise Resource Pool, Enterprise Global Template, and a
number of other settings that are maintained in Project Web Access (and discussed in
this chapter).
Enterprise features include (but are not limited to) the following:
• Enterprise Resource Pool Project has always provided for a local resource pool to
be used for assigning resources to tasks in projects. The Enterprise Resource Pool is
stored in the Project Server database and can be accessed by users of Project
Professional when assigning resources to enterprise projects if they have been granted
the Assign Resources category permission and the Assign Resource to Project
Team global permission. Using the Enterprise Resource Pool can make it easier to
manage resource allocation and usage and improve overall performance in a large
organization by providing a centralized pool of resources from which all projects (and
project managers) can draw.
• Enterprise Global Template The Enterprise Global Template ensures that all
projects published to the Project Server database use a consistent set of fields and
(therefore) generate a consistent set of data for enterprise project reporting. Project
Server allows Project Professional users the ability to open, edit, and save the
Enterprise Global Template; any user granted the Save Enterprise Global permission
will be able to perform these actions. The Enterprise Global Template is loaded into
memory every time Project Professional is started (requires the Read Enterprise
Global permission).
• Portfolio Analyzer Portfolio Analyzer allows project managers, resource managers,
and executives to use powerful online analytical processing (OLAP) tools to view and
evaluate how enterprise projects and enterprise resources are performing across the
organization. OLAP cube generation creates the Portfolio Analyzer fact and dimension
tables based on existing data for all projects published to the Project Server database
from Project Professional.
• Portfolio Modeler Portfolio Modeler allows resource managers to plan project

resource allocation by comparing generic skill requirements to actual resources before
beginning work on a project. Managers can also use Portfolio Modeler to project how
adjusting resource allocations on a particular project might affect its completion rate.
Portfolio Modeler can help project managers quickly identify staffing problems across
projects in an organization and then plan how staffing changes could affect schedules,
costs, and workloads. Model results can be saved as reports, which can then be used
with the Project Professional Resource Substitution Wizard to apply the model to
actual enterprise project plans.
• Enterprise templates Users with the Save Project Templates permission can store
project plan templates in the database. Project Professional users can view templates
saved to the Project Server database, and can then create new projects based on the
templates. Assigning generic resources to tasks in project templates can provide project
managers with an easy way to identify required skills when staffing a project and later
use the Resource Substitution Wizard to swap generic resources for actual resources
before beginning the project.
• Resource Center The Resource Center allows users with the View Resource Center
permission to view detailed resource assignment data. The Resource Center displays
properties of resources, showing predefined groups and filters. Users can also access
resource assignment and availability charts.
Running Project Server in Non-Enterprise Mode

In non-enterprise mode, Project Professional users have more flexibility in terms of
calendars and the creation of users. This mode is useful for an organization that wants to
provide a central server for a number of independent project teams.
When running Project Server in non-enterprise mode, you will be unable to perform the
actions associated with the following tasks when using Project Professional:
• Connect to Project Server from Project Professional and open the Enterprise Global
Template or Enterprise Resource Pool.
• Use the following commands on the Collaborate menu: Resource Center, Portfolio
Analyzer, and Portfolio Modeler.
• Select the following commands on the Tools menu: Build Team from Enterprise
and Substitute Resources.
• Use the Tools, Customize menu to work with Enterprise Fields (you will be able to
access the Custom Fields dialog box, but will not be able to modify or save your
settings).
• Select the following commands on the Tools, Enterprise Options menu to work with
Enterprise Resource Pool and Enterprise Global Template data: Open Enterprise
Global, Open Enterprise Resource Pool, Import Project to Enterprise, Import

Resources to Enterprise, and Backup Enterprise Global.
When running Project Server in non-enterprise mode, you will be unable to perform the
following tasks when using Project Web Access:
• Select the following commands on the Projects menu: Check-in my projects,
Analyze projects in Portfolio Analyzer, Model projects with Portfolio Modeler, or
Manage Administrative Projects.
• Select the following commands on the Resources menu: View enterprise resources
in the Resource Center or Analyze resources in Portfolio Analyzer.
• Access the Manage enterprise features link in the Admin center under Actions; this
will prevent you from creating the OLAP cube, checking in enterprise projects and
enterprise resources, and managing versions.
• Select the Features link under Configuration options in the Server configuration link
in the Admin center under Actions, including the following options:
• Allow master projects to be saved to Microsoft Project Server
• Allow master projects to be published to Microsoft Project Server
• Allow projects to use local base calendars
• Enforce single currency as specified in the Enterprise Global Template
• Allow only enterprise projects to be published to this server
• Synchronize Active Directory with the Enterprise Resource Pool.
• Create Resource Center or Portfolio Analyzer views in Manage views.
Enabling Enterprise Features

You can decide whether to enable or disable enterprise features, both as a group or
individually. If a feature is enabled for the organization, individual users with the proper
permissions can use the feature. If a feature is disabled for the organization, no user,
regardless of permissions, can use the feature. Non-enterprise features simply represent the
standard set of features that is always available to users of Project Server unless the users
are specifically disabled or denied.
The Server configuration page in Project Web Access.

X To enable enterprise features in Project Server
1. In the Project Web Access Admin center, in the side pane under Actions, click Server
configuration.
2. In the side pane, under Configuration options, click Features.
3. Under Specify the mode used to run Project Server, select Enable enterprise
features.

X To enable non-enterprise features in Project Server
configuration.
3. Under Specify the mode used to run Project Server, select Enable only non-
enterprise features.
Using Master Projects with Project Server

Using master projects to provide rolled-up reports across multiple projects is valuable
when using Project Professional (or Microsoft Office Project Standard 2003) as a stand-
alone application, but does not work as well when all projects are integrated into a common
repository like the Project Server database.
Because of the way projects are stored in the Project Server database, the way projects are
added to the Project Center, displayed in the Project Center (both master projects and
regular projects are displayed in the same way), and the way that this affects project-to-
project interaction, double-counting of resource assignments will occur and (ultimately)
inaccurate Project Web Access views will be created if a master project is published to the
Project Server database. It is therefore recommended that master projects not be published
to the Project Server database if they have resource assignments in them.
Note Saving a master project to the Project Server database does not cause this behavior
because master projects that are just saved to the Project Server database will not be displayed in
the Project Center. Only projects that have been published to the Project Server database will be
available in the Project Center. For this reason, it is recommended that master projects not be
published to the Project Server database.
Project Server provides several useful alternatives to the traditional master project:
• Administrative projects These projects allow you to create projects that are used to
track non-working and non-project time in Project Professional and published to the
Project Server database.
• Enterprise Outline Codes and the Project Center Use these two features together
to provide your organization with a way to group related projects and then open them
together in Project Professional. Use Enterprise Outline Codes to enable a variety of
ways to group projects together and eliminate the need to save each unique grouping
of projects.
• Portfolio Analyzer Provides users with better reporting and data results across
projects than the traditional use of master projects can.
X To allow master projects to be saved to Project Server
configuration.
3. On the Server Configuration page, under Specify the mode used to run Project
Server, select the Enable enterprise features option.
4. Select Allow master projects to be saved to Microsoft Project Server.

X To allow master projects to be published to Project Server
configuration.
Note This feature can be enabled whether Project Server is in Enterprise Mode or Non-
Enterprise Mode.
4. Select Allow master projects to be published to Microsoft Project Server.
Note Publishing master projects to the Project Center in Project Web Access will cause
inaccuracies in reports contained in the Project Center. Allowing users to publish master
projects to the Project Server database is not recommended.
Using Administrative Projects

An Administrative project can be used to track non-project or non-working time outside of
projects that are used to track progress on assignments. For example, an Administrative
project could be created to track vacation time or sick time. Administrative projects can
only be created by users who have both the Save Project permission that allows them to
save projects to the Project Server database from Project Professional, and the Create
Administrative Projects permission that allows a user to select the Administrative
project option in the Save to Project Server dialog box during the initial save of a project
to the Project Server database.
X To create an Administrative project from Project Professional
1. Open Project Professional and connect to Project Server.
2. Create a project plan without tasks or resources.
3. On the File menu, click Save.
4. In the Save to Project Server dialog box, type the Name of the Administrative
project, and then select Administrative project.
5. Click Save.
Allowing Projects to Use Local Base Calendars

To indicate whether local base calendars can be created and used for projects in Project
Server, select the Allow projects to use local base calendars check box. This setting only
affects Project Professional users and projects published to Project Server from Project
Professional that contain local base calendars.
Setting this option enables users to create their own calendars and partially defeats the goal
of having a consistent set of calendars across all projects within your organization.
However, Enterprise Calendars can still be created along with local calendars without
totally compromising standardization. Usually, satisfying requests for additional Enterprise
Calendars is a manageable task even in the largest organizations, so leaving this option
disabled is the recommended setting for organizations that want to completely standardize
their project management.
X To allow projects to use local base calendars
configuration.
4. Select Allow projects to use local base calendars.
Enforcing a Single Currency

It is possible to allow each individual project in your organization to determine its own
currency setting. However, it may not be practical to do this because all resources in the
Enterprise Resource Pool can only have a single currency associated with them. Project
Server allows you to specify a single currency to be used in association with all projects in
your organization.
When resources and projects are saved to the server with currencies other than the
enforced currency, the user is prompted to change currency or to abort the save. Setting
this option is highly recommended. Allowing multiple currencies cannot extend to
resources in the Enterprise Resource Pool, as they are stored in a single project in the
Project Server database and must all share the same basic currency rate. Opening a project
set to a different currency than the currency set in the Enterprise Global Template will
result in the display of inaccurate resource costs in task views.
Enforcing a single currency involves checking out the Enterprise Global Template and
specifying a currency using Project Professional, and then enforcing that currency in
Project Web Access.
X To enforce a single currency in the Enterprise Global Template
configuration.
4. Select Enforce single currency as specified in the enterprise global template.
Allowing Only Enterprise Projects to Be Published to Project Server

An enterprise project is simply a project that, when saved or published to the Project
Server database, is validated against the settings defined in the Enterprise Global Template.
You can enforce whether users of Project Professional can publish enterprise projects only
(projects validated against the Enterprise Global Template), or any project to the Project
Server database.
X To only allow enterprise projects to be published to Project Server
configuration.
4. Select Allow only enterprise projects to be published to this server.
Synchronizing the Enterprise Resource Pool with Active

Directory
You can also synchronize the Enterprise Resource Pool in Project Server with a group in
Active Directory. This will enable new additions in the Active Directory group to be added
to the Enterprise Resource Pool during the next synchronization. When a resource exists in
Active Directory that does not also exist in the Enterprise Resource Pool in Project Server,
it will be added to the Enterprise Resource Pool.
Note For more information about clearing the Active Directory globally-unique identifier (GUID), see
the topic Clearing the Active Directory Globally-Unique Identifier in Chapter 2, Managing Users and
Specifying Active Directory synchronization settings for the Enterprise Resource

Pool.
If a user exists in both Active Directory and the Enterprise Resource Pool, the Active
Directory connector for Project Server compares the user’s metadata based on the user’s
GUID. Whenever there is a match, the Active Directory data will be written to the
Enterprise Resource Pool entry for that user. If the Active Directory connector for Project
Server finds a user in Active Directory who is absent from the Enterprise Resource Pool, it
will add the user and apply any security group memberships. If a user with an AD GUID is
found in the Enterprise Resource Pool that is not also in Active Directory, the user account
will be deactivated in the Project Server database.
Note For more information about what happens when a user is deactivated in the Project Server
database, see the topic Deactivating or Reactivating a User in Chapter 2, Managing Users and
Before synchronizing the Enterprise Resource Pool with Active Directory:

• Check in all resources that are part of the Enterprise Resource Pool.
• If you are using the Update Now option, the Project Server administrator must also
log on to the server running Project Server using a Microsoft Windows® user account
that also has permission to read from Active Directory.
• Be sure your organization is committed to using Active Directory for Enterprise
Resource Pool synchronization.
If you begin this process, you should be prepared to minimize the creation of
Windows user accounts directly in Project Server for resources who also need to be
part of the Enterprise Resource Pool. Consider only synchronizing resources who
belong to the Team Members and Team Leads security categories with the Enterprise
Resource Pool. If you do need to add a resource, use Project Professional to insert a
new resource from Active Directory directly into the Enterprise Resource Pool.
X To synchronize the Enterprise Resource Pool with Active Directory
configuration.
3. On the Server Configuration page, under Specify the mode used to run Microsoft
Project Server, select Enable enterprise features.
4. In the Active Directory Group to Synchronize text box, type the alias, user name, or
display name of the Active Directory group you want to synchronize to the Project
Server Enterprise Resource Pool.
5. You can set a schedule for regular updates or you can synchronize immediately:
• To update on a regular basis, select Update every and then select the number of
days, weeks, or months you want the update frequency to occur. In the Start
update on calendar list, select the date to begin updates and then select the time
of day to run the updates.
• To update immediately, select Update only when specified, and then click the
Update Now button.
Note A user can only select Update Now when he or she is logged on locally to the
Project Server computer and has permission to read from Active Directory.

Troubleshooting Enterprise Resource Pool synchronization with Active Directory
• If you receive a partial error, check the Windows Server Event Viewer application log
for Project Server events to help isolate and determine the cause of the error. Some
causes for partial errors when synchronizing the Enterprise Resource Pool include:
• Resetting Internet Information Services (IIS).
• Checking out the Enterprise Resource Pool during synchronization.
• You cannot synchronize the Project Server Enterprise Resource Pool with an Active
Directory security group that is non-trusted, including an Active Directory security
group that lies within your organization’s extranet.
• Internet Information Services (IIS) should not be reset while synchronization is in
progress. This will stop the Project Server Scheduled Process Service immediately
without any error handling. The Project Server database will still show the processes as
running and the user interface will be disabled. You will need to restore the
MSP_WEB_ADMIN_AD.WADMIN_AD_ERESPOOL_UPDATE to 0 (from 1) in
the Project Server database, and then re-synchronize the Enterprise Resource Pool.
• Because Active Directory synchronization is most often a timed event, sometimes you
may need to add resources to the Enterprise Resource Pool before the next timed
synchronization will occur. In this case, check out the Enterprise Resource Pool in
Project Professional. On the Insert menu, point to New Resource From, and then
select Active Directory. This will add the resource to the Enterprise Resource Pool
and is otherwise the exact same process used by the Active Directory synchronization
process with the Enterprise Resource Pool.
• Enhanced security on Windows Server 2003 may need to be disabled so that the
account used to synchronize has access to read the AD group information.
• Clearing the AD GUID will prevent a resource from getting deactivated during
synchronization.
• If a resource name contains a list separator in Active Directory, this list separator will
be modified by Project Server when the resource is added to the Enterprise Resource
Pool during Active Directory synchronization. Semi-colon (;) list separators will be
replaced by a comma (,); all other list separators will be replaced by a semi-colon.
Selecting the Features Available to Users in Project Web Access

You can completely enable or disable the Project Server, Project Web Access, and Project
Professional features at the site level. Most features should be allowed at all times; however,
there may be some features to which you do not want any user to have access. Use the
Deny option carefully, as this will affect every single user on Project Server. For example, if
you disable the Manage Users and Groups command, then no user will be able to add,
modify, or delete users using the Manage Users and Groups page in the Admin area of
Project Web Access. If this is allowed, then only users or members of groups with
permission to access this page will be able to do so. In addition, features are allowed and
denied on this page based on which mode (enterprise or non-enterprise) Project Server is
being run in.
X To specify the features available to users in Project Web Access

configuration.
3. On the Server Configuration page, Under Specify the mode used to run Microsoft
Project Server, select Enable enterprise features.
4. Under Select the features that you want to make available to users in Project
Web Access, specify the features available in Project Web Access.
To allow or deny a feature, select the command, and then click Allow or Deny.
• If you deny a feature on this page, users in your organization, regardless of
whether they have permission specified as a user, group, or category, will not be
able to use this feature.
• If you allow a feature on this page, a user, group, or category will still require
permission to access this feature, either through a security group to which they
belong or by a security category to which they have been assigned.
• If a feature is neither allowed nor denied, the menu item associated with the
feature will be removed from the Project Web Access user interface.
Specifying the Intranet or Extranet Addresses for Project Server

Project Server can be configured to support both intranet and extranet addresses. These
can be created during Project Server setup (recommended) but can also be entered or
updated in Project Web Access.
X To specify the intranet or extranet address for Project Server
configuration.

3. On the Server configuration page, under Enter the intranet and/or extranet addresses
of Project Server, type the intranet or extranet server addresses for the computer
running Project Server. This address will be displayed when using e-mail notifications
and reminders.
Menus
In Project Web Access, centers, such as Admin or Tasks, are listed in the top link bar.
When a user chooses a center from the link bar, a list of activities, such as Manage users
and groups or Manage security, appears in the side pane. When the user chooses an
activity, the page for that activity is displayed. Project Server allows administrators to add
top-level and side-pane links to the Project Web Access user interface. These custom
menus can then be linked to Web pages. It is also possible to reorder menu items in the
Project Web Access user interface.
The Menus page in Project Web Access.
Adding a Custom Top-Link or Side-Pane Menu

You can add a custom center to Project Web Access. To do so, first add the center name as
a top-level menu. Then add activities to the center as submenus; you can specify a custom
Uniform Resource Locator (URL) for each submenu. You can also add submenus to
existing top-level menus.
Note A top-level menu will not be visible until after a side pane menu has been created for it. Both
top-level menus and side pane menus will not be available until you log off Project Web Access and
then log back on.
You can order top-level menus by typing a number in the Order box. Top-level menus and
activities will be listed in sequential order based on the order number, left-to-right for top-
level menus, top-to-bottom for activities. If you give two top-level menus or activities the
same number, they will be displayed based on their original placement in the Project Web
Access user interface.
X To add a new top-link menu
configuration.
2. In the side pane, under Configuration options, click Menus.

3. On the Menus page, click Add Custom Menu.
4. In the Add Custom Menu dialog box, select Add a top level menu.
• In the Menu Name box, type the name as you want it to appear in the top-link
bar.
• In the Menu ToolTip box, type the descriptive text that you want to appear when
a user rests his or her pointer over the center name in the link bar.
5. Click OK. By default, the new center is displayed as the last top-link menu listed in the
link bar.
6. Click Save Changes. You must log off, and then log back on to Project Web Access
before the changes will take effect. In addition, a top-menu will not be available until
one or more submenus are associated with it.
X To add a submenu
configuration.
3. On the Menus page, select a custom center, and then click Add Custom Menu.
4. In the Add Custom Menu dialog box, select Add a submenu.

• In the Submenu Name box, type the name as you want it to appear in the link
bar.
• In the Submenu ToolTip box, type the descriptive text that you want to appear
when a user rests his or her pointer on the center name in the link bar.
• In the Submenu URL box, enter the URL for the page used to complete this
activity. This URL must be fully-qualified.
5. Click OK.
6. Repeat steps 3 and 4 in this procedure for each sidebar activity you want to add.
7. Click Apply Menu Changes to see the changes on this page. This button displays the
changes but does not apply the changes to Project Web Access.
8. Click Save Changes to apply your changes to Project Web Access. You must log off,
and then log back on to Project Web Access before the changes will take effect.
Modifying a Top-Link or Side-Pane Menu

You can modify both Project Web Access default menus and custom menus, with the
exception of the URL associated with default Project Web Access menus.
X To modify a menu
configuration.
3. On the Menus page, make any necessary changes. Top-level navigation links appear in
bold. The custom name appears in the link bar, or if no custom name is defined, the
center name appears in the link bar.
• To move an activity to a different center, in the Menu column, select the name of
the center to which you want the activity moved.
• To change the order of centers in the link bar or the order of activities within a
center, type new numbers in the Order column. Activities are grouped from top to
bottom, and centers are grouped from left to right, lowest number at the top or
left, in the order you put them in.
• To assign a new name to a center or activity, type the name in the Custom Name
column.
• To bring up a different page for a default activity, or to change the page brought
up by a custom activity, type the URL in the Custom URL field. Custom activities
require a URL.
Note You cannot change the URL of default Project Web Access top-level menus.
• To create or change a ToolTip for any item, type ToolTip text in the Custom
ToolTip column.
4. Click Apply Menu Changes to see the changes on this page. This button displays the
changes, but does not apply them to Project Web Access.
5. To apply the changes, click Save Changes. You will need to log off and then log on
again in order to see the changes in Project Web Access.
Deleting a Top-Link or Side-Pane Menu

You can delete any unused custom top-link or side pane menu. You cannot delete Project
Web Access default top-link or side pane menus.
X To delete a custom menu
configuration.
3. On the Menus page, in the Name column, click the center or activity you want to
delete, and then click Delete Custom Menu. You must log off, and then log back on
to Project Web Access before the changes will take effect.
Note You cannot delete the default Project Web Access menus.
6
Managing Windows SharePoint
Services
Microsoft® Windows® SharePoint™ Services adds Web publishing and project
collaboration features to Microsoft Office Project Server 2003 that can improve
communication and increase idea-sharing among users who are assigned tasks in projects.
Microsoft Office Project Web Access 2003 includes links to locations for storing
documents, tracking issues, and discussing potential risks related to projects. The Project
Server administrator can use the Manage Windows SharePoint Services link in the
Admin Center to maintain this data. New Web sites can be provisioned to store project
data, existing Web sites can be modified and deleted, and Project Server users can be kept
synchronized with the Windows SharePoint Services sites related to the projects they are
working on.
In addition, a Project Server administrator can link directly to the Project Workspace Site
Settings and Windows SharePoint Services Central Administration pages on the
server running Windows SharePoint Services from the Manage Windows SharePoint
Services pages in Project Web Access.
Windows SharePoint Services Collaboration Features

Windows SharePoint Services can improve project collaboration. Every project plan
published to the Project Server database can be associated with a site located on a server
running Windows SharePoint Services that can contain multiple document libraries and a
single list of issues and risks. In addition to tracking documents, issues, and risks at project
and task levels, issues and risks can be associated with each other. The Documents, Issues,
and Risks features are available to users of both Project Web Access and Project
Professional.
Collaborating with Documents

Document management using Windows SharePoint Services is integrated into Project
Server with the Documents top-level link in Project Web Access and the Documents
command on the Collaborate menu of Project Professional or by directly navigating to the
Project Workspace in Windows SharePoint Services. Document libraries can be created for
each project published to the Project Server database. Use documents to capture non-
structured, project-related information that would not otherwise be available in a typical
project plan.
The Documents center in Project Web Access.

Document management features include:
• Associating project-related documents with tasks, issues, and risks.
• Using multiple document libraries and hierarchical folders within a project workspace.
• Checking in, checking out, and versioning documents.
• Saving documents directly from other Microsoft Office applications.
• Receiving e-mail notifications when a document has been modified.
• Performing full-text search on documents; use SharePoint Portal Server to improve the
full-text search capability.
• Graphical indicators for documents that can be associated with tasks, projects, and
resource assignments.
Tracking Issues
Issues tracking can be an integral part of project management. Issues are best used to
capture work items that are not easily identified in assignments or tasks within projects.
Team members can use the Issues top-level link in Project Web Access and the Issues
command on the Collaborate menu in Project Professional to submit issues about project
details that can then be used by project managers, resource managers, and team leads to
determine whether the issue will have an effect on the project and to then identify
strategies to deal with the issue before it becomes a major problem.
The Issues center in Project Web Access.

Issues tracking features include:
• Customizing forms used to track issues for a project.
• Linking issues to multiple tasks in a project, and issues with documents, risks, and
other issues.
• Viewing issue histories.
• Searching issues.
• Receiving alerts about issues status.
• Viewing graphical reports on issues.
• Editing in a datasheet view, including exporting to Microsoft Office Excel 2003 and
Microsoft Office Access 2003.
• Graphical indicators for issues that can be associated with tasks, projects, and resource
assignments.
Identifying Risks
Risks are events or conditions that can affect the outcome of a project; in many ways,
managing risks proactively is critical to the success of managing projects. Risk management
involves proactively identifying and tracking events and conditions that have the potential
to affect future planning for a project. Identifying risks is not the same thing as tracking
issues because risks deal with an event or condition in terms of how it can affect the
outcome of a project, whereas issue tracking is about dealing with the actual effects on the
outcome of a project. Risks can exist in the present time and can have up to one hundred
percent probability that they will occur. Risks can also exist in the far future and have up to
one hundred percent probability that they will eventually be a factor in a project’s life cycle.
Using Windows SharePoint Services, risk management is now fully integrated into the
overall project life cycle in Project Server. Users can now use the Risks top-level link in
Project Web Access and the Risks command on the Collaborate menu in Project
Professional (or link to the Project Workspace in Windows SharePoint Services directly) to
create and track risks for each project published to the Project Server database.
Note Risk management in Project Server 2003 does not provide cross-project risk tracking and
reporting or sophisticated risk management, such as Monte Carlo analysis.
The Risks center in Project Web Access.

Risks can be created by users of Project Professional and Project Web Access. The Risks
management feature allows project team members to identify risks that could affect the
outcome of a project in a number of ways and route risks to other team members for their
input or resolution. The default support for risks includes the following:
• Status Indicates whether the risk is active, closed, or postponed.
• Probability A percentage-based indicator ranging from 0-100 percent.
• Impact Identifies the significance of the risk to affect the outcome of a project.
• Exposure A calculation of probability times impact, adding an additional measuring
tool for risk management.
• Cost The cost of the risk on the project, in monetary terms, should the risk actually
affect the outcome of a project.
• Cost Exposure A calculation of cost times probability that can be used to predict the
cost of the risk before it actually affects the outcome of a project.
• Description Various text fields that can be used to provide descriptions of a risk,
mitigation and contingency plans, and descriptions for risk triggers.
• Mitigation Plan Analyze risks and determine action items that will help mitigate risks.
• Contingency Plan Plan for dealing with risks before they affect your projects.
• Trigger Events that cause a risk to actually affect the outcome of a project, including
dates, exposure, or incomplete tasks. You can also enter a description for a trigger.
Risk tracking allows project managers to record, escalate, share, update, and analyze
project-related risks from within Project Professional and Project Web Access among their
team members and for their projects. A section titled Risks on the Project Web Access
home page indicates the number of risks currently assigned to the logged-in user.
In Project Server, risks are:
• Easy to create, update, and track.
• Easy to customize.
• Able to be assigned per project.
• Well integrated into the project life cycle.
• Part of the Windows SharePoint Services e-mail reminders and notification service.
Users can use the Risks top-level link in Project Web Access and the Risks command on
the Collaborate menu in Project Professional or directly in the Project Workspace to:
• Submit and update risks.
• Associate a risk to other risks (create dependencies). Tasks can be the cause of this risk,
part of the mitigation plan, part of the contingency plan, or the trigger for the risk.
• Associate a risk to documents.
• Associate a risk to issues.
• Associate graphical indicators for risks with tasks, projects, and resource assignments.
Using the Project Workspace

The Project Workspace is a feature of Windows SharePoint Services that holds documents,
issues, and risks for a given project. Users can access the Project Workspace directly to
view documents, issues, and risks. In addition, all of the collaboration features built-in to
Windows SharePoint Services will be available, including team events, discussions, and
surveys. A user can navigate to the project Workspace by going to the Project Center in
Project Web Access, selecting a project, and then clicking Go to selected project
workspace. The Project Workspace is also available from the Documents, Issues, and
Risks areas in Project Web Access.
The Windows SharePoint Services Project Workspace.

Collaboration-focused users of Project Web Access (team leads and team members, for
example) can also access project data using Project Server Web Parts found in the Project
Workspace. The Project Server Web Parts include:
• Project Center
• Project Report
• Project Timesheet
• Project Manager Updates (for timesheet approvals)
• Project Portfolio Analyzer
• Project Resource Assignments
Managing Windows SharePoint Services

There are a number of tasks a Project Web Access administrator can perform that affect
the overall connectivity and performance of a Windows SharePoint Services server that has
been configured to support the Documents, Issues, and Risks features of Project Server.
Some of these tasks should only be performed on an as-needed basis, like specifying the
servers running Windows SharePoint Services to which Project Server will be connected.
Some of these tasks may require a daily check, like synchronizing users in Project Server
with users in Windows SharePoint Services.
In addition, there are a number of ways you can customize Windows SharePoint Services
to better meet the needs of your organization, ranging from customizing documents, issues,
or risk tracking forms, to standardizing issue and risk management across your
organization, to creating your own custom solutions for your organization.
Connecting to Windows SharePoint Services

Use the Connect to SharePoint Server page to specify the information required to
connect Project Sever to a Web server running Windows SharePoint Services. Project
Server requires that the root path for a server running Windows SharePoint Services exists
when Project Server connects to the server running Windows SharePoint Services. The
URL specified for the server running Windows SharePoint Services must always point to a
top-level site at the root of the virtual server. If this top-level site at the root of the server
running Windows SharePoint Services does not exist, or if a redirect is in place, the
connection will fail. For example, if the Windows SharePoint Services URL is
http://MyServer:80/projects, the connection will only work if this URL is also a top-level
site.
The Connect to SharePoint server page in Project Web Access.

X To connect to a server running Windows SharePoint Services
Manage Windows SharePoint Services.
2. In the side pane, under Options, click Connect to SharePoint server.
3. On the Connect to SharePoint server page, under Enter information on the web
server running Windows SharePoint Services, in the SharePoint Central
Administration URL box, type the Uniform Resource Locator (URL) for the
SharePoint Central Administration page.
4. In the Create a site under this SharePoint URL box, type the SharePoint Managed
Path URL for the server running Windows SharePoint Services that will host the site
collections for projects. A SharePoint Managed Path is simply the URL for the server
running Windows SharePoint Services with /sites appended to it. For example,
http://serverName:80/sites.
5. (Optional) Type the extranet address for the server running Windows SharePoint
Services in the SharePoint Extranet Address box. This URL is also a SharePoint
Managed Path URL. When you enter the Windows SharePoint Services extranet
address, you must also ensure that an extranet address is entered for the computer
running Project Server as well. The extranet address for Project Server can be specified
on the Server configuration page in Project Web Access by a Project Server
administrator.
6. Perform the following validation steps before saving your changes:

• Step One Verify that the SharePoint Central Administration URL is valid. Click
the Test URL hyperlink to the right of the SharePoint Central Administration
URL box to navigate to the page. You should be able to view the page content or
receive a logon prompt. To view the page content, the current logon account
administrator must have administrative access to the server running Windows
SharePoint Services.
• Step Two Verify that the Windows account (domain\user) that was used to
create the Project Server Windows SharePoint Services Admin COM+ application
has SharePoint administrative account permissions. Log on to the server running
Windows SharePoint Services as domain\user name (specified in your local user
interface) and browse to the SharePoint Central Administration page in
Administrative Tools on the Start menu. Note that Project Server remotely
administers the Web server running Windows SharePoint Services using this
domain name. To change this account information, you must once again run the
PSComPlus.exe tool that is provided by Project Server and then reset the account.
• Step Three Verify that the Public Documents site is valid. Click the Public
Documents site URL to navigate to the page. You should be able to view the page
content or receive a logon prompt. To view the page content, the current logon
account administrator must have at least read-only access to the site. The Public
Documents site is automatically created when you run the SharePoint
Configuration Wizard during Project Server setup.
Note You can only connect to a server running Windows SharePoint Services if the
language pack and the project template are identical to the language used by Project
Server. In addition, the language used in Internet Explorer must match the languages of
both Project Server and Windows SharePoint Services. For example, if Project Server is
deployed using German as the base language, then the server running Windows SharePoint
Services and Internet Explorer must also use German.
Site Provisioning Settings

Project Web Access Documents, Risks, and Issues are stored on a server running Windows
SharePoint Services. Windows SharePoint Services is installed on a server during setup of
Project Server. Each project will have its own site collection located on a server running
Windows SharePoint Services; you can create sites manually or have Project Server do it
automatically when a project is published to the Project Server database from Project
Professional. On the Windows SharePoint Services team Web site provisioning
settings page, you can specify the language and template settings for your project site
collections, specify whether Project Server creates site collections automatically, and specify
whether Project Server users are added automatically to the site collections.
The settings on this page will be applied to all future Windows SharePoint Services site
collections that are created through Project Web Access. If you want to create settings for a
specific Windows SharePoint Services site collection, you must do this on the Manage
Site Collection Owners page in Windows SharePoint Services administration.
Note For more information about managing site collection owners for specific Windows SharePoint
Services sites, see the topic Central Administration (Security Configuration section) in Chapter 6,
Managing Windows SharePoint Services of the Microsoft Office Project Server 2003
The Windows SharePoint Services team Web site provisioning settings page in
Project Web Access.
X To automatically have Project Server create Windows SharePoint Services sites

2. In the side pane, under Options, click Site provisioning settings.
3. On the Windows SharePoint Services team Web site provisioning settings page,
under Windows SharePoint Services Central Administrator Site, click URL to
verify the settings on the server running Windows SharePoint Services.
This command opens a new browser window that displays the Windows SharePoint
Services Central Administration page. To access this page, you must have
Administrator privileges on the server running Windows SharePoint Services. When
you have verified the settings, close the secondary browser window.
Note For more information about Central Administration, see the topic Central
Administration in Chapter 6, Managing Windows SharePoint Services of the Microsoft Office
4. On the Windows SharePoint Services Team Web Site Provisioning Settings page,
under Specify root Web site settings, verify the information for the following
options: Site template language, Site template, Site Owner, Site owner e-mail
address, Site secondary owner, and Site secondary owner e-mail address:
5. Under Settings for Web site creation, indicate whether you want to have Project
Server create Web sites for newly-published projects at the time the project is
published or if you want the Project Server administrator to create the sites manually
after the project has been published to the Project Server database.
• If you choose the option Automatically create a team Web site for the project
when a project is published to Project Server, a Windows SharePoint Services
site collection will be created when a project is published to the Project Server
database from Project Professional. This is the easiest way to create Windows
SharePoint Services site collections for use with Project and is generally
recommended.
However, this option is not recommended if either of the following conditions

apply: if your organization plans to allow project managers to delete projects from
the Open from Project Server dialog box in Project Professional (Windows
SharePoint Services sites associated with a project deleted in this manner will not
be deleted) or if your organization plans to provide multiple versions of the Project
Workspace template based on the type of project plan published to the Project
Server database.
• If you choose Manually create a team Web site for each project in Project
Server, a Windows SharePoint Services site will not be provisioned when a project
is published to the Project Server database. There are two methods available to the
Project Server administrator for manually creating a Windows SharePoint Services
site: Create Site and Edit Site Address. Both of these options can be found on
the Manage Windows SharePoint Services sites page in Project Web Access.
Note For more information about the Create Site and Edit Site Address options for
manually creating a Windows SharePoint Services site for a project in the Project
Server database, see the topic Managing SharePoint Sites in Chapter 6, Managing
Windows SharePoint Services of the Microsoft Office Project Server 2003
6. Under Grant user access to the project team Web sites, set the permissions for
how users will be granted permissions to sites and the public Web site:
• Select the Automatically add Project Web Access users to the project team
Web site check box if you want to allow user to be automatically added to a
project Web site. When automatic site provisioning is enabled, Project Server will
add users to the custom site collections. When Project Server creates a site
collection, four custom site groups are created as follows:
Web Administrators (Microsoft Office Project Server) site group has permissions
based on the default Windows SharePoint Services Administrator site group.
Project Managers (Microsoft Office Project Server) site group has permissions
based on the default Windows SharePoint Services Web Designer site group.
Project managers who publish projects or otherwise are granted the Save Project
permission will be automatically added to this cross-site group.
Team Members (Microsoft Office Project Server) site group has permissions based
on the default Windows SharePoint Services Contributor site group, with the
exception being that the ability to delete Issues and Risks is denied by default.
Team members assigned tasks in projects published to the Project Server database
will automatically be assigned to this cross-site group.
Readers (Microsoft Office Project Server) site group has permissions based on the
default Windows SharePoint Services Reader site group. Other Project Server
users with the View Project Documents, Issues, and Risks permission will be
added to this cross-site group.
• Select the Automatically add a new Project Web Access user into a cross-site
group called Project Manager check box if you want to allow users to be
automatically added to the public Web site.
Note If you clear either of these check boxes, users are not automatically added to
the respective Web sites. To add or update users, click the Synchronize button on the
Manage Windows SharePoint Services sites page in Project Web Access.
Managing SharePoint Sites

The Manage Windows SharePoint Services sites page in Project Web Access can be
used to view all of the project site collections that have been created on a server running
Windows SharePoint Services.
The Manage Windows SharePoint Services sites page in Project Web Access.
Creating, Editing, and Deleting Windows SharePoint Services Sites

If a project does not have a path name specified in the Site address box, a Windows
SharePoint Services site does not exist for that project. You can create and delete Windows
SharePoint Services sites, as well as update or remove the Windows SharePoint Services
URLs associated with Project Server sites.
If you have chosen not to create Windows SharePoint Services sites automatically when
projects are published to the Project Server database, then you can use the Create Site and
Edit Site Address options on the Manage Windows SharePoint Services sites page in
Project Web Access to manually create a new site or to associate an existing Windows
SharePoint Services site with a project plan.
The difference between Create Site and Edit Site Address is as follows:
• Create Site creates a Windows SharePoint Services site and associates it with the
selected project in the Project Server database. This is the same process that occurs
when you choose to automatically create Windows SharePoint Services sites when
projects are published to the database.
• Edit Site Address allows the Project Server administrator to specify the URL for the
Windows SharePoint Services site. This requires that a Windows SharePoint Services
site be created in advance. This option allows your organization more flexibility and
control over when (and for which projects) Windows SharePoint Services sites are
created, but (depending on the number of projects that will require a Windows
SharePoint Services site) may also be the most time consuming option.
X To create a Windows SharePoint Services site for a Project
2. In the side pane, under Options, click Manage SharePoint sites.
3. On the Manage Windows SharePoint Services Sites page, select a project in the
Project name column, and then click Create Site.
A new site for the project will be created. This may take a few minutes. When finished,
the path name for the new Web site appears below the list. All projects that have a
Windows SharePoint Services site will have the site address listed in the Site Address
field in the same row as the project plan that it is associated with.
X To edit a Web site address on a server running Windows SharePoint Services
3. On the Manage Windows SharePoint Services Sites page, select a project in the
Project name column, and then click Edit Site Address.
4. In the Edit Site Address dialog box:

• Select Enter new SharePoint site URL to update the Windows SharePoint
Services URL for the Project Server site. If you choose to update the link, be sure
to test the URL using the Test URL link.
• Select Remove SharePoint site URL to clear the Windows SharePoint Services
URL for the Project Server site.
5. Click OK.
X To delete a site
3. On the Manage Windows SharePoint Services Sites page, select the site you want
to delete, and then click Delete Site.
4. Click Yes in the alert dialog box to delete the site, or click No to cancel. Deleting a site
will also permanently remove all Documents, Issues, and Risks associated with the
project you are deleting, including any links the documents, issues, or risks had to
project tasks.
Synchronizing Users, Permissions, and Other Information

You can manually synchronize users and other Project Server-related information for each
project published to the Project Server database. During synchronization, Project Server
updates the following properties for each site:
• Project ID
• Project Server intranet URL
• Project Server extranet URL
More importantly, you should synchronize Windows SharePoint Services and Project
Server whenever there are changes to Project Server user permissions that affect how users
are added to the Windows SharePoint Services custom site groups. You should manually
synchronize Project Server and Windows SharePoint Services when Project Server users
who belong to the following Windows SharePoint Services security groups have been
modified:
• Web Administrators (Microsoft Office Project Server)
• Project Managers (Microsoft Office Project Server)

• Team Members (Microsoft Office Project Server)
• Readers (Microsoft Office Project Server)
Synchronization of Project Server resources in Windows SharePoint Services is a one-way
process and is determined by Project Server. Every time Project Server and Windows
SharePoint Services are synchronized, all valid Project Server users (with Windows
authenticated user accounts) will be added to the appropriate groups in Windows
SharePoint Services. If resources were removed in Windows SharePoint Services, but they
are still valid Project Server users, then they will be re-added to the list of users in Windows
Project Server automatically synchronizes with Windows SharePoint Services after the
following user actions:
• A user is deactivated or reactivated by the Project Server administrator or Active
Directory synchronization.
• The Project Server intranet or extranet URL is updated and saved on the Server
Configuration page in Project Web Access.
• The settings are updated on the Connect to SharePoint Portal Site page in Project
Web Access.
X To synchronize users, permissions, and other Project Server-related information
3. On the Manage Windows SharePoint Services Sites page, select the row you want
to update, and then click Synchronize to synchronize Project Server and Windows
SharePoint Services users.
4. Click Yes in the alert dialog box to continue synchronizing Project Server and
Windows SharePoint Services, or click No to cancel.
Going to Windows SharePoint Services Site Administration

In addition to administering settings, sites, and users in Project Web Access, the
administrator is responsible for keeping Project Server and Windows SharePoint Services
synchronized and up-and-running so that users will be able to link between Project Server
and Windows SharePoint Services data and effectively collaborate on projects using the
Documents, Issues, and Risks feature of Project Server.
The Project Server administrator may also need to access administrative tasks on the server
running Windows SharePoint Services. A link to the Project Workspace Site Settings
page is provided in Project Web Access. Use the Go to Site Administration link to go
directly to the Project Server relevant pages in Windows SharePoint Services.
Note For more information about the Project Workspace Site Settings page, see the topic Project
Workspace Site Settings in Chapter 6, Managing Windows SharePoint Services of the Microsoft
Office Project Server 2003 Administrator’s Guide.
X To link to the Project Workspace Site Settings pages from Project Web Access
3. On the Manage Windows SharePoint Services sites page, select a project from the
table for which you want to change the site settings, and then click Go to site
administration.
This will open the Project Workspace Site Settings page in a new browser window.
Note If you have applied Project Server 2003 Multilingual User Interface Packs (MUI
Packs), when you click Go to Site Administration, the Windows SharePoint Services site will
be shown in the same language as Project Web Access even if the actual site should be
shown in a different language. For example, if Project Web Access is currently set to display
in German and the Windows SharePoint Services site is configured to display in Swedish,
when you click Go to Site Administration the Windows SharePoint Services site will display
in German, not Swedish. To display Windows SharePoint Services sites in the correct
language, you should click Manage SharePoint sites, then navigate to the Windows
SharePoint Services site using the link that can be found under the Site Address column.
From the Project Workspace Site Settings page you can:

• Manage users.
• Manage sites and workspaces.
• Configure Site and Workspace Creation.
• Go to Site Administration (this link opens the Project Workspace Top-level Site
Administration page).
• Change site title and description.
• Apply theme to site.
• Modify site content.
• Customize home page.
• Update my information.
• View my alerts on this site.
• View information about site users.
Synchronizing Administrator Accounts

When you modify a user (Windows accounts only; Windows SharePoint Services requires
Windows authentication) in Project Server by granting (or removing) the Manage
Windows SharePoint Services permission to a user, he or she is not automatically added
to (or removed from) all project sites created on the specified server running Windows
A user with Manage Windows SharePoint Services permission in Project Server does
not automatically have access to the project sites created on the server running Windows
SharePoint Services. In addition to granting users the Manage Windows SharePoint
Services permission, you must also synchronize Project Server with Windows SharePoint
Services by clicking the Synchronize Administrators button in the Manage Windows
SharePoint Services area of Project Web Access.
When you click this button, each Project Server Windows account user with Manage
Windows SharePoint Services permission is added to the Web Administrators (Project
Server) group on all project sites created on the server running Windows SharePoint
Services.
The Synchronize administrator accounts page in Project Web Access.

X To synchronize Project Server and Windows SharePoint Services administrator accounts
2. Under Options, click Synchronize administrator accounts.
3. On the Synchronize administrator accounts page, click Synchronize
Administrators.
Note If there are no synchronized users and/or all administrators are synchronized, then
an alert will appear. Click OK. If the synchronization process has been run previously, a
timestamp will be shown on the page, for example: 09/25/2003 11:21 A.M.
Connecting to SharePoint Portal Server

You can connect Project Server to a Windows SharePoint Services-compatible portal site
running Microsoft SharePoint Portal Server. This feature takes advantage of the integration
between Windows SharePoint Services and SharePoint Portal Server. Once the connection
to SharePoint Portal Server is specified and saved, each Windows SharePoint Services site
collection created by Project Server is automatically aware of the server running SharePoint
Portal Server. Users will be able to search documents, issues, and risks, add sites in
SharePoint Portal Server that can be used to personalize, or promote a document in a

document library onto your organization’s portal site.
The Connect to SharePoint Portal Site page in Project Web Access.

X To connect Project Server to SharePoint Portal Server
2. Under Options, click Connect to SharePoint Portal Server.
3. On the Connect to SharePoint Portal Site page, under Portal Configuration, select
Connect to portal site.
4. In the Portal Web Address box, type the Web address for the portal site to which you
want to connect.
5. In the Portal Name box, type a name for the portal.

Project Workspace Site Settings

After Project Server has been connected with a server running Windows SharePoint
Services, Project Web Access and Project Professional users will be able to collaborate by
associating documents, issues, and risks with their projects, in addition to using any other
features of Windows SharePoint Services that your organization decides to include.
Note If you apply a Microsoft Windows SharePoint Services <Lang> Template Pack that enables
the Project Workspace to be available in the non-default language for the server running Windows
SharePoint Services, you will need to restart COM+ on the server running Windows SharePoint
Services.
Users can access the Project Workspace and collaborate by using Project Web Access or
directly navigating to the Project Workspace for his or her project. A Project Workspace is
created for each project using the Project Workspace site template. This template is
custom-designed for use by Project Server and includes the following differences from the
standard Project Workspace template:
• Documents and Issues are customized exclusively for Project Server.
• Risks are an entirely new list type that only work with Project Server.
• Contains six Project Server Web Parts.
• Does not include the Tasks list.
The Project Workspace site template is only available when you use the Windows
SharePoint Services Configuration Wizard (WSSWIZ.EXE) to configure Windows
SharePoint Services for use with Project Server.
This custom template defines the basic Documents, Issues, and Risks pages that Project
Server, Project Web Access, and Project Professional users experience while working with
Project-related data saved on a server running Windows SharePoint Services. Documents
and Issues, when used with Project Server, are not the same default Documents and Issues
that are available with Windows SharePoint Services.
Everything in the Project Workspace is unique to Project Server and can only be accessed
by authorized Project Server users or a Windows SharePoint Services administrator.
The Project Workspace Site Settings page in Windows SharePoint Services.

The Project Workspace Site Settings page has three major areas:
• Administration Use Manage Users, Manage Sites and Workspaces, Configure
Site and Workspace Creation, and Go to Site Administration to add or remove
users, add or remove sites, or navigate to other administrative features.
• Customization Use Change Site Title and Description, Apply Theme to Site,
Modify Site Content, and Customize Home Page to change the presentation of the
Windows SharePoint Services sites.
• Manage My Information Use Update My Information, My Alerts on This Site,
and View Information About Site Users to update personal information and to
manage the list of documents or other items in this site for which you receive alerts.
Note Some of these areas are not critical to maintaining a reliable interaction between Project
Server and Windows SharePoint Services. Others, where noted, are tasks that should be done from
within Project Server to ensure proper synchronization of data.
Administration
The Administration page lets you manage users, sites, and workspaces; configure sites and
workspaces; and go to the Site Administration page. The following sub-features are all
optional and can only be used within Windows SharePoint Services:
• (Optional) Manage Users The Manage Users page lists all of the users who have
been added to the Project Workspace during synchronization from Project Server. You
can use the Windows SharePoint Services default site groups to grant additional users
permission to access documents, issues, and risks. You should not modify the
memberships in any of the four custom site groups that are created by Project Server.
Project Server removes all members and replaces them during synchronization.
• (Optional) Manage Sites and Workspaces This page shows all of the Project
Server-related sites that can have been created under the Project Workspace. There is
no integration between Project Server and sub-workspaces by default. You can use
sub-workspaces, but they will not be accessible by users of Project Web Access.
• (Optional) Configure Site and Workspace Creation This page enables workspace
creation for individual site groups. The custom site groups related to Project Server will
be listed on this page. Only the Web Administrators and Project Managers groups have
workspaces created by default.
• (Optional) Go to Site Administration Opens the Project Workspace Top-Level
Site Administration page. Use the links on this page to perform administrative tasks,
such as changing permissions, selecting regional settings, viewing usage statistics, and
managing sites.
Note For more information about the Project Workspace Top-Level Site Administration page
see the topic Top-Level Site Administration in Chapter 6, Managing Windows SharePoint
Services of the Microsoft Office Project Server 2003 Administrator’s Guide.
Customization
The Customization page lets you modify default settings like the Site Settings page name,
color schemes, add custom site content, and make changes to the Project Workspace home
page. The following sub-features are all optional and can only be used within Windows
SharePoint Services:
• (Optional) Change Site Title and Description You can change the Site Settings
page from Project Workspace to any custom name.
• (Not Recommended) Apply Theme to Site You can apply custom themes to
Windows SharePoint Services. It should be noted that Project Web Access is designed
to share the same user interface (UI) styles as the No Theme (Default) theme in
Windows SharePoint Services. If you change the theme for a project-related subsite or
for Windows SharePoint Services in general, you may notice variances in the Project
Web Access UI when working with data stored on the server running Windows
Only Windows SharePoint users belonging to the Web Designer or Administrator site
groups will be able to apply themes to Project-related Web sites.
Note For more information about applying custom themes to Windows SharePoint
Services, see the topics About Themes and Apply or Remove a Theme in Microsoft Windows
SharePoint Services 2.0 Help.
• (Optional) Modify Site Content You can create new content and customize existing
content in the Project Workspace:
• Custom Content Add custom content repositories to the Project Workspace,
including Document Libraries (documents and forms), Picture Libraries, Lists
(links, announcements, contacts, and events), Custom Lists (custom lists, custom
lists in datasheet views, and imported spreadsheets), Discussion Boards, Surveys,
and Web Pages (basic, Web Parts, and sites and workspaces).
• Announcements Use announcements to post list message on the Project

Workspace home page.
• Contacts Use contacts to keep track of resource-related information that needs to
be available to all users of the Project Workspace.
• Events Use events to track upcoming meetings, deadlines, or other important
events related to projects.
• General Discussion Use to create newsgroup-style discussions about projects.
• Issues and Risks Users should not create issues or risks lists on this page. Project
Server is not able to integrate with issues or risks lists created in Windows
• Links Add links to the Project Workspace that can help project managers,
resource managers, and team members track, manage, and complete projects.
• Shared Documents Store documents related to projects in a document library.
This is the same location that is linked to from Project Web Access when you click
Documents.
• (Optional) Customize Home Page You can use the Project Workspace as a single
point of reference for all project managers, resource managers, and team members to
track project-related information about status, deadlines, events, issues, links, and
more. The Project Workspace home page can be customized to add nearly any type of
content, including using the six Web Parts available that allow a user to add Project
Server data to the Project Workspace.
Manage My Information
(Optional) The Manage My Information section in Windows SharePoint Services does
not synchronize with Project Server. The following sub-features are optional, and can only
be used within Windows SharePoint Services:
• Update My Information Edit user information for the currently-logged on user and
link to a list of all Project Server users in Windows SharePoint Services. These updates
will not be updated on Project Server.
• My Alerts on This Site Manage the list of Windows SharePoint Services libraries,
files, lists, and items for which you can receive alerts. Create, modify, and delete alerts
from this page. Alerts can be created for the following:
• All document libraries on the site (including Shared Documents)
• Announcements
• Contacts
• Events
• Links
• Issues
• Risks
• General Discussion
• View Information About Site Users View a list of all Project Server users who have
been added to Windows SharePoint Services.
Top-Level Site Administration

The Top-Level Site Administration page in Windows SharePoint Services can be
accessed from the Go to Site Administration link on the Project Workspace Site
Settings page. It has four major areas:
• Users and Permissions Allows you to manage users and site groups, configure
anonymous access, and manage cross-site groups.
• Management and Statistics Allows you to view how the site is used, manage sites
and workspaces, review discussions and alerts, and delete sites.
• Site Collection Galleries Allows you to manage Web Parts, list templates, and site
templates available to this site and all sites underneath it.
• Site Collection Administration Allows you to manage the site collection. All
changes to these pages will affect the MS_ProjectServer_PublicDocuments site and all
subsites and workspaces underneath it.
Users and Permissions

The Users and Permissions section might be the most important section of the whole
Windows SharePoint Services administration area.
• (Optional) Manage Users and Manage Cross-Site Groups Project Server
automatically adds users to four custom site groups in Windows SharePoint Services.
Adding users and cross-site groups to project-related sites in Windows SharePoint
Services is done by adding each user’s Windows user account to the Windows
SharePoint cross-site group. These updates will not be updated on Project Server.
Note For more information about managing users and cross-site groups in Windows
SharePoint Services, see the topic Managing Users and Cross-Site Groups in the Microsoft
Windows SharePoint Services 2.0 Administrator’s Guide.
• (Not Recommended) Manage Anonymous Access Anonymous access can allow

Project Server users to browse Windows SharePoint Services sites without
authenticating. Anonymous access grants access to the IUSR_[computer name] account in
Internet Information Services (IIS) by default.
For better security of Windows SharePoint Services (and project-related data stored on
a server running Windows SharePoint Services), it is recommended that your
organization not enable anonymous access.
• (Optional) Manage Access Requests Allows you to configure e-mail requests about
gaining access to specific Windows SharePoint Services sites.
Management and Statistics

The Management and Statistics section can help you keep track of how the Project
Workspace is being used, including managing sites, reviewing discussions, configuring
alerts, and deleting sites.
• (Optional) Save Site as Template Allows you to save Web sites to use later as site
templates.
The tasks that an organization will want to perform after configuring Windows
SharePoint Services for Project Server are:
• Customizing the issue and risk tracking forms
• Customizing the home page to be more specific to Project Server users.
• Standardizing all other aspects of customization so that new project sites in
Windows SharePoint Services all share the same characteristics.
• (Optional) View Site Usage Data You can track the number of Project Server users
that use the Documents, Issues, and Risks features of Windows SharePoint Services,
including the number of hits a particular set of project-related documents, issues, or
risks is getting and the number of unique users who are accessing those documents,
issues, and risks.
Tracking site usage can help you keep an eye on overall server storage capacity and
identify which content is being used more often, which content is not being used often
enough, and the level of activity a particular project-related subsite is getting. Usage
information is dependent on usage log data gathered from Windows SharePoint

Services subsites and is stored in the Windows SharePoint Services Content database.
Only users with administrative permissions to access Windows SharePoint Services will
be able to view site collection data.
• (Not Recommended) Manage Sites and Workspaces You should not create sub-
workspaces or delete project-related sites using this section. All modifications to the
Project Workspace should be managed from Project Web Access and synchronized to
Windows SharePoint Services. Sites and workspaces created directly in Windows
SharePoint Services will not work in Project Web Access.
• (Optional) Manage Web Discussions Project Server does not support Windows
SharePoint Services Web Discussions out of the box. You can configure support for
discussions using this page.
• (Optional) Manage User Alerts You can configure Windows SharePoint Services to
allow Project Server users to receive e-mail notifications when Documents, Issues, or
Risks are created, modified, or deleted for any of the projects they are currently
working on. The Windows SharePoint Services Alerts feature itself is a simple e-mail
notifications service.
Note For more information about configuring the Alerts feature on a server running
Windows SharePoint Services, see the topic Managing Alerts in the Microsoft Windows
SharePoint Services 2.0 Administrator’s Guide.
Users can specify the following:

• The types of events that will trigger an e-mail notification, for example when a
document is added, updated, or deleted in a document list.
• The frequency of an e-mail notification; for example a user could specify to receive
alerts right away, or on a daily or weekly basis.
The Project Server administrator can enable or disable the Alerts feature, as well as
specify how many alerts each user may have created.
Note If a user is removed from a Windows SharePoint Services site, site group, or cross-
site group, any e-mail notifications that have been created for that user must be deleted
manually. In addition, if you change the security settings for a particular area of Windows
SharePoint Services, any user that has previously set up e-mail notifications will continue to
receive them despite the change in the overall security settings. You should manually
delete e-mail notifications specified for users in this situation.
• (Optional) Change Regional Settings Windows SharePoint Services supports

locale, sort order, time zone, and time format regional settings. This can be done
through Windows SharePoint Services administration or by using the command line.
Note For more information about Windows SharePoint Services and regional settings, see
the topic Configuring Regional Settings in the Microsoft Windows SharePoint Services 2.0
• (Not Recommended) Delete This Site Allows you to delete the selected Web site.
This action should only be done using Project Web Access.
Site Collection Galleries

The Site Collection Galleries section can be used to manage the set of Web Parts, list
templates, and site templates available to all sites in the Project Workspace.
• (Optional) Manage Web Part Gallery Use this page to store and retrieve Web Parts
for use with Project Server. Web Parts in this gallery will be available to the Project
Workspace and all sites underneath it. Project Server or Windows SharePoint Services
administrators will be able to view all Project Server-related Web Parts from this page.
• (Optional) Manage List Template Gallery Use this page to make a custom
template available for use in list creation. Templates available in this gallery will be
available to all users and sites within the Project Workspace. Note that Project Server
Documents, Issues, and Risks use a custom template; if you create an Issues template
using this page, it will not work with the Issues feature in Project Web Access or
Project Professional.
• (Optional) Manage Site Template Gallery Use this page to make a template
available for use in site creation by adding it to the Project Workspace template gallery.
These templates have no integration with Project Web Access and would only be
available in the Project Workspace.
Site Collection Administration

The Site Collection Administration section is used to manage the site collection defined
by http://<server name:port>/sites and all sites and workspaces underneath it.
• (Optional) View Site Hierarchy Displays all of the sites and workspaces created in
the Project Workspace site collection.
• (Optional) View Site Collection Usage Summary Shows information about how
the site collection is being used, including storage, number of active users, and the
number of hits the site is experiencing.
• (Optional) View Storage Space Allocation Contains all of the folders that are
storing files, for example Shared Documents folders for each project subsite, Web Part
Gallery, List Template Gallery, or the Site Template Gallery.
• (Optional) View Site Collection User Information Allows you to view users in this
site collection. You can modify a user’s properties, prevent users from accessing sites
within the site collection, and display cross-site groups.
• (Not Recommended) Configure Connection to Portal Site Allows you to
configure a SharePoint Portal Server site. This is the same information entered in the
Connect to SharePoint Portal Server page in the Admin area of Project Web Access.
Performing this through Windows SharePoint Services will not trigger the
synchronization of site properties (these only occur when this is run through Project
Web Access).
Central Administration
You can manage virtual server configuration from Project Web Access if you are an
administrator on both Project Server and Windows SharePoint Services (you must have the
same account in both places).
X To access Windows SharePoint Services Central Administration from Project Web Access
2. Under Options, click Site provisioning settings. Then, on the Windows

SharePoint Services team Web site provisioning page, under Windows
SharePoint Services Central Administration Site, select the URL.
The Central Administration page has four major areas:
• Virtual Server Configuration Allows you to configure Windows SharePoint Services
on additional virtual servers, configure settings across all sites on a single virtual server,
or create a new top-level Web site.
• Security Configuration Allows you to update the security options that affect all
virtual servers, and to add, update, or change user information for a single top-level
Web site.
• Server Configuration Allows you to configure server connections for e-mail,
databases, and Web servers.
• Component Configuration Allows you to manage components that work across all
virtual servers, including search, usage analysis, and site quotas.
Virtual Server Configuration

The Virtual Server Configuration section is used to extend and upgrade virtual servers,
manage top-level sites, delete site collections, and configure virtual server settings.
• (Optional) Extend or Upgrade Virtual Server Before you can create Windows
SharePoint Services virtual sites for use with Project Server, you must create a virtual
server in Windows SharePoint Services to contain them in IIS 6.0 (on the server
running Windows SharePoint Services). When setting up virtual servers in a Windows
SharePoint Services server farm, update the URL namespace to remove the default
paths and add the wildcard path that allows you to use multiple host names (that is,
build multiple sites with the same IP address).
• (Optional) Create a Top-Level Web Site Allows you to perform administrative
tasks for a virtual server.
• (Not Recommended) Delete Site Collection Allows you to completely delete sites
collections and any related subsites on the virtual server. You should delete Project
Server-related site collections using Project Web Access only.
• (Optional) Configure Virtual Server Settings Allows you to perform administrative
tasks like automated Web site collection management, security settings, virtual server
management, virtual server lists, and component configuration.
Security Configuration
The Security Configuration section enables you to update security settings that affect all
virtual servers and manage user information at the single top-level Web site level.
• (Required) Set SharePoint Administration Group Allows you to specify a

Windows group account that has administrative access to a server running Windows
SharePoint Services. Project Server requires a member of this group account to
remotely administer Windows SharePoint Services for Project Server users.
• (Optional) Manage Site Collection Owners Allows you to view and change owner
and secondary owners for site collections. The settings on this page will be applied only
to the current Windows SharePoint Services site collection. If you want to apply
settings to all site collections created by Project Web Access, then you must use the
Windows SharePoint Services team Web site provisioning settings page in
Project Web Access.
Note For more information about applying site collection settings to all site collections
created by Project Web Access, see the topic Site Provisioning Settings in Chapter 6,
Managing Windows SharePoint Services of the Microsoft Office Project Server 2003
• (Optional) Manage Web Site Users Every Windows SharePoint Services Web site
has users, and part of the job of the Project Server administrator is to ensure that
Project Server users can access the Documents, Issues, and Risks sites from Project
Web Access. Users must have their Windows user accounts added to the site, and then
be assigned to a site group. Because Project Server does not update user information,
such as display names or e-mail addresses during synchronization, it is recommended
that a Project Server or Windows SharePoint Services administrator update this

information using Manage Web Site Users page.
Note Domain account mode allows you to add Project Server users with Windows user
accounts to Windows SharePoint Services Web sites using the user’s account name and e-
mail addresses.
The Manage Users page allows the Project Server administrator to view a list of users,
check the sites to which a user is assigned, add new users, delete users, and set up e-
mail notifications.
• (Optional) Manage Blocked File Types Allows you to specify the file types that
cannot be uploaded to a server running Windows SharePoint Services.
• (Optional) Configure Antivirus Settings Allows you to configure settings for virus
scanning.
Server Configuration
The Server Configuration section enables you to configure default e-mail server settings,
Web server lists, default content database and configuration database server settings, and
Central Administration configuration.
• (Optional) Configure Default E-mail Settings Windows SharePoint Services has
its own e-mail notifications engine that can be configured to send e-mail notifications
to Project Server users when Documents, Issues, or Risks are added, modified, or
deleted. Windows SharePoint Services e-mail notifications require an Simple Mail
Transfer Protocol (SMTP) server be configured in IIS to:
• Send outbound e-mail messages from the server running Windows SharePoint
Services.
• Relay e-mail messages.
• (Optional) Manage Web Server List Allows you to manage the Web servers that
belong to the server farm running Windows SharePoint Services.
• (Optional) Set Default Content Database Server Allows you to specify the default
content database server. This is used when extending new virtual servers.
• (Optional) Set Configuration Database Server Allows you to specify the default
configuration database server. This database stores settings for all SharePoint sites and
virtual servers.
• (Optional) Configure HTML Viewer Allows you to manage the HTML Viewer
service.
• (Optional) Configure Virtual Server for Central Administration Allows you to

manage the IIS application pool for the Windows SharePoint Services Central
Administration virtual server.
Component Configuration
The Component Configuration section allows you to manage components that work across
virtual servers including search, usage analysis, and setting site quotas.
• (Optional) Configure Full-Text Search You can configure Windows SharePoint
Services to support full-text searches of the Documents, Issues, and Risks libraries.
You must enable search before your site members can use it. If you want to enable
SharePoint Portal Server searching, you must be sure that SharePoint Portal Server is
available, and then configure Windows SharePoint Services to be indexed by the portal
site. If you want to enable SQL Server 2000 searching, you must install the full-text
searching feature for SQL Server 2000 and then enable search for Windows SharePoint
Services.
• (Optional) Configure Usage Analysis Processing Allows you to enable and
configure usage analysis processing.
• (Optional) Manage Quotas and Locks If you are using Windows SharePoint
Services over the Internet or have a very large intranet and need to keep a close eye on
the amount of traffic that passes through your network, you can specify site quotas and
site limits, or block access to project-related subsites altogether. Site quotas can have
two values:
• Warning When a site passes the Warning limit, e-mail notifications are sent to the
site owners (project managers and administrator) until the site quota has fallen
below the Warning level.
• Maximum When a site reaches the Maximum limit, another e-mail notification is
sent to the site owners, and no further content may be added to the site.
The site quotas feature is turned off by default in Windows SharePoint Services. It can
be turned on or off at any time by the Project Server administrator. You can specify
site quota values for each project-related subsite currently in use by Project Server
users.
Note For more information about specifying site quotas and site limits for Windows
SharePoint Services, see the topic Configuring Site Quotas and Locks in the Microsoft
Windows SharePoint Services 2.0 Administrator’s Guide.
You can use site locks to prevent project subsites from exceeding storage quota limits
or to block users from accessing project-related data, should the need to do so arise.
Sites are automatically blocked if they have reached their maximum site quota capacity.
There are two ways a Project Server subsite can be locked by Windows SharePoint
Services:
• Automatically Project Server users who attempt to access project data stored on
a Windows SharePoint Services site that has been locked automatically for
exceeding the Maximum capacity will receive a disk-full error when attempting to
add new content to the site.
• Manually If the site has been blocked manually, users who attempt to view the
site will receive an access-denied message or a disk-full error if they try to add new
content. If a project-related site has been locked manually, only a Project Server
administrator can unlock it.
• (Optional) Configure Data Retrieval Service Settings Allows you to manage
settings for data retrieval.
7
Managing Enterprise Features
Users with permission to access the Manage Enterprise Features page in the Admin area
of Microsoft® Office Project Web Access 2003 can work with the following features:
• Creating OLAP cubes and resource availability tables
• Checking in enterprise projects
• Checking in enterprise resources
• Managing versions
The Manage Enterprise Features page can be a useful page for more than just the
Microsoft Office Project Server 2003 administrator. By granting permission to access this
page to non-administrators in your organization, you can offload the day-to-day activities
available in this section to people who are closer to the actual work being done on projects.
For example, you may want members of your organization’s Project Management Office to
handle the administrative tasks of checking in enterprise projects and enterprise resources
that were left checked-out by a project manager who is on vacation. Or maybe it is better
for a small group of project managers to manage versions instead of a Project Server
administrator because the project managers are better able to understand which versions
are needed and what they are supposed to be used for.
Updating Resource Tables and OLAP Cubes

Project Server relies on Analysis Services to support the Portfolio Analyzer feature. All
project-related data is stored in the Project Server database. Analysis Services uses the
information in the Project Server database (Views tables) to create the online analytical
processing (OLAP) cube database on the Analysis Services server.
The database in Analysis Services contains three cubes: MSP_ASSN_FACT,

MSP_RES_AVAIL_FACT, and a linked cube MSP_PORTFOLIO_ANALYZER. The
MSP_ASSN_FACT and MSP_RES_AVAIL_FACT cubes are created in the Analysis
Services database when a user clicks the Update Now button on the Update resource
tables and OLAP cube page in Project Web Access.
The MSP_PORTFOLIO_ANALYZER table is a linked cube that connects the
MSP_ASSN_FACT and MSP_RES_AVAIL_FACT cubes together. It is the primary table
that is used when interacting with the Portfolio Analyzer.
The Update resource tables and OLAP cube page in Project Web Access.
View tables are based on a date range specified by the Project Server administrator in
Project Web Access. Since these tables only get data for a specific date range, they also
need to be updated regularly to get new data. The settings for the date range, as well as the
frequency of resource updates can be specified in Project Web Access.
Note For more information about extending the OLAP cube to include task information, see the
Microsoft Office Project Server 2003 Software Development Kit (SDK) on MSDN:
Once you have published a project to Project Server, you will be ready to build the OLAP
cube. Building an OLAP cube requires that you have set up Analysis Services and set the
permissions on Project Server components to access Analysis Services. Project Server does
not give any user permission to view the OLAP cube; users and groups must be granted
permission on each Analysis Services database. You will need to set security for the cube
on the database in Analysis Manager after it has been created.
Note Generating the OLAP cube uses a significant amount of resources on the server running
Analysis Services. These operations are server-intensive because large amounts of data are
gathered for reporting. It is recommended that these processes be run at a time when you expect
the activity on the Project Server computer to be low.
Before building the OLAP cube, and after Microsoft SQL Server™ 2000 Analysis Services
has been configured, you should verify that you have done the following:
• Created any projects that you want to use in Portfolio Analyzer.
• Published all projects that you want to view in Portfolio Analyzer to Project Server;
you must publish at least one project before you can create views using Portfolio
Analyzer.
• If you did not configure the server running Analysis Services during Project Server
installation, you will need to run the PSCOMPlus.exe COM+ tool.
In addition, the following tasks can affect the way that users interact with Portfolio
Analyzer. Before using Portfolio Analyzer, you should consider the following:
• Have permissions been set on the database in Analysis Services?
• Has your organization defined Enterprise Project Outline Codes and Enterprise
Resource Outline Codes?
• Are the values for lookup tables stored in the Enterprise Global Template?
• Have all required resources been added to the Enterprise Resource Pool?
• (When appropriate), have values been assigned to any of the Enterprise Outline
Codes?
• Have resources been assigned in the Enterprise Resource Pool to the correct Project
Server security categories your organization is using to allow access to Portfolio
Analyzer views? (If you import resources or synchronize the Enterprise Resource Pool
with Microsoft Active Directory®, all resources will be added to the Team Members
security category.)
X To check status of the most recent OLAP cube build
Manage enterprise features.
2. In the side pane, under Enterprise options, click Update resource tables and
OLAP cube.
3. On the Update Resource Tables and OLAP Cube page, under Current Cube
Status, the status of the most recent OLAP cube build is shown. For example, “The
cube process has been initiated [date, time]” or “The cube is currently being built” or
“The cube was successfully built at [date, time].”
Building the OLAP Cube and Updating Resource Availability

The OLAP cube must be built before you can use Portfolio Analyzer. You must publish a
project to the Project Server database before you can build the OLAP cube.
X To build an OLAP cube for use with Portfolio Analyzer
OLAP cube.
3. On the Update Resources Tables and OLAP Cube page, under Build the OLAP
cube, select Yes, I want to update resource availability information and build an
OLAP cube.
4. Under OLAP cube name and description, enter the name of the Analysis Server (or
the name of the server running Analysis Services), a name and description for the cube,
and the extranet address for the server running Analysis Services.
• The following characters cannot be used: / “ ; : < > | [ ] , . ‘ ? ~ ` ! $ % ^ & * ( ) -

+={}\
• Check with your Analysis Services or SQL Server 2000 administrator if you do not
know the name of the Analysis Server.
• Specify the extranet address of the Analysis Services server if Portfolio Analyzer
will be accessed from an extranet.
5. Under Date range, select the date range around which to build the OLAP cube.
Choose from three options:
• Use the earliest project start date and the latest project finish date
• Use the following date range at the time the cube is built, which allows you to
specify the number of days, weeks, or months before and after today’s date around
which you want to build the OLAP cube
• Use the fixed date range specified below, which allows you to define a specific
date range around which to build the OLAP cube
Note If the date range specified for building the resource availability tables is smaller
than the date range specified for building the OLAP cube, resource availability will be
calculated using the date range specified for building the OLAP cube. The span for
resource availability can be greater than the span for building the OLAP cube, but it
cannot be smaller.
6. Under Date range for resource availability, select a date range to check for resource
availability.
• If you select Use the following date range for retrieving resource availability
information, indicate the number of days, weeks, or months before and after
today’s date for which to verify resource availability.
• If you select Use the fixed date range specified below, type or select dates in
both the From and To boxes.
7. Indicate how often you would like to run OLAP cube updates.
You can set up the updates to be run on a predefined cycle or you can choose to run
them manually:
• If you select Update every, enter the number of days, weeks, or months in-
between updates, and then select the start date and time.
• If you select Update only when specified, you can click Update Now later
when you want to build an OLAP cube.
Updating Resource Availability

You can update resource availability by itself. This may need to be done more often than
building the OLAP cube; as-needed updates can be easily managed by a Project
Management Office.
X To build a resource availability OLAP cube
OLAP cube.
3. On the Update Resource Tables and OLAP Cube page, under Build the OLAP
cube, click No, I only want to update resource availability information.
4. Under Date range for resource availability, select the date range around which to
build the resource availability cube:
• To indicate a rolling date range, select Use the following date range for
retrieving resource availability information, and then select the number of
days, weeks, or months before and after today’s date around which you want to
build the resource cube.
• To indicate a fixed date range, select Use the fixed date range specified below,
and then type or select dates in both the From and To boxes.
5. Under Update frequency, indicate how often you would like to build the resource
availability cube:
• If you click Update every, enter the number of days, weeks, or months, and then
select the start date and time.
• If you click Update only when specified, click Update Now when you want to
build a resource cube.
Checking In Enterprise Projects

If a checked-out project needs to be checked in to Project Server for any reason (for
scheduled maintenance or a database server migration, for example), you can force a check-
in of the project. Forcing a check-in of an enterprise project will result in the loss of any
changes made to the project since the last save.
The Check in enterprise projects page in Project Web Access.

X To manually check in a checked-out project (as the Project Server administrator)
2. In the side pane, under Enterprise options, click Check-in enterprise projects.
Only users with the Check In My Projects global permission can access the Check in
enterprise projects link.
3. On the Check In Enterprise Projects page, select the project (or projects) that you
want to check in, and then click Check-In.
4. If you check in a project that is checked out, the user who has the project checked out
can only save the project to the database if the project is saved as a new project.
Note Update the list of projects by clicking the Refresh button.
Project Server administrators are the only users who can force a check-in of any project
plan saved to the Project Server database. However, any owner of a project plan can force
a check-in of the projects they manage using Check in my projects available in the
Project Center. You should make sure that all project managers in your organization
understand how to use this feature; it can save you from having to deal with multiple
requests from project managers to perform steps that they can easily perform themselves.
X To force a check-in of a project that you manage
1. In Project Web Access, click Projects.
2. In the side pane, under Actions click Check in my projects.
3. Select the name of the project you want to check in, and then click Check-in.
Note If you use this method of checking in a project while the project is open in Microsoft
Office Project Professional 2003, you will not be able to save the version of the file that is
open in Project Professional.
Checking In Enterprise Resources

If a user in the Enterprise Resource Pool is checked out and needs to be checked in for any
reason, you can force a check-in using the Check in my resources page in Project Web
Access. Forcing a check-in of an enterprise resource will result in the loss of any changes
made to the resource since the last save.
The Check in enterprise resources page in Project Web Access.

Note The Enterprise Resource Pool is stored as a project in the Project Server database. If, for
some reason, the entire Enterprise Resource Pool is left checked out and needs to be checked in,
use the Check in enterprise projects link to do this.
X To manually check in a checked-out enterprise resource

2. In the side pane, under Enterprise options, click Check-in enterprise resources.
3. On the Check In Enterprise Resources page, select the resource you want to check
in, and then click Check-In.
If you check in an enterprise resource that is checked out, the user who has the
enterprise resource checked out will not be able to save changes to the database.
Note You can update the list of resources by clicking the Refresh button.
Using Versions
All Project Professional projects must have a version type associated with them. The
default version for Project Server is always Published; this is the only version that can be
selected when a project plan is first saved to the Project Server database. A version is a
complete copy of a project plan saved to the Project Server database as both a project plan
file name and a version type. Versions can only exist for a project if there is already a
Published version in the Project Server database.
Note Versions can be available in Portfolio Analyzer, Project Center, and Project views in Project
Web Access and Project Professional. Depending on the number of versions your organization is
using, you should consider filtering out versions, especially when using the Portfolio Analyzer.
Versions are best used to capture snapshots of project data over time. Your organization
can use versions to help track variations of the Published project plan. For example, you
could create the following custom versions in your organization and use them to track a
project’s life cycle, and then create snapshots of project data around important milestones:
• Published Use this version to track all project data during the entire project life cycle.
This is the only type of project from which you can publish assignments. This is the
version that must be used for all types of project status. This version can never be
overwritten (otherwise assignment data would be lost).
• M0 or Plan Use the M0 version to save a project plan as it existed before work began
on the project, but after the project plan is complete and otherwise ready to begin.
• M1 or Work Use the M1 version to save a project plan as it existed when work was
completed at the planned or actual finish date. You can compare this version against
the M0 version to help determine whether the initial project plan was scoped out
realistically against the actual work on the project.
• M2 or Maintain Use the M2 version to track follow-up work after the primary work
phase has been completed. You can compare this version to the M1 and M0 versions
to help determine the amount of work that went unplanned or was required to take
place after the expected finish date for the project.
• M3 or Closed Use the M3 version to save a project plan as it existed when the project
was closed. You can compare this version to all previous versions for this project to
help determine the overall success of the project. This is the version that you may want
to run a post-mortem against.
Note Only the Published version is available for use with projects saved to the Project Server
database by default.
Versions are flexible; your organization can create custom versions that fit within the way
your organization approaches project management. Versions can also track resource
allocation at the time of the version save (select Yes from the Version archived drop-
down when creating versions in Project Web Access).
The Published version type:
• Cannot be renamed or deleted.
• Is used as a method of tracking assignment data; only the Published version can be
used to track assignment data.
• Must be the initial version of any project plan published to the Project Server database.
• Is the version of any project plan published to the Project Server database that should
be used for reporting and tracking actual work.
The Project Server administrator manages the list of valid versions that can be associated
with project plans when they are saved to the Project Server database. If you want to
provide other types for users in your organization, you will first need to define them.
The Versions page in Project Web Access.
When to Use Project Versions

There are many uses for versions, including:
• Defining project milestones.
• Making a full comparison between versions that includes added and deleted tasks and
assignments, constraints, and other changes not saved in baselines. Versions can be
used to compare the project at the start of the development with a copy taken at the
end of the project. Analyzing this type of data can help your organization understand
how project plans can change during the project life cycle.
• To assess project portfolios at planned time intervals, for example quarterly or yearly.
• To provide a method of releasing data in published project plans to users outside of
your project management organization.
• Performing trend analysis between snapshots of a project plan taken at regular
intervals. This can help your organization determine patterns of change and plan for
these changes. Only comparing between baselines may not show a significant variation
between versions, but comparing versions will better show the trends of a project.
• Providing a temporary storage location that can be used to track and analyze “what-if”
scenarios, or to separate published versions from working versions of projects.
• As a comparative alternative to baselines. Baselines are normally used as a starting

point for schedule or earned-value comparisons. Only certain field values are saved for
each baseline in a project and comparisons can be easily made at the task level with
baseline comparisons. Versions offer a higher-level method for comparing projects as
they progress.
• Comparing finished projects and in-progress projects against planned or proposed
projects. For example, creating a version called Planned and then later comparing the
Finished version against it to help determine the overall effectiveness of the planning
effort against the actual results.
• Tracking major updates to a project’s schedule or to capture the history of a project
before a significant reallocation of resources.
When to Use the Version Archived Option

The Version Archived option can be used to prevent updates of summary resource
assignments in a saved project version. Select Yes when you want to freeze the resource
assignment data in the project. Select No, then resource assignment data will be updated in
the custom version as the resource assignment data is updated in the Published version.
• If Version Archived is set to Yes, summary resource assignments will not be saved,
and all resources shown in the project will be shown as allocated at the time the
version was saved.
• If Version Archived is set to No, the summary resource assignments will be saved in
the version.
For example, if you save a project as an archived version (Version Archived is set to Yes),
then the project will show the resource assignments as they existed at the point the
resources were added to the project. The next time this project is opened, the project will
not show the current assignments for the resources. If you save the project as a non-
archived version (Version Archived is set to No), the summary resource assignments will
be updated every time the project is opened. So if the resources have been assigned more
work since the project was last opened, you would see these changes to a resource’s
availability in the project.
Saving a Version of a Project

When connected to Project Server from Project Professional, saving a project plan for the
first time prompts the user to enter a name for the project and to specify a version. The
project name and version are stored together in the Project Server database and are
separated by a PERIOD, for example ProjectOne.Published. This has two purposes: It
supports backward compatibility with earlier versions of Microsoft Office Project, and it
helps ensure that all project names saved to the Project Server database are unique.
Before a project can be saved as a version other than Published, there must be a Published
version of that project in the Project Server database. The first time you save a project to
Project Server, you must select Published as the version. If a Published version of a project
already exists, you will be allowed to save a project as a version by using any of the available
custom version types.
Adding a Custom Version

You can add custom versions to Project Server.
X To add a version
2. In the side pane, under Enterprise options, click Versions.
3. On the Versions page, click Add Version.
4. On the Add Versions page, in the Version box, type the new version name as you
want it to appear to project mangers in Project Professional.
• The following characters cannot be used: / “: < > | , . ‘ ? * #.
5. Use the Version Archived option to take snapshots of resource allocations in saved
project versions over time. Set Version Archived to Yes if you want to preserve
resource allocation within project versions.
6. In the Gantt Bar Name list, select the Gantt bar used to display the version.
Modifying a Custom Version

You can modify existing versions, except for the version name if a published project is
using that version name.
Note You cannot modify the default version named Published.
X To modify a version
3. On the Versions page, select the version you want to modify, and then click Modify
Version.
4. In Version Archived, select Yes if this version name will refer to archived versions of
projects. Select No if it will refer to un-archived versions.
• The following characters cannot be used: / “: < > | , . ‘ ? * #.
5. In the Gantt Bar Name list, select the Gantt bar used to display the version.
Deleting a Custom Version

You can delete custom version types from the Project Server database if no projects are
associated with them. You must first remove the associated projects from the Project
Server database before you can delete the version.
X To delete a version
3. On the Versions page, select the version you want to delete, and then click Delete
Version.
4. In the confirmation dialog box, click OK to delete the version, or click Cancel.
You cannot delete the Published version type, nor can you delete any other version
that has a project associated with it in the Project Server database.
8
Customizing Project Web Access
Microsoft® Office Project Server 2003 has many features that are available by default that
later can be customized to the needs of your organization. These features include:
• Customizing Timesheet settings, including defining managed timesheet periods.
• Customizing the appearance of Gantt Chart views and Grouping formats.
• Adding custom links and content windows to the Microsoft Office Project Web
Access 2003 home page.
• Defining the settings required to use the e-mail notifications and reminder service.
Timesheet Tracking Settings

You can specify a number of default tracking and timesheet settings for Project Server for
all users of Project Web Access and Microsoft Office Project Professional 2003, including:
• Identifying the methods (and enforcing the methods) that users have available to them
when reporting their time worked on project tasks using the Project Web Access
timesheet.
• Defining the time period for reporting that is available in the timesheet.
• Specifying how often resources can enter tracking information.
• Setting how early upcoming tasks appear in the timesheet.
Note Resources must have assignments that overlap with the current timesheet period, have an
assignment that is pending approval, or have an ongoing assignment in order for their assignments
to be available in the Timesheet view. If a resource’s timesheet is not available in the Timesheet
view, they will not be able to report hours worked or submit a timesheet, and will not count as an
un-submitted timesheet. Un-submitted timesheets only exist if a resource fails to enter actuals and
submit a timesheet that is available in the Timesheet view.
The Tracking Settings page in Project Web Access.

Project Server can also be configured to support managed reporting periods. Reporting
periods are simply a date range in which team members can report actuals in the timesheet
(an open period) or cannot report actuals in the timesheet (a closed period). Using open
and closed reporting periods could be important for limiting updates made to actuals
following the posting of entered actuals into a General Ledger system, for example.
Project Server can be configured to support:
• Reporting periods that are always open; actuals can be entered by team members or
project managers.
• Manually defined reporting periods that can be open or closed, and where actuals can
only be entered by team members or by users with permission to change timesheet
entries.
Note To use manually defined reporting periods, Project Server also requires that actuals be
entered as hours per day (the Hours of work done per day or per week option is selected on the
Tracking Settings page in Project Web Access) and that project managers use the hours per day
tracking mode for their projects.
Specifying the Default Tracking Settings for Project Plans

You can track progress in projects in three ways in Project Server: by percent complete, by
actual work, or by hours of work done.
Note If you plan on using the managed time periods (see below), you must choose Hours of work
done per day or per week as your enterprise project tracking setting.
X To specify the default tracking settings

Customize Project Web Access.
2. In the side pane, under Customization options, click Tracking settings.
3. On the Tracking settings page, under Specify the default method for reporting
progress on tasks, choose the default tracking method:
• To track progress based on a percentage of total work completed, click Percent of
work complete.
• To track projects based on how much work is completed compared to how much
work remains, click Actual work done and work remaining.
• To have resources periodically enter hours worked (daily or weekly), click Hours
of work done per day or per week. This option is required if you want to use the
timesheet lockdown feature.
Locking Down the Default Tracking Setting

After you have selected the default tracking setting for projects, you can decide to enforce
this tracking method for all projects saved to the Project Server database or to allow
individual project managers to change the default method at the project level.
Note If project managers are allowed to specify their own tracking methods, they can do so in
Project Professional by pointing to Tools, selecting Options, and then, in the Options dialog box,
choosing the Schedule tab and specifying their options under Scheduling options.
X To specify the default method for reporting progress on project tasks

3. On the Tracking settings page, under Lock down defaults, indicate whether project
managers will select their own tracking methods or will be required to use the default
tracking method as defined in the Enterprise Global Template.
Working with Managed Timesheet Periods

You can define specific timesheet reporting periods, or managed timesheet periods, in
Project Web Access. Managed timesheet periods define how resources report their time
against assignments in projects. You can specify that resources report their hours every day,
every week, or every defined time period. You can also specify the maximum number of
working hours a resource can enter during any given day.
Note When managed timesheet periods are enabled (the Managed Periods option is selected
under Time period settings on the Tracking settings page in Project Web Access), users of Microsoft
Project Professional 2002 will not be able to connect to the Project Server database.
Enabling and disabling managed timesheet periods is a simple procedure within the context
of Project Web Access. You should consider the effects of enabling and disabling managed
timesheet periods on your own organization’s business processing before making the
decision to do this, however. For example, when managed timesheet periods are disabled,
you can create assignments with any of the three available tracking methods. When
managed timesheet periods are on, you can only use the hours-worked-per-day method. So
if you take the time to convert all of your assignment tracking to hours-worked-per-day and
then enable managed timesheet periods, and you later disable managed timesheet periods,
you have effectively re-enabled the three available tracking methods instead of just the one.
If any of your project managers use the two non-hours-worked-per-day methods, before
you can re-enable managed timesheet periods, you will have to make this conversion again.
Working with managed timesheet periods in Project Web Access.

In addition to being able to define specific time periods, Project Server 2003 introduces the
concept of open and closed time periods. When you create the reporting periods, you must
specify each period as either Open or Closed. Resources may only report their time
worked in a managed timesheet period marked as Open. Once you have defined a
managed timesheet period and marked it as Closed, then Project Web Access resources
will not be able to enter or modify their time entries; only users with the Adjust Actuals
permission in Project Web Access will be able to access the Adjust actuals page in Project
Web Access and adjust timesheet actuals.
You can only used managed timesheet periods with projects that are tracked by Hours of
work done per day or per week. Entering actuals cannot be disabled in managed
timesheet periods for projects that are tracked in any other way (Percent of work
complete or Actual work done and work remaining). Actuals entered using these
tracking methods are distributed over a timephased period according to the usual
scheduling rules.
X To define a managed timesheet period
3. On the Tracking settings page, under Specify the default method for reporting
progress on tasks, select Hours of work done per day or per week.
4. Under Time Period Settings, select the day the week begins from the Week starts
on drop-down list, and then select Managed Periods.
5. Under Managed timesheet periods, select a time period adjacent to the time period
that you want to add, and then click Insert Before or Insert After.
6. For time period you are adding, click Start and Finish to specify the start and finish
dates, and then click Open to specify the status of the time period, either Open or
Closed.
• To delete a timesheet period, select the period you want to delete and click the
Delete button.
• To verify that the time periods are valid time periods based on the Standard
Enterprise Calendar as it is defined in the Enterprise Global Template, click the
Check button.
7. Indicate whether you would like resources to report hours worked on a daily basis,
weekly basis, or for the entire time period that defined in steps 5 and 6.
8. Type the maximum number of hours that a resource can enter per day for a single task.
Type 0 if you do not want to set a maximum number of hours per day.
Working with Non-Managed Timesheet Periods

You are not required to use managed timesheet periods in Project Server. The other option
is to use non-managed timesheet periods. You will not be able to define these time periods
as Open or Closed, but otherwise they behave much like managed timesheet periods.
Non-managed timesheet periods can be defined to span 1-4 weeks or months. You can
require resources to enter their time on a daily basis, by week, or by time period.
X To specify non-managed timesheet periods
3. On the Tracking settings page, under Time period settings, select the day the week
begins from the Week starts on drop-down list, and then select Non Managed
Periods.
4. For projects that require resources to specify hours worked during each time period,
you can specify the default time periods that are displayed in a resource’s timesheet.
Start by indicating the period that a timesheet should span, either Weekly or Monthly:
• If you select Weekly, then indicate the number of weeks the timesheet period will
span (1-4).
• If you select Monthly, indicate the number of timesheet periods per month (1-3)
and the range spanned for each reporting period.
5. Indicate whether you would like resources to report hours worked on a daily basis,
weekly basis, or for the entire time period defined in step 4.
6. Type the maximum number of hours that a resource can enter per day for a single task.
Type 0 if you do not want to set a maximum number of hours per day.
Moving to Managed Timesheet Periods from Non-Managed

Timesheet Periods
The ability to define managed timesheet periods is a new feature that is only available in
Project Server 2003.
Important You must follow one of the procedures described below for all existing projects that you
want to migrate to a managed timesheet environment or you will lose timesheet data that is already
present in the document during the migration.
If your organization is moving from Microsoft Project Server 2002 or any other non-
managed timesheet period scenario, there are some extra steps that you will need to take
while moving the project data in order to define managed timesheet periods for these
migrated projects.
There are three scenarios:
• Moving from Microsoft Project Server 2002 (all timesheet periods) This scenario
requires that the Microsoft Project Server 2002 database be upgraded to the Project
Server 2003 database format. After successfully upgrading the Project Server database,
open all of the upgraded projects in Project Professional 2003. Publish each project to
the Project Server 2003 database using Project Professional 2003. Point to
Collaborate, then Publish and select Republish Assignments. Be sure to select the
Overwrite actual work entered by resources option.
This process will move the data that was defined as Actual Work (the
MSP_ASSIGNMENTS.ASSN_ACT_WORK field in the Microsoft Project
Server 2002 database) and redefine it as Actual Work Protected (the
MSP_ASSIGNMENTS.ASSN_ACT_WORK_PROT field in the Project Server 2003
database). When the project plan is published to the Project Server database, the
corresponding fields in the MSP_WEB_WORK and MSP_WEB_ASSIGNMENTS

tables are updated.
• Moving a stand-alone project plan file (MPP) to Project Server (with managed
timesheet periods defined) This scenario requires that you save your project plans
to Project Server while using non-managed timesheet periods. It is recommended that
this be done before enabling managed timesheet periods. If this is not possible, then
you must ensure that existing projects are not published to the Project Server database
and that users do not enter timesheet data while Project Server is being run with non-
managed timesheet periods. To use non-managed timesheet periods, select Non
Managed Periods from the Tracking settings page in Project Web Access.
Open all of the projects in Project Professional 2003. Publish each project to the
Project Server 2003 database using Project Professional 2003. Point to Collaborate,
then Publish and select Republish Assignments. Be sure to select the Overwrite
actual work entered by resources option. Turn on managed timesheet periods.
Caution Users of Project Professional will be prompted to synchronize actuals when
opening, closing, or saving (and/or publishing) a project plan. Any project published after
managed timesheet periods are enabled will lose data if the publishing process is not
cancelled and redone when managed timesheet periods are turned off. If the project is
published, all data associated with Actual Work will be deleted.
• Moving from Project Server 2003 (non-managed to managed timesheet periods)

This scenario requires that you save your project plans to Project Server while using
non-managed timesheet periods. Open all of the projects in Project Professional 2003.
Publish each project to the Project Server 2003 database using Project
Professional 2003. Point to Collaborate, then Publish and select Republish
Assignments. Be sure to select the Overwrite actual work entered by resources
option. Turn on managed timesheet periods.
Caution Users of Project Professional will be prompted to synchronize actuals when
opening, closing, or saving (and/or publishing) a project plan. Any project published after
managed timesheet periods are enabled will lose data if the publishing process is not
cancelled and redone when managed timesheet periods are turned off. If the project is
published, all data associated with Actual Work will be deleted.
If a project is not updated using the methods described above, a project manager will be
alerted that the tracking method used in the project plan is not the same as the tracking
method required by Project Server, and that they will lose their data if they continue to save
the project plan to the Project Server database. Do not save or publish projects to the
Project Server database that have not been properly migrated to the managed timesheet
environment.
Define Current and Future Task Visibility

When resources view their lists of current tasks, they will be able to view every task to
which they are currently assigned and every task currently in progress, as well as tasks that
are scheduled to start within a specified number of days from the current date. For
example, if you select 20 days, then all resources would be able to see the tasks to which
they are currently assigned, plus any upcoming task within the next twenty working days.
X To set the number of days a resource will be able to view tasks in advance
3. On the Tracking Settings page, under Define current tasks, type the number of
days in advance of its start date that a task begins to appear in a resource’s list of
current tasks.
Gantt Chart Formats

You can customize the colors, patterns, shapes, and styles of the Gantt Charts available in
Project Web Access. The changes you make to each Gantt Chart will be available wherever
that Gantt Chart appears in Project Web Access. Project Web Access has 22 different
Gantt Chart formats available, seven of which are preconfigured for use in the Project
Center, Views, and Tasks areas in Project Web Access and Project Professional.
The Gantt Chart formats page in Project Web Access.

X To customize a Gantt Chart
2. In the side pane, under Customization options, click Gantt Chart formats.
3. On the Gantt Chart Formats page, under Specify the bar styles and timescale for
Gantt Charts, select the Gantt Chart you want to customize from the Gantt Chart
drop-down list.
4. Customize the Gantt bars as necessary. To change the middle bar shape, bar color, bar
pattern, and start and end shapes and colors, select the new style from the drop-down
list. To show or hide a bar when the Gantt Chart is displayed, select the bar, and then
select or clear the Display check box.

X To rename a Gantt Chart
2. In the side pane, under Customization options, click Gantt Chart formats.
3. On the Gantt Chart Formats page, under Specify the bar styles and timescale for
Gantt Charts, select the Gantt Chart that you want to customize from the Gantt
Chart list. Click Rename, type the new name, and then click the green check mark
button to save the new name.
Grouping Formats
You can customize the appearance of the standard Timesheet and Views color
representations that are used in Project Web Access. And you can create up to nine custom
grouping formats for use with other areas in Project Web Access. Customizing the Views
grouping format will apply the updates to all Project Center, Resource Center, Project, and
Assignment views.
The Grouping formats page in Project Web Access.

X To customize grouping formats
2. In the side pane, under Customization options, click Grouping formats.
3. On the Grouping Formats page, under Specify grouping formats, select the
grouping format you want to customize from the Grouping format list.
4. Customize the grouping format as desired. To change the cell color, cell pattern, font
color, or font style for a grouping format, first select the grouping format, and then
select the new style from the drop-down list.

X To rename a grouping format
2. In the side pane, under Customization options, click Grouping formats.
3. On the Grouping Formats page, under Specify grouping formats, select the
grouping format you want to rename from the Grouping format list. Click Rename,
type the new name, and then click the green check mark button to save the new name.
Home Page Formats

You can modify the contents of the Project Web Access home page by adding links to
external content or by adding content windows with which you can interact on the Project
Web Access home page itself.
The Home page format page in Project Web Access.
Links
You can add custom links to the Project Web Access home page. They will appear in a
special Links section at the bottom of all users’ home pages. You must specify the full path
for the link Uniform Resource Locators (URLs), including the http:// or file prefix.
X To add or modify links to the Project Web Access home page
2. In the side pane, under Customization options, click Home page format.
3. On the Home page format page, under Add Links, click Insert Row.
• In the Link Name column, type the name of the link as you want people to see it
on the Project Web Access home page.
• In the URL column, type the URL (including the http:// prefix).
4. Click the Up or Down buttons to change the order that content sections will appear

X To delete custom links on the Project Web Access home page
3. On the Home page format page, under Add Links, select the row containing the link
you want to delete, and then click Delete Row.
Content
Content will appear in a window placed on the Project Web Access home page. You can
specify the height (in pixels) for each content window. The full path for the URLs,
including the http:// or file prefix must also be provided.
X To add custom content to the Project Web Access home page
3. Under Add Content, click Insert Row.
• In the Section Name column, type the title for the content section.
• In the URL/Path column, type the complete URL or path name (including the
http:// or file prefix).
• In the Height column, type a height for the window (in pixels).
Note Use caution when adding content from an external Web site to your Project Web
Access home page. You should perform a thorough security check on all external content
that you want to add to the Project Web Access home page in order to help minimize
unnecessary security risks.
4. Click the Up or Down buttons to change the order that content sections will appear
X To delete custom content sections on the Project Web Access home page
3. On the Home page format page, under Add Content, select the row that contains
the content you want to delete, and then click Delete Row.
Keyboard Shortcuts for the Home Page Formats Page

Project Web Access can be accessed using keyboard shortcuts. Depending on the version
of Internet Explorer that you are using, when using the TAB keyboard shortcut to navigate
the Home page formats page, the cursor may get trapped in the grid control. The
following keyboard shortcuts can be used to work around this limitation.
X To navigate the Links section:
• Use ALT + . (PERIOD) to move to the first cell in the Add Links section.
• Use ALT + SHIFT + < (LEFT ANGLE BRACKET) to move just after the start of
the Add Links section.
• Use ALT + SHIFT + > (RIGHT ANGLE BRACKET) to move just before the start
of the Add Links section.
• Use ENTER to move out of the Add Links section.
• The TAB keyboard shortcut does not work for the Add Links section.
X To navigate the Content section:
• Use ALT + , (COMMA) to move to the first cell in the Add Content section.
• Use ALT + SHIFT + { (LEFT CURLY BRACE) to move just after the start of the
Add Content section.
• Use ALT + SHIFT + } (RIGHT CURLY BRACE) to move just before the start of
the Add Content section.
• Use ENTER to move out of the Add Content section.
Notifications and Reminders

Project Server generates e-mail notifications and reminders for each user whenever new,
overdue, rejected, or forthcoming events occur. Users can configure alerts for their
reminders from the Project Web Access home page.
Before e-mail notifications and reminders can be used by members of your organization,
the appropriate server and account information must be identified, either during Project
Server setup or later using Project Web Access. As the Project Web Access administrator,
you can:
• Configure a Simple Mail Transfer Protocol (SMTP) server to handle e-mail
notifications and reminders.
• Specify the default contents of e-mail notifications and reminders.

• Set the time that Project Server sends e-mail notifications and reminders.
The Notifications and Reminders page in Project Web Access allows the Project Server
administrator to maintain the default sender e-mail address and message information that is
automatically included with each e-mail notification or reminder sent by Project Server, as
well as specify the SMTP server and associated port number.
The Notifications and reminders page in Project Web Access.

This page also allows the Project Server administrator to set the frequency at which the
Project Server Views Notification Service scans the Project Server database to
determine who should receive e-mail reminders (this setting does not apply to e-mail
notifications). Depending on the volume of notification and reminder e-mails, you should
consider setting the Views Notification Service to run at a time where the overall load on
the server is low.
Note For more information about the Project Server Views Notification Services, see Appendix F:
Project Server Registry Settings, Services, and Application Folders in the Microsoft Office Project
X To set default e-mail notification and reminder settings

2. In the side pane, under Customization options, click Notifications and reminders.
3. On the Notifications and reminders page, under Set default sender e-mail
address and e-mail message, enter the default e-mail information.
• In the SMTP mail server box, type the name of your SMTP server. Verify the
port number in the Port box.
• (Optional) In the From address box, type the default e-mail address. This address
is the reply-to address for all notification and reminder e-mails.
Note If you enter a fictitious address in the From address box it will become an
unmonitored e-mail address.
• In the Company e-mail address box, type the host and domain portion of your
company’s default e-mail address.
The company e-mail address is appended to user e-mail addresses where a host
and domain are not specified. For example, for users at Microsoft, the address
microsoft.com would be appended to a user’s e-mail address:
someone@microsoft.com. Each user’s e-mail name is entered in the E-mail field
on the Add user page (click Manage users and groups, then choose Use
accounts, and then Add user). The part of the address entered here is appended
to the user’s e-mail name if no host and domain name is specified, creating a full e-
mail address for the user.
• In the Default e-mail message box, type the default message you want appended
to all notification e-mails. For example: This e-mail message may contain confidential
information and is intended only for the recipients named above. If you do not want a
message automatically appended to notification e-mails, leave the Default e-mail
message box blank.

X To schedule e-mail notifications and reminders

2. In the side pane, under Customization options, click Notifications and reminders.
3. On the Notifications and reminders page, under Schedule e-mail reminder
service, select the time of day you want Project Server to scan for and send e-mail
reminders to users about upcoming or overdue tasks and status reports.
4. Click Save Changes. A message is displayed if the e-mail processing engine is not set
up properly on the Project Server.
X To sign up for e-mail notifications and reminders
1. In Project Web Access, on the home page under Actions, choose from the two types
of e-mail notifications available:
• Click Alert me about my tasks and status reports to set up e-mail notifications
for when your tasks and status reports are updated.
• Click Alert me about my resources on tasks and status reports to set up e-mail
notifications for when you would like to be notified when your resource’s tasks
and status reports are updated.
9
Cleaning Up Project Server Data
Sometimes it may be necessary to create more space in the Microsoft® Office Project
Server 2003 database. This can be done by removing redundant or old information from
the database. The Clean up Project Server database page in Microsoft Office Project
Web Access 2003 allows the administrator to remove specific task assignments, task
updates, projects, to-do lists, resources, and status reports from the database on time- or
user-based criteria.
The Clean up Project Server database page in Project Web Access.

You can clean up data for all users or just the data associated with a particular user:
• To remove everything associated with a specific project, regardless of time or user,
select the Projects and To-do list items radio button and choose the appropriate
project.
• If a time criterion other than Ever sent is selected for Task, Resource task changes,
or Status Reports, two additional fields will display to specify the exact time period.
• Once the items are selected, click Delete.
Note In rare cases, when two projects are deleted at the same time, and one of the deletions fails,
you may need to complete the failed transaction by manually deleting the project from the
MSP_WEB_PROJECTS table in the Project Server database. This can only occur if two Project Server
administrators, using two different computers, run the delete process simultaneously on two
separate projects and one of the project deletions fails. Access to this page in Project Web Access
should be limited to only those users in your organization who are capable of dealing with this type
of scenario, should the need arise. You can use the Event Viewer on the server running Project
Server to obtain the ID for the project involved with the failed transaction.
What really happens when you delete a project using this page?
• Project Server calls the Project Data Service (PDS) method ProjectDelete and deletes
all associated project data.
• Project information in the MSP_ and MSP_WEB_ tables is deleted and will be non-
recoverable. (The same is true if you use the delete function in the Open from
Microsoft Office Project Server dialog box.)
• Project subwebs in Microsoft Windows® SharePoint™ Services are deleted only when
the user selects the Delete the SharePoint team Web site for the specified project
check box. The subweb will be removed entirely, and all of its contents will be deleted
and will be non-recoverable.
• All project-related records are also deleted, including tasks, assignments, and timesheet
data will be lost. Resources are only assigned to projects, so unless you also choose to
delete a resource, the resource will not be deleted or modified outside of its association
with the project you are deleting.
What really happens when you delete a resource using this page?
This process is not a complete removal of resource data from the Project Server database.
Completely removing resource data can have unintended long-term consequences with the
integrity of Project Server data, which is why resources are not completely removed from
the Project Server database. This process simply removes users from their current and
future assignments (replacing them with local resources) and removes them completely
from the Enterprise Resource Pool, plus any associations with the Enterprise Resource
Pool (for example, the Build Team feature in Project Professional or Project Web Access).
What other options do you have?
• There is no archiving option available for Project Server.
• You can delete individual projects directly from Microsoft Office Project
Professional 2003 in the Open from Microsoft Office Project Server dialog box.
• Use the PDS method ProjectDelete to delete projects directly in the database.
• If your organization wants to preserve the resource in the Project Server database in its
entirety, you should simply deactivate the user. Deactivated users can later be
reactivated without a loss of data.
Note For more information about deactivating Project Server users, see the topic
Deactivating or Reactivating a User in Chapter 2, Managing Users and Groups of the
X To delete task assignment data from the Project Server database

1. In the Project Web Access Admin center, in the side pane under Actions, click Clean
up Project Server database.
2. On the Clean up Project Server database page, under Specify items you want to
delete, select Tasks.
3. In the Delete list, select either All task assignments or Only completed task
assignments and then indicate the range of tasks that Project Server will delete:
• Ever sent.
• Older than Type a number in the text box and then select days, weeks, months,
or years from the drop-down list.
• Sent between Select a date from each of the calendar dialog boxes.
4. Under If necessary, specify the users whose items should be deleted, indicate
whether you want to delete the specified task data for all users or for just a specified
user.
5. Click Delete.
Note Items removed from the database using the Clean Up Project Server database page
are permanently removed from the Project Server database (MSP_WEB_ tables). However,
they are not removed from the project files that are the original source of the data.
X To delete resource task changes from the Project Server database

delete, select Resource task changes.
3. Indicate the range of resource task changes that Project Server will delete:
• Ever sent.
whether you want to delete the specified resource task change data for all users or for
just a specified user.
5. Click Delete.
X To delete status report data from the Project Server database
delete, select Status Reports.
3. Indicate the range of status reports that Project Server will delete:
• Ever sent.
whether you want to delete the specified status report data for all users or for just a
specified user.
5. Click Delete.
X To delete project and to-do list data from the Project Server database
delete, select Projects and To-do Lists.
3. Select a project from the list of available projects. Select Delete the SharePoint team
Web site for the specified project to delete all Windows SharePoint Services data
associated with the project.
4. Click Delete.
X To delete resources from the Project Server database
delete, select Resource.
3. Select a resource from the Delete the selected resource list.

4. Type a comment in the Deletion Comment text box.
5. Click Delete.
Using the example shown above, the enterprise resource Adam Barr has been removed
from the Project Server database with the following exceptions:
• A record of Adam Barr will remain in the MSP_WEB_RESOURCES table that will
contain his name and the comment entered in the Deletion Comment field appended
to it.
• Any project in which Adam Barr was assigned to a task will have the enterprise
resource assignment updated to contain a local resource instead of an enterprise
resource. The name of the local resource will remain Adam Barr, but will have the
comment entered in the Deletion Comment field appended to the name, for example
Adam Barr Deleted 8/1/2003.
• Any associated historical information, like timesheet entries (actuals), status reports,
etc., will remain in the database and the resource will be completely removed from the
Enterprise Resource Pool.
• Project assignments will retain all of the information that was previously assigned to
the enterprise resource (Adam Barr), but is now assigned to the local resource.
• The Project Server user account for the deleted resource will have the Account Status
updated to Inactive.
Deleting Projects Using the Open from Microsoft Office

Project Server Dialog Box
You can permanently delete projects that are stored in the Project Server database by using
the Open from Microsoft Office Project Server dialog box in Project Professional. You
can only delete projects that would otherwise normally be available by using the Open
from Microsoft Office Project Server dialog box.
Note Deleting projects using the Open from Microsoft Office Project Server dialog box does not
automatically delete an associated Windows SharePoint Services site. Your organization should
consider, when allowing users to delete their own projects, to also disable the automatic creation of
Windows SharePoint Services sites when projects are saved to the Project Server database.
Deleting projects using the Open from Microsoft Office Project Server dialog box.
Note A user requires the Delete Project category permission in Project Web Access before they
delete projects that have been saved to the Project Server database. They must also have the Open
Project category permission to view projects in the Open from Microsoft Office Project Server dialog
box.
X To delete projects using the Open dialog box in Project Professional

1. Open Project Professional and connect to Project Server.
2. On the File menu, select Open to open the Open from Microsoft Office Project
Server dialog box.
3. Select the project you want to delete, and then click the Delete button to the right of
the Group by drop-down list.
4. Confirm the deletion. This action is permanent; the project will no longer be available
on Project Sever.
Note You cannot delete the Published version of a project if there are versions of that
project currently saved in the Project Server database.
10
Working with Portfolio Analyzer
Portfolio Analyzer takes advantage of Microsoft Office Web Components, which is a
collection of Microsoft ActiveX® components. Project uses two Office Web Components
(PivotTable and Chart) to access OLAP cube data stored in the Analysis Services database
(an Analysis Services database is created for each OLAP cube created in Project Web
Access). Users can interact with this data in Project Web Access and Project Professional
using fully interactive PivotTable and PivotChart reports. Users can sort, filter, add, or
modify data, expand and collapse details, and save their results for future reference.
Note For more information about extending the OLAP cube, see the Microsoft Office Project
Server 2003 Software Development Kit (SDK) on MSDN:
Portfolio Analyzer views can be accessed from the following areas:

• In Project Web Access, click Projects in the top-level navigation, and then under
Actions, select Analyze projects in Portfolio Analyzer in the side pane, or click
Resources, and then under Actions, select Analyze resources in Portfolio Analyzer.
• In Project Professional, point to the Collaborate menu, and then select Portfolio
Analyzer.
Using Portfolio Analyzer from Project Professional 2003.
Configuring Portfolio Analyzer

There are a number of steps that you must complete in order to properly configure
Portfolio Analyzer for use in your organization. Portfolio Analyzer requires Analysis
Services, Service Pack 3, which is part of Microsoft SQL Server™ 2000. Analysis Services
also requires Decision Support Objects (DSO), running with the same service pack as
Analysis Services. If Analysis Services is not installed on the same computer as Project
Server 2003, then DSO must also be installed on the same computer as Project
Server 2003. Additionally, if the Project Server Views Processing service is offloaded, then
DSO must be installed on that server.
Creating and working with Portfolio Analyzer views is done using Project Web Access
(creating and working with) or Project Professional (working with only). There are three
requirements for creating and working with Portfolio Analyzer views:
• Users must have permission to access the pages in Project Web Access that allow
interaction with Portfolio Analyzer, and they must have permission to access the data
that will be part of the Portfolio Analyzer views.
• Office Web Components (OWC) 2003 is required for users to interact fully with
Portfolio Analyzer data. Users without OWC 2003 will not be able to create or modify
Portfolio Analyzer views.
• Users must have permission to view Portfolio Analyzer from the Project Center in
Project Web Access or Project Professional. Users can always view Portfolio Analyzer
data, but must have a fully-interactive version of OWC to create or modify Portfolio
Analyzer views. Fully-interactive versions of OWC are only available in Microsoft
Office 2003 and Project Professional 2003. OWC must be available on the computer
from which Portfolio Analyzer is being accessed. If the client computer does not have
OWC, Project Server 2003 will install a non-interactive version of OWC that will allow
users to view Portfolio Analyzer views, but it will not allow them to create or modify
them.
The following information is intended to help you understand the bigger picture around
using and configuring Portfolio Analyzer. You should refer to the more detailed sections
that the following information points to, as needed.
1. Install Analysis Services (with Service Pack 3). If Analysis Services is not on the same
computer as Project Server 2003, then Decision Support Objects (with Service Pack 3)
must be installed on the Project Server 2003 computer. Analysis Services can be
configured during Project Server Setup from the Enter Analysis Services
Connection Information page. This page allows you to specify the analysis server to
be used with Project Server in addition to the connection account information. If you
did not configure the server running Analysis Services during Project Server
installation, you will need to re-run the PSCOMPlus.exe COM+ tool to set the COM+
object that will use the Microsoft Windows account that has OLAP administrative
permissions.
Note For more information about configuring Analysis Services during Project Server setup,
see the topic Enter Analysis Services Connection Information in Chapter 7, Install Project
Server 2003 of the Microsoft Office Project Server 2003 Installation Guide.
After Analysis Services is configured, the repository should be migrated from a

Microsoft Access database (the default) to a Microsoft SQL Server 2000 database to
avoid permissions issues caused when users access an Access database from other
computers.
Note For more information about migrating the Analysis Services repository, see the topic
Migrate the Analysis Services Repository to a SQL Server Database in Chapter 8, Post
Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.
The Decision Support Objects component of Analysis Services is required to be on the

Project Server 2003 computer if Analysis Services is configured to be on a separate
computer. In addition, if the Views Processing service is offloaded to a different
computer from the Project Server 2003 computer, it must also have Decision Support
Objects installed. The version of Decision Support Objects installed on the Analysis
Services, Project Server 2003, and Views Processing computers must be the same
version and service pack release.
Note For more information about installing Decision Support Objects, see the topic Install
Decision Support Objects in Chapter 4, Prepare the Servers of the Microsoft Office Project
Server 2003 Installation Guide.
After Analysis Services is configured and Decision Support Objects is installed on all
the required computers, you will need to create the OLAP Administrator account. This
is required by users of the Portfolio Analyzer feature of Project Server when they
access information stored in an Analysis Services database. The OLAP Administrator
account must be added to the Analysis Services, Project Server 2003, and Views
Processing computers and be identical on all three servers.
Note For more information about creating the OLAP Administrator account, see the topic
Create an OLAP Administrator in Chapter 4, Prepare the Servers of the Microsoft Office
Project Server 2003 Installation Guide.
Microsoft SQL Server 2000 Enterprise Edition is also required to enable Analysis
Services to be available over the Internet. When users try to access this extranet-
enabled view from Microsoft Project or from the Resource Center of Microsoft
Project Web Access, they will be prompted to enter their Windows user account name
and password before they can see the view. Since the Windows user account name and
password are sent in plain text, you should be sure to configure Project Web Access to
use SSL so that information will be sent encrypted.
Note For more information about configuring Portfolio Analyzer to be accessible using
HTTP, see the topic Set Up Analysis Services to be Accessible Using HTTP in Chapter 8, Post
Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.
2. Office Web Components (OWC) 2003 is required in order to interact with Portfolio
Analyzer views. A fully-interactive version of OWC 2003 is required to create or
modify Portfolio Analyzer views; a read-only version can be used to view Portfolio
Analyzer views. A read-only version will be made available to Project Web Access
users from Project Server. The fully-interactive version of OWC 2003 is only available
in Microsoft Office 2003 and Project Professional 2003.
3. Settings in the Project Server 2003 Enterprise Global Template and Enterprise
Resource Pool can have a significant effect on the way that data is handled when using
Portfolio Analyzer. Before using Portfolio Analyzer, you should consider the following:
• Has your organization defined Enterprise Project Outline Codes and Enterprise
Resource Outline Codes?
• Are the values for lookup tables stored in the Enterprise Global Template?
• Have all required resources been added to the Enterprise Resource Pool?
• (When appropriate), have values been assigned to any of the Enterprise Outline
Codes?
• Have resources been assigned in the Enterprise Resource Pool to the correct
Project Server security categories your organization is using to allow access to
Portfolio Analyzer views? (If you import resources or synchronize the Enterprise
Resource Pool with Microsoft Active Directory®, all resources will be added to
the Team Members security category.)
Note For more information about configuring the Enterprise Global Template and
Enterprise Resource Pool, see the Microsoft Office Project Server 2003 Application
Configuration Guide.
4. Publish a project plan to the Project Server database. There must be data in the Project
Server database to move data into the Analysis Services database when the OLAP cube
is built. In Project Professional, this includes selecting Publish, then All Information
from the Collaborate menu for every project that you want to make available using
Portfolio Analyzer.
5. Once you have published a project to Project Server, you will be ready to build the
OLAP cube. Building an OLAP cube requires that you have set up Analysis Services
and set the permissions on Project Server components to access Analysis Services.
Project Server does not give any user permission to view the OLAP cube. You will
need to set security for the cube on the database in Analysis Manager after it has been
created. A Project Server administrator can build the OLAP cube from the Update
resource tables and OLAP cube page that is available in the Manage enterprise
features section of the Admin center.
Note For more information about building the OLAP cube, see the topic Updating Resource
Tables and OLAP Cubes in Chapter 7, Managing Enterprise Features of the Microsoft Office
6. You must create a role on the Cube database on the Analysis Services computer for
each user or group of users (for example, a Project Server security group). If your
organization is using Active Directory synchronization, consider using the Active
Directory security group name. In addition, you can also use a local Windows user
account, but this local Windows user account must also be on the Analysis Services
server and on the client (Project Web Access and Project Professional) computers.
To bind to a new Analysis Services database, simply enter the database name in the
Cube Name text box and click Apply. Each Analysis Services database must have the
Project Server users and security groups added to the database roles in order for those
users to be able to access the data.
7. Create a Portfolio Analyzer view in Project Web Access using the Manage views
section of the Admin center. If all of the settings required by Portfolio Analyzer are
configured properly, the PivotTable Field List will appear on the Specify Views
page when Portfolio Analyzer is selected. In addition, while creating Portfolio
Analyzer views, you must add the view to a Project Server security category. Users and
groups that have been assigned to this category will be able to access the Portfolio
Analyzer view.
8. After a user has navigated to the Portfolio Analyzer page in Project Web Access
(select Analyze Projects in Portfolio Analyzer from the Project Center). All available
Portfolio Analyzer views will be listed in the Choose a view drop-down menu; only
the Portfolio Analyzer views that belong to the same category as the current user will
be accessible.
Permissions required for users of Portfolio Analyzer
• Open Project is a category permission that allows a user to use the Portfolio Analyzer
feature in Project Web Access or Project Professional.
• See Enterprise Resource Data is a category permission that allows a user to view
resources and resource data stored in the Enterprise Resource Pool.
• See Projects in Project Center is a category permission that enables a user to access
the Project Center from both Project Professional and Project Web Access.
• Mange Enterprise Features is a global permission that allows a user to access the
Manage enterprise features page in the Admin center in Project Web Access. Users
with permission to access the Manage enterprise features page can create the OLAP
cube for Portfolio Analyzer.
• Mange Views is a global permission that allows a user to access the Manage views
page in the Admin center in Project Web Access. Users with permission to access this
page will be able to add, modify, or delete Portfolio Analyzer views.
• View Portfolio Analyzer is a global permission that allows a user to view the Portfolio
Analyzer using Project Web Access or Project Professional.
• View Project Center is a global permission that allows a user to access the Project
Center from Project Web Access or Project Professional.
Creating Portfolio Analyzer Views

After you have installed and configured Project Server and added users to the Enterprise
Resource Pool, most organizations will be ready to start letting users interact with Project
Server data from Project Professional and Project Web Access without a lot of additional
configuration. However, users who will want to create views will need to be granted
permission to do so.
Users must have the appropriate permissions to access the Manage views area of Project
Web Access in order to create new views. Users must also have the appropriate
permissions to access the Projects and Resources areas of Project Web Access in order to
access existing views.
On the Specify Views page in Project Web Access, all of the Project, Project Center,
Assignment, Resource Center, and Portfolio Analyzer views that are currently available will
be displayed. Each view has the following descriptive elements:
• View Name is the name of the view. This is the same as the Name field under View
name and description when adding or modifying a view.
• View Type is the type of view. There are five types of views: Project, Project Center,
Assignment, Resource Center, and Portfolio Analyzer.
• Portfolio Analyzer views take advantage of Microsoft Office Web Components to
display online analytical processing (OLAP) data stored in cubes in the Analysis
Services server. This combination of technology allows you to use PivotTable and
PivotChart features to display and manipulate project data. Setting up and using
Portfolio Analyzer involves some additional steps.
• View Description is the description of the view. This is the same as the Description
field under View name and description when adding or modifying a view.
The Manage Views section provides a location to define Project, Project Center, Resource
Center, Assignment, and Portfolio Analyzer views.
Preparing to Create Portfolio Analyzer Views

Before you can create Portfolio Analyzer views, you must build an OLAP cube that
contains resource availability and cube data.
Note Before you can create Portfolio Analyzer views, you must first build the OLAP cube. For
information about building the OLAP cube and other prerequisites for using Portfolio Analyzer, see
the topic Updating Resource Tables and OLAP Cubes in Chapter 7, Managing Enterprise Features in
the Microsoft Office Project Server 2003 Administrator’s Guide.
After you have set up OLAP services in Project Web Access, you can set up Portfolio
Analyzer views. Portfolio Analyzer uses the following Microsoft Office Web Components
features:
• PivotTable provides dynamic views that enable users to analyze information by
sorting, grouping, filtering, and pivoting Project Server data. The data is pulled
from the Project Server database view tables and is displayed in a familiar
Microsoft Excel spreadsheet format.
• Chart provides graphical displays of information of PivotTable data. Chart is

linked directly to the PivotTable component so it always updates instantly in
response to user interactions in the PivotTable.
When you are working in Portfolio Analyzer, you will be able to choose whether to build a
PivotTable, a Chart, or a combination of both representations of data, and you will be able
to switch between workspaces while you are working on the Portfolio Analyzer view.
Creating Portfolio Analyzer views in Project Web Access.

Note For information about building the OLAP cube and other prerequisites for using Portfolio
Analyzer, see the topic Updating Resource Tables and OLAP Cubes in Chapter 7, Managing
Enterprise Features in the Microsoft Office Project Server 2003 Administrator’s Guide.
X To add a Portfolio Analyzer view

Manage views.
3. Under View Type, select Portfolio Analyzer.

5. Under Analysis Server and Cube, type the name of the Analysis Services server and
the OLAP cube name in the Analysis Server and Cube Name fields. This page will
load with the Analysis Server most recently used to build an OLAP cube.
Note You cannot use the following characters: / “ ; : < > | [ ] , . ‘ ? ~ ` ! $ % ^ & * ( ) - + = {
} \ in the Analysis Server or Cube Name fields.
6. Under Portfolio Analyzer Mode, select one of the following options:
• PivotTable with Chart Displays both the PivotTable and Chart workspaces.
• PivotTable only Displays only the PivotTable workspace.
• Chart only Displays only the Chart workspace.
7. Under Customize the PivotTable and Chart, you can add data to a Portfolio
Analyzer view. The Field List dialog boxes contain two types of data: totals and
dimensions. To add information to the PivotTable, simply drag a field with your
mouse from the PivotTable Field List into the colored rectangular zones in the
PivotTable. Chart data will automatically be updated to match the PivotTable.
An empty PivotTable has four main areas into which fields and information can be
dropped:
• Filter Fields The contents of this area will act as filters for incoming data.
Information from the OLAP cube will only be displayed if the data passes the
criteria that is defined here.
• Column Fields The fields in this area contain the groups that the data will be
aggregated into. They will form the columns of the PivotTable (spreadsheet).
• Row Fields These are the sets of data that will define the discrete sets of data and
will be stored in the rows of the PivotTable.
• Total or Detail Fields These fields provide the data to be totaled and will form
the values in each of the cells in a PivotTable.
An empty Chart has four main areas into which fields and information can be dropped:
• Filter Fields The contents of this area will act as filters for incoming data.
Information from the OLAP cube will only be displayed if the data passes the
criteria that is defined here.
• Category Fields The fields in this area contain the groups that the data will be
aggregated into. They will form the X-axis of the Chart.
• Series Fields These are the sets of data that will define the discrete sets of data
and will be stored in the rows of the Chart.
• Data Fields These fields provide the data to be totaled and will form the values
in each of the cells of the Y-axis of a Chart.
8. Under Default View Settings, select Show Field List or Show toolbar options to
make the Portfolio Analyzer Field List and Toolbar available to users of Portfolio
Analyzer for the particular view. Enabling these features will allow users of Portfolio
Analyzer to work with views and change view data at the session level while working in
the Portfolio Analyzer.
Note The only way to make Portfolio Analyzer views available to users of Project Web
which you want to add the view. In addition, adding Portfolio Analyzer views to Project
Server security categories is not the same thing as securing access to Portfolio Analyzer or
Analysis Services. Securing access to the OLAP cube in Analysis Services must be done at
the database level in Analysis Services, whereas Project Server security categories only
determine which Project Server users will be able to access a particular Portfolio Analyzer
view.
Using Multiple OLAP Cubes

Project Server supports the use of multiple OLAP cubes (databases in Analysis Services).
However, each Portfolio Analyzer view can only be connected to a single Analysis Services
database (OLAP cube). For example, when you create a new Portfolio Analyzer OLAP
cube from the Update resource tables and OLAP cube page in Project Web Access, the
information entered in the Cube Name field is compared against the existing database
names on the Analysis Services server. If the information specified in the Cube Name
field does not match a database name on the Analysis Services server, a new database will
be created (a new OLAP cube will be created) with the name specified in the Cube Name
field. If the name specified in the Cube Name field matches an existing database name on
the Analysis Services server, then all information in the existing database will be
overwritten with the updated information.
When you create a Portfolio Analyzer view in Project Web Access using the Specify Views
page, the information entered in the Cube Name field is compared against the existing
database names on the Analysis Services server. If the information specified in the Cube
Name field does not match a database name on the Analysis Services server, then you will
not be able to connect to the cube. You can create a Portfolio Analyzer view against any
database that exists on the Analysis Services server.
There are several ways to bind a Portfolio Analyzer view to an Analysis Services database:
• Create a new view and enter the Analysis Services database name that you want to
connect to in the Cube Name field.
• Modify an existing Portfolio Analyzer view and enter the Analysis Services database
name that you want to connect to in the Cube Name field.
• Specify a new Analysis Services database name while working with a Portfolio Analyzer
view. Click the Command and Options button, select the Data Source tab, and then
select the cube name from the drop-down list under Use data from.
Note Portfolio Analyzer views can be bound to any database in Analysis Services, not only to ones
created using Project Web Access.
X To specify the OLAP cube to which a Portfolio Analyzer view is connected

Manage views.
2. On the Specify Views page, select a Portfolio Analyzer view, and then click Modify
View.
3. After the page has refreshed, under Analysis Server and Cube, verify the information
in the Analysis Server and Cube Name text boxes. This information should point to
the Analysis Services server (and OLAP cube name) to which you want to bind the
view. If you want to connect to a different Analysis Services database, enter the
database name in the Cube Name field.
Note The information entered in the Cube Name field is the same name as the database
in Analysis Services.
4. If you entered a new Analysis Services name in the Cube Name field, click Apply.
5. Complete building the Portfolio Analyzer view.
Note For more information about creating Portfolio Analyzer views, see the topic Preparing
to Create Portfolio Analyzer Views in Chapter 4, Managing Views of the Microsoft Office
Add Users to Cube Database Roles in Analysis Services

SQL Server Analysis Services uses Windows authentication to control access to online
analytical processing (OLAP) cubes—for example, when using Portfolio Analyzer. By
default, the OLAP cube database created by Project Server has no database roles defined
so that only users or groups specifically added have access to the cubes.
Note This procedure cannot be performed until an OLAP cube database has been built. To check
the status of the cube database, open Project Web Access, and then click Admin in the top link bar
to go to the Admin center. In the side pane, click Manage enterprise features, and then click
Update resource tables and OLAP cube. The status of the OLAP cube database is shown under
Current Cube Status.
1. Log on to the Analysis Services computer with a user account that has permissions
equivalent to either of the Administrators or OLAP Administrators groups, and start
Analysis Manager.
2. Expand the name of your server under Analysis Servers to see the cube databases on
that computer.
3. Right-click the name of the database (as shown in the Cube name box of the Update
Resource Tables and OLAP Cubes page in Project Web Access), and then click
Manage Roles.
4. Click New, and type a name for the new database role in the Role name box.
5. On the Membership tab, click Add to add users and groups to the role, and then click
OK.
6. On the Cubes tab, click Check All to enable access to all three cubes in the database.
7. Click OK to add the role.
Making Views Available to Project Web Access Users

Views only define fields and format available in a report. Views do not define the resources
or projects visible in the report. After a view is defined, the view must be added to one or
more categories in order for the view to be accessed by the Project Web Access users who
are also assigned to that category. Categories define the specific projects and resources that
a particular user will be able to see. By adding views to categories, administrators can define
the objects (projects and resources) and the properties of the objects (views) available to
any given user or group of users.
Note For more information about adding views to Project Server security categories, see the topic
Managing Categories in Chapter 2, Managing Users and Groups of the Microsoft Office Project
X To add a view to a category

Manage security.
3. On the Categories page, select a category in the Category Name column, and then
click Modify Category.
4. Under the sections Projects: Select the projects that users in this category can
view, Resources: Select the resources whose information can/cannot be viewed
by users in this category, and Project Center Views: Select views for displaying a
portfolio of projects, select the view you want to make available to the selected
category, and then click Add.
Working with Portfolio Analyzer Views

This chapter explains how to use the Portfolio Modeler feature that is available when using
Microsoft Office Project Server 2003, Microsoft Office Project Web Access 2003, and
Microsoft Office Project Professional 2003 as part of your organization’s Enterprise
Project Management (EPM) Solution. The Portfolio Analyzer is available from the Project
Center in Project Web Access or the Collaborate menu in Project Professional.
Portfolio Analyzer relies on the following features:
• OLAP Cube The Portfolio Analyzer works with a cube of data that is created,
processed by, and stored in the OLAP Cube provided by SQL Server 2000 Analysis
Services. The OLAP Cube is generated on a scheduled basis, as determined by the
Project Server administrator.
• Office Web Components The Portfolio Analyzer pages in Project Web Access
require the use of Office Web Components in order to use the PivotTable and
PivotChart features. These features allow users to interact with the controls in the
Portfolio Analyzer to work with the data in the views.
• Enterprise Outline Codes Enterprise Outline Codes are used to define the hierarchy
of data presented in the Portfolio Analyzer. They can be used to categorize projects
and resources by location, department, etc. Each Enterprise Outline Code
automatically becomes a dimension in the OLAP Cube. The availability of multiple
dimensions is what enables Portfolio Analyzer to provide in-depth reporting of data on
many different levels.
• Metrics Metrics are the data values presented in the Portfolio Analyzer, such as Work,
Actual Hours, Cost, Baseline Cost, etc. The Portfolio Analyzer contains many metrics
that can be displayed. Users can also create their own custom metrics using Enterprise
Custom Fields..
• Portfolio Analyzer Views Many styles of charts, graphs, and PivotTables are available
when using the Portfolio Analyzer. Each is given a name by the individual creating the
view and the view determines which controls are exposed and which metrics are
displayed. If the user has the Manage Views permission, they will be able to create
their own views and edit existing views in the Project Web Access Admin Center.
Note The Project Server administrator determines when the OLAP Cube processing will be run.
OLAP Cube generation can be a very lengthy process; therefore it is recommended that it be run on
off-hours for your organization. The OLAP Cube should not be run more often than necessary to
support a normal status reporting interval for your organization. For example, if timesheets are
submitted, approved, and posted to projects on a weekly basis, it doesn’t make sense to generate
a cube every night.
Portfolio Analyzer can be accessed from both Project Web Access and Project
Professional. Portfolio Analyzer views are stored in the Project Server database in the View
tables (MSP_VIEW_). The view tables are updated when a Project Professional user does
any of the following:
• Publishes a project plan from Project Professional to Project Server
• Checks in, saves, or imports a project to the Project Server database
• Checks in, saves, or imports resources to the Enterprise Resource Pool
• The Project Server administrator updates the resource availability tables or the OLAP
cube in Project Web Access, either as a scheduled event or manually
Project Web Access views are simply a way to create a visible list of data that can be
targeted at the type of user who needs to view the data. Portfolio Analyzer uses views in a
way that allows project managers, resource managers, members of your organization’s
Project Management Office, or executives to view more than just tasks, assignments, and
projects. They can use Portfolio Analyzer to learn and understand critical information
about the entire organization, such as how projects compare to each other, in addition to
drilling into project details. Portfolio Analyzer views are one of five types of views that can
be created in Project Web Access by users with the Manage Views permission.
Saving Portfolio Analyzer Views as GIF Images

You can save Portfolio Analyzer PivotTable and Chart views as GIF images for use in
other applications, like Microsoft Office Word 2003 or Microsoft Office PowerPoint 2003.
X To save a PivotTable or Chart as a GIF image

1. On the Portfolio Analyzer page, while working with a Portfolio Analyzer view, right-
click the view and deselect Toolbar and Drop Areas to only show data in the saved
GIF image.
For example:
2. When you have the Portfolio Analyzer view the way that you want it, on the Portfolio
Analyzer page, click Save PivotTable as GIF or Save Chart as GIF.
3. In the Specify the GIF file name that you want to export to dialog box, enter the
name of the GIF image.
4. Click OK.
Saving Portfolio Analyzer Views as Links in Project Web Access

You can save links to Portfolio Analyzer views in the Project Web Access side pane.
X To save Portfolio Analyzer views as links in Project Web Access
1. On the Portfolio Analyzer page, while working with a Portfolio Analyzer view that you
want to access on a regular basis, click Save Link.
2. In the Save Link dialog box, enter the name of the link you want to save in the Project
Web Access side pane.
3. The link will be available under Saved Links in the side pane that is available from
within the Project Center, for example:
(Sample) Tracking Resource Workload by Skill Level

There are many different ways to use Portfolio Analyzer; this chapter is not intended to
present any specific way to use Portfolio Analyzer. How your organization uses Portfolio
Analyzer will largely depend on the type of data you want to analyze, the size and number
of projects, and the type of results you hope to obtain. In general, Portfolio Analyzer
should be one of the final major features of Project Server that is added to your
organization’s production environment. The following example shows you how you can
use Portfolio Analyzer to create a view that tracks resource workload by skill level.
X To create a Portfolio Analyzer view to track resource workload by skill level
Manage views.
3. Under View Type, select Portfolio Analyzer.

5. Under Analysis Server and Cube, type the name of the Analysis Services server and
the OLAP cube name in the Analysis Server and Cube Name fields.
Note You cannot use the following characters: / “ ; : < > | [ ] , . ‘ ? ~ ` ! $ % ^ & * ( ) - + = {
} \ in the Analysis Server or Cube Name fields.
6. Under Portfolio Analyzer Mode, select one of the following options:
• PivotTable with Chart Displays both the PivotTable and Chart workspaces.
• PivotTable only Displays only the PivotTable workspace.
• Chart only Displays only the Chart workspace.
7. Under Customize the PivotTable and Chart, add data to the Portfolio Analyzer
view. Click the Chart workspace to open the PivotTable Field List dialog box.
8. Select Versions, Resource RBS, and Resource Department from the PivotTable
Field List and drag them to the Drop Filter Fields Here area. Resource RBS and
Resource Department are outline code dimensions defined using Enterprise
Resource Outline Codes in the Enterprise Global Template.
Next, expand the Time category in the PivotTable Field List, select Years, and then
add it to the Drop Column Fields Here area.
Next, add the Resources category to the Drop Row Fields Here area.
Next, expand the Totals category in the PivotTable Field List, select Availability
and Work, and then add them to the Drop Totals or Detail Fields Here area.
This will be all of the data required to be part of the A.Datum Resource Workload
by Department Portfolio Analyzer view. As this view currently exists, there is a large
amount of data (every resource in the organization). You can use two Enterprise
Resource Outline Codes to filter out unwanted data.
9. Currently, every resource is loaded into this view. Use the Resource RBS filter to
focus on a specific group of resources for analysis. Select Resource RBS and then
check the boxes next to the RBS nodes for which you want to view resources. For
example, uncheck all boxes except for the West node under USA.
10. Next, use the Resource Department filter to select resources for a particular
department in your organization. Resource Department is created in the Enterprise
Global Template using an Enterprise Resource Multi-Value Outline Code. To filter
resources by department, select Resource Department and then check the boxes next
to the outline code nodes for the resources that you want to view. For example,
uncheck all boxes except for the Corporate node.
11. Once the number of resources is filtered to the right level of detail, you can begin
working with the type of graph you want to use. The default graph looks like this:
12. Select a different chart by selecting the Chart Type button (in the top left) to open the
Commands and Options dialog box.
There are twelve types of graphs available, including the bar graph (shown below).
13. Currently, this Portfolio Analyzer view includes all Version types. To filter for only the
Published versions of projects, select Versions and ensure that only Published is
checked.
The graph will be updated to only reflect the Published version types.
14. To narrow down the number of resources further, select the individual resources from
the Resources drop-down list.
15. The graph will be updated to only reflect the selected resources.
16. To focus on a specific set of time, select the time dimension (Years, in this scenario)
and select the appropriate range of time.
The graph will be updated to only reflect the selected time dimensions.
17. Under Default View Settings, select Show Field List or Show toolbar options to
make the Portfolio Analyzer Field List and Toolbar available to users of Portfolio
Analyzer for the particular view. Enabling these features will allow users of Portfolio
Analyzer to work with views and change view data at the session level while working in
the Portfolio Analyzer.
19. Click Save Changes. This Portfolio Analyzer view is now available to all users in your
organization who belong to the security categories this view belongs to. On the
Portfolio Analyzer page, users will need to select the Portfolio Analyzer view from the
Choose a view drop-down list.
Appendix
A
Additional Resources
If you want to learn more about Microsoft® Office Project Server 2003, Microsoft Office
Project Web Access 2003, and Microsoft Office Project Professional 2003, or how to use
these three applications as part of your organization’s Enterprise Project Management
(EPM) solution, please refer to the following online books, planning and training guides,
and Web sites.
Microsoft Office Project Server 2003 Online Books Series

• Microsoft Office Project Server 2003 Configuration Planning Guide
• Microsoft Office Project Server 2003 Disaster Recovery Guide
• Microsoft Office Project Server 2003 Installation Guide
• Microsoft Office Project Server 2003 Application Configuration Guide
• Microsoft Office Project Server 2003 Administrator’s Guide
Project Server-Related Web Sites

The following Web sites are also available:
• Microsoft Office Project Server 2003 Software Development Kit
• Microsoft Office Online: http://www.office.microsoft.com
Send us your feedback. Please let us know what you think about the quality of this
content. If this text does not meet your needs, let us know how we can improve it. If this
text was helpful to you, let us know how it helped.
mailto:projdocs@microsoft.com?subject=Feedback: Microsoft Office Project Server 2003
Administrator’s Guide
B
Project Server Administrative Tools
This appendix describes tools available to the Microsoft® Office Project Server 2003
administrator. These tools can be used during initial deployment and during day-to-day
post-deployment operations.
Delete Duplicate Projects Utility

The Delete Duplicate Projects tool (DupeProj.exe) is a command line tool that you can use
to remove duplicate projects from the Project Server database. This tool can help project
managers and database administrators in your organization determine the correct duplicate
project to delete. This tool works with Project Server 2002 and Project Server 2003
databases.
The Delete Duplicate Projects tool uses a stored procedure to remove the specified
duplicate project. This stored procedure is created dynamically by the Delete Duplicate
Projects tool and is deleted when DupeProj.exe terminates. The removal of duplicate
projects is based only on a project’s Web Project ID in the MSP_WEB_PROJECTS table.
The Delete Duplicate Projects tool deletes data from the following tables:
• MSP_WEB_TRANSACTIONS
• MSP_WEB_WORK
• MSP_WEB_WORKGROUP_FIELDS
• MSP_WEB_MESSAGES_ASSIGNMENTS
• MSP_WEB_DELEGATIONS
• MSP_WEB_DELEGATION_ASSIGNMENTS
• MSP_WEB_WORK_ADJUSTED (Project Server 2003 only)
• MSP_WEB_WORK_APPROVAL (Project Server 2003 only)
• MSP_WEB_ASSIGNMENTS
• MSP_WEB_TRANSACTIONS
• MSP_WEB_MESSAGES_ASSIGNMENTS
• MSP_WEB_NONWORKING
• MSP_WEB_MESSAGES
• MSP_WEB_OBJECT_LINKS
• MSP_WEB_OBJECTS
• MSP_WEB_PROJECTS
• MSP_WEB_PROJECT_WORKGROUP_INFO
• MSP_WEB_MGR_RULES_LISTS
• MSP_WEB_MESSAGES_NONWORKING
The syntax for DupeProj.exe is as follows:
DupeProj [-l] | [-d:project-id,project-id...] [-cs:"<connection-
string>")
The following command line parameters can be used with DupeProj.exe:
Parameter Description
-? Displays usage information.
-l Lists all duplicate projects. The Delete Duplicate Projects tool will display the
following information, if available, about each duplicate project:
• Web Project ID
• Project Name
• Project Owner
• Date Last Published
• Version
-d Deletes the specified duplicate project from the database. The project list
should be formatted as a comma-separated list of integers without any
spaces. For example:
DupeProj -d:101,215,311 -cs:"..."
-cs Required. Specifies the connection string required to connect to your

database. The connection string must be formatted as a quoted literal string
with the following parameters:
• Use the Server keyword to specify the server name.
• Use the Integrated Security keyword, set to a value of SSPI,
to specify Windows Authentication (recommended).
or
Use the User ID and Password connection properties to
specify SQL Server Authentication.
• Use the Database keyword to specify the database.
For example:
DupeProj -l -cs:"server=(local);Integrated
Security=SSPI;database=ProjectServer"
X To install the Delete Duplicate Projects utility

• Download and run the file DupeProjDownload.exe from the Microsoft Download
Center: http://go.microsoft.com/fwlink/?LinkId=20893.
Note You must have .NET Framework version 1.1 installed on the computer where you will run the
Delete Duplicate Projects tool.
X To delete duplicate projects

1. Run DupeProj.exe with the –l parameter to check for the presence of duplicate
projects. For example,
DupProj.exe –l –cs:”server=(local);Integrated
Security=SSPI;database=ProjectServer”
2. Run DupeProj.exe with the –d parameter to delete the duplicate projects from your
database. For example,
DupProj.exe –d:456,457,459 –cs:”server=(local);Integrated
Security=SSPI;database=ProjectServer”
Working with projects in the Project Server database

Use the Delete Duplicate Projects tool to remove duplicate projects in the event that
duplicate projects are created during normal publish and save operations to the Project
Server database from Project Professional. This tool can be run periodically by the Project
Server administrator to check the Project Server database for the existence of duplicate
projects or run if notified by a project manager or Project Web Access user of the presence
of one or more projects with the same identifier.
Deleting duplicate projects prior to upgrade

If you are upgrading from Project Server 2002 to Project Server 2003, use this tool to
delete duplicate projects in your Project Server 2002 database before upgrading the
database. If there are duplicate projects in the database, the upgrade scripts could fail.
Project Server Cleaner

Project Server Cleaner is a tool that can be used by project managers, resource managers,
and administrators to bulk delete unwanted enterprise projects and enterprise resources
from the Microsoft® Office Project Server 2003 database. Project managers will be able to
delete any projects they manage, resource managers will be able to delete any resources they
manage, and administrators will be able to delete any enterprise project or enterprise
resource in the Project Server database.
Project Server Cleaner uses two methods in the Project Data Service (PDS) to delete
enterprise projects and enterprise resources from the Project Server database:
• ProjectDelete This method deletes an enterprise project from the Project Server
database. This is the same process as using the delete button in the Open from
Microsoft Project Server dialog box in Microsoft Office Project Professional 2003.
• ResourcesDelete This method deletes an enterprise resource from the Enterprise
Resource Pool. This process involves checking out the Enterprise Resource Pool,
deleting the resource from the Enterprise Resource Pool, and then checking the
Enterprise Resource Pool back in. Users will also automatically be removed from any
associated Windows SharePoint Services site. Enterprise resources will be changed to
local users and will have a comment appended to their name (the appended comment
is specified during the delete process in the Project Server Cleaner tool). The
WRES_CAN_LOGIN and WRES_COUNT_LICENSE fields in the
MSP_WEB_RESOURCES table are set to 0 for each deleted user.
X To install Project Server Cleaner
1. Download and run the file PSCleanerDownload.exe from the Microsoft Download
Center (http://go.microsoft.com/fwlink/?LinkId=20899).
2. Run the file Setup.msi to install Project Server Cleaner.
3. Follow the steps in the PSCleaner Setup Wizard. When finished, you are ready to run
Project Server Cleaner.
X To delete enterprise projects using Project Server Cleaner
1. Run PSCleaner.exe.
2. In the Project Server URL text box, enter the Project Server URL.
3. In the Username and Password text boxes, enter the user name (domain\user name
if using Windows authentication) and password for the user account that you want to
use to delete enterprise projects. If the user account is Windows authenticated, click
the Windows authentication check box.
4. Select Enterprise Projects, and then click the Retrieve button. A user will only be
able to view the projects they would normally have access to in Project Professional or
Project Web Access. A project manager (or member of the Project Managers security
group) can only delete projects they manage. A Project Server administrator can delete
any project.
You cannot delete enterprise projects that are checked out. To force a check in of a
checked out project, right-click the project in the Project Name column. If a project is
checked in using this method, the current user of the project will not be able to save
any changes they have made and will no longer have access to that project.
5. In the list of projects, select the projects you want to delete. You can use the SHIFT
and CTRL keys to select more than one enterprise project.
6. When you are ready to delete the selected projects, click the Delete button.
7. In the Delete Confirmation alert message, click Yes.
X To delete enterprise resources using Project Server Cleaner

1. Run PSCleaner.exe.
2. In the Project Server URL text box, enter the Project Server URL.
3. In the Username and Password text boxes, enter the user name (domain\user name
if using Windows authentication) and password for the user account that you want to
use to delete enterprise resources. If the user account is Windows authenticated, click
the Windows authentication check box.
4. Select Enterprise Resources, and then click the Retrieve button. A user will only be
able to view the resources they would normally have access to in Project Professional
or Project Web Access. A resource manager (or member of the Resource Managers
security group) can only delete resources they manage. A Project Server administrator
can delete any enterprise resource. In addition, this user must also be granted the
Clean up Project Server Database global permission.
You cannot delete enterprise resources that are checked out. To force a check in of a
checked out enterprise resource, right-click the enterprise resource in the Resource
Name column. If an enterprise resource is checked in using this method, the current
user of the enterprise resource will not be able to save any changes they have made and
will no longer have access to that enterprise resource.
5. In the list of resources, select the resources you want to delete. You can use the SHIFT
and CTRL keys to select more than one enterprise resource.
6. When you are ready to delete the selected resources, click the Delete button.
7. In the Delete Confirmation alert message, click Yes.
8. In the Get Deletion Comment dialog box, enter the comment that you want
appended to each deleted enterprise resource’s name.
9. Click OK.
Project Server Documentation

The following files and folders provide more information about the Project and Project
Server databases, using data available through the OLE DB Provider, Microsoft Visual
Basic® for Applications, XML, and the Project Data Service.
On the Project Server and Project Professional CDs

The following documents are available in the C:\Program Files\Microsoft Office Project
Server 2003\Help\1033 folder after you have installed Project Server, or on the Project
Server CD in the \Docs folder.
• PjDB.htm Documents the Project database, including most pieces of core project
data.
• PjSvrDB.htm Documents the Project Server database, including security, views, and
web tables.
• PjXML.chm Documents the Project XML schema.
• PjOLEDB.htm Documents project data as available in the OLE DB Provider.
Note PjOLEDB.htm is only available on the Project Professional CD.
Project Server Health Monitor

The Project Server Health Monitor (psHealthMon.exe) is designed to provide detection
and notification of specific system components that are responding slowly or not at all in a
Microsoft Project Server 2002 or Project Server 2003 deployment. This tool will monitor
the number of files in the ViewDrop folder and the response time for Project Data Service
(PDS) calls. You can configure thresholds for the number of files in the ViewDrop folder,
the length of time a file spends in the ViewDrop folder, and time allowed for basic PDS
calls. If any of these thresholds are exceeded, the Project Server Health Monitor can record
this information in a log file or notify you by email.
The Project Server Health Monitor utility can be configured to monitor up to three
ViewDrop folders and up to four Project Servers for PDS response time.
X To install the Project Server Health Monitor
1. Download and run the file PSHealthMonDownload.exe from the Microsoft Download
2. Run the file setup.msi to install the Project Server Health Monitor. By default,
psHealthMon.exe will be installed in the \Program Files\Microsoft Office Project
Server 2003 Resource Kit\Toolbox\Project Server Health Monitor directory.
Note Project Server Health Monitor requires Windows 2000 or above.
X To run Project Server Health Monitor

1. Run the PSHealthMon.exe file.
2. Configure the settings you want to use on the ViewDrop, PDS Info, Admin, and
Notify tabs. See the information on each tab below.
3. Click Start.
Note If you want to save your configuration for the next time you run Project Server Health
Monitor, click Save Settings before you exit the application.
Monitor Tab
Use the Monitor tab to monitor the current status of the servers you have configured. The
following information is displayed:
• For each ViewDrop folder, the Last column shows the number of files in the folder at
the last run, and the Max column shows the highest number of files that have been in
the folder since you started the Project Server Health Monitor application. The length
of time that the oldest file has been in the folder is shown in the Oldest XML (min)
box.
• For each Project Server you configured on the PDS Info tab, the time in milliseconds
for a simple PDS call is shown under PDS Status Result. The Last column shows the
time for the last run, and the Avg and Max columns show the average time and
maximum time for all the runs since you started the Project Server Health Monitor
application. The Result box will show PASS if the PDS call was successful.
ViewDrop Tab
Use the ViewDrop tab to specify which ViewDrop folders you want to monitor.
X To configure ViewDrop folder settings
1. If the ViewDrop folder you want to monitor is on another computer, create a share to
that folder with read permissions for the Windows NT account you will be using when
you run Project Server Health Monitor.
2. For each ViewDrop folder you want to monitor, enter the local or network path to the
ViewDrop folder in the ViewDrop Folder box.
PDS Info Tab
Use the PDS Info tab to specify which Project Servers you want to monitor. Project Server
Health Monitor will monitor the PDS response time for each server you specify here.
X To configure PDS monitoring information
• For each Project Server you want to monitor, enter the Project Server URL, and then
select the NT Authentication check box if you want to access the Project Server with
your Windows NT account, or type the user name and password of a Project Server
account.
Admin Tab
Use the Admin tab to specify Project Server Health Monitor logging options, thresholds,
and how often Project Server Health Monitor tests those thresholds.
X To configure Admin settings
1. Specify the interval at which to check the ViewDrop folder status and test the PDS
response time by choosing an interval from the Run Every list.
2. Optionally, to require a password to run Project Server Health Monitor, select the
Require Password check box, and then specify the password in the Change
Password and Retype Password boxes.
3. Configure logging by selecting one of the logging options, and then typing a path and
filename for the log file in the Log to File box if you choose to use logging.
4. Under Thresholds, specify the values you want for the number of files in the
ViewDrop folder, the length of time a file stays in the folder, and the PDS response
time. Notification and logging events occur when the thresholds you set here are
exceeded.
Notify Tab
Use the Notify tab to specify when email notifications will be sent by Project Server
Health Monitor.
X To configure notification settings
1. Under When do you want to be notified?, select the option you want.
2. In the Who should receive notifications box, specify the email addresses to which
notifications should be sent.
Errors Tab
Use the Errors tab to see any runtime errors that Project Server Health Monitor has
encountered. This information can be useful if you are having trouble configuring Project
Server Health Monitor.
Note Notifications of your thresholds being exceeded will not appear here; they will be written to
the log file or emailed to you, depending on your configuration.
Project Renaming Utility

The Rename Project tool enables Project Server 2003 administrators to rename a project,
or multiple projects, stored in the same SQL Server database. This tool combines a PDS
extension with an application.
The Rename Project application.

Note To rename projects, a user must have read/write access to the project(s) they are renaming,
and the PERMISSION_ADMIN_ENTERPRISE and PERMISSION_ENT_NEW_PROJECT permissions on
Project Server.
Using this tool requires three steps:

• Downloading the file package from the Microsoft Download Center.
• Installing the PDS extension.
• Preparing the application.
Download and run the file ProjRenamerDownload.exe from the Microsoft Download
Center (http://go.microsoft.com/fwlink/?LinkId=21541). The download will install by default to
the C:\Program Files\Microsoft Office Project Server 2003 Resource Kit\Toolbox
directory; however, you can choose to download the files to any directory.
Note: If SQL Server and Project Server are installed on different computers, ensure this directory is
shared and that you have access.
Installing the PDS Extension

Installing this extension requires two separate procedures:
• Register DLL on the computer running Project Server 2003.
• Modify the registry on the computer running Project Server 2003.
To register the DLL

1. Log on to the computer running Project Server 2003 using the built-in Administrator
account.
2. Open a command prompt and locate the directory into which you downloaded
ProjRenamer.dll.
3. Type regsvr32 ProjectRenamer.dll and press ENTER.
4. Click OK to confirm the DLL was registered successfully.
To update the registry

1. If you have no current PDS extensions, double-click PDSExtensionEX.reg from the
download location.
Note To verify that you have no PDS extensions, check the registry key
\HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\MS Project\WebClient
Server\ProjectServer for the string value PDSExtensionEx1.
2. Click OK to add the information to the registry update, and then click OK again to
confirm.
3. If you do have other PDS extensions, click Start, click Run, type regedit, and then
click OK.
4. In the registry editor, navigate to
\HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\MS
Project\WebClient Server\ProjectServer.
5. Right-click the ProjectServer key, point to New, and then click String value.
6. Type PDSExtensionExN (where N is the next number in sequence), and then press
ENTER.
7. Double-click this new string value, type PDSRights.CPDSRights, and then click OK.
8. Close the registry editor.
Running the Application

1. Double-click ProjRenamer.exe from the download location, and then click Login.
2. Enter the URL for the Project Server, and then enter your user name and password.
3. Select a project from the list of available projects, and then click Rename.
4. In the Rename Project To dialog box, type a new name, and then click OK.
5. The renamed project appears in the list. If it does not, click Refresh.
6. Repeat steps 3 and 4 to rename additional projects, or click Exit.
Project Server SetTracing Utility

Microsoft® Office Project Server 2003 uses the Project Server Tracing Service to log
application errors to the Event Viewer. You can use the Project Server SetTracing Utility to
redirect the tracing output to a log file, or to the Event Viewer and a log file. Directing
application errors to a log file will output the errors to a format that you can send to
Microsoft Product Support Services. This makes it easier for product support specialists to
determine the cause of any errors your organization may be running into.
The SetTracing Utility set to full logging to both the Event Viewer and a text output
file.
Running the SetTracing Utility

Use the SetTracing Utility to indicate whether you want the Project Server Tracing Service
to generate alert messages. After you set values in the SetTracing Utility and begin using the
Project Server Tracing Service, the Project Server Tracing Service will create or update a
log file and/or the Event Viewer. The logging settings entered in the SetTracing Utility will
remain the default settings until the next time you run the SetTracing Utility and save new
settings.
X To run the SetTracing Utility
1. Open the SetTracing Utility from the Project Server computer by double-clicking the
file SetTracing.exe.
2. In the Microsoft Project Server Tracing Settings dialog box, check one or both of
the following:
• Text Provider Enabled Select this option to create a text file that tracks the
service settings you want to see in the Project Server Tracing Service. You can then
send this file to Microsoft Product Support Services.
• Event Log Provider Enabled Select this option to write the output data to the
Event Viewer. You can view the log information by accessing the Event Viewer.
3. Set the values for each of the types of alerts that you want the Project Server Tracing
Service to track. If you set the field to 0, the SetTracing Utility will not log the error. If
you set the field to 5000, the SetTracing Utility will log every alert of that type.
• Success Indicates that an operation was completed successfully.
• Error Indicates that a significant problem, such as loss of data, has occurred. This
utility may load with a default value of 20480, which also indicates maximum
logging.
• Warning Indicates an event that is not necessarily significant, but may indicate a
future problem.
• Information Indicates the successful loading of a program, driver, or service, and
logs all successful events of this type.
• Audit Success Project Server does not perform this function. Entering a value in
this field other than 0 will not generate any additional log information. Leave this
field at the default setting of 0.
• Audit Failure Project Server does not perform this function. Entering a value in
this field other than 0 will not generate any additional log information. Leave this
field at the default setting of 0.
4. If you select the Text Provider Enabled check box, specify the path and name of the
output text file in the Output file name text box. It is recommended that you assign a
.txt extension to the output file. This allows you to quickly view the output file in any
editor application, such as Microsoft® Notepad. This file will be updated each time
you start, stop, or modify the settings in the SetTracing Utility. A new file name will
not be created unless you specify a new file name.
5. Click Save. The SetTracing Utility will save your settings and close. Logging will run in
the background.
Troubleshooting
• If you use the SetTracing Utility to log information in addition to what is logged in the
Event Viewer, first gather the information that you will need to capture the errors.
Then open the SetTracing Utility and set the values of any fields you are tracing to 0.
Information available in the output file could possibly compromise your organization’s
security. In addition, when the Project Server Tracing Service is running in the
background, it will continue to use the system resources of the Project Server
computer.
• If you are running the Project Server Tracing Service against a busy site and the Text
Provider Enabled check box is selected, you should periodically create a new text file
or backup and delete the existing file. As the Project Server Tracing Service runs, it will
continually append information to the specified log file. As that file grows in size,
system performance will degrade.
• You should not modify the text in the output log file. The contents of this file are
designed to help Microsoft Product Support Services and other Microsoft specialists
help to determine where an error is being caused should your organization require this
level of support.
• If you are viewing the contents of the output file, or are viewing information in the
Event Viewer, be aware that, in some cases, information you think may be wrong is
actually a false-positive return value. There can be instances when an event logs as a
failure, but then later logs as a success. When looking at events in the Event Viewer,
look for trends that include the same error, as opposed to singular events.
SmokeTest
The SmokeTest utility performs a series of tests to verify the basic functionality of a
Microsoft Office® Project Server 2003 installation and reports the results and performance
timings of each test that is run.
The computer where you run the SmokeTest utility should have Project Professional 2003
installed and your Project Server should be in Enterprise Mode. If the server is in Non-
Enterprise mode, some of the tests will fail. If Microsoft Office Project Professional 2003
is not installed, only the Project Web Access tests will be run. The Project
Professional 2003 scripts will show “0” if Project Professional is not installed.
To run the Microsoft Office Project Professional 2003 tests, you must save a file to the
enterprise database on the Project Server where you want to run the test. This should be a
test project for use with the SmokeTest application only.
Note The SmokeTest utility requires the .NET Framework Version 1.1 and Office Web Components
2003.
SmokeTest runs the following tests:

• Navigate The time it takes to direct Internet Explorer to the server login page.
• Login The time it takes to login.
• TasksView The time it takes to go to the Tasks Views page.
• ViewPortfolioOpen The time it takes to open all views for a portfolio.
• ViewHomePage The time it takes to go to the Home page.
• ViewResourcesOpen The time it takes to open all the views for Enterprise
resources.
• ViewResourceAvailabilityOpen The time it takes to open views for enterprise
availability for all resources.
• ViewProjectOpen The time it takes to open an enterprise project in Project
Professional.
• EnterpriseProjectOpenReadWrite The time it takes to open an enterprise project

read/write in Project Professional.
• EnterpriseProjectSave The time it takes to save an enterprise project in Project
Professional.
• Logout The time it takes to log out of Project Professional.
X To install the SmokeTest utility
1. Download the file SmokeTestDownload.exe from the Microsoft Download Center:
http://go.microsoft.com/fwlink/?LinkId=20890.
2. Run the file SmokeTestSetup.msi to install SmokeTest. By default, psHealthMon.exe
will be installed in the \Program Files\Microsoft Office Project Server 2003 Resource
Kit\Toolbox\SmokeTest directory.
3. Make sure you have added the Project Server site you are going to test to the trusted
sites list in Internet Explorer.
Running SmokeTest
We recommend creating a Project Server user account exclusively for use with the
SmokeTest Utility. The user account must have the following attributes:
• Global Permissions
• Log On
• Publish/update/status
• Read Enteprise Global
• View Home
• View Project Center
• View Project View
• View Resource Allocation
• View Resource Center
• The user does not belong to any groups.
• The user belongs to a single category.
• Category Permissions:
• Open Project
• Save Project
• See Enterprise Resource Data
• See Projects in Project Center
• See Projects in Project Views
• The project that the user will open and save must be added to the category.
• The resources the user will view in Resource Center and in Resource Availability must
be added to the category.
• One or more Project Views must be added to the category.
• One or more Resource Center views must be added to the category.
• One or more Project Center views must be added to the category.
Note For more information about permissions, see Appendix C, Project Server Permissions of the
X To run the SmokeTest utility

1. Close all Internet Explorer and Microsoft Office Project Professional 2003 instances.
2. Start the SmokeTest application.
3. In the Server box, type the URL for the Project Server on which you want to run the
SmokeTest utility.
4. In the Login box, type the Project Web Access login you want to use.
5. In the Password box, type the password for the login you are using.
6. In the Project Name box, type the name of the project you saved from Project
Professional. This project will be used when running the Project Professional tests.
7. In the Iterations box, type the number of times you want the test to be executed.
8. Click Execute Test.
The SmokeTest utility will run and the results will be displayed when the application has
completed running the number of iterations you specified.
You can save your settings by choosing Save from the File menu. You can then choose
Open from the File menu the next time you run SmokeTest, and your configuration
settings will be reloaded.
Results Page
The Results page will load automatically after the SmokeTest utility has completed running
the tests. You can also access the Results page from the SmokeTest login page by
choosing View Results from the File menu.
Results are shown for the currently selected run in the “Run Time (s)” column as well as
the average time across all the runs. Values displayed with “0” mean that some error or
failure occurred for that script and run. Failures are not included in average time
calculations. The results are stored in the Results.xml file in your installation directory.
You can select a specific run to view by choosing the run from the View Run list. You can
delete a run by clicking Delete.
When you are finished reviewing the results, click Close to return to the SmokeTest login
screen.
Command Line Interface

The SmokeTest utility can be run from a command prompt using the following syntax:
SmokeTest.exe –S Server -L Login -P <Password> -I <Iterations> -N
<ProjectName> <-Q>
The Server and Login parameters are required. If you do not specify the number of
iterations, SmokeTest will default to one iteration. Optionally, you can include the -Q
option to have SmokeTest run in quiet mode.
You can also run SmokeTest with previously saved configuration information by using the
–C option:
SmokeTest.exe –C
Running SmokeTest as a Scheduled Task

You can run the SmokeTest utility as a Scheduled Task. When adding a scheduled task, you
must use the following syntax when choosing a task to run:
“C:\Program Files\Microsoft Office Project Server 2003 Resource
Kit\Toolbox\Smoketest\SmokeTest.exe” -S Server –L Login –P
<Password> -I <Iterations> -N <ProjectName> -Q
Note You must include the double-quotes.

Or you can use the previously saved configuration by using the –C option:
“C:\Program Files\Microsoft Office Project Server 2003 Resource
Kit\Toolbox\Smoketest\SmokeTest.exe” -C -Q
View Backup and Restore

The View Backup and Restore utility is a command line tool that will back up and restore
the views you create in Project Web Access. Use this tool to move views to a different
Project Server. The following types of views can be backed up and restored to another
server:
• Project views
• Project Center views
• Assignment views
• Resource Center views
• Timesheet views
• Portfolio Analyzer views
For more information about Project Server views, see Chapter 4, Managing Views of the
X To install View Backup and Restore
• Download and run the file ViewBackupDownload.exe from the Microsoft Download
To back up views, run ViewBackup.exe from the command line using the /B parameter:
ViewBackup /B /N filename /S SQL Server name /D PS DB name [/U PS DB
UID] [/P PS DB pwd] [/G] [/T view type] [/V view name]
For example, to back up all views in the ProjectServer database on the SQL Server named
redbird, you would use the following syntax:
ViewBackup /B /N ProjectServerViews.xml /S redbird /D ProjectServer
/U sa /P hello
To restore views, run ViewBackup.exe from the command line using the /R parameter:
ViewBackup /R /N filename /S SQL Server name /D PS DB name [/U PS DB
UID] [/P PS DB pwd] [/O]
For example, to restore the views from the example above to a new database called
NewPSDB on the SQL Server named rockaway, you would use the following syntax:
ViewBackup /R /N ProjectServerViews.xml /S rockaway /D NewPSDB /U sa
/P hello
ViewBackup.exe Command Line Parameters

Parameter Description
/B Backup
/D The name of the Project Server database.
/F Overwrite existing file. Using the /F parameter will cause an existing backup
file to be overwritten.
/I The ID of the view you want to back up.
/N The name of the backup file.
/O Overwrite (restore only). Optional. If the /O parameter is not specified, views

that already exist will be skipped during the restore process.
/P SQL Server password. Optional. Use with the /U parameter. If /U and /P are
not specified, NT Authentication is used.
/R Restore
/S The name of the instance of SQL Server where the Project Server database
is located.
/T View Type (backup only). Optional. Specifies the type of view to back up:
Project = 0
Project Center = 1
Assignment = 2
Resource Center = 3
Time Sheet = 4
When using the /T parameter, you must also specify the /V parameter.
/U SQL Server user name. Optional. Use with the /P parameter. If /U and /P are
not specified, NT Authentication is used.
/V The name of the View you want to back up. Optional. When using the /V
parameter, you must also specify the /T parameter. The value must be
placed in quotes. For example, /V “Resource Summary”
View Effective Rights

The View Effective Rights tool enables Project Server 2003 administrators to more easily
troubleshoot issues with security settings and access control by combining a PDS extension
with a Project Web Access ASP page. This tool enables administrators to identify the
projects or resources to which users have access.
The View Effective Rights Project Web Access page.

Using this tool requires three steps:
• Downloading the file package from the Microsoft Download Center.
• Installing the PDS extension.
• Installing the ASP page.
Download and run the file PDSRightsDownload.exe package from the Microsoft
Download Center (http://go.microsoft.com/fwlink/?LinkId=20898). The download will install
by default to the C:\Program Files\Microsoft Office Project Server 2003 Resource
Kit\Toolbox directory; however, you can choose to download the files to any directory.
Note: If SQL Server and Project Server are installed on different computers, ensure this directory is
shared and that you have access.
Installing the PDS Effective Rights Extension

After download, installing this extension requires three separate procedures:
• Register a DLL on the computer running Project Server 2003.
• Install stored procedures on the computer running SQL Server 2000.
• Modify the registry on the computer running Project Server 2003.
To register the DLL
1. Log on to the computer running Project Server 2003 using the built-in Administrator
account.
2. Open a command prompt and locate the directory into which you downloaded
PDSRights.dll.
3. Type regsvr32 pdsrights.dll and press ENTER.
4. Click OK to confirm the DLL was registered successfully.
To install the stored procedures

The PDS extension requires a number of stored procedures to be installed.
1. Log on to the computer running SQL Server 2000.
2. On the Start menu, point to Programs, point to Microsoft SQL Server, and click
Query Analyzer.
3. In the Connect to SQL Server dialog, type the name of the SQL server where you
will install the stored procedures, select the authentication method, and provide
credentials if necessary. Click OK.
4. On the File menu, click Open.
5. In the Open Query File dialog box, browse to the directory location where you
downloaded the PDS extension files.
6. Click PDSStoredProc.sql, and then click Open.
7. On the Query menu, click Change Database.
8. Select the ProjectServer database, and then click OK.
9. On the Query menu, click Execute.
To update the registry

In order for the PDS to become aware of the extension, an entry into the registry under
needs to be made.
1. Log on to the computer running Project Server 2003
2. Click Start, click Run, type regedit, and then click OK.
3. In the registry editor, navigate to
\HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\MS
Project\WebClient Server\ProjectServer
4. Copy PDSRightsActivate.reg to the Project Server key.
Note You may need to update the value of PDSExtensionEx to match the number of extensions.
Installing the ASP page

Installing the ASP page requires three separate procedures:
• Copy the ASP page to the proper directory on the computer running Project
Server 2003.
• Install stored procedures on the computer running SQL Server 2000.

• Modify an existing stored procedure on the computer running Project Server 2003.
To copy the ASP page
1. Log on to the computer running Project Server 2003.
2. Copy the sec_audit.asp from the download location to the Program Files\Microsoft
Office Project Server 2003\IIS Virtual Root\ADMIN directory.
To install the stored procedures

1. Log on to the computer running SQL Server 2000.
2. On the Start menu, point to Programs, point to Microsoft SQL Server, and click
Query Analyzer.
3. In the Connect to SQL Server dialog, type the name of the SQL server where you
will install the stored procedures, select the authentication method, and provide
credentials if necessary. Click OK.
4. On the File menu, click Open.
5. In the Open Query File dialog box, browse to the directory location where you
downloaded the PDS extension files.
6. Click install.sql, and then click Open.
7. On the Query menu, click Change Database.
8. Select the ProjectServer database, and then click OK.
9. On the Query menu, click Execute.
To update another stored procedure

1. Log on to the computer running Project Server 2003.
2. Using a text editor, such as Microsoft® Notepad, open QyLibStd.txt from the
download location.
3. Open a second instance of the text editor and open QyLibStd.sql from the Program
Files\Microsoft Office Project Server 2003\BIN directory.
4. Copy and paste the contents of QyLibStd.txt into QyLibStd.sql immediately past
line 20023 (using the numbers in the left margin).
5. Save and close QyLibStd.sql.
Using the ASP Page

1. Log on to Project Web Access as an administrator and click Admin.
2. In the left navigation bar, under Actions, click View Effective Rights.
3. Create an effective rights query by selecting drop-down options.
a.Audit. You can select to view security reports by all users, single user’s project
access, single user’s resource access, and global.
b. Object Type. You can define the permission types by user, resource, projects, or
global.
c. Object. You can define the object by user, resource, and project.
d. Permission. You can select all permissions or specific permissions.
4. Click Submit. The query results are displayed.
View Populator Utility

The View Populator utility (View Populator.exe) can be used to publish project plans
without the need to use Project Professional. The View Populator utility places XML files
in your Project Server ViewDrop folder for each project you publish. The Views
Notification Service then publishes the information in the XML files to the view tables in
the database.
To use the View Populator utility, you must have Project Manager or higher permissions
on Project Server. You can use either Windows Authentication or Project Server
Authentication.
The View Populator utility is useful in the following scenarios:
• Disaster recovery of your Project Server deployment If you are recovering your
Project Server database after a system failure, you can use the View Populator utility to
republish your project plans rather than restoring the view tables database from a
database backup.
• Publishing projects that did not publish properly If you have a project that did
not publish properly, or if you have mismatched data between Project Professional and
Project Web Access or the OLAP Cube, you can use View Populator to republish the
view information for that project.
• Troubleshooting the Views Notification Service You can use View Populator to
easily send XML files to the ViewDrop folder without the need to use Project
Professional. This can assist in troubleshooting issues with the View Notification
Service.
X To install the View Populator utility
1. Download and run the file ViewPopulatorDownload.exe from the Microsoft
Download Center: http://go.microsoft.com/fwlink/?LinkId=20888.
2. Run the file Setup.msi to install View Populator. By default, View Populator.exe will be
installed in the \Program Files\Microsoft Office Project Server 2003 Resource
Kit\Toolbox\View Populator directory.
Using the View Populator Utility
Before using View Populator to publish a project, make sure the project is checked in. You
can use View Populator to force a project checkin by selecting the project and then clicking
Checkin Project(s), but you will lose any unsaved data if you do so.
X To publish projects
1. Run View Populator.exe
2. In the Project Server URL box, type the URL to access Project Server.
3. If you are connecting with a Project Server account, type the username and password
for the account you want to use. Otherwise, select the Windows authentication
checkbox to use Windows Authentication.
4. Click Get Projects.
5. In the List of Projects, select the projects you want to publish.
6. Click Publish Project Plan.
The Results box will show the results of the publish operation.
C
Project Server Permissions
This appendix lists all of the Microsoft® Office Project Server 2003 permissions that can
be managed using Microsoft Office Project Web Access 2003. These permissions can be
associated with users, groups, categories, and views, and can be accessed by a user with
permission to log on to Project Web Access as an administrator.
Project Server Category Permissions

Category permissions should be used to control access to a category of objects such as
projects, resources, and models in Project Server. Project Server supports object-level
security by securing collections of objects rather than individual objects. Typically, category
permissions control whether an object is displayed in Project Web Access and Project
Professional and what actions a user can perform on the object. Categories can be defined
on the Manage security section of the Admin center in Project Web Access.
Adjust Actuals
Adjust Actuals is a category permission that allows a Project Web Access user to adjust a
team member’s submitted timesheet entries (actuals). Grant this permission to any member
of your organization who requires the ability to adjust a resource’s timesheet entry.
For example, grant this permission to project managers, resource managers, and financial
managers who need to ensure that the Project Server timesheet reporting can be
synchronized with an external timesheet application like Siebel®.
This permission requires that users:
• Have permissions to a category or group that also has the View Adjust Actuals global
permission.
Approve Timesheets for Resources

Approve Timesheets for Resources is a category permission that allows a user to
approve a team member’s submitted timesheet entries (actuals). Grant this permission to
any member of your organization who requires the ability to approve a resource’s
timesheet.
• Have permissions to the same category as the resource for which they want to approve
timesheets.
• Have permissions to a category that has the Approve Timesheets for Resources
permission.
• Have permissions to a category or group that has the Timesheet Approval
permission.
Note By default, this permission is denied at the organizational level on the Server Configuration
page in Project Web Access.
Assign Resources
Assign Resources is a category permission that determines whether a user can assign or
allocate a given resource to projects. This permission controls the list of available resources
in Team Builder Lite (Project Web Access) or Build Team (Project Professional). Grant
this permission to all project managers and resource managers who need to assign, manage,
or allocate resources.
For example, if you want to add resource R to project P, then you must have permission to
assign resources (Assign Resources) on R, as well as permission to add the resource to
project P (Build Team on Project). In addition, you must have the Assign Resources to
Project Team global permission to use the Build Team feature in Project Professional or
Project Web Access.
• Have the Assign Resource to Project Team global permission in order to use the
Build Team page in Project Web Access.
• Have the Build Team on Project category permission in order to assign a resource in
an existing enterprise project.
• Have the Build Team on New Project global permission in order to assign a
resource in a new enterprise project.
Build Team on Project

Build Team on Project is a category permission that determines whether a user can add
resources to a project that has already been saved to the Project Server database. Grant this
permission to project managers who want to use the Build Team feature in Project
Professional to staff their projects before saving (and publishing) them to the Project
Server database. Or, grant this permission to resource managers who want to use the Build
Team feature in the Project Center of Project Web Access to add resources to a project
that has already been saved to the Project Server database.
• Be granted the See Enterprise Resource Data and Assign Resources category
permissions in order to see resources that are part of the Enterprise Resource Pool in
the Build Team feature in Project Professional and Project Web Access.
• Have permission (at the category level) to access the specific projects and resources
that need to be accessed to build the project team or assign resources.
Create New Task or Assignment

Create New Task or Assignment is a category permission that determines which projects
are available when creating new tasks. Grant this permission to any group of projects that
individual users will be allowed to create new tasks in using the Create a new task page in
Project Web Access.
• Be granted the New Project Task global permission in order to access the Create a
new task page in Project Web Access.
Delete Project
Delete Project is a category permission that allows users of Project Professional to delete a
project saved to the Project Server database from the Open from Microsoft Project
Server dialog box in Project Professional. Grant this permission to members of your
organization to allow them to more closely manage the projects he or she has saved to the
Project Server database from Project Professional or by using the Clean up Project Server
database link in Project Web Access. Before allowing users to delete projects, you should
consider how your organization will recover those projects, should you need to do so.
• Be granted the Open Project category permission on the project that they want to
delete.
Edit Enterprise Resource Data

Edit Enterprise Resource Data is a category permission that allows a project manager to
edit enterprise resource data using Project Professional (checked-out Enterprise Resource
Pool) or a resource manager to edit enterprise resources using Project Web Access
(Resource Center). Grant this permission to project managers and resource managers who
need to make updates to resources that belong to the Enterprise Resource Pool.
Resource managers with this permission will be able to edit enterprise resource data in the
Resource Center in Project Web Access, as well as make updates to cost data, custom
outline code data, custom field data, and other static information related to resources.
Resource managers cannot add or delete resources from the Enterprise Resource Pool in
Project Web Access.
Project managers can add or delete resources from the Enterprise Resource Pool in Project
Professional if they have the New Resource global permission (to add resources) or the
Clean Up Project Server Database global permission (to delete resources). These
permissions are required in addition to the Edit Enterprise Resource Data category
permission.
Note The Project Data Service (PDS) can also be used to create or delete resources in the
Enterprise Resource Pool and to edit enterprise resource data.

• Be granted the See Enterprise Resource Data category permission.
Open Project
Open Project is a category permission that allows a user to open a project from the
Project Server database in read-only or read/write modes using Project Professional, or to
use the Portfolio Modeler feature in Project Web Access or Project Professional. Grant this
permission to any member of your organization who needs to use the Open from
Microsoft Project Server dialog box in Project Professional to open projects that have
been saved to the Project Server database in read-only mode.
Save Project
Save Project is a category permission that allows a user to save projects to the Project
Server database using Project Professional. Grant this permission to all members of your
organization who will be saving projects from Project Professional to the Project Server
database using the Save to Project Server dialog box.
• Be granted the Create Administrative Projects global permission to save the project
as a project that tracks non-project or non-working time using the Save to Project
Server dialog box in Project Professional.
• Be granted the Open Project category permission on any project that needs to be
checked out from the Project Server database.
See Enterprise Resource Data

See Enterprise Resource Data is a category permission that allows a user to view
resources and resource data stored in the Enterprise Resource Pool. Grant this permission
to any user who needs to view resources and resource data stored in the Enterprise
Resource Pool.
Users of the following Project Server features must have this permission:
• Build Team (Project Professional users only. On the Tools menu, select Build Team
from Enterprise.)
• Build Team (Project Web Access users only, Resource Center).
• Resource Center (both Project Professional and Project Web Access users).
See Projects in Project Center

See Projects in Project Center is a category permission that enables a user to access the
Project Center from both Project Professional and Project Web Access. Grant this
permission to any member of your organization who needs to view projects (at the project
level) in the Project Center.
See Projects in Project Views

See Projects in Project Views is a category permission that enables a user to view project
information for a specific project in the Project Center from both Project Professional and
Project Web Access. Grant this permission to project managers and resource managers
who need to view project details in the Project Center. This will allow users to click a
project in the Project Center and view it at the assignment level (or any other defined view).
See Resource Assignments in Assignment Views

See Resource Assignments in Assignment Views is a category permission that enables
a user to view assignment details using assignment views in the Resource Center. Grant this
permission to project managers and resource managers who need to view resource
assignment details in the Resource Center from Project Professional or Project Web
Access.
View Risks, Issues, and Documents

View Risks, Issues, and Documents is a category permission that allows users to view
Windows SharePoint Services Risks, Issues, and Documents areas in Project Web Access
and Project Professional. Grant this permission to any user of Project Professional who
needs to select Documents, Issues, or Risks on the Collaborate menu or any user of
Project Web Access who needs to access the Documents, Issues, or Risks top-level
navigation links.
Project Server Global Permissions

A global permission exists for each activity, or interaction, with Project Server data, or for a
page or group of pages in Project Web Access. Generally, global permissions map to a page
in Project Web Access or a feature in Project Professional. In many cases, global
permissions only allow access to the page or feature; category-level permissions are
required in order to have access to interact with the object.
About Microsoft Office Project Server 2003

About Microsoft Office Project Server 2003 is a global permission that allows a user to
access the About Microsoft Office Project Server 2003 page from the Admin top link in
Project Web Access. Grant this permission to any member of your organization
responsible for tracking Project Server and Project Web Access licensing information.
Assign Resource to Project Team

Assign Resource to Project Team is a global permission that allows a user to use Build
Team in Project Web Access and Project Professional, as well as determine the list of
available resources. Grant this permission to resource managers to allow them to use Build
Team in Project Web Access to add resources to projects that have been saved to the
Project Server database. Grant this permission to a project manager to allow them to use
Build Team in Project Professional to add resources to projects.
• Be granted the Assign Resources category permission in addition to the Assign
Resource to Project Team global permission. The Assign Resources category
permission determines the list of resources available in Build Team in both Project
Professional and Project Web Access.
• Be granted the Build Team on Project category permission. The Build Team on
Project permission determines with which projects Build Team can be used. This
applies to using Build Team in both Project Professional and Project Web Access.
Assign To-Do List Tasks

Assign To-Do List Tasks is a global permission that determines to whom a user can
assign a to-do list task. Grant this permission to any user in your organization who needs to
create and assign a to-do list using the Create a new personal or shared to-do list,
Manage my to-do lists, and To-do list options links in the Project Center in Project
Web Access.
• Be granted the Create and Manage To-Do List global permission in addition to the
Assign To-Do List Tasks global permission in order to view to-do list-related pages
in Project Web Access.
Backup Global
Backup Global is a global permission that allows a user to create a copy of the Enterprise
Global Template as an offline Project template file (MPT) using Project Professional.
Grant this permission to any user who needs to save offline copies of the Enterprise
Global Template using the Enterprise Options option in the Tools menu in Project
Professional. Your organization’s Project Management Office (PMO) should always keep
an offline copy of the Enterprise Global Template.
• Be granted the Save Enterprise Global global permission in addition to the Backup
Global global permission if you want this user to later be able to restore the backed-up
Enterprise Global Template to the Project Server database.
Build Team on New Project

Build Team on New Project is a global permission that determines whether a user can
add resources to a project that has not been saved to the Project Server database. Grant this
permission to project managers who want to use the Build Team feature in Project
Professional to staff their projects before saving (and publishing) them to the Project
Server database.
• Be granted the Assign Resources and See Enterprise Resource Data category
permissions in order to see resources that are part of the Enterprise Resource Pool in
the Build Team feature in Project Professional.
Change Password
Change Password is a global permission that allows a user to change their Project Server
user account password from the home page in Project Web Access. Grant this permission
to users with Project Server user accounts so that they can periodically change their
passwords.
• Be granted the View Home global permission.
Change Work Days

Change Work Days is a global permission that allows a user to send working time updates
to their manager and create exceptions in the Standard Enterprise Calendar. Grant this
permission to most Project Web Access users unless your organization is using
Administrative projects to track non-project and non-working time.
It is recommended that users:
• Not be granted the Create Administrative Projects global permission (your
organization should not use Administrative projects if users are allowed to change their
own working days).
Check In My Projects
Check In My Projects is a global permission that allows a user to check in their projects
on the Check in my projects page available from the Project Center in Project Web
Access. Grant this permission to users in your organization who have permission to check
out projects from the Project Server database.
• Be granted the View Project Center global permission.
• Be granted the Save Project category permission.
Clean Up Project Server Database

Clean Up Project Server Database is a global permission that allows a user to access the
Clean up Project Server Database link in the Admin center in Project Web Access.
Grant this permission to users who need to delete tasks, status reports, projects, resources,
and status updates from the Project Server database. In addition, project managers who
need to delete resources from the Enterprise Resource Pool using Project Professional are
required to have this permission.
Note This permission should only be granted to a small group of users within your organization.
The ability to delete projects, resources, tasks, status reports, and status updates could create
significant problems with Project Server data if performed by the wrong set of users.
Connect to Project Server using Microsoft Project 2002

Connect to Project Server using Microsoft Project 2002 is a global permission that
allows Microsoft Project Professional 2002 to connect to the Project Server 2003 database.
Grant this permission to members of your organization who are using Microsoft Project
Professional 2002 and who need to connect to the Project Server 2003 database.
Users of Microsoft Project Professional 2002 who are allowed to connect to the Project
Server 2003 database will be limited to the same feature set provided in Microsoft Project
Professional 2002. For example:
• There will be no access to the Risks feature from the Collaborate menu.
• There will not be an option to save Administrative projects using the Save to Project
Server dialog box.
• There will not be an option to delete projects in the Open from Microsoft Project
Server dialog box.
• There will be no managed timesheet or protected actuals options.
• There will be no Enterprise Multi-Value Outline Codes available in project plans.
• There will not be a way to propose resources to project assignments.
• Be granted the same set of category and global permissions that your organization
would otherwise assign to Project Professional 2003 users.
Note Users with this permission will be able to perform all functions allowed by Microsoft Project
Professional 2002, even if denied on Project Server 2003 for Project Professional 2003 users. For
example, if you allow Microsoft Project Professional 2002 users to connect to Project Server 2003,
they will be able to assign resources to their projects using Build Team even if this is denied. This is
because Microsoft Project Professional 2002 is not able to validate the new permissions in Project
Server 2003 against the actions they are designed to regulate in Project Professional 2003.
Create Accounts from Microsoft Office Project

Create Accounts from Microsoft Office Project is a global permission that allows a user
to create new Project Server or Windows authenticated resource accounts when publishing
projects to the Project Server database from Project Professional. Grant this permission to
project managers who need to create Project Server or Windows authenticated resources
while working in Project Professional. This permission does not create accounts in the
Enterprise Resource Pool and is denied when enterprise options are enabled.
Create Accounts when Delegating Tasks

Create Accounts when Delegating Tasks is a global permission that allows a user to
create new resource accounts while delegating tasks in projects while using Project
Professional. Grant this permission to project managers who need to add resources that are
not currently part of a project to tasks, or add resources that are not available in the
Enterprise Resource Pool, while assigning resources to tasks in Project Professional. This
permission does not create accounts in the Enterprise Resource Pool and should be denied
if your organization has enabled enterprise options.
Create Accounts when Requesting Status Reports

Create Accounts when Requesting Status Reports is a global permission that allows a
user to create new resource accounts when requesting status reports. Grant this permission
to project managers who need to add resources that are not currently part of a project to
tasks, or add resources that are not available in the Enterprise Resource Pool, while
working on status reports. This permission does not create accounts in the Enterprise
Resource Pool and should be denied if your organization has enabled enterprise options.
Create Administrative Projects

Create Administrative Projects is a global permission that allows a user to select the
Administrative projects option in the Save to Project Server dialog box to save projects
to the Project Server database as administrative projects or to access the Manage
Administrative Projects page in the Project Center in Project Web Access. Grant this
permission to users in your organization who need to create projects that are only used to
track non-working and non-project time. Project managers can use Project Professional to
create Administrative projects, while both project managers and resource managers can use
Project Web Access to manage them.
Note The Administrative projects option in the Save to Project Server dialog box is only available if
the project has not already been saved to the Project Server database.
It is recommended that users:

• Not also be granted the Change Work Days global permission (your organization
should not use allow users to change their own working days when using
Administrative projects).
Create and Manage To-Do List

Create and Manage To-Do List is a global permission that allows a user to access the
Manage my to-do lists and Create a new personal or shared to-do list pages in Project
Web Access. These pages give users the ability to create, modify, delete, or transfer
ownership of a to-do list. Grant this permission to project managers, resource managers,
and members of your organization’s Project Management Office (PMO).
For example, you could grant this permission to a team member who will be out of the
office for an extended period of time. The team member could then create to-do lists that
identify their day-to-day duties, and then assign the list to other members of their
organization who will help cover these duties in their absence.
• Be granted the Assign To-Do List Tasks global permission in order to determine to
whom a user can assign a to-do list task.
Customize Project Web Access

Customize Project Web Access is a global permission that allows a user to access the
Customize Project Web Access pages in the Admin center in Project Web Access. Grant
this permission to users in your organization who need to manage the following areas of
Project Web Access:
• Custom links and custom content on the Project Web Access home page.
• Custom Gantt Chart view color combinations.
• Custom Grouping format color combinations.
• Starting, stopping, or modifying the management settings for the Project Server
Scheduled Process Service.
This permission could be granted to members of your organization who are not Project
Server administrators to help offload some of the less critical day-to-day operations.
Delegate Task
Delegate Task is a global permission that allows a user to delegate an assigned task to
another (existing) user. Grant this permission to members of your organization who need
the ability to delegate task assignments to other resources.
For example, a large project may be run by a single project manager, but actually
implemented by several teams, each with their own team lead. A project manager could
assign the team leads in the project plan, and then the team leads could in turn delegate
each task to individual members of their teams. This example creates an additional layer of
task management within the larger organization, but it can also simplify resource allocation
within projects themselves and make it easier for a project manager to manage large
projects.
Or, if you have a resource that is about to leave on a three-week vacation, and this resource
had this permission, they would be able to assign their tasks directly to other resources
rather than having the project manager check out the project and reassign resources.
• Be a member of a category with the Assign Resources permission.
Go Offline from Project Web Access

Go Offline from Project Web Access is a global permission that allows a user to click the
Go offline link on the Project Web Access home page. Grant this permission to users who
need to be able to track their timesheet and status report information when unable to
access Project Web Access.
For example, users that travel frequently may want to be able to manage their timesheet
and status reports while traveling. The next time they log on to Project Web Access, the
timesheet and status report data they entered while offline will be updated.
Hide Task from Timesheet

Hide Task from Timesheet is a global permission that allows a user to hit X (delete) to
remove a task from their timesheet. Grant this permission to team members so they can
clear tasks from their timesheet that have been completed. A task that is deleted using this
method removes the item from the Project Server database. The task is not deleted from
the actual project plan; it will reappear the next time the project plan is published to the
Integration with External Timesheet System

Integration with External Timesheet System is a global permission that allows a user to
report their actuals on project assignments without using the timesheet included in Project
Web Access. Grant this permission to any user who needs to update their timesheet and is
not using the default timesheet included in Project Web Access.
The Microsoft Office Project Server 2003 Outlook Integration feature is the only default
timesheet management feature that does not use the timesheet included in Project Web
Access. All users who will use the Outlook Integration feature to manage their timesheet
must have this permission.
This global permission is used by the Project Data Service (PDS) to allow calls to the
Project Server database from an external timesheet system. All users who are using a
timesheet other than the one included in Project Web Access must be granted this
permission. The Timesheet API in the PDS allows users to integrate an external timesheet
application with Project Server, including editing assignment data and programmatically
notifying a project manager with updates made by team members when using an external
timesheet system.
Note A project manager will still need to approve a resource’s timesheet entries using Project Web
Access.
This permission supports the following PDS methods in the Timesheet API:
• AssignmentsGet
• AssignmentsSave
• AssignmentsProjectManagerUpdate
Note For more information about these PDS methods, see the Timesheet API chapter in the PDS
Reference for Microsoft Office Project Server that is available in the Microsoft Office Project
Log On
Log On is a global permission that allows a user to connect to Project Server from Project
Professional or to log on to Project Web Access. Grant this permission to any user who is
authorized to connect to Project Server from Project Professional or log on to Project Web
Access.
Manage Enterprise Features

Manage Enterprise Features is a global permission that allows a user to access the
Manage enterprise features page in the Admin center in Project Web Access. Users with
permission to access the Manage enterprise features page can create the OLAP cube for
Portfolio Analyzer, manage versions, and force check-ins of enterprise projects and
enterprise resources. Grant this permission to any member of your organization who is
responsible for OLAP cube creation, managing versions, and keeping track of enterprise
projects and enterprise resources at the day-to-day level within your organization.
For example, if your organization has a Project Management Office (PMO), permission to
access this page could be granted to all members of the PMO or to a custom security
category used to support the needs of your organization’s PMO. By granting permission to
access this page to specific, non-IT administrators, you can offload some of the day-to-day
functions that your Project Server administrators may not have time to manage closely.
Manage Rules
Manage Rules is a global permission that allows a user to access the Update page in
Project Web Access and set rules on how update transactions will be automatically
processed. Grant this permission to project managers, resource managers, or members of
your organization’s PMO office so they can define how they will automatically receive and
accept changes to transactions by their resources.
Manage Security
Manage Security is a global permission that allows a user to access the Manage security
page in Project Web Access to define security categories, security templates, and user
authentication settings. Grant this permission to Project Server administrators or a very
small and closely managed group of people.
This page allows users to change Project Server security settings, create security categories
and security templates, specify how user accounts should be created, and define the types
of accounts (Project Server, Windows, or Mixed) that are available for the authentication of
users when accessing Project Server using Project Professional or Project Web Access.
Changes to settings on this page, once you have begun using Project Server in your
organization, should be carefully managed and (ideally) infrequent.
Manage Server Configuration

Manage Server Configuration is a global permission that allows a user to access the
Server configuration page in the Admin center in Project Web Access. Users with
permission to access the Server configuration page can enable or disable enterprise
features, manage organizational permissions, and create custom menus (both top-level and
side-pane) in Project web Access. Grant this permission to Project Server administrators or
a very small and closely managed group of people.
Manage Status Report Requests

Manage Status Report Requests is a global permission that allows a user to access the
Request a status report link on the Project Web Access Status Reports center and to view
team reports. Grant this permission to any member of your organization who needs to
create status report requests and view team reports, usually project managers, resource
managers, team leads, and members of your organization’s PMO office.
• Be granted the View Status Report List permission.
Manage Task Changes

Manage Task Changes is a global permission that allows project managers or resource
managers to access the Updates center in Project Web Access and get task updates, and
view, accept, or reject a resource’s task transactions. Grant this permission to any project
manager, resource manager, or member of your organization’s PMO who is responsible for
approving task updates. Resource managers may also use this to track non-working time
that is saved in an Administrative project.
Manage Users and Groups

Manage Users and Groups is a global permission that allows a user to access the
Manage users and groups page in the Admin center in Project Web Access. Users with
this permission will be able to add, modify, or delete Project Server users and manage
Project Server security groups. Grant this permission to members of your organization
who are Project Server administrators. Only a small group of people should have
permission to access this set of pages.
Manage Views
Mange Views is a global permission that allows a user to access the Manage views page
in the Admin center in Project Web Access. Users with permission to access this page will
be able to add, modify, or delete Project, Project Center, Resource Center, Assignment, and
Portfolio Analyzer views, as well as modify Timesheet views. Grant this permission to
project managers, resource managers, and members of your organization’s PMO office so
they can create project data views for users to access in Project Web Access and Project
Professional. It is important to remember that if your organization is allowing project
managers to create custom fields at the project level, then each project may require its own
unique view. The number of projects in this type of environment may be too numerous for
your IT administrator team; offloading this work to the people in your organization that
work at the project level on a day-to-day basis is one way of distributing the workload of
managing views.
Manage Windows SharePoint Services

Manage Windows SharePoint Services is a global permission that allows a user to create
and delete Windows SharePoint Service sites, update the list of authorized users, and
maintain the servers running Windows SharePoint Services from the Admin center in
Project Web Access. Grant this permission to members of your organization who are
administrators for Project Web Access and/or administrators for the servers running
Windows SharePoint Services and SharePoint Portal Server.
• Be granted administrative privileges to all of the servers running Project Server,
Windows SharePoint Services, and SharePoint Portal Server.
New Project
New Project is a global permission that allows a user to add a new project to the Project
Server database using Project Professional or the Project Data Service (PDS). Grant this
permission to any user in your organization who needs to publish or save new projects to
the Project Server database from Project Professional using the Save to Project Server
dialog box or the Import Projects Wizard or create new projects in the Project Server
database using the PDS.
New Project Task

New Project Task is a global permission that allows users to access the Create a new
task page in the Tasks center of Project Web Access. Grant this permission to any member
of your organization who needs to create new tasks in projects that have been published to
the Project Server database. Users with this permission will be able to use the Create a
new task page in Project Web Access to create tasks that can be inserted into any available
project.
The list of available projects for a user to create new tasks in is determined by the Create
New Tasks or Assignment category permission. A user with the New Project Task
permission must also have access to the projects to which they want to add a task.
New Resource
New Resource is a global permission that allows a project manager to add new resources
to the Enterprise Resource Pool using Project Professional or the Project Data Service
(PDS). Grant this permission to any member of your organization who needs to create new
enterprise resources in the Project Server database.
Note If your organization is using the Active Directory synchronization feature, you may want to
consider denying this permission to all non-IT administrators in your organization.
New Task Assignment

New Task Assignment is a global permission that allows users to access the Assign
myself to an existing task page in the Tasks center of Project Web Access. Grant this
permission to any member of your organization who needs to create new assignments on
existing tasks in projects that have been published to the Project Server database. Users
with this permission will be able to use the Assign myself to an existing task page in
Project Web Access to create assignments to themselves on tasks in any project the user
has access to.
The list of available projects for a user to create new tasks is determined by the Create
New Tasks or Assignment category permission. A user with the New Project Task
permission must also have access to the projects to which they want to assign themselves
to a task.
Open Project Template

Open Project Template is a global permission that allows a user to open an Enterprise
Project Template from the Project Server database using Project Professional. Grant this
permission to all users in your organization who will be using Project Professional to create
and manage projects that are based on Enterprise Project Templates.
• Be granted the New Project global permission in order to save the project to the
Project Server database as an actual project.
Publish To-Do List to All Users

Publish To-Do List to All Users is a global permission that allows a user to make a to-do
list available to users in Project Web Access. Grant this permission to all users in your
organization who will need to be able to make their to-do list available to any Project Web
Access user.
• Be granted the Create and Manage To-Do List global permission in order to access
the Create a new personal or shared to-do list page in Project Web Access.
Publish / Update / Status

Publish / Update / Status is a global permission that allows a project manager to assign
tasks, change tasks, and request a task’s status when a project is published using the
Collaborate menu (point to Publish, and then select All Information, New and
Changed Assignments, Project Plan, or Republish Assignments) to the Project Server
database from Project Professional. Grant this permission to all users in your organization
who will be using Project Professional to collaborate using Project Server.
• Be granted the Open Project category permission.
Read Enterprise Global

Read Enterprise Global is a global permission that allows a user to load the Enterprise
Global Template when connecting Project Professional to the Project Server database.
Grant this permission to all users in your organization who will be using Project
Professional to connect to the Project Server database.
Save Baseline
Save Baseline is a global permission that allows a user to save a baseline or clear a baseline
associated with an enterprise project published to the Project Server database. Grant this
permission to project managers who need to save baselines in their projects. Baselines are
saved using the Tools menu in Project Professional. On the Tools menu, point to
Tracking, and then select Save Baseline or Clear Baseline.
One alternative to using baselines is to create an enterprise version called Baseline that
project managers can use to save a version of a project plan after initial resource creation,
but before progress is reported on tasks. Later, this version can be used to compare against
milestone or completed versions of the project.
Save Enterprise Global

Save Enterprise Global is a global permission that allows a user to check out, modify, and
save the Enterprise Global Template to the Project Server database from Project
Professional. Grant this permission to users of Project Professional who need to be able to
choose the Tools menu, point to Enterprise Options, and select Open Enterprise
Global.
This permission should only be granted to a small group of people in your organization;
either project managers, members of your organization’s PMO, or Project Server
administrators.
Users with this permission should be aware that if they also have the Backup Global
global permission, there is the potential to back up the Enterprise Global Template, and
then later inadvertently save the backed-up Enterprise Global Template over the current
Enterprise Global Template. This is a risk, but can be easily managed by users aware of this
scenario.
Save Project Template

Save Project Template is a global permission that allows a user to create and save a
project as an Enterprise Project Template from Project Professional to the Project Server
database. Grant this permission to members of your organization who are tasked with
creating Enterprise Project Templates. When a user saves a project to the Project Server
database for the first time, the option to select Template (as opposed to Project) from the
Type drop-down list in the Save to Project Server dialog box is enabled.
• Be granted the Assign Resources and See Enterprise Resource Data category
permissions in addition to this permission if they are also responsible for adding
Generic resources to the Enterprise Project Template.
Set Personal Notifications

Set Personal Notifications is a global permission that allows a user to access the Alert
me about my tasks and status reports link on the Project Web Access home page. Grant
this permission to any user you want to be able to sign up for e-mail notifications and
reminders related to tasks and status reports.
Set Resource Notifications

Set Resource Notifications is a global permission that allows a user to access the Alert
me about my resources on tasks and status reports link on the Project Web Access
home page. Grant this permission to any resource manager or project manager you want to
be able to sign up for e-mail notifications and reminders related to their resource’s tasks
and status reports.
Submit Status Report

Submit Status Report is a global permission that allows a user to access the Submit a
status report link on the Status Reports center in Project Web Access. Grant this
permission to any user of Project Web Access who needs to be able to submit status
reports.
• Be granted the View Status Reports List global permission.
Timesheet Approval
Timesheet Approval is a global permission that allows resource managers to approve
team member’s timesheets in Project Web Access. Grant this permission to resource
managers who need to access the Approve Timesheets for Resources page in Project
Web Access.
• Be granted the Approve Timesheets for Resources category permission.
Note This permission is denied at the organizational level by default on the Server Configuration
User Defined
User Defined is a set of custom global permissions that allow you to customize access to
specific areas of Project Web Access and Project Professional. You cannot use the User
Defined permissions upon installation; these permissions require customization in order to
be used.
Note For more information about using these permissions, see the Microsoft Office Project
View Adjust Actuals

View Adjust Actuals is a global permission that allows a user to access the Adjust
Actuals page in Project Web Access. Grant this permission to any category of users who
need to adjust timesheet entries in your organization, for example some project managers,
resource managers, or members of your organization’s PMO office.
View Adjust Actuals only determines access to the Adjust Actuals page in Project Web
Access. The Adjust Actuals category permission determines which timesheets will be
available for adjustment. If users are not also granted the Adjust Actuals category
permission, they will be able to view the Adjust Actuals page in Project Web Access, but
will not be able to access or adjust any assignment data.
• Be granted the Adjust Actuals category permission.
View Assignments View

View Assignments View is a global permission that allows a user to access the View
resource assignments link from the Resource Center in Project Web Access. Grant this
permission to any category of users who need to view assignment data in Project Web
Access.
View Documents
View Documents is a global permission that allows a user to view the Documents center
in Project Web Access or from the Collaborate menu in Project Professional. Grant this
permission to any category of users who need to create, update, or delete project-related
documents, or link to tasks in any project-related site the user has permission to view.
• Be granted the View Risks, Issues, and Documents category permission.
View Home
View Home is a global permission that allows a user to view the Project Web Access
home page. Grant this permission to any category of users who need to access the Project
Web Access home page.
View Issues
View Issues is a global permission that allows a user to view the Issues center in Project
Web Access or from the Collaborate menu in Project Professional. Grant this permission
to any category of users who need to add or update project-related issues, or link to tasks
or documents in any project-related site the user has permission to view.
View Models
View Models is a global permission that allows a user to use Portfolio Modeler in Project
Web Access or Project Professional to create, modify, open, analyze, delete, and unlock
models. Grant this permission to any user who needs to access the Model projects with
Portfolio Modeler link in the Project Center in Project Web Access, or select Portfolio
Modeler on the Collaborate menu in Project Professional.
• Be granted the Open Project permission in order to load the data in a project plan
into the Portfolio Modeler.
View Portfolio Analyzer

View Portfolio Analyzer is a global permission that allows a user to view the Portfolio
Analyzer using Project Web Access or Project Professional. Grant this permission to users
who need to access Portfolio Analyzer in Project Web Access by clicking the Analyze
projects in Portfolio Analyzer link from the Project Center, or in Project Professional by
selecting Portfolio Analyzer on the Collaborate menu.
View Project Center

View Project Center is a global permission that allows users to access the Project Center
from Project Web Access or Project Professional. Grant this permission to users who need
to view the Project Center in Project Web Access by clicking the Projects link in the top-
level navigation, or in Project Professional by selecting Project Center on the Collaborate
menu.
• Be granted the See Enterprise Project Data category permission.
View Project View

View Project View is a global permission that allows a user to access project views in
Project Web Access. Grant this permission to users who need to drill down into project
details using the Project Center in Project Web Access or Project Professional.
View Resource Allocation

View Resource Allocation is a global permission that allows a user to access the View
Resource Availability page to view resource allocation data in Project Web Access. Grant
this permission to users in your organization who need to view resource availability in
Project Web Access.
View Resource Center

View Resource Center is a global permission that allows users to access the Resource
Center from Project Web Access or Project Professional and view resource allocation data.
Grant this permission to users who need to view the Resource Center in Project Web
Access by clicking the Resources link in the top-level navigation, or in Project
Professional by selecting Resource Center on the Collaborate menu.
View Risks
View Risks is a global permission that allows a user to view the Risks center in Project
Web Access or from the Collaborate menu in Project Professional. Grant this permission
to any category of users who need to add or update project-related risks.
View Status Report List

View Status Report List is a global permission that allows a user to view sent status
reports stored in the Status Reports Archive in Project Web Access, plus view the
Miscellaneous Reports page to view all messages that were either forwarded to the user,
not requested, or cc’d to the user. Grant this permission to any member of your
organization who needs to view information in the Status Reports center in Project Web
Access.
• Be granted the Submit Status Reports, Create Accounts when Requesting Status
Reports, or Manage Status Reports Request global permissions (depending on the
user’s role).
View Timesheet
View Timesheet is a global permission that allows a user to view the Timesheet in Project
Web Access and report their progress against project assignments. Grant this permission to
any team member or team lead who needs to report his or her hours using a timesheet that
is tracked within (or related to) the Project Server timesheet.
• Be granted the Hide Task from Timesheet or Timesheet Approval permissions
(depending on his or her role).
Project Server Organizational Permissions

Organizational permissions are identical to global and category permissions. They can be
used to allow or deny access to all Project Server users for a particular feature in Project
Professional or Project Web Access. Organizational permissions can only be allowed or
denied by a Project Server administrator with permission to access the Server
configuration page in the Admin center of Project Web Access. Organizational
permissions are listed in the grid under Select the features that you want to make
available to users in Project Web Access. Access to this page should be restricted only
to Project Server administrators.
The list of organizational permissions is identical to the global and category permissions
described above. Only five organizational permissions are denied as a default setting for
Project Server:
• Create Accounts when Requesting Status Reports
• Create Accounts when Delegating Tasks
• Create Accounts from Microsoft Office Project
• Approve Timesheets for Resources
• Timesheet Approval
D
Project Server Default Settings
This appendix documents the default security settings for Microsoft® Office Project
Server 2003 users, security groups, and security categories, including the security categories,
views, users, and groups they are associated with.
Note Default security settings for the default security templates in Project Server are identical to
the settings in the default security category with the same name.
Users
The following section describes the default settings for the default Project Server
Administrator user account.
Administrator
The administrator account is the only user account available upon completion of Project
Server setup. The administrator account is active, uses Project Server authentication, and
belongs to the My Organization security category.
The default category permission settings for the Administrator are outlined in the following
table:
Category Permissions Allow Deny
Adjust Actuals 5 □
Approve Timesheets for Resources 5 □
Assign Resources 5 □

Build Team on Project 5 □
Create New Task or Assignment 5 □
Delete Project 5 □
Edit Enterprise Resource Data 5 □
Open Project 5 □
Save Project 5 □
See Enterprise Resource Data 5 □
See Projects in Project Center 5 □
See Projects in Project Views 5 □
See Resource Assignments in Assignment Views 5 □
View Risks, Issues, and Documents 5 □
The default group permission settings for the administrator account are outlined in the
following table:
Group Permissions Allow Deny
About Microsoft Office Project Server 2003 5 □
Assign Resource to Project Team 5 □
Assign To-Do List Tasks 5 □
Backup Global 5 □
Build Team on New Project 5 □
Change Password 5 □
Change Work Days 5 □
Check In My Projects 5 □
Clean Up Project Server Database 5 □
Connect to Project Server Using Microsoft Project 2002 5 □

Create Accounts from Microsoft Office Project 5 □
Create Accounts when Delegating Tasks 5 □
Create Accounts when Requesting Status Reports 5 □
Create Administrative Projects 5 □
Create and Manage To-Do List 5 □
Customize Project Web Access 5 □
Delegate Task 5 □
Go Offline from Project Web Access 5 □
Hide Task from Timesheet 5 □
Integration with External Timesheet System 5 □
Log On 5 □
Manage Enterprise Features 5 □
Manage Rules 5 □
Manage Security 5 □
Manage Server Configuration 5 □
Manage Status Report Request 5 □
Manage Task Changes 5 □
Manage Users and Groups 5 □
Manage Views 5 □
Manage Windows SharePoint Services 5 □
New Project 5 □
New Project Task 5 □
New Resource 5 □
New Task Assignment 5 □

Open Project Template 5 □
Publish To-Do List to All Users 5 □
Publish / Update / Status 5 □
Read Enterprise Global 5 □
Save Baseline 5 □
Save Enterprise Global 5 □
Save Project Template 5 □
Set Personal Notifications 5 □
Set Resource Notifications 5 □
Submit Status Report 5 □
Timesheet Approval 5 □
User Defined 5 □
View Adjust Actuals 5 □
View Assignments View 5 □
View Documents 5 □
View Home 5 □
View Issues 5 □
View Models 5 □
View Portfolio Analyzer 5 □
View Project Center 5 □
View Project View 5 □
View Resource Allocation 5 □
View Resource Center 5 □
View Risks 5 □

View Status Report List 5 □
View Timesheet 5 □
Groups
The following sections describe the default settings for Project Server security categories.
Administrators
The Administrators security group belongs to the My Organization security category by
default. The default category permission settings for the Administrators security group are
outlined in the following table:
Open Project 5 □
Save Project 5 □
The default group permission settings for the Administrators security group are outlined in
the following table:
Backup Global 5 □
Clean Up Project Server Database 5 □
Connect to Project Server Using Microsoft Project 2002 5 □
Delegate Task 5 □
Log On 5 □
Manage Rules 5 □

Manage Security 5 □
Manage Server Configuration 5 □
Manage Users and Groups 5 □
Manage Views 5 □
New Project 5 □
New Resource 5 □
Save Baseline 5 □
User Defined 5 □

View Home 5 □
View Issues 5 □
View Models 5 □
View Risks 5 □
Executives
The Executives security group belongs to the My Organization security category by default.
The default category permission settings for the Executives security group are outlined in
Adjust Actuals □ □
Approve Timesheets for Resources □ □
Assign Resources □ □
Build Team on Project □ □
Create New Task or Assignment □ □
Delete Project □ □

Edit Enterprise Resource Data □ □
Open Project □ □
Save Project □ □
The default group permission settings for the Executives security group are outlined in the
following table:
About Microsoft Office Project Server 2003 □ □
Assign Resource to Project Team □ □
Backup Global □ □
Build Team on New Project □ □
Change Work Days □ □
Clean Up Project Server Database □ □
Connect to Project Server Using Microsoft Project 2002 □ □
Create Accounts from Microsoft Office Project □ □
Create Accounts when Delegating Tasks □ □
Create Accounts when Requesting Status Reports □ □

Create Administrative Projects □ □
Customize Project Web Access □ □
Delegate Task □ □
Hide Task from Timesheet □ □
Log On 5 □
Manage Enterprise Features □ □
Manage Rules □ □
Manage Security □ □
Manage Server Configuration □ □
Manage Task Changes □ □
Manage Users and Groups □ □
Manage Views □ □
Manage Windows SharePoint Services □ □
New Project □ □
New Project Task □ □
New Resource □ □
New Task Assignment □ □
Open Project Template □ □
Publish / Update / Status □ □

Read Enterprise Global □ □
Save Baseline □ □
Save Enterprise Global □ □
Save Project Template □ □
Timesheet Approval □ □
User Defined 5 □
View Adjust Actuals □ □
View Home 5 □
View Issues 5 □
View Models 5 □
View Risks 5 □
View Timesheet □ □
Portfolio Managers
The Portfolio Managers security group belongs to the My Organization security category
by default. The default category permission settings for the Portfolio Managers security
group are outlined in the following table:
Open Project 5 □
Save Project 5 □
The default group permission settings for the Portfolio Managers security group are
Assign To-Do List Tasks □ □

Create and Manage To-Do List □ □
Log On 5 □
Manage Status Report Request □ □

Manage Views 5 □
New Project 5 □
New Resource 5 □
Publish To-Do List to All Users □ □
Submit Status Report □ □
User Defined 5 □
View Home 5 □
View Issues 5 □
View Models 5 □

View Risks 5 □
View Status Report List □ □
Project Managers
The Project Managers security group belongs to the My Organization and My Projects
security categories by default. The default category permission settings for the Project
Managers security group are outlined in the following table:
See Projects in Project Center □ □

See Projects in Project Views □ □
See Resource Assignments in Assignment Views □ □
View Risks, Issues, and Documents □ □
The default group permission settings for the Project Managers security group are outlined
in the following table:
Delegate Task 5 □

Log On 5 □
Manage Rules 5 □
New Project 5 □
Save Baseline 5 □

User Defined 5 □
View Home 5 □
View Issues 5 □
View Models □ □
View Portfolio Analyzer □ □
View Resource Allocation □ □
View Resource Center □ □
View Risks 5 □
Resource Managers
The Resource Managers security group belongs to the My Direct Reports, My
Organization, My Projects, and My Resources security categories by default. The default
category permission settings for the Resource Managers security group are outlined in the
following table:

See Enterprise Resource Data □ □
The default group permission settings for the Resource Managers security group are

Log On 5 □
New Project □ □

New Resource 5 □
User Defined 5 □
View Home 5 □
View Issues 5 □
View Models □ □

View Risks 5 □
Team Leads
The Team Leads security group belongs to the My Projects security category by default.
The default category permission settings for the Team Leads security group are outlined in
The default group permission settings for the Team Leads security group are outlined in

Log On 5 □

New Project □ □
User Defined 5 □

View Home 5 □
View Issues 5 □
View Models □ □
View Project Center □ □
View Project View □ □
View Risks 5 □
Team Members
The Team Members security group belongs to the My Tasks security category by default.
The default category permission settings for the Team Members security group are outlined

The default group permission settings for the Team Members security group are outlined

Log On 5 □
Manage Status Report Request □ □
New Project □ □

Set Resource Notifications □ □
User Defined 5 □
View Assignments View □ □
View Home 5 □
View Issues 5 □
View Models □ □
View Risks 5 □
Categories
The following sections describe the default settings for Project Server security categories.
My Direct Reports
The Resource Managers security group is assigned the My Direct Reports security category
by default. No views are assigned to the My Direct Reports security category. The default
category permission settings for the My Direct Reports security category are outlined in the
following table:
My Organization
The Project Server Administrator user account and the Administrators, Executives,
Portfolio Managers, Project Managers, and Resource Managers security groups are assigned
the My Organization security category by default. The following views are assigned to the
My Organization security category:
• Project Center views: Cost, Earned Value, Summary, Tracking, and Work.
• Project views: Assignments Cost, Assignments Detail, Assignments Earned Value,
Assignments Summary, Assignments Tracking, Assignments Work, Resources Cost,
Resources Earned Value, Resources Summary, Resources Work, Tasks Cost, Tasks
Detail, Tasks Earned Value, Tasks Leveling, Tasks Schedule, Tasks Summary, Tasks
Top-Level, Tasks Tracking, and Tasks Work.
• Assignment views: Summary.
• Resource views: Resources Summary.
• Portfolio Analyzer views: None.
The default category permission settings for the My Organization security category are
Open Project 5 □
Save Project 5 □
My Projects
The Project Managers, Resource Managers, and Team Leads security groups are assigned
the My Projects security category by default. The following views are assigned to the My
Projects security category:
• Project Center views: Cost, Earned Value, Summary, Tracking, and Work.
• Project views: Assignments Cost, Assignments Detail, Assignments Earned Value,
Assignments Summary, Assignments Tracking, Assignments Work, Resources Cost,
Resources Earned Value, Resources Summary, Resources Work, Tasks Cost, Tasks
Detail, Tasks Earned Value, Tasks Leveling, Tasks Schedule, Tasks Summary, Tasks
Top-Level, Tasks Tracking, and Tasks Work.
The following rules can be applied to the My Projects security category:
• Allow users in this category to view all projects they manage.
• Allow users in this category to view all projects in which they are a team member.
• Allow users in this category to view all projects assigned to resources that they manage.
• Allow users in this category to view their own information.
• Allow users in this category to view information for all resources that they manage.
• Allow users in this category to view their own models.
• Allow users in this category to view models created by resources that they manage.
The default category permission settings for the My Projects security category are outlined

Open Project 5 □

Save Project 5 □
My Resources
The Resource Managers security group is assigned the My Resources security category by
default. The following views are assigned to the My Resources security category:
• Project Center views: None.
• Project views: None.
• Assignment views: None.
The following rules can be applied to the My Resources security category:
• Allow users in this category to view information for all resources that they manage.
The default category permission settings for the My Resources security category are


My Tasks
The Team Members security group is assigned the My Tasks security category by default.
The following views are assigned to the My Tasks security category:
• Project Center views: None.
• Project views: None.
• Resource views: None.
The following rules can be applied to the My Projects security category:
• Allow users in this category to view all projects in which they are a team member.
• Allow users in this category to view their own information.
The default category permission settings for the My Tasks security category are outlined in


Organization
Organization permissions are only accessible from the Server Configuration page in
Project Web Access. Allowing or denying organization permissions will make that feature
available or unavailable to all Project Server, Project Professional, and Project Web Access
users even if they have been granted permission to the feature by a category or group.
Note The following table lists organization permissions in the order in which they appear in the grid
under Select the features that you want to make available to user in Project Web Access on the
Server configuration page in Project Web Access.
Organization Permissions Allow Deny

Create Accounts from Microsoft Office Project □ 5
Create Accounts when Delegating Tasks □ 5
Create Accounts when Requesting Status Reports □ 5

Clean up Project Server database 5 □
Manage enterprise features 5 □
Manage security 5 □

Manage users and groups 5 □
Manage views 5 □
View Issues 5 □
View Risks 5 □
Assign Resource 5 □
Backup Global 5 □
Check in my projects 5 □
New Project 5 □
New Resource 5 □
Open Project 5 □
Save Baseline 5 □
Save Project 5 □
Save Enterprise Resource Data 5 □

Connect to Project Server using Microsoft Project 5 □
User Defined 5 □
View Home 5 □
Approve Timesheets for Resources □ 5

Delegate Task 5 □
Timesheet Approval □ 5
Manage Rules 5 □

View Models 5 □
View Resource View 5 □
E
Project Server Spooler
Microsoft® Office Project Professional 2003 users can publish project and resource data to
Microsoft Office Project Server 2003. When information is published to Project Server
from Project Professional, the Project Server Spooler queues the messages to the Project
Server database and listens for confirmation from the Project Server database.
Activating the Project Server Spooler

The Project Server Spooler is loaded every time you start Project Professional and connect
to Project Server. An icon is placed in the Microsoft Windows® taskbar and remains there
until Project Professional is closed.
The Project Server Spooler behaves in a similar way to a familiar print spooler and, in the
majority of cases, users will not even be aware that the Project Server Spooler is active.
There are three ways that you can view the Project Server Spooler:
• Double-click the icon when it appears in the Windows taskbar.
• Right-click the icon when it appears in the Windows taskbar and select Open Project
Server Spooler.
• Select Yes when you receive a Microsoft Project Server Spooler Alert dialog box.
When the Project Server Spooler is activated, the Microsoft Office Project Spooler dialog
box opens.
The Microsoft Office Project Server Spooler dialog box.

If an error occurs when information is published, a red exclamation mark will appear next
to the Project Server Spooler icon in the Windows taskbar:
• If the error initially occurs during publishing of assignment data, a dialog box is
displayed with options to Undo, Retry, or Cancel the publishing action.
• If an error occurs while publishing a project plan, a dialog box is displayed with
options to Retry or Cancel.
• If both publishing of assignment data and publishing a project plan are associated with
the same error message, such as an error caused by the Publish All Information
action, then a dialog box is displayed with options to Undo, Retry, or Cancel.
With any alert dialog box, you will also have the option to click Show Details to open a
text version of the associated error message.
Using the Project Server Spooler Dialog Box

When the Project Server Spooler is active, you have the following options within the
Project Server Spooler:
• File Select Exit to close the Project Server Spooler.
• View You can sort all Project Server Spooler alerts by either Newest First or Oldest
First.
• Actions If you receive a Project Server Spooler alert, you can try to address the cause
of the alert, select the alert and then click Retry, or you can select the alert and click
Undo to cancel the action.
When you send a message that contains data, the Project Server Spooler keeps the
message until it is sent correctly. The following describes the difference between
choosing Undo and Retry:
• Undo If you click Undo, the Project Server Spooler will re-open Project
Professional and will have Project Professional revert to the state before the
message was sent.
• Retry If you click Retry, the Project Server Spooler will submit the same message,
whether or not Project Professional is open.
In general, if you have received a Project Server Spooler error, you should choose
Undo instead of Retry because Project Professional assumes that communication to
Project Server using the Project Server Spooler will be successful; if not, you will
receive the error message, but Project Professional will not. Therefore, if you get an
error message and simply click Retry, Project Professional will believe that the message
has already been sent correctly.
Note If you are unable to Undo or Retry a Project Server Spooler publish action, simply
close the Project Server Spooler.
• Help To learn more about the Project Server Spooler, click About Microsoft Project
Server Spooler.
Resolving Project Server Spooler Errors

Errors received during publish operations to the Project Server database from Project
Professional are displayed in the Microsoft Office Project Server Spooler dialog box.
Each error identified by the Project Server Spooler will include the following information:
• Message Type The publishing operation that failed.
• Error A short description of the error and the error code.
• Time The time of the error.
• Project File The name of the file associated with the error.
• Server The path name for the Project Server interacting with Project Professional at
the time of the error.
• Manager The resource running Project Professional at the time of the error.
• Affected User Account(s) The user account or user accounts affected by or causing
the error.
Project Server Spooler Errors

A variety of errors can be reported in the Project Server Spooler. The most common
errors, plus descriptions and recommendations, are described below. Project Server
Spooler errors are listed in numerical order by error code, for example 0x8c040003,
0x8c04000d, etc. The error code can be found at the beginning of each Project Server
Spooler error description.
Note DATABASE and SYSTEM ERROR errors do not share the same pattern as the rest of the
Project Server Spooler errors. For these types of errors, you will need to look in the Event Log for
Project Server to help determine the cause of the error.
Generic error during database access or update

(0x8c040003) The Project Server Scheduled Process Service failed to connect to the
Possible Causes
• The settings on the server running Project Server are incorrect.
• There is a (temporary) database problem on the server hosting the Project Server
database.
• There is a general (temporary) system or services problem.
X To resolve this Project Server Spooler error
• The Project Server administrator should ensure that all Project Server services are
functioning correctly. Any Project Server service that is not functioning correctly must
be restarted. In some cases, the server running Project Server will need to be restarted.
• Analyze the Event Log on the server running Project Server to help determine which
services may need to be restarted.
• When finished, retry the publishing operation that failed.
Data corruption in Project Server Database

(0x8c040004) The MSP_WEB_ADMIN or MSP_WEB_RESERVED_DATA tables have
been corrupted, or contain more than one record.
• The Project Server administrator should restore the records in the
MSP_WEB_ADMIN and/or the MSP_WEB_RESERVED_DATA tables.
MSP_WEB_ADMIN table not initialized

(0x8c040005) The MSP_WEB_ADMIN table has been corrupted or contains more than
one record.
• The Project Server administrator should restore the record in the
MSP_WEB_ADMIN table.
Invalid Resource Name

(0x8c04000b) The name of the resource involved with a publishing operation is invalid.
Possible Causes
• The name of the resource involved in a publishing operation is empty, contains spaces,
or contains invalid characters (a list separator, for example).
• Verify that the resource names involved in a publishing operation are valid. Fix all
invalid resource names.
Domain validation of Windows account failed

(0x8c04000c) The Windows account used by a publishing operation failed to validate with
Project Server.
Possible Causes
• The Windows account has the wrong domain or user name.
• The domain is unavailable for user validation at the time of the publishing operation.
• Verify that the domain and user names are correct and that the domain is available.
Resource already exists
(0x8c04000d) A resource account already exists in the Project Server database. Duplicate
resource accounts are not allowed.
Possible Causes
• The information used by a user account associated with a publishing operation already
exists for another user in the Project Server database.
• Check the MSP_WEB_RESOURCES table in the Project Server database for duplicate
resources.
• In Project Professional, point to Tools and select Options to open the Options dialog
box. On the General tab, ensure that the resource does not conflict with an existing
Windows or Project Server user account in Project Server.
• You can add the Windows User Account field to the Resource Sheet view in Project
Professional. This will help to identify the resource names and minimize the risk of
saving duplicate resources.
Windows authentication only

(0x8c040014) If Project Server is set to allow only Windows authentication, this error will
be generated when adding Project Server user accounts is attempted.
Possible Causes
• Project Server is set to accept Windows authentication only.
• If your organization requires that non-Windows authenticated users be able to log on
to Project Server using Project Professional, either set the authentication method to
Project Server or Mixed.
Project Server authentication only

(0x8c040015) If Project Server is set to allow only Project Server user authentication, this
error will be generated when adding Windows user accounts is attempted.
Possible Causes
• Project Server is set to accept Project Server authentication only.
• If your organization requires that non-Project Server authenticated users should be
allowed to log on to Project Server using Project Professional, either set the
authentication method to Windows or Mixed.
All authentication types disallowed

(0x8c040016) Both Windows and Project Server user accounts are unable to authenticate
to the server running Project Server.
Possible Causes
• There has been a database corruption error. Contact your Project Server administrator
and/or check the Project Server Event Viewer to determine the error.
• The Project Server administrator should restore the correct value for user
authentication in the WADMIN_AUTHENTICATION_TYPE field in the
MSP_WEB_ ADMIN table in the Project Server database.
Manager not allowed to create a new account

(0x8c040017) You will get this error if you attempt to create a duplicate user account or a
user account that is not specified correctly. This error can also occur when you attempt to
publish projects to Project Server from Project Professional while in offline mode (not
connected to Project Server).
Possible Causes
• The domain\user name combination for the resource is specified incorrectly.
• Double-check that you have specified the correct domain\user name combination for
the resource
• Log on to Project Web Access as an administrator. Click Admin, then click Manage
Organization. Allow the Create Manager Accounts from Microsoft Project and
Create Accounts from Microsoft Project permissions. Close Project Professional.
Restart Project Professional and connect to Project Server.
Beta or evaluation version has expired

(0x8c040027) A beta or evaluation version of Project Server has expired.
Possible Causes
• Beta and evaluation versions of Project Server are designed to expire after 90 days.
• Install a non-beta or non-expiring version of Project Server.
Manager requires authentication for Publish operation
(0x8c040028) Occurs when a project manager’s user account does not exist (in the Project
Server database) and when creating accounts during publishing is not allowed.
Possible Causes
• A project manager is attempting to publish a project to the Project Server database
when the project manager does not have a user account (either Project Server or
Windows authenticated) in the Project Server database.
• Create the user account for the manager in Project Web Access; republish the project.
Insufficient manager permissions for Publish
(0x8c040029) You do not have permission to publish project plans to the Project Server
database from Project Professional.
Possible Causes
• You have not been granted the Save Project category permission in Project Web
Access.
• You do not belong to a security category in Project Server that has been granted the
Save Project category permission.
• Contact your Project Server administrator and request that the Save Project
permission either be granted to you or to a category to which you are a member.
Windows account already exists

(0x8c040031) You cannot create duplicate Windows user accounts in Project Server. For
all Windows authenticated user accounts, the Windows User Account and E-mail fields
must be unique to a single user.
Possible Causes
• A resource with the same Windows User Account and E-mail information already
exists in the Project Server database.
Session has expired

(0x8c040032) The connection to Project Server was inactive for too long or has been
terminated.
Possible Causes
• The connection to Project Server expired because it was inactive or terminated.
• Repeat the previous publishing operation to initiate a new connection to Project
Server.
• Increase server session expiration time.
Cannot create manager account from Project Professional
(0x8c04003c) A user has attempted to create a manager account, but does not have
permission to create accounts in the Project Server database from Project Professional.
Possible Causes
• Project 2003 does not allow users to create user accounts in the Project Server database
from Project Professional by default. The Create Accounts from Microsoft Office
Project, Create Accounts when Delegating Tasks, and Create Accounts when
Requesting Status Reports permissions are denied at the organizational level during
initial deployment and configuration of Project Server. Users will not receive this error
message unless one or more of these permissions are allowed and the Project
Professional user does not have permission to create users in the Project Server
database.

• Create user accounts from the Manage Users and Groups pages in Project Web
Access.
Cannot publish master project

(0x8c04003f) Project Server can be configured to deny the publishing of master projects to
Project Server.
Possible Causes
• The Allow master projects to be published to Microsoft Project Server option is
disabled in the Server configuration page of the Admin Center in Project Web
Access.
• Use the Administrative project option when saving projects to Project Server; this
option can help provide the functionality of a master project without actually
publishing the master project to the Project Server database.
• Enable the Allow master projects to be published to Microsoft Project Server
option in the Server configuration page of the Admin Center in Project Web Access.
Cannot publish non-enterprise resources

(0x8c040040) Project Server can be configured to only accept projects with resources
assigned to tasks that belong to the Enterprise Resource Pool, which is a project that is
saved to the Project Server database.
Possible Causes
• You have created an assignment with a resource that does not belong to the Enterprise
Resource Pool.
• Add the resource to the Enterprise Resource Pool.
• Assign a new resource to the task that does belong to the Enterprise Resource Pool.
Cannot publish non-enterprise projects on this server
(0x8c040041) Project Server can be configured to only accept projects that are validated
against the Enterprise Global Template when saved to the Project Server database.
Possible Causes
• The Allow only enterprise projects to be published to this server option is enabled
in the Server configuration page of the Admin Center in Project Web Access.

• Uncheck the Allow only enterprise projects to be published to this server option.
• Publish the project as an enterprise project.
F
Project Server Registry Settings,
Services, and Application Folders
This appendix describes the contents of the Project Server registry, Project Server services,
and the application folders that are created after installation of Project Server is complete.
Project Server Registry

Dedicated entries in the registry are used to store connection information for the
Microsoft® Office Project Server 2003 database and the settings that link other
applications to Project Server. These entries are created by default during Setup.
\CubeProcess
This folder is not created as a default registry folder during Project Server setup. This
registry folder can be created with the following registry key to change the default timeout
of the OLAP cube building process. If this folder and registry key are not created, Project
Server will use the value of 600 as the default timeout.
• \SQLTIMEOUT 600; The number of seconds available for OLAP cube generation
before timeout. This registry key should be created as a String Value. This value can
be modified; for example 1800 would set a 30-minute timeout.
\OLE DB Provider
This folder contains information about the OLE DB Provider used by Project Server.
These registry settings determine the number of seconds that must elapse before certain
timeout conditions occur.
• \TimeBeforeRefresh 0; Determines how long the provider attempts to load a
project before returning an error message that it is unavailable. Setting this key to 0 will
prevent a timeout.
• \TimeBeforeUnload 37; Determines how long a project remains open after another
project is loaded. Until a new project is loaded, the current project remains in memory,
regardless of this setting.
• \TimeoutOnLoad 5; Determines how often the current project is checked for
updated information.
\Services\Configuration
The \Configuration folder holds information about where Project Server service
configuration data resides. Subfolders of the \ Configuration folder include \Connector,
\SessionMgr, and \Views Notification. They are described in greater detail below.
The \ Configuration folder can be found in the following location:
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\
MS Project\Services
\Configuration\Connector
This folder holds information about the Connector Services for the Project Server Service
for Enterprise Data Maintenance.
• \ProjectServer The default name of the virtual directory in the \Connector folder for
Project Server:
• Drop Directory = The directory that the Connector Service listens to for new
XML documents. Be sure this registry key points to a unique directory. If any
other Project Server configuration points to the same directory, the behavior of
the Connector Service will be unpredictable.
• Failed Directory = The directory for failed documents to be moved to.
• Project Server URL = The Project Server URL to use for SOAP calls, for
example http://myserver/projectserver.
• Success Directory = The directory for successful documents to be moved to.
• Timeout = 150000; The timeout value in milliseconds for a SOAP call.
• Verbosity = 3; 1 = low, 2 = medium, 3 = high. The verbosity level of the
response.
Note For more information about the Project Server Service for Enterprise Data Maintenance, see
the section Service for Enterprise Data Maintenance in the Project Data Service Reference for
Microsoft Office Project Server 2003 on MSDN. http://go.microsoft.com/fwlink/?LinkID=20266
\Configuration\Views Notification
This folder holds information about the Project Server Views Notification Service.
• ConnectType 0
• Directory C:\Program Files\Microsoft Office Project
Server 2003\BIN\VIEWDROP\
• Filter *.xml. (This must always be .xml and must exist in the registry for the Views
Processing service to run.)
• Forward Set to 1 if the Views Processing service is offloaded. This setting instructs
Internet Information Services (IIS) to forward any XML data to the ViewDrop folder
on the server running the offloaded Views Processing services.
• Priority Sets the process scheduling priority. Set to 2 by default; should not be set
when the Views Processing service is offloaded.
The following table lists the Priority setting and the corresponding Process Priority
Class and Thread Priority settings:
Process Priority Class Thread Priority
1 Below Normal Lowest
2 Below Normal Below Normal
3 Below Normal Normal
4 Normal Normal
5 Normal Normal
6 Normal Normal
\Configuration\SessionMgr
This folder contains information related to the configuration of services related to Project
Server and the Project Server Session Manager Service.
• LoadBalanceAutoAcceptLevel 400
• LoadBalanceMaximum 10000
• Timeout 14400
\WebClientServer\Languages
The \Languages folder holds information related to the languages supported by the current
installation of Project Server. The \Languages folder can be found in the following
location:
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\MS
Project\WebClient Server
The \Languages folder has the following values:

• defLCID Stores the Locale ID (LCID) of the default language of the Project Server
computer.
• LCID The LCID of the first language supported by the Project Server installation;
this is the default language. This entry will be appended with the numerical language
identifier, for example for English; this registry entry will appear as LCID1033.
• LCID The LCID for any additional language supported by Project Server, which can
be added by installing Project Server MUI Packs. This entry will be appended with the
numerical language identifier, for example for German; this registry entry will appear as
LCID1031.
\WebClient Server\ProjectServer\Datasets
The \Datasets folder holds information about where Project Server data resides.
Subfolders of the \Datasets folder include \Application, \EnterpriseDatabase, \WSS,
\ViewsFileDrop, and \ViewsSchedulingDatabase. They are described in greater detail
below.
The \Datasets folder can be found in the following location:
Project\WebClient Server\<Virtual Directory>
Note The default name for the virtual directory is ProjectServer.
\Datasets\Application
This folder holds information about how components of Project Server connect to the
• connectInfo Stores the database connection information for the Project Server
database. You should only use ConnInfo.exe to modify this entry.
• QueryFileExt Points to the extended Project Server SQL Query Library.
• Value = <drive>:\Program Files\Microsoft Project Server\Bin\QYLIBSQL.sql
• QueryFileStd Points to the standard Project Server SQL Query Library.
• Value = <drive>:\Program Files\Microsoft Project Server\Bin\QYLIBSTD.sql
• QueryTimeout The amount of time the component will wait for the SQL server.
• Value = 1200
• PartitionedViews
• Value = 1
• DisableAuthEdit This is a custom registry DWORD value that must be created in
the \Application folder in the Project Server registry by the Project Server
administrator before you can disable the user authentication settings for Project Server.
If this is set to 1, then a Project Server administrator will be unable to modify the
settings under Specify how users should be authenticated by Project Server on the
User authentication page in Project Web Access.
If this is set to 0, then the Project Server administrator will be able to modify these
settings. Before using this registry key to disable the authentication settings, be sure to
select the authentication setting (Mixed, Windows Authentication only, or Project
Server authentication only) first.
\Datasets\EnterpriseDatabase
This folder holds information specific to the Project Server Views Notification Service for
• DSN The DSN utilized by the Project Server Views Notification Service that provides
access to the Microsoft Project OLE DB Provider:
• Value = PC11DSN
• Password Stores the database password information for the Project Server database.
You can only use ConnInfo.exe to modify this entry.
• User Name The user name associated with the DSN:
• Value = MicrosoftProjectServerUser
\Datasets\STS
This folder contains information related to Microsoft Windows® SharePoint™ Services.
Values include:
• IsExtranet The extranet URL for Windows SharePoint Services.
\Datasets\ViewsFileDrop
This folder holds information about where the Project Server Views Notification Service
service receives new files to process.
• DropLocation Stores the path to where the Views Processing service listens for new
publish action view files.
• Value = <drive>:\Program Files\Microsoft Project Server\Bin\ViewDrop
• ForwardUNC The location of the server running the offloaded Views Processing
service.
\Datasets\ViewsSchedulingDatabase
This folder holds connection information for the views scheduling database.
• QueryFileExt Points to the extended Project Server SQL Query Library.
• Value = <drive>:\Program Files\Microsoft Project Server\Bin\QYLIBSQL.sql
• QueryFileStd Points to the standard Project Server SQL Query Library.
• Value = <drive>:\Program Files\Microsoft Project Server\Bin\QYLIBSTD.sql
\WinProj
This folder stores the information that Project Professional uses to create ODBC
connections to the Project Server database.
• Proj Password Stores the database password information for the Project Server
• Proj Username The user name associated with the Project Professional connection to
• Value = MSProjectUser
\WebClient Server\ProjectServer\Services
The \Services folder holds information related to the configuration of services related to
Project Server. The \Services folder can be found in the following location:
Project\WebClient Server\<Virtual Directory>
Note The default name for the virtual directory is ProjectServer.
Services
There are several services that can be managed from the Services dialog box on the server
running Project Server.
The Services dialog box.

X To start or stop a Project Server service
1. On the Start menu of the Project Server computer, point to Programs, then
Administrative Tools, and then select Services.
2. In the Services dialog box, double-click a Project Server service in the list of services
to open the Properties dialog box for the service you want to start or stop.
• If the Project Server service is not running, click the Start button under Service
status. If the Project Server service is already running, Service status will specify
Started.
• If the Project Server service is running, click the Stop button under Service
Status. If the Project Server service is already stopped, Service status will specify
Stopped.
Note You can also Start, Stop, Pause, Resume, or Restart a Project Server service by
right-clicking the service in the list of services in the Services dialog box.
3. Click Apply and then OK to close the Properties dialog box.
Project Server Session Mgr Service (PjSessionMgr)

This Project Server Session Mgr Service maintains session state information for Project
Web Access users. Each user is issued a session ID when they log on to Project Web
Access. This ID is used to save and retrieve session-specific information, such as which
panes are displayed or to identify recently-viewed pages. This services runs at Normal
priority by default.
Project Server Tracing Service (PjTraceSvc)

The Project Server Tracing Service is installed during setup of Project Server and is set to
start automatically. If it is not turned on, you must start the service in order to enable
logging of Project Server events and errors using the Event Viewer or as a text output file.
You can use the Project Server SetTracing Utility to specify the format of the output from
the Project Server Tracing Service.
When the Project Server Tracing Service generates a text file of the Event Log and the
output file points to a language in an NTFS partition, the Project Server Tracing Service
will not be able to create the output file because LocalService does not have write
permissions to the NTFS partition.
Note For more information about the SetTracing Utility, see Project Server SetTracing Utility in
Appendix B of the Microsoft Office Project Server 2003 Administrator’s Guide.
Project Server Views Notification Service (PjViewNotify)

The Project Server Views Notification Service processes requests to publish project plans
and enterprise resources to the Project Server database. The service listens for operating
system events to know when files have been dropped to the ViewDrop folder on the server
running Project Server. When a file is dropped, the service processes the content, opens the
project using the OLE DB Provider, and publishes it to the View tables in the Project
Server database. When finished, the XML data is deleted from the ViewDrop folder. If this
service is not running properly, resources will not be available in the Resource Center and
projects will not be available in the Project Center. By default, this service runs at below-
normal priority and thread priority, which throttles the service’s use of the processor.
The Views Notification service is also involved in the process of updating and building the
OLAP cube used by the Portfolio Analyzer. The OLAP cube building process begins with
an update of the resource availability tables, which is handled by this service. After the
resource availability tables have been updated, this service is no longer involved in the
process of building an OLAP cube.
When this service is distributed to another server, it is appropriate to change its priority
setting to higher than Below Normal.
Project Server Scheduled Process Service (PjSchSvc)

This Windows service starts several scheduled processes, including the Notification
Processing Engine for Project Server e-mail notifications and reminders, Views
Notification Services for OLAP cube generation, and Active Directory synchronization. By
default, the Project Server Scheduled Process Service polls for eligible processes every
thirty minutes. The Scheduled Process service uses the Log On As permissions assigned to
the Project Server Scheduled Process Service. It is recommended after the installation to
assign a domain user with Active Directory read permissions for the Project Server
Scheduled Process Service.
Project Server Connector Service (PjConnectSvc)

The Project Server Connector Service supports the Service for Enterprise Data
Maintenance (EDM), a component of the Project Data Service. The Service for EDM
relies on XML as its data format and uses the PDS to provide an easy way to exchange data
between Project Server and other applications through a file-drop mechanism as well as a
SOAP programmatic interface.
An organization may have several Line of Business (LOB) applications in place, in addition
to Project Server as the Enterprise Project Management (EPM) solution. Other LOB
applications may include human resources (HR), financial, professional services automation
(PSA), customer relationship management (CRM), and skills learning portal systems. Many
LOB applications have the ability to drop a formatted XML file to a designated location on
a regular basis. In other cases, a developer could easily add a SOAP call or HTTP Post that
directly accesses the Service for EDM.
Note For more information about the Service for Enterprise Data Maintenance, see the chapter
Service for Enterprise Data Maintenance in the Project Server Data Reference on MSDN:
Folders
All of the folders used by Project Server can be found from the following root path by
default:
C:\Program Files\Microsoft Office Project Server 2003
\BIN\1033
This folder contains Project Server services and configuration files that are localized.
• ConnInfo.exe
• PSComPlus.exe
• Pjintlw.dll
\BIN\Connector
The directory where XML files are dropped for processing by the Project Server Service
for Enterprise Data Maintenance. XML files are marked either SUCCESS or FAIL and are
placed in the appropriate folder.
\BIN\ViewDrop
The ViewDrop folder where all project plans published to Project Server from Project
Professional are placed as XML files to queue to the Project Server view tables. Files are
sent to here when the following actions are taken from Project Professional (only when
connected to Project Server):
• On the Collaborate menu, any Publish action is selected.
• On the File menu, Close.
\Help\1033
This folder contains the following files:
• Pjdb.htm
• Pjsvrdb.htm
• Pjsvr.chm
• Pjxml.chm
• Psreadme.htm
\IIS Virtual Root

This folder stores the core Active Server Pages (ASP) files used by Project Web Access.

Libros - Microsoft - Project Server 2003 Administrators Guide

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Libros - Microsoft - Project Server 2003 Administrators Guide

Transféré par

Droits d'auteur :

Formats disponibles

Microsoft Office Project

Server 2003 Administrator’s Guide

Modifying a User ............................................................................................... 30

Site Collection Administration........................................................................146

Project Server SetTracing Utility............................................................................253

Create Accounts from Microsoft Office Project .............................................278

View Project View ............................................................................................291

Manager not allowed to create a new account......................................336

Microsoft Office Project Server 2003 Online Books Series

What Will You Learn from this Book?

Who Should Read this Book?

How is this Book Structured?

January 2004 • Added information about Project Server

Working in the Project Web Access Admin Center

Managing Users and Groups

The Users page in Project Web Access.

The Categories page in Project Web Access.

The Specify Views page in Project Web Access.

Configuring Project Server

The Server configuration page in Project Web Access.

Managing Windows SharePoint Services

The Connect to SharePoint server page in Project Web Access.

Managing Enterprise Features

Customizing Project Web Access

The Tracking settings page in Project Web Access.

Cleaning Up Project Server Data

The Clean up Project Server database page in Project Web Access.

Understanding Project Server Security

Project Server Security

Users and Groups

Understanding Project Web Access Permissions

Permissions in Project Web Access work similarly to permissions in Microsoft Windows.

• Categories A category is a collection of security objects. Create custom categories

Server, or Project Professional, depending on the permission. If you allow or deny

When to Allow and Deny Project Web Access Permissions

Understanding Active Directory Synchronization with Project

Understanding Project Server 2003 Web Parts

Using the Default Project Server 2003 Web Parts

Creating Custom Project Server 2003 Web Parts

The Users page in Project Web Access.

• Synchronization of Project Server security groups with Active Directory security

The Add User page in Project Web Access.

• If you select Project Server authentication, complete the User Account, E-

9. Click Save Changes.

4. On the Modify User page, make any necessary changes.

5. Click Save Changes.

Deactivating or Reactivating a User

X To deactivate a user account

Merging Two User Accounts

X To merge two user accounts

The Groups page in Project Web Access.

categories (My Organization, My Projects, My Resources, My Direct Reports, and My

• Administrators group This group is granted all available permissions in Project

The Add Group page in Project Web Access.

10. Click Save Changes.

Using a Portal Site with Project Web Access

The Modify Group page in Project Web Access.

Security Group Synchronization with Active Directory

• Setting up the timing options for Active Directory synchronization.

Synchronizing Project Server Groups with Active Directory

4. Click Save AD Options.

X To remove regular synchronization of Project Server groups with Active Directory

4. Click Save AD Options.

X To manually set synchronization of Project Server groups with Active Directory