1

Microsoft Project Server 2010 Administrator's Guide

Copyright This document is provided ―as-is‖. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Excel, Internet Explorer, Outlook, SharePoint, SQL Server, and Windows are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.

Table of Contents

Table of Contents
Introduction 1 What Will You Learn from this Book? ..................................... 1 Who Should Read this Book? ................................................. 1 How is this Book Structured? ................................................. 2 1 Security 5 Manage Permissions .............................................................. 6 Manage Users ......................................................................... 8
Add or Edit a User ...................................................................................................... 8 Deactivate a user account ...................................................................................... 19 Reactivate a user account ....................................................................................... 20

Manage Groups..................................................................... 20
Create or modify a security group ........................................................................... 21 Delete a security group ............................................................................................ 26 Active Directory Group Synchronization ................................................................. 26

Manage Categories ................................................................31
Create or modify a category .................................................................................... 32 Delete a category ..................................................................................................... 39

Manage Security Templates ................................................. 40
Create or modify a security template ...................................................................... 40 Delete a security template ...................................................................................... 43

Manage Project Web App Permissions ................................. 44 Manage Delegates ................................................................ 45
Turn Delegation on or off ......................................................................................... 46 Set up who can act as delegate .............................................................................. 46 Set up who can have delegates assigned to them ................................................ 48 Create a new delegation .......................................................................................... 49

2 Enterprise Data 50 Enterprise Custom Fields and Lookup Tables .......................51
Understanding Enterprise Custom Fields ............................................................... 52 Creating Enterprise Custom Fields ......................................................................... 52 Creating Enterprise Custom Lookup Tables ........................................................... 64

Departments ......................................................................... 68
Configuring departments ......................................................................................... 72

The Resource Breakdown Structure (RBS) ............................74 Enterprise Global................................................................... 77 Enterprise Calendars ............................................................ 79
Create a New Calendar ............................................................................................ 80 Copy an Existing Calendar ....................................................................................... 81 Edit an Existing Calendar ......................................................................................... 82 Delete a Calendar .................................................................................................... 83 Modify Working and Nonworking Times ................................................................. 84

Resource Center.................................................................... 95
Create a New Resource ........................................................................................... 95

3 Database Administration 103 Delete Enterprise Objects ................................................... 103
Delete projects .......................................................................................................103 Delete resources and users ..................................................................................105 Delete status report responses.............................................................................106 Delete timesheets ..................................................................................................106 Delete user delegates............................................................................................107

Force Check-in Enterprise Objects ...................................... 108
Check-in Enterprise Projects .................................................................................109 Check in Enterprise Resources .............................................................................110 Check in Enterprise Custom Fields .......................................................................110 Check in Enterprise Calendars ..............................................................................111 Check in Lookup Tables for Enterprise Custom Fields ........................................111 Check in Resource Plans .......................................................................................112

Daily Schedule Backup ....................................................... 113
Project Retention Policy Versions .........................................................................113 Items .......................................................................................................................113

Administrative Backup and Restore ................................... 115
Administrative Backup ...........................................................................................115 Administrative Restore ..........................................................................................115

OLAP Database Management.............................................. 117
Create an OLAP Cube ............................................................................................117 Configure an OLAP cube ........................................................................................121 Copy an OLAP cube ................................................................................................125 Delete an OLAP cube .............................................................................................126 Build an OLAP cube ...............................................................................................126

Table of Contents

4 Look and Feel 128 Manage Views ..................................................................... 129
Create a New View .................................................................................................134 Modify a View .........................................................................................................137 Copy a View ............................................................................................................138 Delete a View .........................................................................................................139

Grouping Formats ............................................................... 139 Gantt Chart Formats ............................................................ 141 Quick Launch .......................................................................142
Change Quick Launch Behavior ............................................................................143 Add a New Link ......................................................................................................144 Modify an Existing Link ..........................................................................................145 Reorder Quick Launch Items .................................................................................145 Delete a Link ..........................................................................................................146

5 Time and Task Management 147 Fiscal Periods .......................................................................148
Define Fiscal Periods .............................................................................................148 Delete Fiscal Periods .............................................................................................151

Time Reporting Periods ....................................................... 151
Create Bulk Time Reporting Periods .....................................................................152 Insert or Delete Time Reporting Periods...............................................................153

Timesheet Adjustment .........................................................155 Line Classifications ..............................................................156 Timesheet Settings and Defaults ........................................158 Administrative Time .............................................................160 Task Settings and Display ....................................................162 Close Tasks to Update..........................................................163 6 Queue Management 165 Queue System Overview ......................................................165 Queuing process ..................................................................167 Queuing architecture ...........................................................168
Queuing modules ...................................................................................................168 How it all works together .......................................................................................172

The Project and Timesheet queues ..................................... 174
How the Project and Timesheet queues are used ...............................................175

Queue groupings ..................................................................177 Parent/Child Relationships between submitted Jobs .........178 Queuing states .....................................................................179
Changes in queue state.........................................................................................180

Queue Administration Settings ........................................... 181
Manage Queue Jobs ..............................................................................................182 Queue Settings .......................................................................................................186

7 Operational Policies Management 197 Alerts and Reminders ......................................................... 197
Notification E-mail Settings ...................................................................................198 Schedule E-Mail Reminder Service .......................................................................199

Additional Server Settings................................................... 199
Project 2007 Compatibility Mode .........................................................................200 Project Professional Versions ................................................................................202 Enterprise Settings ................................................................................................203 Currency Settings ...................................................................................................204 Resource Capacity Settings...................................................................................206 Resource Plan Work Day .......................................................................................208 Exchange Server Details ........................................................................................208 Task Mode Settings ...............................................................................................209

Server Side Event Handlers .................................................210 Active Directory Resource Pool Synchronization ................ 212
To configure Enterprise Resource Pool synchronization .....................................213

Project Sites .........................................................................216
Create Site ..............................................................................................................217 Edit Site Address ....................................................................................................218 Synchronize ............................................................................................................219 Delete Site ..............................................................................................................220 Go to Project Site Settings .....................................................................................220

Project Site Provisioning Settings ....................................... 221
Site URL ..................................................................................................................222 Default Site Properties ..........................................................................................222 Automatic Provisioning ..........................................................................................223 Project Site Permissions ........................................................................................224

Bulk Update Project Sites ................................................... 225
Update Site Paths ..................................................................................................226 Update Content Types ...........................................................................................227 Project Site Permissions ........................................................................................227

..................................................237 Create or Edit Project Detail Pages .......................................................................................233 Change or Restart Workflows ........................................ 236 Change or Restart a Workflow .................................................240 A Project Server 2010 Category Permissions B Project Server 2010 Global Permissions 243 255 C Project Server 2010 Default Security Groups 280 Default global permissions ............................231 Workflow Stages ...................................... 285 D Project Server 2010 Default Categories 289 Categories ..................Table of Contents 8 Workflow and Project Detail Pages 228 Enterprise Project Types ............................... 233 New Workflow Stages ......... 231 New Workflow Phase ........................................................................................................229 Workflow Phases ............ 229 Create New Enterprise Project Type ..............................................................................................................................237 Project Workflow Settings ................................................................................................................ 290 ................................................................................................. 289 Category permissions ...............................281 Default category permissions .........................................................................236 Project Detail Pages ....................................................................

.

 Managing time and task tracking. and categories. Send us your feedback (projdocs@microsoft. SharePoint Server farm administrators Those individuals responsible for administering the SharePoint Server Central Administration web site and ensuring that Project Server and Microsoft SharePoint .  Configuring Active Directory synchronization to security groups and resources. Please let us know what you think about the quality of this content. If this text does not meet your needs.  Customizing Project Web App to fit the specific needs of your organization. let us know how we can improve it.1 Introduction The Microsoft Project Server 2010 Administrator’s Guide helps your organization understand the tasks involved with administering Microsoft Project Server 2010. If this text was helpful to you. Who Should Read this Book? This book is designed to produce maximum benefits for the following professionals: Project Server administrators Those individuals who will have administrative privileges for Project Server and will perform the duties required to configure and maintain Project Server. including:  Managing users. let us know how it helped. views. groups.).  Managing queue settings for your specific environment.  Managing workflows. calendars. What Will You Learn from this Book? There are several important tasks that an administrator must manage in Microsoft Project Server 2010 for Project Web App users to access and interact effectively with project data.  Managing enterprise data (custom fields. etc.com).

they are organized in the same manner in this book as they are organized in Project Web App. Project site administrators Those individuals who will have administrative privileges for Project Server and will perform the duties required to configure Project Server to meet organizational portfolio and project management needs.2 Project Server 2010 Administrator's Guide Server are always properly synchronized and that SharePoint Server features and functionality are available. You can review these chapters in any order you need to. 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 2010 and who may need a better understanding of the day-to-day Project Server administrative tasks that are available in Project Web App. Appendix data is primarily reference data and lists: . How is this Book Structured? This book has eight chapters and four appendices. Project Management Office (PMO) Those individuals who help to define and maintain project management standards and practices throughout the organization.

“Time and Task Management” Chapter 6. “Project Server 2010 Category Permissions” Appendix B “ Project Server 2010 Global Permissions” Appendix C “ Project Server 2010 Default Security Groups” Appendix D “ Project Server 2010 Default Categories” . “Queue Management” Chapter 7. “Operational Policies Management” Chapter 8. “Workflow and Project Detail Pages” Appendix A.Introduction              Introduction Chapter 1. “Security” Chapter 2. “Database Administration” Chapter 4. “Enterprise Data” Chapter 3. “Look and Feel” Chapter 5.

.

5 1 Security This chapter about Project Server 2010 Security contains the following sections:        Manage Permissions Manage Users Manage Groups Manage Categories Manage Security Templates Manage Project Web App Permissions Manage Delegates .

Permissions can be set in a number of different places within the Project Server 2010 administration menu. The Not Allow state does not prevent users from accessing the feature associated with the permission if they are granted permission in some other way. There are two types of permissions in Project Server:  Global Permissions grant users and groups the ability to perform actions throughout an instance of Microsoft Project Web App (PWA). Category Permissions are assigned on a category level. if the permission is explicitly denied anywhere. the default state is Not Allow. If neither the Allow nor the Deny check boxes are selected. or not configure (select neither Allow nor Deny) each permission in Project Server. You can Allow.  Category Permissions grant users and groups the ability to perform actions on specific projects and resources. Category Permissions also grant permissions to Views in PWA. You can allow or deny permissions by selecting the check boxes in the Allow and Deny columns. but might be granted permission by means of membership in a group for which the permission is allowed. For example. permission is denied everywhere for a particular user or group. However. Global Permissions are assigned on a user or group level. For example.6 Project Server 2010 Administrator's Guide Manage Permissions A permission is the authority to perform a specific action within the context of Project Server. Deny. the Log On permission can be allowed or denied for any given user or group. a user might belong to one group for which permission is not configured (Not Allowed). .

 Deny Prevents a user or group from performing the actions associated with the permission. Therefore. Permissions can be configured in the following ways:  Allow Enables users or group members to perform the actions associated with the permission. the default state is Not Allow. Select the Deny check box to prevent a user from outside the organization from accessing Project Server security objects or to deny functionality to a user or group). No permissions are set to Deny by default. If a user belongs to more than one group. . Create the groups and define the set of permissions to associate with the groups as part of your initial Project Server 2010 deployment planning process. because this setting overrides the Allow setting. before you assign users to groups and groups to categories. Note that if a user is denied a specific permission. Important The Deny setting enables you to deny access to functionality. Use caution when denying permissions. It is important to consider when you are configuring a permission to Deny that the Deny setting supersedes any Allow settings that apply to the user for that permission by means of other group memberships. the deny setting supersedes any Allow settings that might apply to other groups to which the user belongs. assigning and administering permissions on an individual basis can be an overwhelming task. Limiting your use of the Deny setting can simplify permissions management for large groups of users. then the user is allowed to perform the actions associated with the permission. and a permission is set to Not Allow for one group and is set to Allow (but not Deny) for another group. For organizations that include a large number of users. You can use groups to assign permissions to multiple users with a single action.  Not Allow If you select neither Allow nor Deny for a permission. use caution when selecting the Deny check box.Security 7 Project Server permissions You can configure all Project Server 2010 permissions from the Project Web App Server Settings page.

in the Security section. See the following sections for details on each option. 2. 2. On the Manage Users page. click Manage Users. and group memberships.  To add a user account 1. perform the following procedure. click the user that you want to edit. perform the following procedure. 4. Note If you have more than 2. Add or Edit a User To add a new user account. This helps to reduce the volume of required day-to-day administrative tasks. See the following sections for details on each option. groups. and can simplify troubleshooting permissions issues.8 Project Server 2010 Administrator's Guide After you define groups. fill out the required information for the user. the day-to-day administration of users.  To edit a user account 1.000 users in PWA. You can also assign permissions to users by adding them to one of the builtin groups or by creating a custom group and assigning specific permissions to the custom group. On the Edit User page. in the Security section. click New User. 3. this initial account can be used to create the user accounts for Project Server administrators. . You can use this initial account to create other user accounts that can access Project Server. On the New User page. you must be logged on by using the account used to provision the PWA site. who can create other user accounts and do additional post-installation configuration. modify existing users. and categories involves adding users to or removing users from security groups. On the Server Settings page. To edit an existing user account. deactivate user accounts. Click Save. Manage Users When you make the initial connection to Microsoft Project Server 2010 through the Microsoft Project Web App (PWA) site. You can use the Manage Users page that is available from the Server Settings page to add new individual users. the Manage Users page will not display users until you select one of the Show options at the top of the page. and reactivate inactive user accounts. click Manage Users. On the Manage Users page. For example. the permissions associated with the groups. fill out the required information for the user. 3. On the Server Settings page.

Security 9 4. Project Server user identification information The following table describes the user identification options. and account status. Click Save. email address. Identification Information Use the Identification Information section to specify user information such as name. This setting is selected by default. Attribute User can be assigned as a resource Description Select User can be assigned as a resource if you want this user account to be able to be assigned tasks as a resource. Selecting this entry makes the user an Enterprise Resource. Once a user account becomes an Enterprise Resource it cannot be changed back to a non-Enterprise Resource even if the check box is .

if applicable. The name for the user account. type the user account name in the form of MembershipProviderName:UserAccount. The user’s initials. The URL of the user’s web site. The user’s position in the Resource Breakdown Structure hierarchy. the user will be unable to access the account. the user account functions normally. a team web site) if applicable. Can be set to Active or Inactive. This is a required field. Prevent Active Directory synchronization for this user . User Authentication Use the User Authentication section to specify the user’s logon account and whether the user account should be synchronized with Active Directory. Attribute User logon account Description If you are using Integrated Windows authentication. If the value is set to Active. If you are using forms-based authentication. Project Server user account information The following table describes the user account options. If the value is set to Inactive. Selecting the Prevent Active Directory synchronization for this user check box prevents a user account from being synchronized during Active Directory Resource Pool Synchronization. The email address for the user. This field is required to synchronize tasks with Exchange Server.10 Project Server 2010 Administrator's Guide Display Name E-mail address RBS Initials Hyperlink Name Hyperlink URL Account Status deselected. type the user's account name in the form of DomainName\UserAccountName. The name of the user’s web site (for example.

Security 11 Assignment Attributes Use the Assignment Attributes section to define information associated with the user’s assignment to tasks. these options are not available. Leveling is the process that is used to resolve resource conflicts or over-allocations by delaying or splitting certain tasks. including calendar. Attribute Resource can be leveled Description Indicates whether the resource can be leveled. . assignment owner. timesheet manager. and cost and availability information. Note If you have not selected the User can be assigned as a resource check box. booking type. Project Server assignment attributes The following table describes the Project Server user assignment attribute options.

a material resource cannot log on to PWA but the assignment owner field allows an enterprise resource to enter progress for the resource within PWA. The latest date that the user is available as a resource. if set. To establish variable rates. The rate for the work on an assignment that is scheduled beyond the regular working hours of an assigned resource. A base calendar is a calendar that can be used as a project and task calendar that specifies default working and non-working time for a set of resources. A committed resource is formally allocated to any task assignment within a project. To establish variable rates. This person can differ from the person first assigned to the task. The earliest date that the user is available as a resource. open the enterprise resource in Project Professional and set this information in the Cost Rate tables. An assignment owner is an enterprise resource who is responsible for entering progress information in PWA. open the enterprise resource in Project Professional and set this information in the Cost Rate tables. specify that user here. For example. If the user has a timesheet manager. if today is 1/1/2011 and the earliest available date is 1/2/2011 .12 Project Server 2010 Administrator's Guide Attribute Base Calendar Default Booking Type Timesheet manager Default Assignment Owner Earliest Available Latest Available Standard Rate Overtime Rate Current Max. This resource assignment does not detract from the availability of the resource to work on other projects. The current max units is tied to the early and late availability dates. Units (%) Description When Project levels a resource. This date corresponds to the resource availability dates for a resource that can be seen in Project Professional. A proposed resource has a pending resource allocation to a task assignment that has not yet been authorized. The percentage of time that the resource is available for assignments. This date corresponds to the resource availability dates for a resource that can be seen in Microsoft Project Professional. its selected assignments are distributed and rescheduled. Using the Default Booking Type list. The rate for the work on an assignment that is scheduled during the regular working hours of an assigned resource. For example. you can configure a user's booking type as either Committed or Proposed.

if applicable.com/enus/library/ff793353. a per-use cost accrues every time that the resource is used. edit in Project Professional.Security 13 Attribute Cost/Use Description then the max value is 0% and text next to the field will say ―Custom availability detected.aspx).microsoft. For work resources.‖ The per-use cost of the resource. see Deploy Project Server 2010 with Exchange Server (http://technet. Exchange Server Details Use the Exchange Server Details section to specify whether the user’s tasks should be synchronized with Exchange Server. Departments Use the Departments section to define whether the user is a member of a particular department. You define departments for your organization by populating the Departments custom lookup table. Exchange integration must be configured for task synchronization to function. For more information about how to configure task synchronization with Exchange Server. a per-use cost is accrued only one time. For material resources. User department configuration . Exchange synchronization configuration Select the Synchronize Tasks check box if you want to enable task synchronization using Microsoft Exchange for this user.

and then click Add. The following table describes the security group configuration options for a user...14 Project Server 2010 Administrator's Guide If the user is a member of a department. Attribute Available Groups Groups that contain this user Description The Available Groups list contains the groups that the user is currently not a member of. Security Categories Use the Security Categories section to specify the user’s membership in security categories. select the group in the Available Groups list. click the expand button (. The Groups that contain this user list contains the groups that the user is currently a member of. Security Groups Use the Security Groups section to specify the user’s membership in security groups. .) and select the department from the displayed hierarchy. Security group configuration To add the user to a security group.

Instead. assign the user to a group and set category permission for the group. To modify the category permissions for this user in a category. The Set permission with Template option can be used to prepopulate a set of category permissions based on a predefined template for the user’s role (such as Executive or Project Manager). Set permissions with Template . The following table describes the security category configuration options for a user. This allows for easier maintenance. and then select Allow for the permissions that you want to allow. select the category in the Available Categories list. and then click Add.Security 15 Security category configuration To add the user to a category. Important We recommend that you do not set category permissions for a single user. The Permissions for <category> area lets you configure category permissions for this user for the selected category. select the category in the Selected Categories list. Attribute Available Categories Selected Categories Permissions for <category> Description The Available Categories list contains the categories that the user is not a member of. The Selected Categories list contains the categories that the user is a member of.

16 Project Server 2010 Administrator's Guide Global Permissions Use the Global Permissions section to configure global permissions for the user. ―Project Server 2010 Global Permissions. but are a way of specifying that a user belongs to a particular group in your organization. configure permissions at the group level and add users to the appropriate group. Doing this allows for much easier administration and helps in troubleshooting permissions issues. Global permissions configuration To allow or deny a global permission for the user. For a complete list of global permissions. These fields appear in the Project Server reporting database and can be used for reporting. Cost Type can be added to the resource and assignment OLAP cubes. We recommend that you do not configure global permission for a single user. Group fields are not tied to Project Server security. select the Allow or Deny check box for the permission. . Instead. see Appendix B.‖ Group Fields Use the Group Fields section to define group and cost information for the user.

you must first do the following: 1. Team details configuration You can use teams to pool assignments under a single resource where they can be later reassigned to other resources. you enable other users on the Development team to see any tasks assigned to the Development resource and to accept the assignments in PWA. type the information in the Group Fields area. Team Details Use the Team Details section to define a team association for the user. Edit the Team Name custom field to use the new lookup table. 2. codes. For example. Create a custom lookup table and populate it with the team names that you want to use. . By assigning this resource to the Development team and selecting the Team Assignment Pool check box. By default. You could also select Team Assignment Pool for a team lead and have all assignments go through that person for distribution to team members. you could create a team resource named ―Development‖ to which you assign software development tasks. the Group field is synchronized with Active Directory if you use Active Directory synchronization. The values available for Cost Type are those that are defined in the Cost Type custom lookup table. To use teams.Security 17 Group fields configuration If your organization uses group names. or cost center information for individuals.

18 Project Server 2010 Administrator's Guide System Identification Data The System Identification Data section displays user meta data. The date this user account was created. Can be used to link this user to external data. . or checked out. The unique ID for this user’s Active Directory account. The date this user account was checked out. This information can be used to link the person to corresponding information elsewhere in the organization. such as when the account was created. or to facilitate the consolidation of reporting of resource use beyond what Project Server provides. type additional identifying information for the user in the External ID box. System identification data In the System Identification Data section. updated. Attribute GUID External ID Active Directory GUID Date Created Date last updated Checked out by Checkout date Description The unique ID associated with this user. The user who currently has this user account checked out. The date this user account was last updated. The following table describes the system identification data fields.

Project Server users not found in the Active Directory group being synchronized will be deactivated.  To deactivate a user account 1. If a user is to be removed from Active Directory but you do not want the account deactivated. but the user is unavailable for new assignments. in the Quick Launch. The user account is inactive until it is reactivated. request status reports. The option to delete a user is available in the Database Administration section in Server Settings. On the Project Web App home page. Deactivate users Use this procedure to deactivate an active Project Server 2010 user account. deactivating a user to preserve data is recommended. are not actually deleted from the Project Server database. After deactivating an account. that user’s information and data remains in the database. This prompt occurs when the Project Manager opens the project in Microsoft Project Professional 2010. However. click Server Settings. the account cannot access Project Server 2010 until it has been reactivated. User accounts. . you may need to make Project Server user accounts unavailable. when deactivated. select the Prevent Active Directory synchronization for this user check box under User Authentication on the Edit User page. Users cannot use this account to send assignment updates. the Project Manager is prompted to reassign the user’s remaining work.Security 19 Deactivate a user account At times. Once a user is deactivated. When using Active Directory synchronization. This ensures that any relationships that resource might have with project data can be preserved in case the account is reactivated later. or delegate tasks. Deactivating a user account means that it can no longer be used to log on to Project Server 2010. The Manage users and groups global permission in Project Server 2010 is required to complete this procedure. When you deactivate a user account.

you simply need to change the account status from Inactive to Active. in the Identification Information section.) Click the check box next to the user name of the account you want to deactivate. On the Server Settings page. the reactivated account is able to access Project Server 2010. On the Manage Users page. Click OK to deactivate the user account or user accounts.) Click the user name of the account. The Manage users and groups global permission in Project Server 2010 is required to complete this procedure. Click Save. (You can use the Search box to search for a specific user. On the Project Web App home page. 7. in the Security section. On the Manage Users page. Use this procedure to reactivate a deactivated Project Server 2010 user account. Reactivate a user account After deactivating a user account. On the Edit User page for the selected user. (You can use the Search box to search for a specific user. 8. you may need to reactivate it at some later time. Note that you can select multiple user accounts. By adding users to groups. find the user account you want to deactivate. you can significantly reduce the amount of time spent managing user . in the Security section. 3. Manage Groups A group is a container for users that can be assigned permissions in Microsoft Project Server 2010. Because the user information still exists in the Project Server database. Click Deactivate Users. in the Quick Launch. click Manage Users. 4. select Active from the Account Status drop-down list. find the user account you want to reactivate. A message box will appear asking confirmation. in the Users list. 6. 2.20 Project Server 2010 Administrator's Guide On the Server Settings page.  To reactivate a user account 1. click Manage Users. click Server Settings. After you have performed this procedure. Users automatically inherit the permissions of any group to which they belong. 5. in the Users list. 5.

This group is intended for users who manage and assign resources and edit resource data. but cannot make changes.  Portfolio Managers Users can create and edit data. . you can also create custom groups by using the Manage Groups page on the Microsoft Project Web App (PWA) site Server Settings page. This group is intended for high-level users who need visibility into projects but are not themselves assigned project tasks. This group is intended to give everyone basic access to PWA. All new users are automatically added to the Team Members group. This group is associated with the My Projects category. These default groups are designed to be used together with the five default categories. It is associated with the My Organization category. This group is associated with the My Organization category. You can manage groups from the Microsoft Project Web App (PWA) Server Settings page.  Project Managers Users have most global and category-level project permissions and limited resource permissions. This group is intended for people in a lead capacity who do not have regular assignments on a project. On the Server Settings page. The following groups are created by default when Project Server 2010 is installed:  Team Members Users have general permissions for using PWA.  Administrators This group is granted all available Project Server permissions. My Projects.  To add a security group 1. To better meet the security requirements of your own organization.  Resource Managers Users have most global and category-level resource permissions. This group is intended for users who maintain project schedules on a daily basis. Create or modify a security group Seven default security groups are installed with Microsoft Project Server 2010. This group is associated with the My Organization and My Projects categories. but limited project-level permissions.  Team Leads Users have limited permissions around task creation and status reports. and My Resources categories. click Manage Groups.Security 21 permissions. Portfolio Managers are able to view and edit all projects and resources in the organization. but cannot perform Project Server administrative tasks such as adding users or creating groups. This group is associated with the My Tasks category. in the Security section. This group is associated with the My Organization category. My Organization. Perform the following procedure to create a custom group in Project Server 2010. This group is associated with the My Direct Reports.  Executives Users have permissions to view project and Project Server data.

Perform the following procedure to modify an existing group in Project Server 2010. in the Security section. 3. Group Information Use the Group Information section to specify a name and description for the group. . click Manage Groups. or for changes to the Active Directory group to which it is currently being synchronized. which can affect performance. You can modify the information associated with any security group in Microsoft Project Server 2010. click Find Group and search for the group that you want to synchronize. See the sections below for information about each area. click the name of the group you want to modify. 5. Complete the required fields on the Add or Edit Group page. in the Quick Launch.22 Project Server 2010 Administrator's Guide On the Manage Groups page. For example. We recommend not modifying the default Project Server groups. On the Project Web App home page. Click Save. make your changes to the group information.  To modify a security group 1. See the sections below for information about each area. On the Manage Groups page. To stop synchronizing an existing group. click Server Settings. but rather creating a new group with the same permissions and modifying the new group. Click Save. large numbers of groups and categories can stress the authorization system. Having a large number of groups and categories within an organization can lead to additional management complexity. 3. 2. On the Server Settings page. Group information If you want to synchronize the membership of this group with an Active Directory group. click New Group. Additionally. click Clear Group. 4. On the Add or Edit Group page for the selected group. you may need to modify the group for changes to users or categories. 2. in the Group Name list. 4. Avoid creating unnecessary groups.

Security

23

The following table describes the group information options.
Attribute Group Name Description Active Directory Group to Synchronize Description The name of the group. A description of the group. The name of the Active Directory group from which this group gets its membership. If you configure this group to synchronize with an Active Directory group, the membership of this group will be synchronized with the Active Directory group specified on the schedule that you configure.

Users
Use the users section to specify which Project Server users are a member of this group.

Available users and users in the group

To add users to the group, select the users in the Available Users list, and then click Add. To remove users from the group, select the users in the Selected Users list, and then click Remove. If you have configured Active Directory synchronization for this group, the group membership is maintained by that mechanism. Any changes you make manually may be overwritten the next time the group is synchronized with Active Directory. The following table describes the options for users in the group.
Attribute Available Users Selected Users Description The users in Project Server that are not members of this group. The users in Project Server that are members of this group.

Categories
Use the Categories section to define which security categories area associated with this group.

24 Project Server 2010 Administrator's Guide

Categories options

To associate a category with this group, select the category in the Available Categories list, and then click Add. To set the category-level permissions for a particular category, select the category in the Selected Categories list, and then click Allow for the permissions that you want to allow for this category/group combination. The following table describes the categories options for a group.
Attribute Available Categories Selected Categories Permissions for <category> Description The categories that are not associated with this group. The categories that are associated with this group. The permissions that members of this group have within

Security

25

Attribute

Set permissions with Template

Description the selected category. This option appears when you select a category in the Available Categories list. To set the category permissions for the selected category from a template – such as Project Manager or Team Member – select the desired template from the dropdown list, and then click Apply.

Global Permissions
Use the Global Permissions section to configure global permissions for this group.

Global permissions

To allow a permission for the group, select the Allow check box for that permission. To deny a permission for the group, select the Deny check box for that permission. For a complete list of global permissions, see Appendix B, ―Project Server 2010 Global Permissions.‖
Note If neither check box is selected for a permission, the user is not allowed the permission unless it
is allowed in another group that the user is a member of, or it is allowed at the user level. If the Deny check box is selected for a permission, that permission is denied for all users in the group and cannot be allowed through other group or user settings.

26 Project Server 2010 Administrator's Guide

Delete a security group
If you no longer need a security group in Microsoft Project Server 2010, you can delete it. Before you delete a group, ensure that no other users or groups depend on it for required permissions. Security groups are permanently deleted, unlike deactivated user accounts (which can be reactivated). If you delete a security group and then find that you want to have it again, you must recreate it. The Manage users and groups global permission in Project Server 2010 is required to complete this procedure.
Important We highly recommend not deleting the default Project Server groups. The Team Members
group cannot be deleted.

Delete a custom security group

Perform the following procedure to delete a group in Project Server 2010.
 To delete a custom group 1. On the Server Settings page, in the Security section, click Manage Groups.

On the Manage Groups page, in the Group Name list, find the group you want to delete. Select the check box next to the group that you want to delete. Note that you can select multiple groups. 3. Click Delete Group. 4. A message box appears, asking for confirmation and noting that the group will be permanently removed. Click OK to delete the group.
2.

Active Directory Group Synchronization
Project Server 2010 security group synchronization controls Project Server security group membership by automatically adding and removing users from specified Project Server security groups based on group membership in the Active Directory directory service. Each Project Server

Security

27

security group can be mapped to a single Active Directory group. This Active Directory group can, however, contain nested groups whose members will also be synchronized. The following actions can occur during a Project Server security group synchronization process:

    

A new Project Server user account can be created based on an Active Directory account. An existing Project Server user can be removed from a Project Server security group. An existing Project Server user can be added to a Project Server security group. An existing Project Server user account's metadata (name, e-mail address, and so on) can be updated if it has changed in Active Directory. A previously inactive Project Server user account can be reactivated.

Before you perform this procedure, confirm that:

 You have access to Project Server through Project Web Access with an account with the  The Service Application service account for the Project Server instance has Read access to
all Active Directory groups and user accounts involved in the synchronization. You can verify this account in the on the Service Application page on the Central Administration site. Manage Active Directory Settings and the Manage users and groups global settings.

To configure security group synchronization
Use this procedure to configure security group synchronization with Active Directory in Project Server 2010. The following table describes possible scenarios and corresponding actions that occur when security group synchronization takes place: Scenario The user exists in Active Directory and is a member of the Active Directory group mapped to the current Project Server security group. The user does not exist in Project Server. The user is not a member of the Active Directory group mapped to the current Project Server security group. The user also exists in Project Server and is a Action A new corresponding user account is created in Project Server and is granted membership to the current Project Server security group.

The existing Project Server user is removed as a member of the current Project Server security group.

28 Project Server 2010 Administrator's Guide

Scenario member of the current Project Server security group. The user exists in Active Directory and is a member of the Active Directory group mapped to the current Project Server security group. The user also exists in Project Server, but is not a member of the current Project Server security group. The user exists in Active Directory and is a member of the Active Directory group mapped to the current Project Server security group. The user also exists in Project Server and is a member of the current Project Server security group. User information has been updated in Active Directory. The user exists in Active Directory and is a member of the Active Directory group mapped to the current Project Server security group. The user also exists in Project Server, but as an inactive account.

Action

The existing Project Server user is given membership to the current Project Server security group.

The corresponding Project Server user information is updated (if applicable).

If the Automatically reactivate currently inactive users if found in Active Directory during synchronization option is selected in Project Server, the account is reactivated and is added to the current Project Server security group. If the option is not selected, the account remains inactive in Project Server.

 To configure security group synchronization 1. On the Project Web App Home page, click Server Settings.

On the Server Settings page, in the Security section, click Manage Groups. 3. On the Manage Groups page, in the Group Name column, click the name of the security group that you want to synchronize. 4. On the Add or Edit page for the group you selected, in the Group Information section, for Active Directory Group to Synchronize, click Find Group.
2.

Global. You can synchronize to a security or distribution group of any scope (Local. To select a group from a remote forest. From the Group Name list. you should see the Active Directory group you selected in the Group Information section next to Active Directory Group to Synchronize. Click OK.contoso. Click the button next to the Group Name field to search the Active Directory forest based on your search criteria. On the Add or Edit Group page.Security 29 5. On the Manage Groups page. select the check box next to the security group that you just configured for synchronization. Note The Active Directory forest that is search is displayed at the top of the Find Group in the Active Directory page. 8. or Universal). in the Group Name field.com). group@corp. The forest is defined by the fully qualified domain name of the account for the Service Application on which the Project Server instance is running. 6. Then click Active Directory Sync Options. enter all or part of the name of the Active Directory group which you want to synchronize with your security group. in the Group Name column. type the fully qualified domain name of the group (for example. select the group with which you want to synchronize your Project Server security group. On the Find Group in Active Directory page. Click Save. 7. .

13. In the Frequency fields. select Automatically reactivate currently inactive users if found in Active Directory during synchronization. To do so. in the Options section.30 Project Server 2010 Administrator's Guide Synchronize Project Server Groups with Active Directory 9. You can check the status of the security group synchronization by returning to the Synchronize Project Server Groups with Active Directory page for the specific security . on the Synchronize Project Server Groups with Active Directory page. 11. or months. you can choose to manually run the security group synchronization. (For example. Click Save to save the settings. If you want to schedule synchronization to occur on a scheduled basis. This can be scheduled over a defined period of days. select Schedule Synchronization. weeks. in the Scheduling section. Select a start date and time. you can rerun it manually when needed by returning to this page and clicking Save and Synchronize Now. skip the following step and continue to step 11. Click Save and Synchronize Now if you want to synchronize your Project Server security group immediately. 12. enabling this option would ensure that if an employee were rehired. Alternatively. define the frequency at which you want synchronization to occur between the Project Server security group and the Active Directory group. 10. If you prefer the manual option. the employee's user account would be reactivated). If you choose not to schedule the synchronization. You can enable inactive user accounts to be reactivated if they are found in the Active Directory group during synchronization.

Any user associated with a category can be granted permission to the projects and resources in that category. Intended for users who need to approve timesheets. My Resources My Direct Reports My Organization Resource Managers Executives Portfolio Managers Project Managers Resource Managers . These default categories enable Project Server to provide the most common layer of security for a hierarchical organization or matrix organization. Manage Categories Categories are the collections of projects. This category is intended for members of a Project Management Office (PMO). resources. Categories also allow the administrator to filter data using security rules. Having a large number of groups and categories within an organization can stress the authorization system. or delete a category. modify. You can manually add projects and resources to categories by choosing them from lists. You must have the Manage users and groups global permission to add. Avoid creating unnecessary categories. and views) that these users and groups have access to. like Resource Breakdown Structure (RBS). Used to grant access to all information in the organization.Security 31 group and reviewing the information in the Status section. Default category My Tasks My Projects Default groups in the category Team Members Project Managers Resource Managers Team Leads Resource Managers Description Primarily used by project resources who have assigned tasks. resources. or delete a group. Microsoft Project Server 2010 creates five default categories during installation. The Manage users and groups global permission in Project Server 2010 is required in order to create. modify. or you can use dynamic filters to automatically add them to categories. and views to which users and groups in Project Server are granted access. Provides access to all projects that a user owns. which can affect performance. that can help organize and display data in specific ways. Categories define which collections of specific data (projects. Intended for resource managers and is useful only after the Resource Breakdown Structure (RBS) is defined. executives in an organization. It will contain information such as when the last successful synchronization occurred.

32 Project Server 2010 Administrator's Guide Default category Default groups in the category Administrators Description and other key users who require the ability to view projects and resources across the entire organization. 3. click Server Settings. To modify an existing category. 2. Complete the Add or Edit Category page. in the Security section. which can affect performance. click Manage Categories. 4. Click Save. click Manage Categories. Having a large number of groups and categories within an organization can lead to greater administrative complexity. Avoid creating unnecessary categories. Click Save. 4. On the Project Web App home page. in the Quick Launch. Additionally. perform the following procedure. in the Security section. 3. To create a new category. The Manage users and groups global permission in Project Server 2010 is required to complete these procedures.  To modify a category 1. On the Server Settings page.  To create a category 1. On the Manage Categories page. so assigning them to this category avoids unneeded work by the authorization system. click the category that you want to modify. you can add custom security categories as necessary to create a Project Server security model that meets the specific needs of users and groups in your organization. click Server Settings. large numbers of groups and categories can stress the authorization system. See the following sections for information about each setting. See the following sections for information about each setting. . consider adding them to a custom category that gives them visibility of all projects (avoiding dynamic rules). in the Quick Launch. On the Manage Categories page. 5. click New Category. Complete the Add or Edit Category page. On the Server Settings page. perform the following procedure. On the Project Web App home page. 2. Create or modify a category In Microsoft Project Server 2010. Top-level RBS users probably have access to all projects. 5. If there are many users at the highest level of the RBS.

This name must different be than that of other categories. Attribute Category Name Description Description The name of the category. select the user or group in the Available Users and Groups list. . Category name and description The following table describes the name and description options for a category. only associate groups with categories.Security 33 Name and Description Use the Name and Description section to specify a name and description for the category. Users and Groups Use the Users and Groups section to specify which users and groups are associated with this category. Description of the category. select the user or group in the Users and Groups with Permissions list and then click Remove. Attribute Available Users and Groups Users and Groups with Permissions Description Users and groups that are not associated with this category. Category users and groups To associate a user or group with this category. To remove the association between a user or group and this category. Users and groups that are associated with this category. and then click Add. For easiest administration.

For a complete list of category permissions.34 Project Server 2010 Administrator's Guide To select the category permissions for each user or group. Category permissions for the Project Managers group Each user or group can be assigned distinct permission within a category. select the user or group in the Users and Groups with Permissions list.‖ Projects Use the Projects section to specify the projects that users associated with this category can view. This will display the category permissions for the selected group in this category. . ―Project Server 2010 Category Permissions. see Appendix A.

When this option is selected. Attribute All current and future projects in Project Server database Only the projects indicated Description When this option is selected. Also gives Status Managers permissions on projects that contain assignments that they manage. Available projects Selected projects The User is the Project Owner or the User is the Status Manager on . users in this category can see all projects in this instance of Project Web App. Gives users permissions on any project they own. Projects that are not explicitly part of this category. Users may still be able to view these projects if any of the dynamic permissions options are configured to allow it. users in this category can view the projects in the Selected Projects list and any projects from the Available Projects list that the user has permissions to see using the dynamic permissions options. or you can use one of the dynamic security options to have projects made available to users based on their relationship to the project or their RBS value.Security 35 Category / project association You can explicitly select projects that users with permissions in this category can view. The dynamic permissions features only work when this option is selected. Projects that users in this category can view.

Avoid using this rule for users who have many resources under them in the RBS. this stress on the authorization system can affect performance (for example. delay the loading of the Project Center page). Users do not need to have assignments on the project. . Allows a user to view any project where a resource subordinate to the user in the RBS is on the project team. The User is on that project's Project Team The Project Owner is a descendant of the User via RBS A resource on the project's Project Team is a descendant of the User via RBS Description The Project Owner has the same RBS value as the User Gives users permissions on any project where they are on the project team. Gives users permissions on any project that is managed by resources subordinate to them in the Resource Breakdown Structure (RBS) hierarchy. Resources Use the Resources section to specify which resources the users associated with this category can view. If the resources under them are on many projects involving many categories.36 Project Server 2010 Administrator's Guide Attribute assignments within that Project. Allows a user to view projects managed by persons that have the same RBS value that the user has.

users in this category can view the resources in the Selected Resources list and any resources from the Available Resources list that the user has permissions to see using the dynamic permissions options. Gives users permissions to view information for all Available Resources Selected Resources The User is the resource They are members of a . Resources that are not explicitly part of this category.Security 37 Category / resource association You can explicitly select resources that users with permissions in this category can view. Gives users permissions to view information about themselves (such as assignments). Attribute All current and future resources in Project Server database Only the resources indicated Description When this option is selected. or you can use one of the dynamic security options to have resources made available to users based on their relationship to the resource or their RBS value. Resources that users in this category can view. users in this category can see all resources in this instance of Project Web App. When this option is selected. Users may still be able to view these resources if any of the dynamic permissions options are configured to allow it.

Views – Add to Category Use the Views – Add to Category section to specify views that users associated with this category can see. . Global permissions To add a view to the category. clear the Add check box for that view. To remove a view. Gives user permissions to view information about resources that have the same RBS value. select the Add check box for that view.38 Project Server 2010 Administrator's Guide Attribute Project Team on a project owned by the User They are descendants of the User via RBS They are direct descendants of the User via RBS They have the same RBS value as the User Description resources in projects they own. Gives users permissions to view information about resources that are directly under them in the RBS. Gives users permissions to view information for all resources under them in the RBS.

Select the check box next to the category that you want to delete.  To delete a category 1. Caution Verify that the category you are deleting is the one you intend to delete. noting that the category will be permanently removed. find the category that you want to delete. . you can delete any existing custom category from the Manage Categories page in Microsoft Project Web App. Delete a custom category Perform the following procedure to delete an existing category in Project Server 2010. Note Default Project Server categories cannot be deleted. 4. 3. in the Security section. Click Delete Categories. The Manage users and groups global permission in Project Server 2010 is required to complete this procedure. Click OK. in the Quick Launch. 5. On the Project Web App home page. Note that you can select multiple categories. On the Manage Categories page. it is permanently deleted and will need to be recreated. On the Server Settings page. click Manage Categories.Security 39 Delete a category In Project Server 2010. If you accidentally delete the wrong category. click Server Settings. in the Category Name list. A warning message appears. 2.

modify. Next. groups. By applying security templates. These align with the predefined groups. . and categories. resources. You must first identify the common Project Server usage patterns in your organization that are not reflected in the default Project Server security templates. determine the permissions that the users who share the common Project Server usage patterns require. The permissions that you define in the custom security template enables users to access the Project Server security objects that they require. Creating custom templates requires planning. you can easily standardize the permissions that you assign according to user's role in the organization. groups. this defines the security category. The Manage users and groups global permission in Project Server 2010 is required to create. Create or modify a security template In Microsoft Project Server 2010. and categories. or delete a security template. A number of predefined security templates are created by default when Microsoft Project Server 2010 is installed. that the users and groups require access to. This defines the security template. when creating new security templates. views. Create the custom security template and apply it to the group of users that share the common usage pattern. you can group commonly used permissions into a security template and then use it to assign permissions to users. Project Server 2010 creates eight default security templates during installation:  Administrators  Executives  Portfolio Managers  Project Managers  Proposal Reviewers  Resource Managers  Team Leads  Team Members Each security template is given a set of default category and global permissions. As mentioned previously. based on the functions that each group typically does in an organization. You can customize these security templates or create new security templates according to your needs. This helps you to identify your requirements for custom security templates.40 Project Server 2010 Administrator's Guide Manage Security Templates Security templates provide a method for you to quickly apply or reset predefined permission profiles to new or existing users. you are allowed to copy the permissions for a default security template and then customize it to suit your needs. determine the set of projects. We recommend not modifying the default templates. and so on. Then.

Perform the following procedure to modify an existing template in Project Server 2010. 3. Click Save. Perform the following procedure to create a template in Project Server 2010. On the Manage Templates page. On the Add or Edit Template page. . On the Server Settings page.  To create a template 1. or categories to which the template was applied in the past. click the template that you want to edit. click Manage Templates.  To modify a template 1. do not make any changes to the default Project Server templates. click Server Settings. On the Project Web App home page. you can modify the permissions for any existing template in the Manage Templates page in Microsoft Project Web App Server Settings.Security 41 The Manage users and groups global permission in Project Server 2010 is required to complete this procedure. On the PWA home page. optionally. in the Quick Launch. See the following sections for information about each setting. to select an existing template to copy the settings from an existing template into the new template. click Manage Templates. in the Security section. in the Template Name list. In Microsoft Project Server 2010. 3. Name Use the Name section to specify a name and description of the template and. Note Modifying a template does not make any changes to users. in the Quick Launch. 5. click Server Settings. 4. 5. 2. groups. make your changes to the template. 4. Click Save. As a best practice. Complete the Add or Edit Template page. On the Server Settings page. click New Template. On the Manage Templates page. See the following sections for information about each setting. in the Security section. 2. The Manage users and groups global permission in Project Server 2010 is required to complete this procedure.

If you do not select the Allow check box for a permission. . you can modify the values as needed to meet your needs. Important The values from the copied template will overwrite any existing values in this template. Category Permissions To allow a category permission for this template. If you do not copy a template. select the Allow check box for that permission. After you copy the template. this template will be blank and you can modify the values as needed.42 Project Server 2010 Administrator's Guide Template name and Copy Template options If you choose a template from the Copy Template dropdown list. Category Permissions Use the Category Permissions section to set the category permissions for this template. the values from that template are copied to this template. that permission will not be allowed in the categories where you use this template. but could be allowed in other categories.

select the Allow check box for that permission. The Manage users and groups global permission in Project Server 2010 is required to complete this procedure. Global Permissions Use the Global Permissions section to set the global permissions for this template. select the Deny check box for that permission.Security 43 To deny a category permission for this template. . Delete a security template In Microsoft Project Server 2010. but could be allowed in other groups. that permission will not be allowed in the groups where you use this template. Global Permissions To allow a global permission for this template. do not delete any of the default Project Server templates. you can delete any existing security templates from the Manage Templates page on the Microsoft Project Web App site. To deny a global permission for this template. As a best practice. If you do not select the Allow check box for a permission. select the Deny check box for that permission.

Click Delete Template. click Manage Templates. On the Manage Templates page. If a Project Web App permission is disabled on this page. 3. users throughout PWA cannot delete projects. in the Template Name list. click Server Settings. regardless of whether they have the Delete project category permission. On the Project Web App home page. Manage Project Web App Permissions You can use the Manage Project Web App Permissions page to control which global and category permissions are enabled on a given Microsoft Project Server 2010 instance. Click OK. All permissions on this page are enabled by default. . Important Before disabling a Project Web App permission. 2. thoroughly consider the effects on your organization of doing so. If you want to turn off a permission for only some Project Web App users. A warning message appears. in the Security section.  To delete a template 1. An administrator can use the Project Web App Permissions page to deny access to all Project Server 2010 users for a particular feature in Microsoft Project Professional or a Microsoft Project Web App (PWA) instance. in the Quick Launch.44 Project Server 2010 Administrator's Guide Delete a template Perform the following procedure to delete a template. 4. verify whether you can do it by creating a custom group and denying the permissions you want to restrict. noting that the template will be permanently removed. For example. if you deny the Delete project permission. 5. select the check box next to the templates that you want to delete. On the Server Settings page. the equivalent global or category permission is disabled for users throughout WPA.

clear the Enable check box next to the permission that you no longer want to make available to Project Web App users. in the Quick Launch. Enabling a previously disabled permission is simply done by selecting the Enable check box next to the permission that has been disabled.Security 45 Disable Project Web App Permission The Manage users and groups global permission in Project Server 2010 is required to complete this procedure. On the Project Web App home page. in the Available Project Web App Permissions list. click Project Web App Permissions. 3. On the Server Settings page. Perform the following procedure to disable a Project Web App organizational permission in Project Server 2010. Manage Delegates Microsoft Project Server 2010 enables user delegation throughout all of Project Web App. in the Security section. On the Project Web App Permissions page. 2.) 4. Click Save. .  To disable a Project Web App permission 1. This means that one user can act as another user in every part of Project Web App. regardless of the permission level difference of one user compared to the other. click Server Settings. (All Project Web App permissions are enabled by default.

you can set permissions to control the specific behavior of the feature in Project Web App.46 Project Server 2010 Administrator's Guide Turn Delegation on or off The user delegation feature in Project Web App can be enabled or disabled globally. 2. there are user or group level permissions that enable you to determine which users or groups can act as delegates for other people. click Project Web App Permissions 3. On the PWA home page. . under Security.  Can be Delegate Select this check box to enable users to actively become a delegate for another user. On the Server Settings page. click Server Settings. 4. after a delegation has been created. select the check box for the Manage Resource Delegates permission to turn on the user delegation feature within Project Web App. you'll need to set the appropriate permissions. the only group with these permissions turned on is the administrators group. so if you want users in your organization to be able to act as delegates. for all users and groups. Set up who can act as delegate In Project Web App. Choose any additional delegation permissions that meet your organization's needs:  Manage My Resource Delegations Select this check box to enable users to set up delegations for other users. Click Save to save the permissions on the server. When user delegation is turned on.  Manage My Delegations Select this check box to enable users to create delegations for themselves. 5. In the Resource section. By default.  To turn delegation on or off 1.

5.  To set permissions for a group 1. 3. In the Global Permissions section. Click Save to save the permissions on the server. choose the appropriate permissions for this group. Click the name of the user for which you are setting permissions. 2. On the Add or Edit Group page. 4. 6. click Manage Groups. 2.  Manage My Resource Delegations Select the Allow check box for this permission to enable this user to set up delegations for other users.  Manage My Delegations Select the Allow check box for this permission to enable this user to create his or her own delegations. expand the Global Permissions section. Click the name of the group for which you are setting permissions. click Manage Users. On the PWA home page. In the Global Permissions section. click Server Settings. Under Security. 3. On the Edit User page. . choose the appropriate permissions for this user. Under Security. under Resource. under Resource. On the PWA home page.Security 47  To set permissions for a specific user 1. 5.  Can be Delegate Select the Allow check box for this permission to enable this user to actively become a delegate for another user. 4. click Server Settings. expand the Global Permissions section.

Under Security. 4. Manage My Resource Delegations Select the Allow check box for this permission to enable members of this group to set up delegations for other users. click the name of group or a specific user in the Users and Groups with Permissions box. 6. click Server Settings. Manage My Delegations Select the Allow check box for this permission to enable members of this group to create their own delegations. In the Users and Groups section.48 Project Server 2010 Administrator's Guide    Can be Delegate Select the Allow check box for this permission to enable members of this group to actively become delegates for other users. the user requesting the delegation must have the correct category permissions. Set up who can have delegates assigned to them Categories are used to determine which users or groups can have delegates do work on their behalf.  To set up who can have delegates assigned to them 1. For a delegation to work properly. On the PWA home page. 3. Click Save to save the permissions on the server. Click the name of the category that contains the user or group for which you want to enable user delegation. and the user who will act as the delegate must have the correct individual user or group permissions. . click Manage Categories. 2.

6. 5. Click Save to save the permissions on the server. click Manage Delegates. Under Security. scroll down to the Resource section. 7. In the Set Delegation Period section. On the interface ribbon click New 2. 4. In the Set Delegation section.  To create a delegation 1. 3. 6. and select the check box for the Manage Resource Delegates permission to turn on the user delegation feature for that user or group. . Create a new delegation Creating a new delegation allows one user to work on behalf of another user. such as submitting a second user’s timesheet. In the Working on Behalf of section. select the user who requires a substitute. On the PWA home page.Security 49 In the permissions box that appears. click Server Settings. 5. Click Save to save the permissions on the server. select the delegate that you want to manage work during the specified period. select the date range for the period during which the delegate will be able to manage work.

50 Project Server 2010 Administrator's Guide 2 Enterprise Data This chapter about Project Server 2010 Enterprise Data Administration contains the following sections:       Enterprise Custom Fields and Lookup Tables Departments The Resource Breakdown Structure (RBS) Enterprise Global Enterprise Calendars Resource Center .

 You can set Enterprise Custom Fields as required fields so that users are prompted to enter information in that field before saving. To determine the scope of Enterprise Custom Fields that your organization requires. tasks. For example:  You can customize project management to reflect your organization’s structure and processes. all users in your organization have access to a standard set of fields. it is important to correctly design your Enterprise Custom Fields. By using Enterprise Custom Fields effectively. Because creating Enterprise Custom Fields can range from being simple to being very complex and time-consuming. When you use Enterprise Custom Fields. and assignments. consider the following questions: . That way you can ensure that fields and associated lookup tables are used in the same way for all projects. enabling the same operations to be completed across entire sets of projects.  You can use Enterprise Custom Fields on a per-department basis. All users in your organization can have access to a standard set of fields. which enables operations to be applied the in same way across entire sets of projects. resources.Enterprise Data 51 Enterprise Custom Fields and Lookup Tables You can use Enterprise Custom Fields to help to establish consistency across all of your organization’s projects. you can help to customize Project Server 2010 to fit the unique needs of your organization. Enterprise Custom Fields can include custom formulas and can allow the use of lookup tables and graphical indicators.

For example. Creating Enterprise Custom Fields Project Server Enterprise Custom Fields are created and maintained through the Server Settings page in Microsoft Project Web App (PWA). . if two project managers use different fields to identify a resource’s location. You can create Enterprise Custom Fields at the task. if each department has a different accounting method or funding process. You can use the Project Departments or Resource Departments custom fields in conjunction with the Department custom lookup table. project. the executives might need to identify a method for defining this. and resource level. It is important to determine which specific Enterprise Custom Fields your organization needs when you review your business requirements while planning your Project Server 2010 deployment. The most important use for Enterprise Custom Fields is to enable organizations to enforce consistency across all projects. then users will be unable to identify when the same resource is assigned to projects managed by each project manager. For example. How will you sort and select data? How will you use graphical indicators to help users identify the correct data?   Understanding Enterprise Custom Fields You can use Enterprise Custom Fields to create a set of project management standards that can be applied across your organization and to enhance the capabilities of Project Server 2010.52 Project Server 2010 Administrator's Guide  What words or phrases are used by stakeholders in your organization. or any enterprise custom filed with the Department property set to accomplish this. they need to define a consistent method for identifying departments within the organization. In order to achieve this business requirement. What are the user requirements in your organization? User requirements are frequently based on reporting requirements. such as return on investment (ROI). It is best to do this after you have performed a gap analysis by comparing the capabilities of Project Server 2010 against the business needs of your organization. as well. Also consider the concepts behind the common words and phrases used by stakeholders in your organization. and so on? You might want to quantify and codify these concepts by means of Enterprise Custom Fields. In addition. a group of executives in an organization wants to be able to view project data by department. Key Performance Indicator (KPI).

Under Enterprise Custom Fields. On the PWA Server Settings page.  To create Enterprise Custom Fields 1. click New Field.Enterprise Data 53 New Custom Field page The New Custom Field page allows you to specify the options for a custom field. 2. Use the following procedure to create a new enterprise custom field. click Enterprise Custom fields and Lookup Tables. .

Resource. Entity and Type Use the Entity and Type areas to specify whether you want a Project. See the descriptions for each field in the following sections. or Task custom field. 4. A description of the custom field. 3. Custom Field Entities The following table describes each of the available entities. Select to create Enterprise Custom Fields . Name and Description Use the Name and Description areas to specify a name and description for the custom field. Custom Field Name and Description The following table describes the name and description fields. Attribute Name Description Description The name of the custom field. Click Save. and what data type the field should be. Attribute Project Resource Description Select to create Enterprise Custom Fields that are applied at the project level.54 Project Server 2010 Administrator's Guide Fill out the New Custom Field page with the custom field options that you want to use.

non-hierarchical. For example. Use custom date fields to specify date-driven data. you might use a task-level field to record the estimated lines of code in a software development project or to compare a project’s actual cost to its proposed cost. Use custom duration fields to define a duration. and Behavior section. For example. and use it to record the date on which a project is approved. Calculation for Summary Rows. alphanumeric Duration Flag Number Text . Select to create Enterprise Custom Fields that are applied at the task level. For example. Custom Field Types The following table describes the available custom field types. The value you choose here will affect which options are available in the Custom Attributes. Attribute Cost Date Description Use custom cost fields to define currency data. Use custom flag fields to define anything that can have only two choices for defining the data. you can create an Enterprise Custom Field called Project Approval Date. For example. you can use a custom cost field to define a project’s Approved Budget. Use custom text fields to define simple. The Type selection defines the data type of the custom field. For example. Use custom number fields to define any numeric set of data or to perform a custom calculation by using a custom formula. a custom duration field can enable your organization to define a way for a project manager to show and store the difference between a project’s original schedule and the actual schedule. you might use a flag field to determine whether to display a field or to enable a macro that controls whether a particular set of data will be available in the project. These are frequently defined as calculations that use custom formulas.Enterprise Data 55 Attribute Task Description that are applied at the resource level.

you have the option of specifying one or multiple lines of text for the custom field. Custom Attributes When you select a Project Text custom field. Select if you want the custom field to be multiple lines of text. This allows you to control the values chosen for the custom field. The project field created with this option is not visible in project information tab in Project Professional. Custom Attributes . Attribute Single line of text Multiple lines of text Description Select if you want the custom field to be a single line of text. Suspended. and Closed.text The following table describes the custom text options. For example. you can create a custom text field called Project Status that includes options such as Initiated. This field however can be exposed via web based PDP page.56 Project Server 2010 Administrator's Guide Attribute Description data. This option is available only for Project Text fields. This option is available only for Project Text fields. Approved. You can:  Choose whether to have a default value if no other is chosen  Choose whether to allow multiple values to be selected from the lookup table  Choose to restrict available values to those values in the table that have no subordinates The lookup table option is available when you have selected Text as the filed type. Cancelled. Custom Attributes – lookup table . You can choose to have a custom lookup table supply the values for a custom field. In-Progress.

Select this option if you want to allow users to select more than one value from the lookup table. If you want to have a default value included in this custom field in cases where the user does not specify one. . click the browse button and select the desired value. Once this selection has been made and saved. create the lookup table before creating the custom field. select this check box. Attribute Lookup Table Description The name of the Enterprise Custom Lookup Table that you want to associate with this custom field. To set the value.Enterprise Data 57 The following table describes the lookup table options for custom fields. Once you have associated a lookup table with a field and have saved it. Therefore. Formulas cannot be used with all types of Enterprise Custom Fields. You can use formulas to define your own parameters for how your Enterprise Custom Fields will measure data or present information when they are used in a project. The formula option is available with all field types. The default value to be used in this field when users do not specify a value. make sure you need the lookup table before making this association. Select this option if you want to allow only values in the lookup table that have no subordinate values (that is. you will not be able to remove the lookup table relationship. values at the lowest level of each branch). Choose a values to use as a default when adding new items Default value Only allow codes with no subordinate values Allow multiple values to be selected from lookup table Note If you plan to create a custom field that will refer to a lookup table. it cannot be removed. and then select the default value.

To reference an existing Enterprise Custom Field. point to a field type. click Pick function. Baseline Finish and Finish in this example.formula Note Once a formula is associated with a custom field. point again to a custom field type (such as Custom Date or Custom Finish). point to a field type. it can be edited but it cannot be removed. and then click the Enterprise Custom Field that you want.  To add a field to the formula. and then click the function that you want. For example.58 Project Server 2010 Administrator's Guide Custom Attributes . type the formula in the Edit formula box. . Each function includes placeholder arguments that you can replace with the fields and values that you want to use. and then click the name of the field that you want to reference.  To use a function in the formula.  To use a known formula. click Pick field. click a function type.

Use Insert operator to insert an operator (mathematical or Boolean) into the formula. date. Attribute Enter formula Insert field Insert function Insert operator Description Type the formula you want to use in the Enter formula text box. If you do not specify a department. The formula can operate by using referenced fields.Enterprise Data 59  To build a formula by using a standard set of operators. Department You can select a department to be associated with a custom field. . Selecting a department allows you to limit a user’s ability to see the custom field if they are not a member of that department. or text) into the formula. or text) into the formula. or literal data. Microsoft Project. Use Insert field to insert a field (cost. flag. click Pick operator and choose the operator that you need. date/time. duration. then all users will be able to see the custom field. The following table describes the formula options. math. functions. general. Use Insert function to insert a function (conversion. number.

The following table describes the options for summary task calculation. you can select options for the calculation of summary rows. You must specify the formula to use under Custom Attributes. Attribute None Rollup Use formula Description Choose None if you do not want the custom field to be applied to summary and group summary rows. . Calculation for Assignment Rows For resource types of Resource and Task. Choose Rollup to roll up the individual rows for the summary row.60 Project Server 2010 Administrator's Guide Custom fields department selector The values available for Department are specified in the Department custom lookup table. Calculation for Summary Rows For entity types of Resource and Task. The following table describes the options for calculating assignment rows. Summary row calculation options Note that summary row calculation is not available with a field type of Text. Choose Use formula to use a specific formula to calculate the summary row. you choose to use a roll down calculation for assignment rows.

Summary rows. When you configure graphical indicators. Choose Roll down if you want data entered at task or resource level to be rolled down and copied to each assignment with the same value. and.data If you choose Graphical indicators. The following table describes the options for graphical indicators. Choose Summary rows to specify criteria for graphical representation of summary rows. if you are using an entity type of Project. Choose Project summary to specify criteria for graphical representation of the project summary.Enterprise Data 61 Attribute None Roll down. Project summary. you can specify the exact value and comparison parameters that determine when a particular graphic will be used. you can choose different criteria for Non-summary rows. unless manually specified Description Choose None if you do not want to roll down assignment rows. Graphical indicators options When you choose an option. Values to display . Attribute Non-summary rows Summary rows Project summary Description Choose Non-summary rows to specify criteria for graphical representation of data rows that are not summary rows. Values to Display You can choose to display raw data or to have the data represented graphically. further configurable parameters specific to that option will be displayed. The available comparison (test) parameters are:  Equals .

For example. Rows in the table will be evaluated from top to bottom and the image associated with the first row where the test/value combination is true will be displayed. Graphical indicators You can specify as many different images for different values as required. Attribute Description . you can configure values greater than or equal to 50 to display a green indicator and values less than 50 to display a red indicator. Add a new row to the table for each test/value comparison.62 Project Server 2010 Administrator's Guide            Does not equal Is greater than Is greater than or equal to Is less than Is less than or equal to Is within Is not within Contains Does not contain Contains exactly Is any value These are used to compare the data value with a threshold value that you specify to determine which graphic to display. The following table describes the graphical indicator options for non-summary rows.

the graphical indicator parameters you configured for the summary rows will be used. determines when to use the image in the Image column. Type the field value or a field reference (e.. the graphical indicator parameters you configured for the non-summary rows will be used.Enterprise Data 63 Attribute Test Values Image Move Show data values in ToolTips Description Choose the operator (equals. . When using graphical indicators for summary rows.g. Select the Show data values in ToolTips to show the field value in the tool tip associated with the image. Graphical indicators – project summary If you select the Inherit criteria from summary rows check box when configuring graphical indicators for project summary. etc. Choose the image to display when the test/value combination is true.) to apply to the field value to determine the image to use. [cost]) that. you can choose to inherit the graphical indicator settings that you have defined for non-summary rows. less than. Graphical indicators – summary rows If you select the Inherit criteria from non-summary rows check box when configuring graphical indicators for summary rows. Use the move buttons to move a row up or down in the table. combined with the operator in the test column. Behavior You can configure a custom field to be controlled by workflow or to require a value.

and another might enter In-Progress. Creating Enterprise Custom Lookup Tables Consider using custom lookup tables for any Enterprise Custom Field for which standardization of data is the most important factor. If you do not specify a lookup table for this custom text field. To do this. Without using lookup tables. For example. . you click the Resource option. the field cannot be left blank). This option is not available if the Behavior controlled by workflow option is selected.64 Project Server 2010 Administrator's Guide Behavior options If you choose to have the custom field controlled by a workflow. you might create a custom text field that is associated with Resources. and rename it Manager. The following table describes the options for configuring custom field behavior. a user can enter any text value in the Manager field. For example. it is difficult to standardize terminology in your organization. One project manager might enter Started. select Text from the list. the required field option will not be available since that behavior will be controlled by workflow. Choose whether you want this to be a required field (that is. it might not be a good practice to allow users to enter any integer value in a custom Status field. Attribute Behavior controlled by workflow Require that this field has information Description Select this check box if you want the custom field behavior to be controlled by workflow. both indicating that the project has begun and is underway.

On the PWA Server Settings page.Enterprise Data 65 New custom lookup table page The New Lookup table page allows you to specify the options for a custom lookup table. 3.  To create Enterprise Custom Fields 1. 2. Fill out the New Custom Field page with the custom field options that you want to use. See the descriptions for each field in the following sections. Under Lookup Tables for Custom Fields. Use the following procedure to create a new enterprise custom lookup table. click Enterprise Custom fields and Lookup Tables. 4. 5. Click Save. . Type a name for the lookup table in the Name box. click New Field.

Code mask options The code mask allows you to specify what type of text characters will appear in the lookup table. and what characters to use to separate levels in a hierarchy. Attribute Cost Date Duration Number Text Description Each field in the table will be a cost value. Each value in the table will be text. Each field in the table will be a date value. Lookup table types The table below describes the options for data types within a custom lookup table. If you . Each value in the table will be treated as a duration. Code Mask The code mask option only appears when a field type of Text has been selected.66 Project Server 2010 Administrator's Guide Type You must specify a data type for each lookup table. Choosing Text also allows a hierarchy of values to be specified if desired. Each value in the table will be a number. It is not possible to mix field types within a table. the length of the string.

Lookup table options Type each that you want in the lookup table in the Value column. Specify the type of text characters to allow. Specify from one to three characters to use as a separator between levels of the table hierarchy.Enterprise Data 67 are creating a hierarchical lookup table. Attribute Description . Choose Numbers. Lookup Table Use the Lookup Table section of the New Lookup table page to specify the values in the lookup table. include a description for the value in the Description column. The following table describes the options available for configuring code masks. Uppercase characters. Create as many rows as needed to accommodate the values that you want to include. you must specify a code mask for each level of the hierarchy. Choose a number from 1 to 255 or Any. Optionally. The following table describes the options for creating lookup table values. Lowercase characters. Attribute Code preview Sequence Length Separator Description Displays a preview of the code mask for the table. or Characters. Specify the maximum length of the string.

In Project Server 2010. Use the display order options do specify how to sort the lookup table. the table will be sorted based on the values in the Value column. Select the row and use the Indent and Outdent buttons to change levels. . If you choose to sort ascending or descending. Both projects and resources can have departments. at a resource. The value of the field. within the OLAP database configuration. you can specify both the project and resource departments so that the database data is filtered based on these criteria. When configuring a cube. Use the Move buttons to change the position of rows in the table. departmental custom fields help relieve the problem of too much information and too many choices. which fields are required or not required. task. Select the row and click the Up or Down Move button to move a row. only those fields that are either global to the system or in the department that the user belongs to. The main purpose of departments is to act as a filter for what custom fields are displayed to users within given areas of Microsoft Project Professional 2010 and PWA. Departments are also used to filter OLAP databases so that only the data for that department is loaded. With Project Server 2010. which means the fields are available to all users. Departments The Department field is a new feature for Project Server 2010. Departments help you manage the custom field list. the table will remain sorted as you specify it. Departments allow for different business units to define and make visible their own set of custom fields.68 Project Server 2010 Administrator's Guide Attribute Level Value Description Move Display order for lookup table Description Denotes the level in the hierarchy. An optional description of what the field represents. fields can be globally scoped or they can be scoped to a specific department. and help you define. by default. This is a read-only field. In Microsoft Office Project Server 2007 all custom fields are globally scoped. These values are specified in the OLAP Database Build Settings page. you can add the Project department field as a dimension to the Project and Tasks cubes. And you can add the Resource department field as a dimension to the Resource cube as long as the department field has not been converted to a multi-value field. or project level. Also.  Controlling which fields require input. Departmental fields enable two primary functions:  Filtering custom fields so that a user sees. If you choose By row number.

Instead. he will see:  ProjectCustomText1  ProjectCustomText2  ProjectCustomText5  ProjectCustomText6 John will be required to enter data into ProjectCustomText2 and ProjectCustomText5. then when he views areas of the product that have departmental custom fields enabled. By default. departments filter the list of custom fields that John Woods and Cindy White see. You cannot use them with security categories and groups to enable or disable fields and their functions.Enterprise Data 69 Example of departments in use Field ProjectCustomText1 ProjectCustomText2 ProjectCustomText3 ProjectCustomText4 ProjectCustomText5 ProjectCustomText6 Scope Global Global Department Department Department Department Department Marketing Marketing Development Development Required? No Yes No Yes Yes No If John Woods belongs to the Development department. when she views areas of the product that have departmental custom fields enabled. Cindy White belongs to the Marketing department. she will see:  ProjectCustomText1  ProjectCustomText2  ProjectCustomText3  ProjectCustomText4 Cindy will be required to enter data into ProjectCustomText2 and ProjectCustomText4. their main purpose is to filter out fields which are not useful for the target user. Department considerations for cubes Which cubes are filtered by which value No resource department specified No project department specified All data is loaded for all cubes Project department specified Project non-timephased cube Task non-timephased cube Issues cube Risks cube . Important Departmental fields are not tied into security. But the filter does not prevent them from viewing custom fields assigned to the other departments.

70 Project Server 2010 Administrator's Guide Which cubes are filtered by which value No project department specified Project department specified Deliverables cube MSP_Project_WSS virtual cube MSP_Project_Timesheet virtual cube MSP_Portfolio_Analyzer virtual cube Assignment non-timephased cube Assignment timephased cube EPM timesheet cube Filtered by Project Department: Resource department specified Assignment nontimephased cube Assignment timephased cube Resource nontimephased cube Resource timephased cube Timesheet cube MSP_Project_Timesheet virtual cube MSP_Portfolio_Analyzer virtual cube       Project non-timephased cube Task non-timephased cube Issues cube Risks cube Deliverables cube MSP_Project_WSS virtual cube Filtered by Resource & Project Department:  Assignment non-timephased     cube Assignment timephased cube EPM timesheet cube MSP_Project_Timesheet virtual cube MSP_Portfolio_Analyzer virtual cube Filtered by Resource Department:  Resource no.timephased   cube Resource timephased cube Timesheet cube .

 All deliverables to which the filtered list subscribes and the projects/tasks that subscribe to the filtered list's deliverables will be included. Timesheet:  Timesheets for departmental list resources will be included. The subset of projects and resources will be used to filter at the project and timesheet level as follows: Project non-timephased:  The data in this cube will be filtered by the departmental project list. Assignment non-timephased:  Non-departmental project assignments for the department’s resources will be included.  All assignments for departmental projects will be included. Assignment timephased:  Non-departmental project assignments for the department's resources will be included. .Enterprise Data 71 Cubes include assignments for resources in projects that belong to other departments or to no department. Resource timephased:  Resources in the departmental list will be included. This ensures that all data is present when examining data such as a department's resources full calendar capacity. Task non-timephased:  Non-departmental tasks with assignments to the department's resources will be included.  All tasks for departmental projects will be included. Resource non-timephased:  Resources in the departmental list will be included. Issues:  Issues connected to the filtered list of projects and tasks will be included.  All assignments for departmental projects will be included. Risks:  Risks connected to the filtered list of projects and tasks will be included. Deliverables:  All deliverables owned by the filtered list of projects will be included.  Projects with assignments to the department’s resources will be included. The full non-departmental project will not be included.  All deliverables offered by non-departmental projects that are subscribed to by departmental projects will be included.

and will only have the relevant assignment facts. assignment owner) The departmental resource list is used to filter facts with focus (Timesheets). a non-departmental resource will never have any timesheets or capacity in the OLAP database if the database has a resource filter. . However the non-departmental resource will be in the Resource List dimension if it has association with a departmental project.72 Project Server 2010 Administrator's Guide EPM Timesheet:  Timesheets for departmental list resources will be included. issue owner. Resources are described in three ways in the OLAP databases:  Fact focus (timesheets. capacity)  Associated with Facts (project task assignments)  Owning Facts (project owner. Assignment Owner) do not have to be in the resource list. Resources who own things that have separate dimensions (that is. By configuring values in this table.  Task assignments from projects outside the department will be included. you can define a hierarchy of departments for your organization. The Resource List dimension for a specific OLAP database contains:  The departmental resources  All resources with assignments to departmental projects Configuring departments Departments are configured using a built in Enterprise Custom Lookup Table called Departments. Consequently.

. choose Characters from the dropdown list. 2. On the Enterprise Custom Fields and Lookup Tables page. In the Code Mask section. In the Sequence column. click Enterprise Custom Fields and Lookup Tables. create a code mask for each level of the hierarchy that you plan to have for the Department lookup table: a.Enterprise Data 73 Department custom lookup table Use the following procedure to add initial values to the Department custom lookup table or to modify it. under Lookup Tables for Custom Fields.  To modify the Department lookup table 1. 3. click Department. Keep the defaults for the Length and Separator columns. On the PWA Server Settings page. b.

although it can also be structured in other ways. The Resource Breakdown Structure (RBS) The Resource Breakdown Structure (RBS) is a hierarchical structure typically based on the management reporting structure of your organization.74 Project Server 2010 Administrator's Guide 4. Click Save. . 5. 6. In the Lookup Table section. you can take advantage of the dynamic security options that can be defined for each security category. If you are creating a hierarchy with more than one level. type a Value and optionally a Description for each Department. use the Indent and Outdent buttons to change the level values for each department as required for you hierarchy. When you specify an RBS value for each Project Server user. The RBS can be an important element in your Project Server security model when it is used to define the reporting relationships among users and projects in your organization.

In the Code Mask section. On the Enterprise Custom Fields and Lookup Tables page. create a code mask for each level of the hierarchy that you plan to have for the Department lookup table: 2. under Lookup Tables for Custom Fields. Categories can use RBS codes to dynamically determine which projects and resources particular users can view or access. click RBS.  To modify the Resource Breakdown Structure 1. Dynamic filtering based on RBS code can be applied to projects in the following ways:  Users can see projects owned by their descendants in the RBS  Users can see projects on which their descendants in the RBS are a resource  Users can see projects owned by other users with the same RBS value Dynamic filtering based on RBS can applied to resources in the following ways:  Users can see their descendants in the RBS  Users can see their direct descendants in the RBS  Users can see other users with the same RBS value Use the following procedure to create a new Resource Breakdown Structure or to modify an existing one. On the PWA Server Settings page. click Enterprise Custom Fields and Lookup Tables. Once the RBS is configured. .Enterprise Data 75 RBS custom lookup table The RBS structure is defined by adding values to the RBS custom lookup table that is built in to Project Server 2010. Once you define the structure. 3. you can assign RBS values to individual users by setting the RBS property in the user's account settings page.

4. In the Sequence column. If you are creating a hierarchy with more than one level. b. use the Indent and Outdent buttons to change the level values for each department as required for you hierarchy. choose Characters from the dropdown list. Keep the defaults for the Length and Separator columns. .76 Project Server 2010 Administrator's Guide a. 5. type a Value and optionally a Description for each Department. In the Lookup Table section.

This allows the user to access all enterprise custom objects available on the server.Enterprise Data 77 6. groups. you are able to enforce standards in your organization that can be applied to all project and resources that work with Project Server data. When a Project Professional user connects to Project Server 2010. tables. filters. Enterprise Global The Enterprise Global setting allows you to make changes to the Enterprise Global file in Project Professional 2010. and other related elements contains in the Enterprise Global file. the latest version of the Enterprise Global file is loaded and cached on the client computer. Click Save. Through the Enterprise Global file. filters. you can help to ensure effective standardization in your organization. tables. and reports). By using views. . views. The Enterprise Global file contains all custom enterprise objects that are available to your users (for example.

2. On the Server Settings page. Click Yes. click Configure Project Professional. After Save has completed successfully. you must have the Save Enterprise Global permission Project Server 2010. under Settings. under Enterprise Data.78 Project Server 2010 Administrator's Guide Decisions regarding what to include in the Enterprise Global file should be made at an organizational level. A dialog box will display asking if you would like to check-in the Enterprise Global file. The name of the project in the title bar will be ―Checked-out Enterprise Global‖. 5. On the Quick Launch. click File. click Server Settings. click File. To open the Enterprise Global file through the Enterprise Global setting: 1. 6. and then click Save. 7. You should check with your Project Management Office (PMO) before making any significant changes to the Enterprise Global file. 4. . 3. Project Professional will open the Enterprise Global file. After you have completed your changes. Note To be able to modify the Enterprise Global file. Make changes to your custom objects through your Enterprise Global file. and then click Close.

select a calendar to edit. Verify that you give any new enterprise-wide elements a unique name that does not conflict. reports. you can view a list of existing calendars. table.Enterprise Data 79 Note If users have Project Professional open when an updated Enterprise Global file is checked in to the server. filter. . holidays. Enterprise Calendars Enterprise calendars capture the predefined working hours. to create or modify a calendar. grouping. In Project Web App. and other schedule details within an organization. Important Make sure not to add into the Enterprise Global file any view. that has the same name as an element that exists natively in Project. the changes in the updated Enterprise Global file will not be available until Project Professional is closed and reopened. They are used to standardize the working time for all of an organization’s projects. etc. However. or begin the process of creating a new calendar. you must have Project Professional 2010 installed on the computer that you are using to access Project Web App.

For example. those workers will likely observe different holidays. or if Project is already connected to the server using the correct profile. click New Calendar. Type a name for the new calendar in the For calendar box. under Settings. if some of your organization’s employees work in another country. 2. blank enterprise calendar using Project Web App and Project Professional 2010. Note If you are using integrated Windows authentication and your Internet Explorer settings are set to automatically log you on. click Enterprise Calendars. Some organizations may use multiple calendars. 4. type your user name and password to connect to Project Server through Project Professional 2010. On the Quick Launch. 3. click Server Settings. 5. blank enterprise calendar 1. and then click OK. To create a new.80 Project Server 2010 Administrator's Guide Create a New Calendar Project Server uses a standard enterprise calendar for scheduling. On the Windows Security dialog box. You can create a new. Project Professional 2010 opens and displays the Change Working Time dialog box. under Enterprise Data. and so will need a different enterprise calendar for scheduling project work. . then you will not be prompted for credentials. by default. On the Server Settings page. On the Enterprise Calendars page.

On the Quick Launch. To create a new calendar as a copy of an existing calendar 1.Enterprise Data 81 Use the calendar with the Exceptions and Work Weeks tabs to modify the working and nonworking times for your organization. and then click Copy Calendar. Copy an Existing Calendar If an existing calendar has many of the same holidays and other calendar items that you want to use in a new calendar. 8. On the Server Settings page. . Click the row containing the calendar you want to copy. Click OK on the Change Working Time dialog box to save the new calendar to Project Server. click Enterprise Calendars. if the standard calendar in your organization captures all of your organization’s unique holidays and events. 3. you can copy the standard calendar and then modify it for the 24/7 schedule. Copy the existing calendar in Project Web App. under Settings. 4. see the ―Modify Working and Nonworking Times‖ section of this guide. The calendar is added to the list on the Enterprise Calendars page. type a name for the new calendar in the Name box. For more information. but you need a separate calendar to reflect a 24/7 working schedule. and then click OK. 2. you can base a new calendar on an existing calendar. On the Copy Calendar dialog box. 7. click Server Settings. under Enterprise Data. and then modify the copy in Project Professional 2010. Close Project Professional 2010. 6. For example.

. Use the calendar with the Exceptions and Work Weeks tabs to modify the working and nonworking times for your organization. copied calendar. and making changes in Project Professional 2010. click Enterprise Calendars. Click OK on the Change Working Time dialog box to save the new calendar to Project Server. On the Server Settings page. see the ―Modify Working and Nonworking Times‖ section of this guide. Click the row containing the calendar you want to change. 3. under Settings. Edit an Existing Calendar As you are initially configuring Project Server. 7. log on to Project Server. and then click Edit Calendar. 6. and then click Edit Calendar. under Enterprise Data. you can modify the default standard enterprise calendar to account for the working and nonworking times observed by your organization. 2. You can modify any enterprise calendar at any time by selecting the calendar in Project Web App. To modify an existing enterprise calendar 1. For more information.82 Project Server 2010 Administrator's Guide 5. On the Quick Launch. If the Windows Security dialog box appears. Click the row containing the new. click Server Settings. Close Project Professional 2010. 8. Project Professional 2010 opens and displays the Change Working Time dialog box.

under Settings. 4. Use the calendar with the Exceptions and Work Weeks tabs to modify the working and nonworking times for your organization. To delete an enterprise calendar 1. 4. Note If the calendar is currently in use. Click the row containing the calendar you want to delete. Delete a Calendar If you find your organization is not using a specific enterprise calendar.Enterprise Data 83 If the Windows Security dialog box appears. 2. Project Professional 2010 opens and displays the Change Working Time dialog box. click OK to delete the selected calendar. under Enterprise Data. On the Quick Launch. 3. and then click Delete Calendar. 5. log on to Project Server. see the ―Modify Working and Nonworking Times‖ section of this guide. you can easily delete it in Project Web App. Close Project Professional 2010. a notification will appear. Click OK on the Change Working Time dialog box to save the new calendar to Project Server. click Server Settings. . On the Server Settings page. For more information. click Enterprise Calendars. When prompted. 6.

For example. The Start and Finish columns are automatically populated with the date you clicked in Step 1. there are a few different things you can do to accurately account for working and nonworking time in your organization. Change a working day into a nonworking day Occasionally. . type a name for the nonworking day in the Name column. you can turn those holidays into nonworking days. Click the date on the calendar that you want to turn into a nonworking day. and walk you through the steps involved with making each change. On the Exceptions tab. The following sections provide examples for each type of change. 2. To change a working day into a nonworking day 1. Project Server will not schedule work on nonworking days. if your organization observes specific days as holidays. you may need to turn a working day into a nonworking day.84 Project Server 2010 Administrator's Guide Modify Working and Nonworking Times When working with calendars in Project Professional 2010.

You can turn the weekend days of the convention into working days. For example. Change a nonworking day into a working day There may be times when your organization has to work on what would otherwise be a nonworking day. For example. you might have one exception that changes the standard working times for a month. Click the date on the calendar that you want to turn into a nonworking day. the single nonworking day exception will be applied on that day. and another exception that calls out a specific day within that month as a nonworking day. so that Project Server knows to schedule work on those days. You cannot create multiple single-day exceptions on the same day.Enterprise Data 85 Note While you can create multiple exceptions that contain a specific day. To change a nonworking day into a working day 1. only the lowest-level exception will apply on that day. say your organization participates in a convention each year that takes place over a weekend. . Because the single-day exception is at a lower level than the month-long exception.

the single nonworking day exception will be applied on that day. and another exception that calls out a specific day within that month as a nonworking day.86 Project Server 2010 Administrator's Guide 2. For example. Note While you can create multiple exceptions that contain a specific day. only the lowest-level exception will apply on that day. type a name for the working day in the Name column. . You cannot create multiple single-day exceptions on the same day. On the Exceptions tab. you might have one exception that changes the standard working times for a month. and then press Enter. Because the single-day exception is at a lower level than the month-long exception.

Monthly. you may find it easier to change the default calendar options under Schedule on the Project Options dialog box in Project Professional 2010. All calendars begin with these default days and times. 4. Click the row you added for the working day.  Weekly Specify how often you want the working times to recur. Under Set working times for these exceptions. For example. choose whether these times should recur Daily. every two weeks on Saturday. once a month or once a year). If your organization observes these working times on a regular basis (for example. under Recurrence pattern. every 10 days. Tip If you find that the working day exception is happening very frequently. Weekly.Enterprise Data 87 3. 5. or Yearly. For example. and then click Details. and then set the following options:  Daily Set the frequency for these working times. and then set the working times for that day by adjusting the times in the From and To columns. It may be easier to change the default calendar options than to set up exceptions that recur frequently. click Working times. and on what day of the week you want them to recur. .

and then choose when the recurrence should stop. 7.  Yearly Choose what day of the year you want the working times to recur. 6.  End by If you want the recurrence to happen only during a certain time period. Under Range of recurrence.  End after If you want the recurrence to happen only a set number of times. or the third Saturday of every 6 months. day 15 of every 3 months. choose End by. August 21. For example. choose the period when you want the recurrence to take place. For example.88 Project Server 2010 Administrator's Guide  Monthly Choose what day of the month and at what monthly frequency you want the working times to recur. and then type the number of instances when the working times should occur. . Click OK. or the third Saturday of July. choose End after.  Start Choose the date when you want the recurrence pattern to begin. if appropriate.

You can adjust the working times for a specific working day so that work is accurately scheduled on that day. and then press Enter. To change the working times for a working day 1. Click the date on the calendar for the working day that you want to adjust. On the Exceptions tab. there may be working days that use a different time schedule than the typical 8hour work day. type a name for the changed working day in the Name column.Enterprise Data 89 Change the working times for a working day While the specific days on the calendar may be accurately accounted for as working and nonworking. . 2.

only the lowestlevel exception will apply on that day. You cannot create multiple single-day exceptions on the same day.90 Project Server 2010 Administrator's Guide Note While you can create multiple exceptions that contain a specific day. the single nonworking day exception will be applied on that day. 4. Click the row you added for the changed working day. 3. and another exception that calls out a specific day within that month as a nonworking day. click Working times. you might have one exception that changes the standard working times for a month. and then click Details. and then set the working times for that day by adjusting the times in the From and To columns. . Because the single-day exception is at a lower level than the month-long exception. Under Set working times for these exceptions. For example.

 Monthly Choose what day of the month and at what monthly frequency you want the working times to recur. For example. or the third Saturday of every 6 months.Enterprise Data 91 5. or Yearly. . every two weeks on Saturday. and on what day of the week you want them to recur. and then set the following options:  Daily Set the frequency for these working times. choose whether these times should recur Daily. Weekly. For example.  Weekly Specify how often you want the working times to recur. under Recurrence pattern. If your organization observes these working times on a regular basis (for example. every 10 days. Monthly. once a month or once a year). For example. day 15 of every 3 months.

during a set period of time. choose the period when you want the recurrence to take place. Click OK. . Change the working times for each day of a work week If your organization has a specific work week (or set of work weeks) when the working times are different from the default. you can change the working times for each day in the work week to reflect your organization’s accurate schedule. 7.  End after If you want the recurrence to happen only a set number of times. you can make those changes to the working times for each day in a work week. Under Range of recurrence. 6. 8am to 5pm schedule. and then choose when the recurrence should stop. August 21.  Start Choose the date when you want the recurrence pattern to begin.92 Project Server 2010 Administrator's Guide  Yearly Choose what day of the year you want the working times to recur. For example. if your organization does not use the default Monday through Friday. choose End after.  End by If you want the recurrence to happen only during a certain time period. choose End by. To change the working times for each day of a work week 1. Click the date on the calendar when you want the changed working times to begin. and then type the number of instances when the working times should occur. For example. or the third Saturday of July. if appropriate.

3. On the Work Weeks tab. type a name for the changed work week(s) in the Name column. . to reflect the last day that you want to include in the changed work week(s).Enterprise Data 93 2. Change the date in the Finish column for the row you just added. and then press Enter.

5. or press Shift and click to select multiple days. If you want to turn the selected day(s) into nonworking time. click the day of the week that you want to use adjusted working times. and then set the working times by typing in the From and To columns. Click Details. Under Select day(s). click Set day(s) to these specific working times. Press Ctrl and click. click Set days to nonworking time. If you want to change the working times for the selected day(s).94 Project Server 2010 Administrator's Guide 4. . 6. 7.

and the project manager can account for when the resource is actually used. . under Settings. click New Resource. Project managers can still assign the resource to work. there is not a need for that resource to also be a user. It can be accessed from the Server Settings page. Resource Center The Resource Center is a view in Project Web App that can be used to create new resources and modify existing ones. However. you can choose to also make that user a resource. you may also be able to access the Resource Center from the Quick Launch. On the Quick Launch. Tip Depending on how your organization has Project Web App configured. 3. such as a conference room. click Server Settings. On the Resources tab.Enterprise Data 95 8. Create a New Resource When you create a new Project Server user. you may want to add a material resource. that has no need to be able to log on to Project Server. On the Server Settings page. click Resource Center. For example. but if there is not any work to track. To create a new resource 1. in the Editing group. under Enterprise Data. Click OK. sometimes you may want to create a resource that cannot log on to Project Server. 2.

 RBS If your organization uses a resource breakdown structure (RBS). select the Generic check box. type the address in this box. click the button next to this field and choose the appropriate RBS code for this resource from the list. Material.  Initials This field is automatically populated with the resource’s initials. complete the following:  Type Choose whether you are creating a Work. . In the Type section. complete the following:  Resource can logon to Project Server Select this check box if you want the resource to also be a Project Web App user. meaning that you will use it for planning purposes and replace it with at least one named resource further in the planning process. type the URL to that site in this box. based on the name typed in the Display Name box. type the name of that site in this box. select the Budget check box.  Generic If the resource is generic.  Hyperlink URL If this resource has an associated Web site. type them in the Initials box.  Display Name Type the resource’s name in this box. This field is required. If you want to use different initials to refer to this resource.  Budget If the resource is a budget resource. In the Identification Information section. or Cost resource.  Hyperlink Name If this resource has an associated Web site.96 Project Server 2010 Administrator's Guide 4.  E-mail address If this resource has an e-mail address that he or she wants associated with project work. 5.

In the Assignment Attributes section. For example.Enterprise Data 97 6. Tip You can set the assignment owner within the project on an assignment-by-assignment basis.  Default Booking Type Choose whether you want this resource to be Committed or Proposed when assigning work.  Base Calendar Choose the calendar that most closely represents this resource’s overall availability. if the resource is a conference room. and work assigned to this resource will be scheduled around the calendar’s nonworking days. complete the following:  Resource can be leveled If you want to enable project managers to balance this resource’s workload based on his or her availability and assignments (leveling). leave this blank. If the resource does not have a set period of availability (that is. the assignment owner may be the project manager. or click Browse to choose the assignment owner from a list.  Earliest Available Choose the date when the resource becomes available to assign to tasks. if your organization has a base calendar that accounts for specific holidays or events. Resources may not have separate timesheet managers. and the project manager tracks the amount of time that the conference room is used. . select this check box. or click Browse to choose the timesheet manager from a list.  Default Assignment Owner Type the name of the person who approves or rejects this resource’s task progress. Resources may not have separate assignment owners. you can set that as this resource’s calendar.  Timesheet manager Type the name of the person who approves or rejects this resource’s timesheets. For example. if appropriate. if he or she is always available).

type that cost in this box. type 50%. If the resource is available half-time. as seen in Project Professional. if appropriate. Cost/Use If the resource has a flat fee associated with each use. leave this blank. . a van rental may require a flat fee upfront. Overtime Rate Type the resource’s overtime pay rate in this box. Standard Rate Type the resource’s standard pay rate in this box. type 100%.98 Project Server 2010 Administrator's Guide Note The earliest and latest available dates correspond to the resource availability dates for a resource. Current Max.      Latest Available Choose the last date that the resource is available to work on tasks. Units (%) Specify the maximum amount of time that a resource is available for work. with an added standard cost per mile. if the resource is available full-time. For example. as a percentage. if he or she is always available). If the resource does not have a set period of availability (that is. For example. The flat fee is its cost per use.

by removing things from other departments that do not apply to his or her work. In the Departments section.  Code Type the code for the group in this box. If the resource is not associated with a particular department. If your organization created codes for grouping and costing purposes. in the Group Fields section.Enterprise Data 99 7. Tip Associating a resource with a department narrows down what the resource sees when using Project Web App.  Cost Center Type the cost center code for the group in this box. click the button next to the Resource Departments box. complete the following:  Group Type the name of the group in this box. . leave this blank. 8. and choose which department(s) the resource is associated with. It can help the resource find what he or she is looking for more quickly.

This way. if appropriate. If the resource will be managing and delegating tasks that are assigned to the team. if appropriate. so that tasks assigned to the team first go to the generic resource. Tip Some organizations create a generic resource for each team. For example. you identify an association between the resource that you are creating and the HR department’s employee data. 10. In the Team Details section. or simply leave this box blank. By providing that ID number in the External ID box. The External ID box can also be used to facilitate the consolidation of reporting of resource use beyond what Project Server provides. select the Team Assignment Pool check box. check with other departments in your organization to find out if it would be useful to connect resource data with other systems. click the button next to the Team Name box. 9. select the Team Assignment Pool check box. . and choose which team the resource belongs to. set the assignment owner for the resource as the team manager. and choose the team from the Team Name list. your organization’s HR department may use employee ID numbers to track data in their HR systems. Tip If you are not sure whether you should be capturing any data in the External ID box. and then choose the type of cost associated with this group. type additional identifying information for the user in the External ID box. no single resource takes on the task assignment before it is appropriately delegated. In the System Identification Data section. If you choose to use a generic resource in this way.100 Project Server 2010 Administrator's Guide  Cost Type Click the button next to the Cost Type field.

you may find that you need to make changes to the resource’s information. click Edit Resource. you will need to replace . you can filter the Resource Center. In some cases. if several resources use the same timesheet manager. Once a resource is added. For example. 3. On the Server Settings page. and then click OK. On the Quick Launch. as needed. Click Save to create the new resource. several resources may require the same change.Enterprise Data 101 11. or needs to use a different base calendar. under Settings. 5. click Server Settings. 4. in the Data group. On the Resources tab. Identify the parameters for the resource you are editing. Make changes to the resource data. click Resource Center. and that person takes a job elsewhere. click Custom Filter in the Filter list. Select the check box in the left column for the row containing the resource you are editing. 2. and then click Save. under Enterprise Data. To edit a resource 1. Tip If your organization has a lot of resources and you cannot easily find the one you want to edit. in the Editing group. On the Resources tab. Perhaps the resource had a rate change.

under Enterprise Data. On the Server Settings page. click Bulk Edit. RBS. To make the same change to several resources simultaneously 1. Project Web App supports bulk editing of several resources at once. in the Editing group. 3. For each field that you want to edit. Default Assignment Owner. On the Quick Launch. 4. expand the Resources Selected section. Click Save to save your changes to all selected resources. Tip Another good way to edit many resources simultaneously is by using Project Professional 2010. and then make your changes. Tip If you are having trouble remembering which resources you are editing. you can add fields that you will not see if you make bulk changes through Project Server 2010. 2. and you can also copy and paste from Microsoft Excel or another list. 5. 6. You can bulk edit the Timesheet manager. This section displays a list of all resources that will be changed when you click Save. under Settings. Select the check box in the left column for each row containing a resource you are editing. click Server Settings. select the Apply Changes check box. Team Name. and Resource Departments fields. By making changes through the Project Professional 2010. to the left of the field. .102 Project Server 2010 Administrator's Guide the timesheet manager for those resources with whoever steps in as a replacement. On the Resources tab. Cost Type. click Resource Center.

Note that this process deletes the project entirely from Project Server and it cannot be retrieved.Database Administration 103 3 Database Administration This chapter about Project Server 2010 Database Administration contains the following sections:  Delete Enterprise Objects  Force Check-in Enterprise Objects  Daily Schedule Backup  Administrative Backup and Restore  OLAP Database Management Delete Enterprise Objects You can delete enterprise objects from Project Server when they are no longer needed. You can delete the following types of objects from PWA:  Projects  Resources and users  Status report responses  Timesheets  User delegates Delete projects When a project is no longer needed. . you can delete it from Project Server.

104 Project Server 2010 Administrator's Guide

Delete project

Use the following procedure to delete a project from Project Server.
Important The project will be permanently deleted from Project Server.  To delete a project 1. On the PWA home page, click Server Settings.

On the Server Settings page, under Database Administration, click Delete Enterprise Objects. 3. On the Delete Enterprise Objects page, select the Projects option. 4. Select one of the following options:  Delete projects from Draft and Published databases to display a list of projects found in both the Draft and Published databases.  Delete projects only from the Published database to display a list of projects in the Published database.  Delete projects only from the Archived database to display a list of projects in the Archive database.
2.

Database Administration

105

5.

To delete the associated SharePoint site, select the Delete the associated Microsoft SharePoint Foundation sites check box.
Note If you do not delete the associate SharePoint site and you save and publish a new project
with the same name as the deleted project, the SharePoint site publish process will fail.

6. 7.

Select the project that you want to delete. Click Delete.

Delete resources and users
When a resource or user is no longer needed, you can delete it from Project Server.
Important We recommend not deleting resources from Project Server as this can affect the reporting of
actuals. Instead, deactivate resources that are no longer needed.

Delete resources and users

Use the following procedure to delete resources and users from Project Server.
Important The resources and users will be permanently deleted from Project Server.  To delete resources and users 1. On the PWA home page, click Server Settings.

On the Server Settings page, under Database Administration, click Delete Enterprise Objects. 3. On the Delete Enterprise Objects page, select the Resources and Users option.
2.

106 Project Server 2010 Administrator's Guide

Select the user or resource that you want to delete. 5. Click Delete.
4.

Delete status report responses
When a status report response is no longer needed, you can delete it from Project Server. Note that this process deletes the status report response entirely from Project Server and it cannot be retrieved.

Delete status report responses

Use the following procedure to delete status report responses from Project Server.
 To delete status report responses 1. On the PWA home page, click Server Settings.

On the Server Settings page, under Database Administration, click Delete Enterprise Objects. 3. On the Delete Enterprise Objects page, select the Status Report Responses option. 4. Specify a period end date parameter (number of days, weeks, months, or years ago prior to which you want to delete all status report responses). 5. Click Delete.
2.

Delete timesheets
When a timesheet is no longer needed, you can delete it from Project Server. Note that this process deletes the timesheet entirely from Project Server and it cannot be retrieved.

Database Administration

107

Delete timesheets

Use the following procedure to delete timesheets from Project Server.
 To delete timesheets 1. On the PWA home page, click Server Settings.

On the Server Settings page, under Database Administration, click Delete Enterprise Objects. 3. On the Delete Enterprise Objects page, select the Timesheets option. 4. Select the range of timesheet end dates that you want to delete. 5. Click Delete.
2.

Delete user delegates
When a user delegate is no longer needed, you can delete it from Project Server. Note that this process deletes the user delegate entirely from Project Server and it cannot be retrieved.

108 Project Server 2010 Administrator's Guide

Delete delegates

Use the following procedure to delete user delegates from Project Server.
 To delete 1. On the PWA home page, click Server Settings.

On the Server Settings page, under Database Administration, click Delete Enterprise Objects. 3. On the Delete Enterprise Objects page, select the User Delegates option. 4. Specify a period end date parameter (number of days, weeks, months, or years prior to which you want to delete all user delegates). 5. Click Delete.
2.

Force Check-in Enterprise Objects
If an enterprise object has been checked out and the user who checked it out is unavailable or unable to check it back in, you can force a check-in.
Important If you force check-in an enterprise object that a user is modifying, the modifications may be
lost.

You can force check-in the following types of enterprise objects:  Enterprise projects  Enterprise resources  Enterprise custom fields  Enterprise calendars  Lookup tables for enterprise custom fields  Resource plans

Database Administration

109

Enterprise object check-in options

On the Force Check-in Enterprise Objects page in PWA Server Settings, choose the type of enterprise object that you want to check in to see a list of objects of that type that are checked out.

Check-in Enterprise Projects
You can force the check-in of an enterprise project that is checked out. Note that forcing a check-in of a project that is being modified by a user may result in the loss of those changes. We highly recommend that users check in projects normally and that you use force check-in only when absolutely necessary.

Check in Enterprise Projects

Use the following procedure to check in enterprise projects.
 To check in Enterprise Projects 1. On the Server Settings page, click Force Check-in Enterprise Objects.

From the Select the type of object you want to force check-in dropdown list, choose Enterprise Projects. 3. Select the projects that you want to check in. 4. Click Check In.
2.

Note that forcing a check-in of a custom field that is being modified by a user may result in the loss of those changes. . choose Enterprise Resources. 3. 4. On the Server Settings page. From the Select the type of object you want to force check-in dropdown list. 2. Check in Enterprise Custom Field Use the following procedure to check in enterprise custom fields. Select the resources that you want to check in. Click Check In.  To check in Enterprise Resources 1.110 Project Server 2010 Administrator's Guide Check in Enterprise Resources You can force the check-in of an enterprise resource that is checked out. Check in Enterprise Resources Use the following procedure to check in enterprise resources. Note that forcing a check-in of a resource that is being modified by a user may result in the loss of those changes. Check in Enterprise Custom Fields You can force the check-in of an enterprise custom field that is checked out. click Force Check-in Enterprise Objects.

3. Select the calendars that you want to check in. click Force Check-in Enterprise Objects. Check in Enterprise Calendars You can force the check-in of an enterprise calendar that is checked out.Database Administration 111  To check in Enterprise Custom Fields 1. 3. 4. Click Check In. Note that forcing a check-in of an enterprise calendar that is being modified by a user may result in the loss of those changes. From the Select the type of object you want to force check-in dropdown list. click Force Check-in Enterprise Objects. From the Select the type of object you want to force check-in dropdown list. Click Check In. 2. choose Enterprise Custom Fields. 4. Check in Enterprise Calendars Use the following procedure to check in enterprise calendars. Note that forcing a check-in of a lookup table that is being modified by a user may result in the loss of those changes.  To check in Enterprise Calendars 1. choose Enterprise Calendars. . Select the custom fields that you want to check in. 2. Check in Lookup Tables for Enterprise Custom Fields You can force the check-in of an enterprise lookup table that is checked out. On the Server Settings page. On the Server Settings page.

click Force Check-in Enterprise Objects. Click Check In. 2.  To check in Lookup Tables for Enterprise Custom Fields 1. Check in Resource Plans You can force the check-in of an enterprise resource plan that is checked out. Note that forcing a check-in of a resource plan that is being modified by a user may result in the loss of those changes. Select the lookup tables that you want to check in. From the Select the type of object you want to force check-in dropdown list. click Force Check-in Enterprise Objects.  To check in Resource Plans 1. On the Server Settings page. From the Select the type of object you want to force check-in dropdown list.112 Project Server 2010 Administrator's Guide Check in Lookup Tables for Enterprise Custom Fields Use the following procedure to check in lookup tables. Check in Resource Plans Use the following procedure to check in resource plans. 4. 2. On the Server Settings page. choose Resource Plans. 3. choose Lookup Tables for Enterprise Custom Fields. .

System settings. 3. Increasing the project retention policy will affect your archive database.Database Administration 113 Select the resource plans that you want to check in. Project Retention Policy Versions The Project Retention Policy sets the number of versions of daily backups that will be kept for item level restore. not instead of. Enterprise Resource Pool and Calendars. Project Retention Policy Items In this area you can select whether or not you want to schedule item level backups for Projects. Click Check In. and Category and Group settings. . SQL Server database backups. Daily Schedule Backup Daily Schedule Backup allows you to define your daily backup schedule to support item-level restore. View Definitions. the greater the disk space required. Enterprise Custom Fields. The more versions in the Project Retention Policy that you keep. Enterprise Global. Delete resources and users Use the following procedure to delete resources and users from Project Server. 4. Item-level backup is designed to work with.

. 6. Under Item change the Option dropdown from ―Never‖ to ―Schedule‖ for each item you would like to backup daily. 5. Click Save. under Database Administration. click Server Settings.114 Project Server 2010 Administrator's Guide Important The resources and users will be permanently deleted from Project Server. On the Server Settings page. 4. click Daily Backup Schedule On the Daily Backup Schedule page.  To schedule an item level backup 1. 2. set the Project Retention Policy to your desired number keeping in mind your disk storage capacity and backup needs. On the PWA home page. Under Time set the dropdown for the time for which you would like to have the system perform he daily backup. 3.

The items that you selected are backed up immediately. As an administrator. On the Server Settings page. . click Administrative Backup. 3. Enterprise Custom Fields. click Server Settings. Items For Backup  To Backup data manually 1. On the PWA home page. Enterprise Resource Pool and Calendars. Items that can be backed up are: Projects. Click Backup. Administrative Backup On this page you can manually select the items that you wish to have backed up. System settings. Administrative Restore Here you can individually select backed up items that you wish to restore. under Database Administration. View Definitions. In the Select Items section.Database Administration 115 Administrative Backup and Restore Administrative Backup allows you to manually backup individual item-level objects to your archive database. you can also restore items that have been accidentally deleted from the database using Administrative Restore. 2. select the check box next to each project item that you want to back up. and Category and Group settings. Enterprise Global. 4.

. 3. click Administrative Restore. 4. select the item that you want to restore. Important The resources and users will be permanently deleted from Project Server. On the PWA home page. If you selected Projects from the Item list. Click Restore.116 Project Server 2010 Administrator's Guide Delete resources and users Use the following procedure to delete resources and users from Project Server. click Server Settings. Note The versions that are available for you to restore depend upon the number of backups that have been completed and the total number of backups that you have chosen to retain. Project Version Selection 5. select the version of the project that you want to restore as the current working version of the project. On the Server Settings page.  To restore project items manually 1. under Database Administration. 2. In the Item list.

multiple OLAP databases can be delivered that contain the specific resources. In Microsoft Project Server 2010. Use the following procedure to create an OLAP cube. click Server Settings. the necessary Office Data Connections and Excel Reporting templates are created in the Business Intelligence Center in the Reports folder. See the following sections for details on each setting. projects. Perform the following procedure to create a new OLAP cube. This data-connected blank template will help you quickly create new reports that are based on the new OLAP database. 5. you can create multiple OLAP databases that have the following characteristics:  They only contain data for projects and resources that they administer  They only contain facts and dimensions that they select from the new integrated OLAP database management user interface  They support departmental filtering to restrict which projects and resources are loaded into the OLAP database  They include data for Inactive Tasks and User Scheduled Tasks  They have support for Multiple Measure groups in a single OLAP database  They contain field names in multiple languages to enable multi-language report creation Also. click OLAP Database Management. you must have the Manage Cube Building Service Global Permission. 2. and custom fields that each group within your organization requires for its particular group reporting needs. 4. Create an OLAP Cube OLAP cubes are managed on the OLAP Database Management page in Server Settings on a Microsoft Project Web App (PWA) site.  To create an OLAP cube 1. .Database Administration 117 OLAP Database Management Through Microsoft Project Web App (PWA). 3. when a new OLAP database is created. click New. On the Server Settings page. On the OLAP Database Management page. On the PWA home page. Configure the settings on the OLAP Database Build Settings page. Click Save. To create an OLAP cube. in the Database Administration section.

. A description of this OLAP cube. The name of the database that you want to create. optionally. you can use this setting to specify the department that you want to have included in the cube. OLAP Department settings (example) If you have projects assigned to departments.118 Project Server 2010 Administrator's Guide Analysis Services Settings Use the Analysis Services Settings area to specify server and database name information along with. an extranet URL and description. Attribute Analysis Services Server Analysis Services Database to be created Extranet URL Description Description The name of the instance of Microsoft SQL Server Analysis Services (SSAS) where you want to build the cube. Project Department Use the Project Department area to specify which department to use to filter project data in the OLAP cube. If no department is selected. Analysis Services Settings The following table describes the server and network settings for an OLAP cube. The URL for the extranet site. then no departmental filtering occurs.

Note To deselect a department once selected. If no department is selected. you can use this setting to specify the department that you want to have included in the cube. click the department again. Resource Department Use the Resource Department area to specify which department to use to filter resource data in the OLAP cube. modify the Project Departments custom field and select the Allow multiple values to be selected from lookup table check box. click the department again. .Database Administration 119 The selection of departments available is controlled by the Department custom lookup table. OLAP Resource settings (example) If you have resources assigned to departments. then no departmental filtering occurs. Note To deselect a department once selected. To allow multiple selections. To allow multiple selections. based on project start date. to include in the OLAP cube. Database Date Range Use the Database Date Range area to specify the date range of projects. modify the Resource Departments custom field and select the Allow multiple values to be selected from lookup table check box. The selection of departments available is controlled by the Department custom lookup table.

type the number of days.120 Project Server 2010 Administrator's Guide OLAP database date range settings The following table describes the database date range options for an OLAP cube. In the Last and Next boxes. OLAP Database Update Frequency Use the OLAP Database Update Frequency area to specify when and how often you want to build the OLAP cube. Select this option if you want the date range to be configured automatically based on a delta from the date on which the cube is built. We recommend you choose a time of low system use because building cubes can be resource intensive. type the dates that you want to use. Attribute Use the earliest project start date and the latest project finish date Use the following last and next time units to calculate the date range at the time that the OLAP database is built Use the fixed date range specified below Description Select this option if you want to base the date range of the cube on the earliest start date of any project and the latest finish date of any project. In the From and To boxes. Select this option if you want to use a fixed date range. or months that you want to use for the delta. weeks. .

On the PWA home page. Select the start date for the first automated cube build. selecting this option causes the build job to start automatically when the queue becomes available instead of waiting for the next scheduled time. the cube is not updated automatically. You can configure OLAP cube dimensions and measures. There are two sets of parameters that can be configured on an existing OLAP cube:  Dimensions and measures  Cube build settings Use the following procedure to configure the build settings of an existing OLAP cube. or months for the cube to be rebuilt. you must have the Manage Cube Building Service Global Permission. or you can configure the build settings of a cube. If the scheduled cube build fails because the queue is not available. To configure an OLAP cube. days. If this option is not selected.  To configure OLAP cube build settings 1.Database Administration 121 OLAP database update settings The following table describes the database update settings for an OLAP cube. . Select the number of hours. Immediately retry the OLAP database update if scheduled time fails because of queue down time Update every Start date Start time Configure an OLAP cube OLAP cubes are managed on the OLAP Database Management page in Server Settings on a Microsoft Project Web App (PWA) site. click Server Settings. weeks. Select the start time for each automated cube build. Attribute Update periodically Description Select this option if you want to schedule an update frequency.

122 Project Server 2010 Administrator's Guide On the Server Settings page. . in the OLAP Database Name column. in the Database Administration section. and then click Configuration. in the Database Administration section. click the database that you want to configure. click Server Settings. 4. Use the following procedure to configure the dimensions and measures of an existing OLAP cube. 2. Cube dimensions Use the Cube dimensions area to specify the custom fields that you want to add to the OLAP cube as dimensions. 3. Click Save. 4. Configure the settings on the Database Configuration page: 5. select an OLAP database from the list. On the OLAP Database Management page. On the Server Settings page. Cube selector Select a cube from the dropdown list to display the available and selected dimensions. On the OLAP Database Management page.  To configure OLAP cube dimensions and measures 1. click OLAP Database Management. click OLAP Database Management. 3. 2. Click Save. Configure the settings on the OLAP Database Build Settings page: 5. On the PWA home page.

Do this for each cube in the Cube dropdown list. Cube measures Use the Cube measures area to specify the custom fields that you want to add to the OLAP cube as measures.Database Administration 123 Cube dimension selector Choose the dimensions that you want to include in that cube in the Available fields list and click Add to include them in the cube. Do this for each cube in the Cube dropdown list. Cube measure selector Choose the measures that you want to include in that cube in the Available fields list and click Add to include them in the cube. Cube selector Select a cube from the dropdown list to display the available and selected measures. .

Inactive tasks Use the Inactive tasks area to specify if you want to include inactive tasks in the OLAP cubes. select the Include Inactive Tasks check box. Task. Calculated measures Use the Calculated measures area to specify an MDX expression to define a calculated measure. Cube selector .124 Project Server 2010 Administrator's Guide Built-in measures Use the Built-in measures area to select the build-in measures that you want to include in the OLAP cubes. Inactive tasks selector If you want the cube to include inactive tasks. and Assignment cubes as measures. Cube built-in measure selector The fields that you select will be added to the Project.

MDX expression tool Click Insert to add a custom MDX expression. 2. click OLAP Database Management. Perform the following procedure to copy an existing OLAP Cube. but rather copies all the cube settings from which you can build a new Analysis Services database. .com/en-us/library/ms145506. and then click Copy. On the OLAP Database Management page. Copying a cube does not copy the Analysis Services database. On the Server Settings page. For more information about MDX expressions.Database Administration 125 Select the cube that you want to define an expression for from the Cube dropdown list. Copying a cube will create a new cube with the same settings and configuration as the cube you copied.microsoft.  To copy an OLAP cube 1. Copy an OLAP cube OLAP cubes are managed on the OLAP Database Management page in Server Settings on a Microsoft Project Web App (PWA) site. select the cube that you want to copy.aspx). in the Database Administration section. see Multidimensional Expressions (MDX) Reference (http://msdn. click Server Settings. On the PWA home page. Copy an OLAP cube Use the following procedure to copy an OLAP cube. you must have the Manage Cube Building Service Global Permission. Note You must specify a new name for the Analysis Services database after you copy the cube. 3. To copy an OLAP cube.

On the OLAP Database Management page. . Build an OLAP cube OLAP cubes are managed on the OLAP Database Management page in Server Settings on a Microsoft Project Web App (PWA) site. 4. To delete an OLAP cube. 5. Delete an OLAP cube Use the following procedure to delete an OLAP cube. Perform the following procedure to delete an OLAP Cube. click Server Settings. type the name of the server and the database that you want created and adjust any other desired settings. select the cube that you want to delete. To build an OLAP cube. click OLAP Database Management. OLAP cubes can be scheduled to be built on a regular basis. 3. On the Server Settings page. Note Deleting an OLAP cube in Project Server does not delete the OLAP database from Analysis Services.126 Project Server 2010 Administrator's Guide On the OLAP Database Build Settings page. Delete an OLAP cube OLAP cubes are managed on the OLAP Database Management page in Server Settings on a Microsoft Project Web App (PWA) site. You can also start the build process manually. For more information. in the Database Administration section.  To delete an OLAP cube 1. and then click Delete. Click Save. see Configure an OLAP cube (Project Server 2010). you must have the Manage Cube Building Service Global Permission. 2. On the PWA home page. Perform the following procedure to build an existing OLAP cube. you must have the Manage Cube Building Service Global Permission.

On the OLAP Database Management page. click OLAP Database Management. in the Database Administration section. 3. On the Server Settings page.Database Administration 127 Build an OLAP cube Use the following procedure to build an OLAP cube. click Server Settings. select the cube that you want to build. . 2.  To build an OLAP cube 1. On the PWA home page. and then click Build Now.

128 Project Server 2010 Administrator's Guide

4
Look and Feel
Project Server 2010 supports customization of various user interface elements, including:  Views  Color and text formats of grouping levels within views  Color and shape options for Gantt bars  Links, or groups of links, included on the Quick Launch in Project Web App The options that are described in this chapter are available under Look and Feel on the Server Settings page in Project Web App.

Server Settings page

Look and Feel

129

Manage Views
Team members can view project information by selecting different views from the View list at the top of most pages within Project Web App. As an administrator, you can better meet the information needs of your organization by adding new views and changing the existing views. There are several different kinds of views in Project Web App, as listed in the following table.
View Type Project Use this type of view to review the task, assignment, and resource details of a specific project when a team member clicks a project in the Project Center. Example

Project Center Use this type of view to review information about all projects in the Project Center.

130 Project Server 2010 Administrator's Guide

View Type Resource Assignments Use this type of view to review details about specific resource assignments.

Example

Resource Center Use this type of view to review and compare all resources in the Resource Center.

Look and Feel

131

View Type My Work Team members use this type of view to review their task assignments.

Example

Resource Plan Managers use this type of view to create resource plans for their projects.

132 Project Server 2010 Administrator's Guide

View Type Team Tasks Team members use this type of view to review the tasks to which their team is assigned as a resource.

Example

Team Builder Managers use this type of view to create a team for their project (not a resource plan).

Look and Feel

133

View Type Timesheet Team members use this type of view to report time against the projects to which they are assigned.

Example

Portfolio Analyses Portfolio managers use this type of view to compare project proposals and determine which meet organizational goals.

click Manage Views. On the Quick Launch. in the View Type list. A list of views is displayed. 5. To create a new view 1. . under Settings. On the Server Settings page. Click New View. 3. Example Create a New View Options for creating a new view vary depending on the type of view you are creating.134 Project Server 2010 Administrator's Guide View Type Portfolio Analysis Project Selection Portfolio managers use this type of view to choose which proposals to approve as projects. 4. 2. In the Name and Type section. select the type of view you are creating. In the Name box. click Server Settings. type the name of the new view.

or Assignment Choose the type of information to display in the view. Setting this value is optional. Note This option is only available for views that can show a Gantt chart. click a field name in the Displayed fields box. Field width Click the name of a field in the Displayed fields box.    Available fields and Displayed fields In the Available fields list. Setting this value is optional. . Team Tasks.  Gantt Chart format Select the type of Gantt chart that you want to use to display information. To reorder the fields. Custom Label Click the name of a field in the Displayed fields box. type a description of the new view. and then type a number of pixels in the Field width box. 7. Note Only the Timesheet and My Work views have this option. Complete the remaining fields on the New View page. 6. Not all fields can be made read-only. or Portfolio view.  Make column read only Click the name of a field in the Displayed fields box. Resource. You can repeat this for each field listed in the Displayed fields box. and then click Up or Down to move it within the list. then select this check box to make that field read-only. Note This option is only available for views that can show a Gantt chart. You can repeat this for each field listed in the Displayed fields box.  Left offset for the splitter bar Type an offset measurement in pixels to define the placement of the splitter bar in the view.Look and Feel 135 In the Description box. Note Custom labels are not available for the Resource Plan. Team Builder. Note These choices are only available when Project is selected as the View Type. select the fields that you want to include in the view and then click Add.  Task. and then type a display name in the Custom Label box. Not all options listed below are available for every view type.

Tip If users are unable to see views that they think they should be able to see. In the Order list. For more information on setting up grouping formats.‖ later in this chapter. select Ascending or Descending to define the order in which you want to sort the view. Filter Click this button to create or edit filters that you can apply to this view. see ―Grouping Formats. and then click Add to make the new view available to users in that security category. Note This option is only available in Resource Center views. For more information. see ―To set up a filter for a view Filter Resources to user’s RBS branch Select this check box to display only those resources that fall under the resource breakdown structure branch of the resource looking at the view. People using the view will be able to expand additional outline levels. Grouping format Select the grouping style that you want to use.     Sort by Select the fields by which you want to sort the view. and then define the order of grouping by using the Group by and Then by lists. a best practice is to first check that the correct categories are added to the view. . in this view.  Available categories and Categories which access this view Click a category in the Available categories list. by default.136 Project Server 2010 Administrator's Guide   Show Select the number of outline levels that you want to display.

Look and Feel

137

8.

After you have set all appropriate options for the new view, click Save.

You can apply a filter to a view, so that data in the view is automatically narrowed down based on a set of criteria. To set up a filter for a view 1. On the New View page, in the Filter section, click Filter. The Custom Filter dialog box is displayed. 2. On the Custom Filter dialog box, select a field in the Field Name list and a test in the Test list, and then type a value to test for in the Value box. You can set a range of values by typing two values separated by a comma (,) in the Value box.
Tip As you create the filter rules, a green check mark or a red X is displayed to the left of the rule, under the Valid? heading. If you see a red X next to a rule, hover over the X for more information on why the rule is not considered.

If the filter contains more than one row, select an operator in the And/Or column to start a new row. 4. Click OK when you have finished setting up filters.
3.

Modify a View
After you have been using a view in Project Web App, you may find that it needs some finetuning. It may need a field added, or some adjustments to the security settings. You can easily modify existing views. To modify an existing view 1. On the Quick Launch, under Settings, click Server Settings. 2. On the Server Settings page, under Look and Feel, click Manage Views. 3. Click the name of the view you want to modify, in the Name column.

138 Project Server 2010 Administrator's Guide

Tip If you know the view type for the view you want to modify, you can collapse the other view types to reduce the number of views to scroll through.

4.

Modify the fields and options for the view, and then click Save.

Copy a View
Sometimes it may be easier to create a new view by basing it on an existing view. You can select a view and copy it to create a new view. To create a new view as a copy of an existing view 1. On the Quick Launch, under Settings, click Server Settings. 2. On the Server Settings page, under Look and Feel, click Manage Views. 3. Click a cell in the row for the view you are copying, and then click Copy View.
Note Be careful NOT to click the name of the view, in the Name column. This will open that view for editing, instead of selecting it.

4.

On the Copy View dialog box, type a name for the new view, and then click OK. The copied view is added to the table on the Manage Views page.

Scroll through the list of views to find the view you just created, and then click the name of the new view in the Name column. 6. Modify the fields and options for the new view, and then click Save.
5.

Look and Feel

139

Delete a View
If a view is not meeting your organization’s needs, or is just not being used, you can delete it from Project Web App. To delete a view 1. On the Quick Launch, under Settings, click Server Settings. 2. On the Server Settings page, under Look and Feel, click Manage Views. 3. Click a cell in the row for the view you are deleting, and then click Delete View.
Note Be careful NOT to click the name of the view, in the Name column. This will open that view for editing, instead of selecting it.

4.

When prompted, click OK to delete the view.

Grouping Formats
You can change how rows (or levels) of information appear when task and resource information is grouped in the Project Center, Resource Center, Project, Task, Timesheet, and Assignment views. By changing the appearance of these grouping levels, you can highlight specific information for your team members. The following figure shows an example of grouping level formatting. The first-level groups are shaded in yellow with bold text, and the second-level groups are shaded in blue with bold text.

140 Project Server 2010 Administrator's Guide

To change the appearance of grouping levels 1. On the Quick Launch, under Settings, click Server Settings. 2. On the Server Settings page, under Look and Feel, click Grouping Formats. A list of grouping formats appears. 3. In the Grouping format list, above the table, select the grouping level that you want to format. This will refresh the table and narrow down which levels are displayed.

4.

To rename the selected grouping level, click Rename. Type the new name in the New name for the grouping format box, and then click OK.

5.

If you do not want to rename the selected grouping level, skip this step. Use the lists in the Cell Color, Font Color, and Font Style columns to define the appearance of each grouping level.

6.

Click Save, at the bottom of the page.

Look and Feel

141

After you have created a format for grouped task or resource information, you apply the formatting when a new view is created or modified. See ―Manage Views,‖ earlier in this chapter, for more information.

Gantt Chart Formats
You can format the color, shape, and pattern of the Gantt bars in Gantt Charts views, Project Center views, and other views. To format a Gantt chart 1. On the Quick Launch, under Settings, click Server Settings. 2. On the Server Settings page, under Look and Feel, click Gantt Chart Formats. 3. In the Gantt Chart list, above the table, select the name of the Gantt chart view that you want to format.

4.

To rename the selected Gantt chart view, click Rename. Type the new name in the New name for Gantt Chart box, and then click OK. If you do not want to rename the selected Gantt chart view, skip this step.
Note You cannot change the names of the individual Gantt bars.

5.

For each bar type within the selected Gantt chart view (represented as a row in the table), choose the following:  Display Select this check box to display this bar type on the selected Gantt chart view.  Middle bar shape Select the shape you want to use for the bar type.

142 Project Server 2010 Administrator's Guide

     

Bar Color Choose a color to fill in the selected bar shape. Bar Pattern Choose a pattern to fill in the selected bar shape. Start shape Choose a graphic to display at the start of a Gantt bar of this type. Start color Choose a color to fill in the start shape. End shape Choose a graphic to display at the end of a Gantt bar of this type. End color Choose a color to fill in the end shape.

A preview of the resulting Gantt bar is displayed on the right side of the table.

6.

Click Save, at the bottom of the page, below the table.

Quick Launch
The Quick Launch is the left navigation list in Project Web App.

Look and Feel 143 You can change how links behave on the Quick Launch. when you are looking at the Project Center. click All sections. 3. You can also choose whether to include links from Microsoft SharePoint Foundation. reorder the links. On the Quick Launch. On the Server Settings page. To change how the Quick Launch displays links 1. choose from the following options:  All sections If you want to display all Quick Launch items at all times. 2. under Look and Feel. . you will only see the Quick Launch items under the Projects heading. under Expand menu items for.  Current section only If you want to collapse the Quick Launch items to just the toplevel headings for sections that do not apply to the current view. regardless of what view is currently displayed. add new links or groups of links. under Settings. click Current section only. click Quick Launch. For example. or delete links or groups of links. click Server Settings. if you have selected Current section only. or you can choose to collapse links based on the context of what a user is currently viewing. Change Quick Launch Behavior Links on the Quick Launch can be displayed at all times. In the Edit Quick Launch section.

. Links can be to views within Project Web App. Type a name for the link in the Custom link name box.144 Project Server 2010 Administrator's Guide Select the Show menu items from Microsoft SharePoint Foundation check box to also show any applicable Quick Launch items that are part of SharePoint Foundation. Under Set Menu Item Details. click New Link. 3. The link will be indented below the selected heading. To add a link to the Quick Launch 1. 6. click Server Settings. 5. In the Heading section. Add a New Link You can also add new links to the Quick Launch. to meet your organization’s needs. click Quick Launch. choose the placement for the new link:  If you are creating a new heading link for the Quick Launch. 5.  If you are creating a link to be included below an existing heading. or even external Web sites. On the Server Settings page. only Project Web App items will be displayed on the Quick Launch. select New Heading. Type the URL for the link in the Custom Web address box. If you clear this check box. similar to the Projects and My Work headings. 2. This is the text that will appear linked on the Quick Launch. under Look and Feel. 4. Click Save. On the Quick Launch. under Settings. intranet sites. select the existing heading from the list. 4.

click Server Settings. When you have the group of links ready to go. . or needs to be temporarily hidden. you may find that the links on the Quick Launch would be more helpful if they appeared in a different order. then create all of the new links below the heading and set those to display. you can change the Display link in Quick Launch setting for the new heading to Yes. If you want to hide the new link from the Quick Launch.Look and Feel 145 7. To modify an existing Quick Launch item 1. 3. you can choose to hide the new heading. under Settings. Modify the link name. Tip If you have a long list of Quick Launch items to scroll through. On the Quick Launch. you can collapse the headers to hide the links you do not want to modify. click the name of the link you want to modify. and/or display option for the link. On the Server Settings page. click Quick Launch. if you are creating a new group of links below a new heading. is not categorized under the right heading. 2. On the Quick Launch. click No in the Display link in Quick Launch list. click Server Settings. To reorder the links on the Quick Launch 1. under Settings. Modify an Existing Link If a link on the Quick Launch is not pointing to the right place. 8. under Look and Feel. Under Set Menu Item Details. Click OK to add the link to the Quick Launch. URL. Reorder Quick Launch Items As you use Project Web App. and the group of links is added to the Quick Launch. click Quick Launch. You can reorder the links to meet your organization’s needs. For example. you can easily make those changes. 2. 4. On the Server Settings page. and then click OK. under Look and Feel. in the Name column.

146 Project Server 2010 Administrator's Guide 3. This will open that link for editing. To delete a link from the Quick Launch 1. 2. If you select a heading. instead of selecting it. click Server Settings. under Look and Feel. Delete a Link If you find that your organization is not using a link that is currently included on the Quick Launch. all items indented below the heading will move with it. 3. Under Set Menu Item Details. click Quick Launch. in the Name column. all items indented below the heading will also be deleted. and then click Move Up or Move Down. under Settings. and then click Delete Link. or group of links. Note Be careful NOT to click the name of the link. Under Set Menu Item Details. If you select a heading. 4. . Note Be careful NOT to click the name of the link. in the Name column. click a cell in the row for the Quick Launch item you are moving. instead of selecting it. On the Server Settings page. On the Quick Launch. When prompted. from the Quick Launch. click a cell in the row for the Quick Launch item you are deleting. you can easily remove it. click OK to delete the link. This will open that link for editing.

Time and Task Management 147 5 Time and Task Management Site administrators and others with appropriate permissions can configure how timesheets and task status are captured and handled in Project Server 2010. . This includes:  Setting up fiscal periods and time reporting periods  Adjusting timesheets  Setting up timesheet line classifications  Choosing the right timesheet settings  Configuring administrative time categories  Choosing task status settings  Preventing certain tasks from being updated The options that are described in this chapter are available under Time and Task Management on the Server Settings page in Project Web App.

if the fiscal year begins on January 1. By setting up fiscal periods in Project Server 2010. 2011. By creating the fiscal periods in bulk. you can use fiscal periods as a dimension in your OLAP cubes. you can base them off of several different models. and then another that is four weeks long— you can specify this model in Project Web App.148 Project Server 2010 Administrator's Guide Server Settings page Fiscal Periods Fiscal periods define the start and beginning dates of the business calendar. followed by one that is five weeks long. They are used to calculate financial statements on an annual basis. and Project Server will create fiscal periods for the year according to that schedule. Once set up. if your organization divides each quarter into three periods—one that is four weeks long. and Project Server will calculate the dates accordingly. you can easily define the fiscal periods for a specific year. So. the first quarter will have three periods:  Period 1: 1/1/2011 – 1/28/2011  Period 2: 1/29/2011 – 3/4/2011  Period 3: 3/5/2011 – 4/1/2011 . For example. you provide a way to map project work against your organization’s fiscal planning structure. Define Fiscal Periods Using Project Web App.

4.5. 6. or select it using the date picker.4. In the Set Fiscal Year Creation Model section. . click Server Settings.  Suffix A suffix of up to 15 characters. In the Define Period Naming Convention section.  13 months This method sets each fiscal period as four weeks.5 Method This fiscal quarter method sets a four-week fiscal period. type the date on which the fiscal year should begin. select a formatting method for the fiscal period:  4. click the year that you want to define as the fiscal period. create a unique name for the periods by entering:  Prefix A prefix of up to 15 characters. followed by another four-week fiscal period.  Next Sequence Number A sequence number of up to six digits.4 Method This fiscal quarter method sets a four-week fiscal period. next to Sample. 2. you can go back and modify the calendar dates to refine the schedule to meet your organization’s needs. followed by a five-week fiscal period.Time and Task Management 149 To set fiscal periods in Project Web App 1. 3. and then a five-week fiscal period. 5. Once you have saved. under Settings. Note If you want to use a different model for your organization’s fiscal year. click Fiscal Periods. Tip As you enter a naming convention in the Prefix.4 Method This fiscal quarter method sets a five-week fiscal period. In the Manage Fiscal Period section.  5. and Suffix fields. use the steps in this procedure to choose a model that is closest to what you would like your fiscal year to look like.  4. beginning on January 1. On the Quick Launch.4. and then another four-week fiscal period. Next Sequence Number. under Time and Task Management. and then another four-week fiscal period. an example of the final naming convention is displayed below the fields. and then click Define. followed by a four-week fiscal period. In the Define Fiscal Period Start Date section.  Standard calendar year This method sets each fiscal period according to the standard 12 month year. On the Server Settings page.

Click Save. On the Quick Launch. you can edit it by using the Adjust Fiscal Months grid. under Time and Task Management. In the Adjust Fiscal Months section.150 Project Server 2010 Administrator's Guide 7. Start and end dates for periods following the modified end date will be automatically adjusted so that all periods are contiguous. 3. In the Manage Fiscal Period section. 2. 4. Click Create and Save. under Settings. . After defining a fiscal period. and then use the date picker to choose a new end date. click Fiscal Periods. 5. select the year that you want to adjust. On the Server Settings page. click Server Settings. To refine the fiscal period dates 1. click the end date that you want to modify. the fiscal period will be displayed with the individual periods showing in the Adjust Fiscal Months grid. On the Fiscal Periods page. in the End Date column.

In the Manage Fiscal Period section. Time Reporting Periods Time reporting periods define the start and end dates used for each timesheet and task status report. On the Server Settings page. and the year returns to an Undefined status. For example.4 schedule over the 4.4. click Fiscal Periods. To delete the fiscal period for a specific year in Project Web App 1. Once you have deleted the fiscal periods for a year. as necessary. or that you would prefer a 5. you may decide that a 13 month schedule would work better. In the Adjust Fiscal Months section. All periods are deleted. 3. you can create several time reporting . Instead of redefining each date. select the year that contains the fiscal periods you want to delete. click Delete. under Settings. and then insert or delete individual periods.Time and Task Management 151 Delete Fiscal Periods After you have initially defined the fiscal periods for your organization. you can redefine them using the process outlined in the ―Define Fiscal Periods‖ section.5.4 schedule that you initially selected. it may be easier to delete the fiscal periods altogether and start over from scratch. under Time and Task Management. You can create several time reporting periods in bulk to set them up. 4. On the Quick Launch. 2. click Server Settings.

enter the following:  Number of periods to be created Type the number of time reporting periods you want to create at one time. based on the date selected in this field. or use the date picker to choose a date. as all time reporting periods will be based on this date.152 Project Server 2010 Administrator's Guide periods for an entire fiscal year. 2. 4. leave this set to 52. under Time and Task Management. click Time Reporting Periods. Create Bulk Time Reporting Periods Rather than creating each time reporting period individually. to meet the individual needs of your organization. you will save yourself quite a bit of time if you create them in bulk. Length of the standard period (days) Type the number of days in each time reporting period. Tip As you enter a naming convention in the Prefix. 3. using parameters for how many periods to create.  Next Sequence Number A sequence number of up to six digits. In the Define Bulk Period Parameters section. as needed. when the first period should begin. and how long each period should last. Project Server will calculate the dates for all subsequent periods.  Suffix A suffix of up to 20 characters. On the Quick Launch. and then modify those periods. under Settings. If you want to use one-week time reporting periods. click Server Settings.  .  Date the first period starts Type the date on which you want the first time reporting period to start. next to Sample. Next Sequence Number. and Suffix fields. create a unique name for each of the periods by entering:  Prefix A prefix of up to 20 characters. an example of the final naming convention is displayed below the fields. leave this set to 7. In the Define Batch Naming Convention section. If you want to create time reporting periods for each week in a year. Note Be sure to select the correct day of the week. To create several time reporting periods at once 1. On the Server Settings page.

scroll through the list to find where you want to insert a new time reporting period. you may need to insert a shortened period to transition between the two models. date. See the ―Timesheet Settings and Defaults‖ section for more information. under Settings. or status. 2. On the Server Settings page. Note The Status column for all new time reporting periods is set to Open. if the current fiscal year uses Monday-Sunday time reporting periods. Only a Project Server administrator can close a period. click Server Settings. Click Save. Click Create Bulk to create the time reporting periods you specified. Click Insert Before or Insert After to create a new row for the period you are inserting. 6. you may need to insert an additional time reporting period. In the Create Periods section. and then click the nearest existing period. . click in the grid in the Create Periods section. under Time and Task Management. click Time Reporting Periods. Insert or Delete Time Reporting Periods Occasionally. For example. See ―Insert or Delete Time Reporting Periods‖ for more information. To make changes to a period label. and you have decided that the next fiscal year will use Sunday-Saturday time reporting periods. 3.Time and Task Management 153 5. 4. It is possible to restrict future timesheets from being submitted. On the Quick Launch. 7. and then enter the modifications. To insert a time reporting period 1.

under Settings. 2. 8. To delete a time reporting period 1. If the inserted period is not currently open for resources to report data. select Closed in the Status column. if your organization has already set up one-week time reporting periods for the entire year. You may also find that you occasionally need to delete existing time periods. you will need to delete the remaining one-week periods. . time reporting periods that have associated timesheets cannot be deleted. click Server Settings. 6. 7. On the Server Settings page. Replace the dates in the Start Date and End Date columns. and partway through the year you decide to switch to two-week time reporting periods. 3. and recreate the rest of the year as two-week periods. Because it is common for time reporting periods to have associated timesheets. replace the New Period text with the name of the inserted period. if necessary.154 Project Server 2010 Administrator's Guide In the Period Label column. click Time Reporting Periods. For example. Important To protect project data provided by team members. On the Quick Launch. Click Save. and then click Delete. under Time and Task Management. In the Create Periods section. click the row for the time period you want to delete. 5. it is unlikely that you will be able to delete past time reporting periods.

This option may display a very long list of timesheets. Timesheet Adjustment Occasionally. click Server Settings. 2. . You can use the options to the right of the line in the shaded filter section to narrow down the list. People with the appropriate permissions can adjust timesheet data. On the Quick Launch. Choose filter options to help you display the timesheet you want to adjust:  Approved by me Choose this option to display only timesheets that you have approved. To adjust timesheets 1. Click Save.Time and Task Management 155 4. under Settings. 3. On the Server Settings page.  Available timesheets to adjust Choose this option to display all timesheets available for adjustment. click Timesheet Adjustment.  My Resources Unsubmitted Timesheets Choose this option to show all timesheets for resources assigned to your projects. a resource will identify changes that need to be made to a timesheet after the timesheet has been submitted and approved. under Time and Task Management.

your organization may have different classifications for Travel. Select the Resources check box. or a Custom Date Range. Available timesheets to adjust. and then choose whether you want to filter for a specific Fiscal Period. This opens the timesheet. Training and Standard (default) work. indicating that the data for those rows was not submitted by the resource. . click Save. Note The Standard line classification is required. 6. Using classifications enables the timesheet user to add the same task assignment once per classification type. Rows that you have adjusted will show as Not Submitted in the Process Status column. For example. even if all work on the task assignment is being reported against timesheet lines with other classifications.  5. Make adjustments to the timesheet.  Resources Use this option in combination with Approved by me. Line Classifications Timesheet line classifications are used to report different types of time against the same task assignment.156 Project Server 2010 Administrator's Guide Date Use this option in combination with Approved by me. 4. or My Resources Unsubmitted Timesheets. or My Resources Unsubmitted Timesheets. Available timesheets to adjust. in the Actions group. Click the name of the timesheet you want to adjust. On the Timesheet tab of the ribbon. and/or a specific Resource Name. as necessary. Click Apply. in the Timesheet Name column. on the far right side of the shaded filter section. to filter the list of timesheets using the options you selected. 7. and then choose whether you want to filter for a specific Cost Center. Select the Date check box.

5. Click Save. under Settings. 3. Enter Line Classification section. choose Inactive in the Status column for the line classification you no longer want available to resources. Resources can manually change a timesheet line to use one of the additional line classifications you have configured. 2. To delete an existing timesheet line classification 1. Click Save. 2. To create a new timesheet line classification 1. under Time and Task Management. click Line Classifications. Enter Line Classification section. under Settings. but that classification has been used in previous timesheets. Enter Line Classification section. 4. If you no longer want resources to be able to use a classification in timesheets. all timesheet lines use the Standard (or default) line classification. In the Edit. In the grid. To inactivate an existing timesheet line classification 1. and then click Delete Classification. click the row for the line classification you are deleting. 3. This will maintain the classification in previous timesheets. click Line Classifications. under Time and Task Management. you can delete it from Project Server altogether. On the Server Settings page. On the Server Settings page. On the Quick Launch. 4. click New Classification. On the Quick Launch. 2. In the Edit. In the Edit. click Line Classifications. you can make the classification inactive. Note The Standard line classification cannot be inactivated. click Server Settings. under Settings. click Server Settings. click Server Settings. 3. but prevent it from being available in future timesheets. If a line classification has never been used on a timesheet. On the Quick Launch. . type a new name and description that identifies the timesheet line classification for team members.Time and Task Management 157 By default. under Time and Task Management. for historical reporting purposes. On the Server Settings page.

each column in a timesheet represents 7 days. a feature new to Project Server 2010 that combines task status updates with timesheets in one view. select the The timesheet will use standard Overtime and Non-Billable time tracking check box to enable team members to submit overtime and non-billable time. type the hours in the The number of hours in a standard timesheet day is box. Timesheet Settings and Defaults Site administrators can choose several different options to control how resources enter time on their timesheets. To specify how many hours constitute an entire day's worth of work. The Timesheet Settings and Defaults page is also where you choose whether your organization will use Single Entry Mode. 5. To configure timesheet settings and defaults 1. Click Save. On the Quick Launch. On the Server Settings page. click Timesheet Settings and Defaults. under Settings. clear this check box. specify which data should be included in the default timesheet:  Select Current task assignments to pre-populate timesheets with information about the team members' tasks assignments. If you do not want team members to be able to submit overtime or non-billable time. specify whether you want timesheet columns to represent Days or Weeks. If you choose Weeks. In the Timesheet Grid Column Units section. In the Default Reporting Units section. 7. and the date in the column represents the first day of the week. specify whether team members report time within each timesheet column in Hours or Days. 3. 6.  Select No prepopulation to create blank timesheets for team members. . and whose approval is required. In the Default Timesheet Creation Mode section. 4. In the Project Web App Display section. 2.  Select Current projects to pre-populate timesheets with information about the team members' current projects.158 Project Server 2010 Administrator's Guide 4. under Time and Task Management. click Server Settings.

you can choose to select the Require line approval before timesheet approval check box.  Under Task Status Manager Approval. if you want each line approved before the entire timesheet can be approved. In the Timesheet Policies section. This time is not mapped to any Project Server project or task. In the Hourly Reporting Limits section. or type 0 in the Minimum Hours per Timesheet box to represent no minimum time. specify the following:  Select the Allow future time reporting check box to enable team members to record time for periods in the future. type the hours in the The number of hours in a standard timesheet work week is box. 9. select Disabled. errors will appear on their timesheets when they submit them. you must enable task status manager approval.  Select the Allow top-level time reporting check box to enable team members to report time against summary tasks. and those values will roll up to the summary level. or internal business policies. If you only want to approve entire timesheets (no line-by-line approval). customers. if your organization uses team resources. as well as the maximum number of hours allowed to be reported in a day. Personal tasks will not show up outside of a team member’s timesheet and/or task status. team members must report time against lower-level tasks. 8.  Select the Allow new personal tasks check box to enable team members to create as many personal tasks as needed.Time and Task Management 159 To specify how many hours constitute a standard work week. remember this when setting the maximum and minimum values in the Hourly Reporting Limits section. Typing either of these options effectively turns off reporting limits. If you don't want to set a maximum or a minimum hourly reporting limit. click Enabled to allow project managers to coordinate or approve/reject timesheet lines on a per-line basis. . Note If you are using Single Entry Mode. 10. Also. If team members report time beyond these limits. type 999 in the Maximum Hours per Timesheet box to represent unlimited hours. If this check box is cleared. If you select Enabled. specify the maximum and minimum hours allowed in a timesheet. Note You may need to put some restrictions on how time is entered based on accounting systems.

sick leave. 3. training. Click Save. 14. 2. 13. Click New Category.160 Project Server 2010 Administrator's Guide 11. On the Server Settings page. under Time and Task Management. select the Fixed Approval Routing check box to prevent team members from manually specifying the next approver when they submit their timesheet. To add an administrative time category 1. organizational meetings. . click Administrative Time. 12. In the Approval Routing section. Site administrators can set up different categories for administrative time. or travel. as well as actual work. Administrative time may include vacation. Administrative Time Time spent on things other than project work can be classified as administrative time. Tip Click Purge Log to clear the auditing log. select the Enable Timesheet Auditing check box to create a detailed record of all changes made to a timesheet. click Server Settings. on their timesheets. select the Single Entry Mode check box if you want to enable team members to report task progress. On the Quick Launch. so that resources can capture those hours on their timesheets to accurately represent what they have done during a given reporting period. A row is added to the table. In the Auditing section. In the Single Entry Mode section. under Settings.

Click the row header for the category you are deleting. Click Save. 5. and be sure the check box in the Always Display column is cleared. by default. click Server Settings. In the Work Type column. you may decide that you do not actually need a category and would rather delete it. 9. 2. To delete an administrative time category 1. Type a name for the new administrative time category in the Categories column. click Administrative Time. 8. In the Approve column. and then click Delete Category. On the Quick Launch. For example. Once you click Save. under Settings. If you have not yet saved the new categories. Select the check box in the Always Display column if you want to display a row for this category. you can easily delete the category you do not need. On the Server Settings page. As you create administrative time categories. 7. or Non Work time. such as training or travel.Time and Task Management 161 4. choose whether you want time reported in this category to require approval from a manager. Tip Before clicking Save. change the Status column for that category to Closed. . The category is removed. such as vacation or sick leave. any new categories you have added cannot be deleted. you might choose to always display a timesheet row for the Sick time category. be sure you have the right set of categories listed. or Closed. 6. so that team members are reminded to report those hours. Tip If you want to make it so that a category that has been saved is no longer available for selection in a timesheet. under Time and Task Management. on every timesheet for every user. choose whether the category captures Working time. In the Status column. choose whether the category is currently Open for use on timesheets. 3.

For example. say you have created several new categories on the Administrative Time page. Options in this section can only be modified if you are not using Single Entry Mode. However. clear the Force project managers to use the progress reporting method specified above for all projects check box. Once you click Save on the Administrative Time page. Task Settings and Display Site administrators can use the Task Settings and Display page to change how resources report task progress. On the Server Settings page. . and other task settings. click Server Settings. In the Reporting Display section. select the tracking method that best represents how you want team members to report their progress on project tasks. requiring the same reporting method provides a consistent user experience throughout all projects in your organization. how actual work can be updated. 3. but have not yet clicked Save on that page. Tip If you want project managers to have the option of displaying different reporting methods for their projects. and may make it easier for team members to report progress.162 Project Server 2010 Administrator's Guide Note You can only delete categories that are not yet saved. specify how you want updates on actuals to occur: 4. 5. Click Save. the Hours of work done per period and Force project managers to use progress reporting method specified above for all projects options are automatically selected and cannot be modified. On the Quick Launch. choose whether you want resources to report their hours daily or weekly. under Time and Task Management. select the appropriate day from the Week starts on list. If you choose the Resources should report their total hours worked for a week option. 4. To configure task settings and display options 1. 2. click Task Settings and Display. In the Protect User Updates section. the categories you added can no longer be deleted. You can delete any of the new categories you created while on that page. under Settings. In the Tracking Method section. If you are using Single Entry Mode.

select the Import all timesheet line classifications check box. On the Quick Launch. in the Lock column. select the Allow users to define custom periods for task updates check box. In the Define Near Future Planning Window section. select the Only allow task updates via Tasks and Timesheets check box. click Server Settings. under Settings.  To enable users to provide task updates using periods that they define. 6. In the Select Tasks section. To prevent updates to a task 1. type the number of reporting periods you want to include in the Near Future Planning Window on the Tasks page. 3. click Select All. in the Select a project list. . Tip If you want to prevent updates to all tasks in a project. You can also click Clear All to remove all current selections in the Lock column. under Time and Task Management. On the Server Settings page. only actual work from timesheet lines that have a standard classification will be imported into task status. click Close Tasks to Update. On the Close Tasks to Update page. Note Changes to task updating will not take effect until the next time that the project is published. below the table in the Select Tasks section. 2. select the check box for each task that you want to close to updating.  To import actual work from all timesheet lines.Time and Task Management 163 To prevent the project manager from updating a team member's actual time worked. 4. click the project that contains that task you want to close for updating.  Close Tasks to Update If you have the appropriate permissions. If this check box is cleared. regardless of line classification. you can lock project tasks in order to prevent people from submitting task updates.

. Tasks that you selected to be closed for updating will remain open until you publish the project.  To save your changes without publishing the project. click Submit instead. click Publish. click Submit. Do one of the following:  To publish your project and close the selected tasks to updating. If you are not ready to publish that information. the task closure settings will also be published. Note Publishing your project to close tasks to updating will also publish all applied task updates and any other changes that were made to the plan.164 Project Server 2010 Administrator's Guide 5. to save your task closure settings. When you are ready to publish other changes to your project.

Queue System Overview A queue is a waiting line that becomes a necessity when the number of service requests becomes greater than the optimum serving capacity. This chapter provides an overview of the Queuing System. This chapter also describes how to manage queuing through the Microsoft Project Web App Server Settings page. and how multithreading works in the queue. the methods in which queuing jobs are grouped. states that queuing jobs can be in. there are several instances when this is true. In an Enterprise Project Management System. which describes the queuing process and architecture.165 6 Queue Management This chapter describes the Microsoft Project Server 2010 Queuing System. For example: .

all jobs are saved into SQL Server (not the file system) and take advantage of SQL Server transactions. and then processes the data asynchronously on a first-come. A few hours before their team status meeting. Fault tolerance: Failed jobs in the queue can be retried. Also. records entries for the requests in Microsoft SQL Server.) o o  Scalability . the Project Queuing System ensures that the Save job is processed first and is then followed by a Publish job. nearly all project managers publish their projects. Also. (This process is called transparent failover. The Project Server 2010 Queuing System takes all the users' input. The purpose of the Project Server 2010 Queuing System is to handle these abrupt changes in demand gracefully and reliably. the other one picks up the extra load automatically.166 Project Server 2010 Administrator's Guide   At the end of the workday on Friday. In-order delivery: If a user of Project Professional clicks Save and then Publish. nearly all 500 employees of a small company submit their timesheets. when more than one instance of the Queue NT Service is running. Nearly all critical operations in the Project Server 2010 system go through the Project Server 2010 Queuing System. it is not processed. first-served basis. Having a queue ensures that the Project Server 2010 EPM solution does not stop working when a spike in demand occurs. if one of them stops responding. If a job is just half-saved. These include:  Project Save  Project Publish  Timesheet Save  Timesheet Submit  Project Backup/Recovery  Report Data Service operations  Cube Building Service operations  Server Side Scheduling The Project Server Queuing System provides the following advantages:  Reliability o Data integrity: There is a well-defined protocol to save any job in the queue.

Project 2 Publish. The number of jobs in the queue is limited only by the scale limitations of SQL Server. Each middle-tier server will have a Project Queuing Service. and the loads will be balanced automatically. For example. o o  Manageability Queuing process The following illustration shows the queuing process: Queuing Process . and a cube building job can be processed simultaneously. You can simply add more middle-tier servers to handle load better.Queue Management 167 o Multithreading: The Project Server 2010 Queuing System can process multiple jobs at the same time. Project 1 Save.

Remember this deployment model when going through the rest of this section. 2. 5. if two Project Web App sites are defined for the Service Application. the Queue Worker Process will service both of them.168 Project Server 2010 Administrator's Guide 1. In this manner. For example. The user makes a server request from a client application (for example. Queuing architecture This section describes:   Queuing modules How the Queuing modules work together Queuing modules The Queue NT Service is installed on every Project Server application server computer as part of provisioning. The user passes a Job ID (a unique identifier that tracks the request) as part of the request. the jobs are backed up and restored as part of the normal Project Server database backup and recovery routines. and is dependent on how the four modules work together: 1. The user queries to check the status of the request through the issued Job ID. Job Storage: Queue jobs are stored in the Draft and Published Project Server databases. publishing a project from Project Professional). The Project Server 2010 Queuing System returns the status of the request to the user. 4. The Project Server Queuing System is composed of the following four modules. 3. . It starts one "Queue Worker Process" per Service Application defined in the farm. and it runs under the "Service Application Administrator" identity. The Queue Worker Process services all the instances of Project Web App (PWA) that are associated with its Service Application. The Project Web service takes the request and puts it in the queue. A Job ID is issued to the user as an acknowledgement.

Every job polling thread looks for jobs originating from a specific instance of Project Web App.  The Queue Worker process starts the Job Polling threads for each instance of PWA that it services. Job Polling: Job storage is polled at regular intervals by a Job Polling thread to check for new jobs.  o . The Job Polling thread has two main properties: o Type . The Job Polling thread runs inside the "Queue Worker Process" process and under the "Queue Worker Process" identity.Queue Management 169 2. Project Web App instance . Polling intervals are configured by administrators in the Project Web App Server Settings Queue Management pages.A given job polling thread could be a "project job polling thread" (looking for project-related jobs) or a "timesheet job polling thread" (looking for timesheetrelated jobs).

 Project Web App Manage Queue page: Administrators use this to see the status of any job in the queue. Job Processing: The Job Polling thread spawns one Job Processing thread for each job that it finds. This feature is part of PWA — there is no need to download a special tool. 4. Note that the job processing threads run under the "Microsoft Project Server Queue Service 2010" identity. The maximum number of Job Polling threads can be configured by administrators.170 Project Server 2010 Administrator's Guide 3. Job Status Check and Management: This is the module of the Project Server Queue that the end user sees. . They can also cancel or retry failed jobs.

. This feature is part of PWA — there is no need to download a special tool. This feature is part of PWA — there is no need to download a special tool.Queue Management 171 Job Grid on the Manage Queue page  Project Web App Queue Settings page: Administrators can view or change the settings of a queue. such as the polling interval and the maximum number of job processor threads. Queue Settings page  Project Web App My Queued Jobs page: Any user can check the status of a job using this interface.

Job Processing Job processing occurs in different phases and involves interaction between various modules: 1.172 Project Server 2010 Administrator's Guide  Queue Status PSI: Software developers can use these APIs to get the status of any queue job. a team member can submit a timesheet. Adding Jobs There are many ways in which jobs can be added to the queue. or a thirdparty application can publish a project. The Queue NT Service should always be running for the Project Queuing System to work. For example. Start Queue Worker Process: When the Queue NT Service starts. a project manager can save a project from Project Professional. How it all works together The Project Server Queuing System modules must interact and work as a whole when the system is tasked with requests. such as adding jobs. . There are several powerful filters to narrow the search. it starts one child Queue Process per PWA instance. Each of these actions causes a call to an element in the Project Server Interface (PSI). processing jobs. which in turn adds the appropriate jobs to the queue. and retrieving job status.

it starts the job polling threads. job processing threads are created. 4. 3. Create job processing threads: If there are new jobs. . the status of the job (success or failure) is written back to the database. Start Job Polling threads: When the Queue Worker Process starts. Write status: Once a job processing thread finishes.Queue Management 173 2. 5. Pick up new jobs: The polling thread looks for new jobs in the project databases. which are specific to instances of Project Web App.

and Cube Building. Administrators can use the Project Web App Queue Management pages. although other types of messages may be sent to this queue as well. team members can use the My Queued Jobs page. Reporting. . Publishing.174 Project Server 2010 Administrator's Guide Retrieving status Job status can be checked in various ways. or software developers can programmatically get status using the Queue PSI methods. Its tables and stored procedures are stored in the Project Server 2010 Draft database. The Project and Timesheet queues The Project Server 2010 Queuing System is composed of two separate queues:  Project Queue Primarily used for project-related messages such as Saving.

This gives administrators flexibility in configuration. That is why Timesheet queue jobs are stored in the "Published" database (where all timesheet core data resides) and Project queue jobs are stored in the "Draft" database (where most of the project core data resides). hours worked) is packaged as part of the submitted queue job and put into the SQL Server job store. the polling interval of the timesheet queue can be set to 10 seconds. and the project queue could be set to a slightly higher time interval. Note The polling interval specifies the frequency with which the queuing service checks either of the queues for new jobs. Performance is improved if both these sets of data reside in the same database. Its tables and stored procedures are stored in the Project Server 2010 Published database. The advantages in having two types of queues include:  Performance: Storing queue job data in the same database as the core data saves the queue from making expensive cross-database calls during job processing. if a customer is using Project Server 2010 primarily for timesheets and there are very few projects. Also. and this information is available in the "Published" database. both sets of data are necessary.Queue Management 175  Timesheet Queue Primarily used for timesheet-related messages such as Timesheet Save and Timesheet Submit. . Let us look at an example: When a Timesheet Submit job occurs. the data entered by the user (for example. and so forth). name. Fine-tuning: Every setting in the queue can be specified separately for the Project and Timesheet queues. although other types of messages may be sent to this queue as well. except that their jobs reside in different databases.  How the Project and Timesheet queues are used The following image shows how the modules in the Project Server Queuing System work with the project and timesheet queues. This setting can be specified in the Project Web App Queue Settings page. The two queues are designed the same way. To process the Timesheet Submit job. For example. there is already existing information about a timesheet (duration.

and so on) are stored in the "Draft" database. . 3.176 Project Server 2010 Administrator's Guide 1. Timesheet submit. new job processing threads are created. Job processing: When the "job polling threads" discover new jobs. Both of these threads reside within the "Queue Worker Process" process space and run under the "Queue Worker Process" identity (which is the Service Application Administrator identity). a polling thread pair is launched — one thread to service the project queue. Job Storage: As mentioned above. Queue management is always done on a per-queue basis — in the 2. they do not care which queue the job is part of. Cube Building. another to service the timesheet queue. Start Job Polling threads: For every instance of Project Web App serviced by the queue (the queue can service more than one instance of Project Web App). Status-checking modules will continue to check for status of a job. Note that the job processing threads still reside within the "Queue Worker Process" process space and run under the "Queue Worker Process" identity (which is the Service Application Administrator identity). Publish. the project-related jobs (Project Save. and so on) are stored in the "Published" database. The timesheet-related jobs (Timesheet save. Reporting.

if the Save Project 1 job (job ID 12) fails. If a job is very large (such as saving a 10 MB project) it will be broken into multiple sub-jobs. reporting data synch-up). It then will attempt to process the jobs in sequence since the Project Server internal rules dictates that there is a dependency between the jobs. email notifications. If the Checkin Project 1 job were executed. project publish. Correlated Job Group A correlated job group is a categorization of jobs imposed by internal rules of Project Server. sub-jobs may be noted in ULS logs (depending on the verbosity option that is selected). In the example below. timesheet submit). if any of the jobs in the correlation fail. project save. Project 1 is then checked out by another user. Jobs are the level at which queuing is tracked (using a Job ID). Sub-jobs Each job can be broken down further into smaller segments called sub-jobs. Sub-jobs are not exposed to the PSI or the Project Web App user. Also. 2. who then publishes it. the other jobs after it in the correlation group will be blocked. Jobs within a correlated job group are always processed together and in order (with some exceptions). Project Server assembles a correlation group comprised of the four jobs related to Project 1. For example. Jobs A job is a trackable packet of work that gets executed by Project Server (for example. . However. The dependency that exists is that the Project 1 publish and the Reporting database update cannot occur until Project 1 is saved. Project 1 is edited and saved from Project Professional and then checked in. 3. administrators have to select which queue (project or timesheet) they are changing the settings for. Publishing Project 1 triggers Reporting and a Reporting job is added to the queue as well. Some jobs are not explicitly initiated by the user (for example. Queue groupings There are three distinct levels of grouping for queued data: 1.Queue Management 177 Project Web App Queue Management pages. this would lead to problems because someone else may then checkout Project 1 and then attempt to modify it which may be in an inconsistent state due to the failed save. the Checkin Project 1 job (job ID 13) should get blocked.

. For example. a reporting request for Project 1 will be generated. if a user publishes Project 1. a child job may fail without any effect to the parent job. as well as notification requests regarding Project 1. the Reporting Project 1 job will not be generated. you can do this through the My Queued Jobs page in Project Web App. For example. Administrators can use the Queue Management UI and see all jobs in the queue. If you would like to verify what child jobs were spawned from a parent job that they had entered into the queue as well as their status. Similarly. Note that Notifications for Project 1 will always be generated. he/she may not be aware that a child job may have failed.178 Project Server 2010 Administrator's Guide Parent/Child Relationships between submitted Jobs It is important to realize that parent/child relationships can exist for submitted jobs which require that further processing be done. but since Reporting Project 1 is generated only if the Publish of Project 1 is successful. It is important to note that although the user may be aware that the publish of Project 1 was processed through the queue. if Notification Project 1 should fail. should the publish job fail. there will be no effect on Publish Project 1 since it will have already occurred.

. a project manager may attempt the following in sequence when working with a project: 1. However. Publishes Project 1 3. For example. Job has been skipped because a duplicate job has been found after it within the group. Publishes Project 1 6. Job has been successfully processed. but is not blocking any other jobs in its group. Changes a task in Project 1 4. For optimization. This is a terminating state in which the job can go no further. Job has been blocked by failure of another job before it in the same correlation group. The user will need to retry or cancel. The table below describes each of these states: State Description Getting queued Waiting to be Processed Processing Success Blocked Failed and Not Blocking Correlation Failed and Blocking Correlation Skipped for optimization Job is put into the queue. If the last publish job is processed. Job is being processed. Save Project 1 8. This is a terminating state in which the job can go no further. Job has failed. the first two publish attempts are skipped. Changes the start date of Project 1 7.Queue Management 179 Queuing states When a job is submitted to the queue it can transition through various states. Save Project 1 5. it would produce the same results as if all three publish jobs were processed. Job has failed and may be blocking one or more dependent jobs. A job ID is issued. Publishes Project 1 All three incremental saves to Project 1 will be processed. Job is in the queue and is waiting to be processed. Saves Project 1 2. all three publish attempts do not need to be processed.

State Next Possible State Getting Queued   Waiting to be Processed Cancelled .180 Project Server 2010 Administrator's Guide State Description Cancelled Job has been cancelled. it is important to understand the possible changes in queue state that can occur. Job could not process immediately because of another conflicting job and is temporarily in an inactive mode. The following flowchart describes the possible paths through each state. The job will be retried. Sleeping Changes in queue state As jobs are entered into the queue and processed. Failed and Not Blocking Correlation). A job can be cancelled from any state except the two terminating states (Success.

Queue Management 181 State Next Possible State Waiting to be Processed Processing Success Blocked Failed and Not Blocking Correlation Failed and Blocking Correlation Skipped for Optimization                      Processing Cancelled Blocked Skipped for optimization Success Failed and Not Blocking Correlation Failed and Blocking Correlation Cancelled End Processing Cancelled End Cancelled Processing Blocked (due to a failed job) Cancelled Success Failed and Not Blocking Correlation Failed and Blocking Correlation Processing End Cancelled Queue Administration Settings Queue management and administration can be done through the Project Web App Server Settings page. In the Queue section of the Server Settings page there are two options to administer the queue: .

Manage Queue Jobs The Manage Queue Jobs page allows you to view jobs in the queue through the jobs grid. This is the default setting. You can also retry or cancel jobs through this page.Displays jobs in the queue in order by status. You can use the configuration options to filter jobs and only see the ones you are interested in viewing. Viewable jobs are displayed according to the following filter options  Filter Type  Job History  Job Types  Job Completion States  Columns  Advanced Options Filter Type This configuration option allows you to select filters to query for specific types of jobs that will display in the Job Grid. Queue Settings You can set configuration options that control the way by which jobs are pulled from the Project and Timesheet queues and processed.  You must have the Manage Queue permission in order to access the Queue Administration settings pages. The filters available in the Filter Type drop-down menu are:  By Status.182 Project Server 2010 Administrator's Guide  Manage Queue Jobs You can use this page to view jobs in the queue. . These settings get applied without the need to restart the Queue Service.

You can use the Maximum Number of Jobs field to limit the number of jobs that display for a given date range. If the selected date range contains a huge number of jobs that need to display in the Job Grid. Project Create. Blocked. . Active – Displays all jobs that have a status of Active.Displays all jobs that have a status of Blocked. Job History This configuration option enables you to select the date range of jobs that display in the Job Grid. the load time for the Manage Queue Jobs page can be very long. Timesheet Submit. all job types will be listed in the Selected Jobs list. By default. The default selection is to select the one-day date range for the present date. By Project – Displays jobs in the queue in order by project. By ID – Displays jobs in the queue in order by Job ID.Queue Management 183      My Jobs – Displays only jobs initiated by you. Job Types The Job Types configuration option enables you to select the type of job (for example. The Maximum Number of Jobs field allows you to limit the jobs that display.) that you want to appear in the Job Grid. The default setting is 500. Use the From and To fields to select a beginning and end data. Notifications etc.

all job state types except Success will be listed in the Selected Jobs list. Blocked Due to a Failed Job. By default. You can also select a Job History date range for that corresponds to when shortly before the problems occurred (for example. For example. etc. Success is not available by default because we assume Project Server Administrators would be more interested about problems that can be caused by non-successful jobs rather than successful one. . seven days). The Job Grid should display information about all jobs that are in a nonsuccessful job status that have occurred over the past week. ) of the jobs that you want to appear in the Job Grid. some of your users might be experiencing problems over the past few days. This setting can be helpful for troubleshooting jobs that are not completing successfully in the queue.184 Project Server 2010 Administrator's Guide Job Completion States The Job Completion States configuration option enables you to select the job states (for example. You can see specifically which jobs are not completing successfully by going to the Job Completion States setting and adding all job states except Success. Columns The columns configuration option allows you to select the columns that will appear in the Jobs Grid section. Processing. Success.

If the job continues to remain in this state after rerunning it. the job will remain in the getting queued state. review your ULS logs to troubleshoot why they problem is occurring. When you save a project from Project Profession to the Project Server. the job synchronizes with the server. it means that the queue has been told to start receiving a job that will be processed later. If the synchronization does not complete. If a job remains in the getting queued state for a prolonged period of time. it is likely that something is preventing the job from finishing.  Cancel subsequent jobs in the correlation: When you cancel a job that spawns additional jobs. this option will automatically cancel those jobs as well. This setting is enabled by default. When a job is in this state. . For example. a Project 1 Publish job that is cancelled will also cancel the Project 1 Reporting job that was automatically created. then the job remains in the enqueued state. Until the full job has been received.Queue Management 185 Advanced Options The Advanced Options queue settings both apply to the way that jobs in the queue are cancelled:  Cancel jobs getting enqueued: Selecting this option will cancel all jobs that remain in a ―getting enqueued‖ state for a prolonged period of time. Saving a project from Project Professional to Project Server is a job that typically enqueues. This setting is also enabled by default. but it has not received a tag telling it that all the data for the job has been received.

Queue Settings Queue Settings options allow you to configure the way the queue does operates.  Refresh Status: Allows you to update the jobs in your job grid with the latest status. if applicable:  Retry Job: Allows you to try to rerun selected jobs in the queue that did not complete successfully.  View Related Jobs: Allows you to view jobs that have a dependency relationship (for example. jobs in the same correlation) with a selected job in the queue.  Cancel Job: Allows you to selected jobs in the queue that did not complete successfully. The Queue Settings page contains the following configuration options:            Queue Type Maximum Number of Job Processor Threads Polling Interval (in milliseconds) Retry Interval (in milliseconds) Retry limit SQL retry interval (in milliseconds) SQL retry limit SQL Timeout (in seconds) Cleanup Interval (in hours) Cleanup Interval Offset (in minutes) Cleanup Age Limit for Successful Jobs (in hours) .186 Project Server 2010 Administrator's Guide Jobs Grid The Jobs Grid provides a view the jobs that meet the criteria listed in the Manage Queue Jobs page. Options within this section enable you to select a job or group of jobs and to apply the following options to them.

Queue Management 187     Cleanup Age Limit for Non-Successful Jobs (in hours) Bookkeeping Interval (in milliseconds) Queue Timeout (in minutes) Fast Polling Queue Type The Queue Type setting allows you to select the queue (either Project or Timesheet) to which the settings on the page will apply. . Maximum Number of Job Processor Threads The Maximum Number of Job Processor Threads setting determines how many job processor threads are available for use for the selected queue type (Project or Timesheet).

configuring the settings for two threads per queue is a good starting point. Polling Interval The Polling Interval setting allows you to specify the time interval (in milliseconds) in which the Queue NT Service polls the project or timesheet database (depending what you selected for Job Type) for new jobs. and ULS logs to guide you in fine-tuning the queue to work with your normal server loads. Additionally. You can adjust these settings accordingly based not only on the volume of transactions. application logs. For example. you can monitor performance counters.188 Project Server 2010 Administrator's Guide As a starting point. The valid range is 500 through 300000. suppose you have eight application servers that can process threads and the Maximum Number of Job Processor Threads setting is at ―4‖ (potential for 32 threads all processing jobs). you might be able to use eight threads per queue. with a default value of 1000. we recommend that you set the maximum number of processor threads settings based on the number of available processors (or cores). If your application server uses a quad dual-core processor. if the Project Server application server uses a single dual-core processor. For example. You should also take into account the farm topology and other applications that are running on the farm. The SQL Server may start having contention issues simply because all the threads are operating on the same table. . a setting of ―4‖ gives you the potential for 32 threads to be operating. It is also important to consider the throughput of the SQL Server hosting the Project Server databases. Adjust the setting accordingly if your application server is also serving as a front-end Web server or running search or other processor-intensive activities. publishing 10-line projects versus 1000-line projects). but also the average size of the transactions (for example. For instance. if you have four application servers on the farm and each server has two cores.

such as SQL deadlocks. The Project Server Queuing System polls the databases on a regular basis to retrieve jobs that need processing. Retry Limit The Retry Limit setting allows you to set the limit on retries on a failed polling query. The valid range is 0 (immediate retry) to 300000. .Queue Management 189 Retry Interval The Retry Interval setting allows you to set the length of time (in milliseconds) between retries for jobs that have failed through SQL-related issues. If this query should fail for an SQL-related reason. the system will attempt to poll the database again after a period of time. with a default value of 1000.

the SQL Retry Limit setting allows you to set the number of times the query will be retried. The valid range is 0 (no retries) to 100. The valid range is 0 (immediate retry) to 60000. with a default value of 5. SQL Retry Limit The queue polls the database at regular intervals for jobs that need processing. with a default value of 1000. the SQL Retry Interval setting allows you to set the length of time (in milliseconds) before the query is retried. If the query fails. If the query fails.190 Project Server 2010 Administrator's Guide SQL Retry Interval The queue polls the database at regular intervals for jobs that need processing. .

Cleanup Interval This Cleanup Interval setting allows you to configure the frequency (in hours) with which the Queue Cleanup job runs. . The valid range is 30 to 86400 (one day). with a default value of 1800 (30 minutes).Queue Management 191 SQL Timeout The queue makes SQL calls for retrieving and executing jobs. The valid range is 1 to 100000. For example. the Queue Cleanup job will run every 24 hours. This SQL Timeout setting allows you to set the timeout value (in seconds) for these calls. you can increase the value for this setting and retry the job. If any job fails due to an SQL Timeout error. You can set the time which the Queue Cleanup job will run with the Cleanup Interval Offset setting. if the cleanup interval is set to the default value of ―24‖. with a default value of 24 (one day).

You can configure this setting by entering the value (in hours) in the Cleanup Age Limit for Successful Job field. Use this in conjunction with the Cleanup Interval setting. For example.) to 1439 (11:59 p. you may want to postpone the cleanup to occur a couple of hours after midnight. Cleanup Age Limit for Successful Jobs The Cleanup Age Limit for Successful Jobs setting allows you to configure when a job that has been completed successfully will be removed from the system. The default value is 0. and the Cleanup Interval value is set to ―24‖. the Queue Cleanup job will run daily at 3:00AM. You may want to use the Cleanup Interval Offset to run after the Cube service is scheduled to run.). only if the age of the successfully created job is equal to or greater than that value. The valid range is 0 (12:00 a. if the Cube service starts at midnight. . if the Cleanup Interval Offset value is set to ―180‖.m. In this situation. The value you enter configures the queue to delete the job during the cleanup interval.m. which sets the cleanup to occur at 12:00AM.192 Project Server 2010 Administrator's Guide Cleanup Interval Offset The Cleanup Interval Offset setting determines the time at which the Queue clean up job will run.

Queue Management 193 For example. Cleanup Age for Successful Jobs is usually set to a lower value in comparison to the Cleanup Age Limit for Non-Successful Jobs value. Cleanup Interval Offset is configured to clean up jobs at 12:00AM daily. The value you enter configures the queue to delete the job during the cleanup interval. Therefore. only if the age of the unsuccessful job is equal to or greater than that value. You can configure this setting by entering the value (in hours) in the Cleanup Age Limit for NonSuccessful Job field. you configure the Cleanup Age Limit for Successful Jobs value to be 24 (default value). Note Default Project Server categories cannot be deleted. The Sept 2 12:00AM cleanup will not remove the job since it will only be five minutes old. Note Typically the number of successful jobs in comparison to non-successful jobs is very high. it will not be removed from the system until September 3 at 12:00AM when it will be over 24 hours old. The method in which unsuccessful jobs are removed from the system is identical to the way successfully completed jobs are removed from the system. Cleanup Age Limit for Non-Successful Jobs The Cleanup Age Limit for Non-Successful Jobs setting allows you to configure when a job that has completed in an unsuccessful state will be removed from the system. If you have a publish job that completed successfully on 11:55PM on Sept 1. .

or checking if the Queue Cleanup job needs to be run. Bookkeeping Interval There are a number of "bookkeeping" tasks that are run by the Queuing System. Since job status information is important in helping to troubleshoot problems when a job has not completed successfully. updating the heartbeat timestamp. with a default value of 10000 (ten seconds). The default value of this setting is 168 hours (7 days). these include awakening jobs in a "sleeping" state. it is recommended to not set this value to less than the default setting. The valid range is 500 to 300000. . For example. The Bookkeeping Interval setting controls the time interval (in milliseconds) at which these tasks are run.194 Project Server 2010 Administrator's Guide Note Jobs that are in an ―Unsuccessful and blocking correlation‖ state will stay in the history until they are successfully retried or cancelled. The cleanup for non-successful jobs does not affect jobs in this state.

jobs are automatically distributed the remaining Application servers on which the Queuing service is active. The heartbeat is updated by the Queue in all the Project Web App databases that it touches (for example. Note Default Project Server categories cannot be deleted. If the Queue Timeout value will automatically be changed to four times the Bookkeeping value if the rule is violated. each time the Published and Draft databases are polled for jobs). A Queue Service is considered to have timed out if it has not updated its heartbeat for longer than the Queue Timeout value (in minutes).Queue Management 195 Queue Timeout In a farm containing multiple Application servers. The valid range is 2 to 20. Note The Queue Timeout value cannot be less than four times the Bookkeeping Interval at any time. with a default value of 3. if the Queue Service fails on one of the servers. .

this setting can be disabled. . If there are. the Queue will not wait for the polling interval if there are pending jobs. if this fast processing overwhelms the server and the Queue needs to slow down. It will then wait for the polling interval.196 Project Server 2010 Administrator's Guide Fast Polling The Fast Polling setting is enabled by default and allows the Queue to process all jobs in a Waiting to be Processed state to be processed as soon as possible. If Fast Polling is disabled. the free threads will be loaded with jobs in a Waiting to be Processed state. the Queue will check if there are any free threads to process jobs. and repeat the process. If Fast Polling is enabled. all pending jobs will start getting processed immediately. However. As jobs get processed.

Operational Policies Management 197 7 Operational Policies Management This chapter about Operational Policies Management contains the following sections:  Alerts and Reminders  Additional Server Settings  Server-Side Event Handlers  Active Directory Resource Pool Synchronization  Project Sites  Project Site Provisioning Settings  Bulk Update Project Sites Alerts and Reminders .

you had to remove the SMTP server details to stop notifications and reminders from being sent. On the Alerts and Reminders page. overdue. 2. in the Notification E-mail Settings section.198 Project Server 2010 Administrator's Guide Project Server 2010 generates e-mail notifications and reminders for each user whenever new. To configure the Notification E-mail setting: 1. It also allows you to specify the SMTP server and associated port number. rejected. or forthcoming events occur. In the SMTP mail server box. but turn off notifications globally. Select Turn on notifications with the following settings check box to maintain all of your Notification email settings. As a Project Web App administrator. you can configure the following settings in the Alerts and Reminders page:  Notification E-mail Settings  Schedule E-mail Reminder Service Notification E-mail Settings The Notification E-mail Settings allows the Project Server Administrator to maintain the default sender e-mail address and message information that is automatically included with each email notification or reminder sent by Project Server. Verify the port number in the Port box. enter the following information: a. type the name of your SMTP server. Before e-mail notifications and reminders can be used by members of your organization. Administrators can configure alerts for their reminders from the Alerts and Reminders page in the Additional Settings page of your Project Web App Server Settings. b. On the Server Settings page. Note This setting was not available in Project Server 2007. in the Operational Policies page. the appropriate server and account information must be identified. click Alerts and Reminders. In Office Project Server 2007. .

On the Server Settings page. 3. In the From address box. This address is the reply-to address for all notification and reminder e-mails. enter the default email address. in the Schedule E-Mail Reminder Service section. in the Operational Policies page. For example: This email message may contain confidential information and is intended only for the recipients named above. Click Save. In the E-mail foot box. d. Click Save. 2. type the default message you want appended to all notification emails. 3. you should consider setting the service to run at a time when the overall load on the server is low. e. click Alerts and Reminders. Schedule E-Mail Reminder Service The Schedule E-mail Reminder Service allows a Project Server Administrator to set the time of day at which the e-mail reminder service scans the Project Server databases to determine who should receive e-mail reminders (users with upcoming or overdue tasks and status reports). click the Schedule e-mail reminder service to run every day at drop-down menu and select the time at which you want the service to run. In the Company domain box. Additional Server Settings The Alerts and Reminders page allows you to configure settings for:  Project 2007 Compatibility Mode  Project Professional Versions  Enterprise Settings . On the Alerts and Reminders page. Contoso. To configure the Schedule E-mail Reminder service: 1. enter the domain name of your company (for example.com).Operational Policies Management 199 c. Depending on the volume of notification and reminder e-mails.

200 Project Server 2010 Administrator's Guide      Currency Settings Resource Capacity Settings Resource Plan Work Day Exchange Server Details Task Mode Settings Project 2007 Compatibility Mode The Project 2007 Compatibility Mode setting allows an upgraded Project Server 2010 instance to accept client connections from Project Professional 2007 with Service Pack 2 (SP2) as well as Project Professional 2010. but it can also accept connections from Microsoft Office Project Professional 2007 with Service Pack 2 (SP2) if BCM is enabled in Project Server 2010. and in batches (running in a mixed environment). Backward compatibility mode (BCM) is a feature in Project Server 2010 that assists in the upgrade of your Enterprise Project Management environment. Because Project Server 2010 accepts connections from both Office Project Professional 2007 SP2 and Project Professional 2010 clients when BCM is enabled. BCM is enabled automatically after you upgrade to Project Server 2010. even if BCM in enabled. Project Server 2010 accepts connections from the Microsoft Project Professional 2010 client. if you want. BCM allows you to avoid having to upgrade your Office Project Professional 2007 client computers at the same time. When you have finished upgrading the clients to Project . This feature in Project Server 2010 is also referred to as Backward Compatibility Mode (BCM). This setting is only configurable if your deployment has been upgraded from Office Project Server 2007 (it is enabled by default after the upgrade). After you upgrade to Project Server 2010 (by either the in-place or database-attach upgrade method). Note Project Server 2010 will not accept connections from Project Professional 2003. you can decide to upgrade your clients later.

only Project Professional 2010 clients are able to connect to Project Server 2010. Font strikethrough is not available. but not to Office Project Professional 2007 SP2 users. For example. become available in Native mode. Timeline. All new features that are available in Project Professional 2010 (for example. Additionally. your cross-project links do not fully function until all of the related projects are opened and saved so that they are all in Project 2010 format. Project Server 2010 does not allow you to create or even connect projects that are in different modes. 32-bit colors) are available to Project Professional 2010 users. Verify that you want to disable BCM if you are going to make the change. In Native mode. Office Project Professional 2007 SP2 connecting to Project Server 2010 in BCM mode is blocked from providing functionality that requires loading a Microsoft Project Web App page in the client. projects that have not been opened and saved remain in Compatibility mode. However. you cannot create a cross-project link from a project that is in Compatibility mode (Office Project 2007 format) with one that is in the Native mode (Project 2010 format).Operational Policies Management 201 Professional 2010. Project Professional 2010 clients that connect with Project Server 2010 have certain features that are disabled. as you open and save projects. As a workaround. However. Important Once the Project 2007 Compatibility Mode is disabled. Team Planner. you can turn off BCM in Project Server 2010 server settings. When Project Server 2010 is configured in backward compatibility mode. These include the following:     Manually scheduled tasks are not available on the server or client. What this means is that after you disable backward compatibility mode. Project Professional 2010 features that were not available in BCM (such as manually scheduled tasks). which then allows for only Project Professional 2010 connections. Therefore. it cannot be re-enabled. and master/subproject) on mixed Project file versions. We recommend that BCM be enabled only as a temporary measure to help in the upgrade process. Tasks cannot be set to inactive. workflow-controlled custom fields are not available in Office Project Professional 2007 SP2. This includes doing approvals and opening enterprise resources. When BCM is disabled in Project Server 2010. you can use Project Web App on a Web browser to do these functions until you are ready to upgrade to Project Professional 2010. they are converted to Native mode. Project Server is running in Native mode. . All departmental custom fields are enforced in Office Project Professional 2007. crossproject dependencies. Project Server 2010 prevents you from creating cross-project type links (resource sharing.

Important The Enterprise Global file must be upgraded to the Project Professional 2010 client after BCM is disabled (step 5 in the procedure above). After making the change. All . clear the Enable Project 2007 Compatibility Mode check box. dragging the splitter bar on the screen). 2. 3. You can verify this by On the Server Settings page. This is required to upgrade the Enterprise Global file to the newer version of the Microsoft Project Professional client. and then check it back in. in the Project 2007 Compatibility Mode section. For example. On the Additional Settings page.202 Project Server 2010 Administrator's Guide To disable Project 2007 Compatibility Mode (Backward Compatibility Mode): 1. In the Enterprise Global file. Project Professional Versions The Project Professional Versions setting allows you to specify which versions (build numbers) of Project Professional client will be able to connect to your Project Server 2010 environment.0. Objects in the file (for example. you must check out and open the Enterprise Global file in Microsoft Project Professional 2010. (All new projects are based on the Enterprise Global file).5128. tables. This step ensures that all new projects are in native mode with all Project Professional 2010 features enabled. in the Operational Policies page. if you recently updated both Project Server 2010 and Project Professional 2010 to the October 2010 Cumulative Update. you can verify that all clients connecting to the server are at least at this level by entering the build number (14.5000). This setting allows you to ensure that Project Professional client connections to the server are all at a required base level. views. Neglecting to upgrade the Enterprise Global file with the Microsoft Project Professional client can lead to serious problems. Click OK. make a very minor change (for example. click Additional Server Settings. Verify that all projects are checked in to Project Server 2010. filters) will remain in Office Project 2007 format and they will be expected to be in Project 2010 format when new projects are created. save the file. 5. 4.

BCM is enabled and you only want the following two builds (and higher) to connect to Project Server 2010:   Project Professional 2007 with Service Pack 3 (SP3) Project Professional 2010 with the December 2010 Cumulative update In the above example. type the build number of each Project Professional version that you want to connect to Project Server 2010. in the Project Professional Versions section. in the Operational Policies section. Check with your Project Management Office to see if your organization prohibits the use of master projects. 2.Operational Policies Management 203 Project Professional 2010 clients that have not been updated to the October 2010 Cumulative Update or later will not be able to connect. you do not need to make any additional changes to this setting to allow Project Professional 2007 SP 2 clients to connect to the server. To configure the Project Professional Versioning Settings: 1. Enterprise Settings The Enterprise Settings setting allows you to determine whether or not Project Server 2010 allows projects to have the following capabilities:  Allow master projects to be saved and published to Microsoft Project Server 2010 (enabled by default) – Enabling this setting allows master projects to be used in Project Server 2010. Click Save. click Additional Server Settings. you can enter a build number for the Office Project Server 2007 client if you require a minimum build. 3. Master projects are projects that contain sub-projects. and usually contain tasks that are dependent on each other. Versions older than the build number you enter will not be able to connect. However. On the Server Settings page. For example. Note If Backward Compatibility Mode (BCM) is enabled. Allow projects to use local base calendars – Enabling this settings allows users to not only use enterprise base calendars that are on the system for their enterprise  . for the Project Professional Versions setting you would enter the build number for each version. separated by a comma. On the Additional Server Settings page.

but to also use base calendars local base calendars that your users create. The currency used will be the one selected as the default server currency. Select Allow projects to use local base calendars if you want to enable this setting (cleared by default). Click Save. July 4th as a working day versus a holiday) can lead to faulty calculations and other issues. click Additional Server Settings. in the Operational Policies section.204 Project Server 2010 Administrator's Guide projects. The default value will be based on the default currency of the language used for the Project Web App instance.  . a project using a local base calendar that differs from an enterprise calendar (for example. To configure the Enterprise Settings: 1. Select Allow master projects to be saved and published to Microsoft Project Server 2010 if you to enable this setting (enabled by default). 2. On the Additional Server Settings page. Restricting your users to use only enterprise calendars gives you more control by preventing problems that can occur when projects use local base calendars that contain conflicting data. Disabling this setting (default) will restrict users to using only enterprise base calendars that are on the system for their projects. Enforce that projects are published in the server currency – Select this option if your company only uses a single currency for costs within projects. in the Enterprise settings section: a. 3. You can also select the currency settings for publishing:  Allow projects to be published in various currencies – Select this option if your company uses multiple currencies for costs within projects (this is the default setting). Currency Settings Through the currency setting you can select the default currency setting for projects that are published to the server (used for reports and the default view for new projects). For example. On the Server Settings page. b.

2. 5. All projects that are not using the default server currency must be changed to the default currency and republished.Operational Policies Management 205  To configure the Currency settings: 1. in the Currency Settings section. On the Server Settings page. select one of the following currency options:  Allow projects to be published in various currencies (default). You will see the following message box if you selected Enforce that projects are published in the server currency: This message box warns you that the change will only be enforced on all subsequent projects that are published to the server. 4. in the Operational Policies section. On the Additional Server Settings page. click Additional Server Settings. .  Enforce that projects are published in the server currency 3. Click OK. Click Save. All projects published to the server that are using a currency that is in conflict with the server currency will be displayed in the Currency Settings section: You can use this as a reference to note which projects need to have their currency changed to the server currency.

On the Project Options page. select the Currency that you want to use for this project. 2. 5. Click File. Click File. 7. Click File. To change the currency for a project in Project Professional 2010: 1. and months in the future – using the . Resource Capacity Settings The Resource Capacity Settings are used to calculate your resources availability for work over a specified time range. Click OK. Check out and open a project from Project Server 2010. You can use this procedure to:   Select the currency for a specific project if the currency setting allows you to use multiple currencies. 4.206 Project Server 2010 Administrator's Guide Change currency option for a project Use the following procedure in Project Professional 2010 to change the currency settings for a project. Change the currency setting on a project to the server currency if the currency setting allows you to only use the server currency. and is updated daily through a timer job which is run at a time you specify in the settings. and then click Publish to publish the project. 3. 6. On the Display page.months in the past. and then click Options. Open Project Professional 2010 and log on to Project Server 2010. click Display. and then click Save to save the project. 8. You are able to set the Active capacity view by entering a time range in relative terms . Your resources capacity data for the specified time range is stored on the Reporting database. in the Currency options for this project section.

The default Active capacity view settings are ―1‖ month behind and ―12‖ months ahead. Note that increasing either value will also increase the amount of time it will take for the daily timer job to run. you can view a resources future availability for up to 12 months from the current date. to account for any users who might report time long after work in completed). On the Additional Server Settings page. This means that when you view the data in the Reporting database. 2. c. you will get more capacity computed for future periods. To configure the Resource Capacity setting: 1. Some customers might want to increase the months behind value if they want to get an accurate report of work completed in the past (for example. In the Months ahead field. enter the time at which you would like latest resource capacity information to be processed (the default value is 1:00 AM). . In the Months behind field. 3. By increasing the Month Ahead setting. a company is planning for new projects later in the year and wants to forecast the capacity for resources from 12 months to 24 months. On the Server Settings page. The data from the timer job is stored on the Reporting database on a day-to-day basis. for Active capacity view. You can use the Resource Capacity report or create a custom report to view this data from the Reporting database. as well as utilization over the last month. in the Resource Capacity Settings section. enter the following: a. and can be configured to run at a specific time through the ―Scheduled Time‖ setting. For Scheduled time. enter the number of months in the past that you want resource data to be calculated from. b. The default value for the Scheduled Time setting is 1:00 AM. For example. in the Operational Policies section. click Additional Server Settings.Operational Policies Management 207 current date as a relative date point. Click Save. enter the number of months in the future that you want resource data to be calculated from.

users could view their tasks in Microsoft Outlook with the use of an Outlook Add-in that had to be downloaded and installed to each user’s computer. or can be manually entered in as a value. b. To configure the Resource Plan Work Day setting: 1. On the Server Settings page. In Project Server 2010. This is the default option. Note that this value will be used for all resources in the resource plan. in the Resource Plan Work Day section. This value can be calculated from either the resource’s base calendar. Click Save. Hours per day – Use this option if you want to specify the full-time equivalents for your resources in the resource plan. Exchange Server Details In Office Project Server 2007. On the Additional Server Settings page. enter the value (in hours) of the standard work day you would like to use for your organization.208 Project Server 2010 Administrator's Guide Resource Plan Work Day The Resource Plan Work Day setting allows you to specify the length of a work day (fulltime equivalents or FTE) for all resources in your resource plan. in the Operational Policies section. click Additional Server Settings. select one of the two options: a. 3. For more information about how to configure task integration with Exchange Server. see the . 2. After selecting this option. Exchange Server can be integrated with Project Server 2010 to provide task synchronization with Outlook 2007 or Outlook 2010. Resource base calendars – Use this option if you want the full-time equivalents to be calculated from each resources base calendar. for Calculate resource full-time equivalent from.

On the Server Settings page. click Additional Server Settings.aspx). see the MSDN article ―Project 2010: Introducing User-Controlled Scheduling‖ (http://blogs. It can be useful for scheduling tasks with hard dates that are difficult to move (for example.microsoft.aspx). Click Save. To configure the Exchange Server Details setting: 1. On the Server Settings page. when a new task is created it ignores the scheduling engine and creates the task without a duration. To configure the Task Mode setting: 1. When a new project is using the manually scheduled task mode. Task Mode Settings The Task Mode Settings allow you to select the default mode in which tasks are scheduled (manually or automatically). in the Operational Policies section.com/b/project/archive/2009/10/23/project-2010-introducing-usercontrolled-scheduling.msdn. click Synchronize Tasks if you want to automatically synchronize tasks from Project Server 2010 with Outlook 2007 or Outlook 2010. 3. On the Additional Server Settings page. Additionally. 2. training). start date. if you select the default setting (Manually Scheduled). or finished date (can be entered manually).Operational Policies Management 209 TechNet article set ―Deploy Project Server 2010 with Exchange Server‖ (http://technet. in the Exchange Server Details section. . you can also configure if you want task to be published to team members. in the Operational Policies section. Manually scheduled tasks (also referred to as ―User-Controlled Scheduling‖) is a new feature available in Project Server 2010. click Additional Server Settings.com/en-us/library/ff793353. For more information about the Manually Scheduled task feature.

Select Users can override the default selection in Project Professional (enabled by default) if you want to allow your Project Professional users to override your default task mode settings you selected. Select Manually Scheduled tasks can be published to team members (enabled by default) if you want to allows project managers to publish their manually scheduled task to team members.microsoft. see the MSDN article ―How to Write and Debug a Project Server Event Handler‖ (http://msdn. Through the Server Side Event Handlers page.12). and finish dates for your tasks. data processing.210 Project Server 2010 Administrator's Guide 2. Click Save. In the Task Mode Settings section: a.aspx) For more information about Project Server Event Handlers. select one of the two following settings:   c. validation.aspx).microsoft. developers in your organization can create an event handler that starts a custom workflow. For Default task mode in new projects. For more information about Project Server Events. and finish dates for your tasks. b. Project Server 2010 provides public events that enable development of custom processes such as adding and enforcing business rules. These custom processes are written as server side event handlers by developers in an organization and can be associated to Project Server 2010 events through the Server Side Event Handlers page in Project Web App Server Settings. Server Side Event Handlers Similar to Office Project Server 2007. Manually Scheduled – You need to enter duration. you can associate that event handler with the Project Published event so that a workflow starts whenever the event occurs. and workflow. This is selected by default. Automatically Scheduled: Scheduling engine will automatically calculate durations.com/enus/library/ms469450(office. .com/en-us/library/ms481079(v=office.12). notification services. see the MSDN article ―Project Server Events‖ (http://msdn. 3. For example. start. start.

Any event handlers that are currently associated with the event will display in the Event Handlers list. c. In the Class Name field. 3. in the Assembly Name field. enter the following information for the event handler you want to associate with the selected event: a. b. 4. In the New Event Handler page. You can also optionally enter a description of the Event Handler.Operational Policies Management 211 To associate an event handler with a server side event: 1. enter the fully qualified name of the class the implements the event handler functionality. in Events list. On the Server Settings page. In the System Information section. the Event Source and Event Name should populate with the Event you selected. click Server Side Event Handlers. enter the Event Handler name. enter the full name of the strongly named event handler assembly. In the Display Information section. On the Server Side Event Handlers page. In the Event Handlers section. 2. . Click New Event Handler. and then click the Event Source listed next to the Event Name (for example. in the Operational Policies section. click the Project Event Source for the Published Event Name). find the event that you want to associate your new event with.

contain nested groups whose members are also synchronized. For example. Click Save. Conversely. If there are multiple event handlers associated with the event. 5. employees who are removed from the Active Directory group have their Project Server accounts deactivated upon synchronization. The Enterprise Resource Pool can be mapped to a single Active Directory group for synchronization. provide the order number of the event handler. Enterprise Resource Pool synchronization also updates enterprise resource properties with the most current data from Active Directory. Project Server enterprise resources can also be automatically activated and deactivated based on group membership in the Active Directory directory service. however. For example. enter ―1‖. Active Directory Resource Pool Synchronization Project Server 2010 Active Directory Enterprise Resource Pool synchronization is used to create or update multiple Project Server enterprise resources at once. an employee's name and e-mail address may change due to marriage. new employees in your department can automatically be added as Project Server enterprise resources as long as they are in the Active Directory group selected for synchronization. the change occurs in the user’s Enterprise Resource properties when synchronization occurs. An active Project Server resource/user account can be deactivated. If it is the only event handler associated with the event. As long as the change is made in Active Directory and the user is in the linked group. In the Order field. . The following actions can occur during the Enterprise Resource Pool synchronization process:   A new Project Server enterprise resource and corresponding user account can be created based on an Active Directory account. enter the order number in which this event handler will be executed.212 Project Server 2010 Administrator's Guide d. This Active Directory group can.

but does not exist in Active Directory or is not a member of the Active Directory group mapped to the Enterprise Resource Pool. confirm that:   To configure Enterprise Resource Pool synchronization Use this procedure to configure Enterprise Resource Pool synchronization in Project Server 2010. the corresponding Project Server user account status is set to inactive. The user exists in Project Server as an enterprise resource and a user. Before you perform this procedure. name. The user exists in Project Server. You can verify this account in the SA's properties on the Service Application Administration page on the SharePoint Central Administration Web site. The user does not exist in Project Server. e-mail address.Operational Policies Management 213   An existing Project Server user account’s metadata (for example. The Service Application (SA) service account for the Project Server instance has Read access to all Active Directory groups and user accounts involved in the synchronization. Otherwise the account will stay active. and so on) can be updated if it has changed in Active Directory. If Prevent Active Directory synchronization for this user is not enabled for the user account in Project Server. The user exists in Active Directory and is a Action A new corresponding Project Server user and enterprise resource is created in Project Server and added to the Team Members Project Server security group. A previously inactive Project Server resource/user account can be reactivated. The corresponding Project Server enterprise resource and user information is updated (if applicable). You have access to Project Server through Project Web App with an account with the Manage Active Directory Settings and the Manage users and groups global settings. The user exists in Active Directory and is a member of the Active Directory group mapped to the Enterprise Resource Pool. If the Automatically reactivate currently . The user's information has been updated in Active Directory. The following table describes possible scenarios and corresponding actions that occur when Enterprise Resource Pool synchronization takes place: Scenario The user exists in Active Directory and is a member of the Active Directory group mapped to the Enterprise Resource Pool.

click Find Group. click Active 2.com). but as an inactive account. Click the button next to the field to search the Active Directory forest based on your search criteria. On the Active Directory Enterprise Resource Pool Synchronization page. On the Find Group in Active Directory — Webpage Dialog page. Note The Active Directory forest that is searched is shown at the top of the Find Group in Active Directory — Webpage Dialog page. . To select a group from a remote forest. enter all or part of the name of the Active Directory group which you want to synchronize with the Enterprise Resource Pool. the account is reactivated. The user exists in Project Server. in the Active Directory Group section. On the Server Settings page. in the Group Name field. type the fully qualified domain name of the group (for example. You can synchronize to a security or distribution group of any scope (Local. Directory Resource Pool Synchronization. in the Operational Policies section. Global.214 Project Server 2010 Administrator's Guide Scenario member of the Active Directory group mapped to the Enterprise Resource Pool. group@corp. or Universal). 4. the account remains inactive in Project Server. Action inactive users if found in Active Directory during synchronization resource option is selected in Project Server. If the option is not selected. under Active Directory Group to Synchronize. 3. The forest is defined by the fully qualified domain name of the account for the Shared Services Provider on which the Project Server instance is running.contoso. Configure Enterprise Resource Pool synchronization 1.

8. This includes all users who are members of nested active directory groups across domains and forests. In the Frequency fields. weeks. select the group with which you want to synchronize your Enterprise Resource Pool. Alternatively. select Schedule Synchronization. 6. the Active Directory group membership of the selected group is put into memory. 7. When you do so. On the Active Directory Enterprise Resource Pool Synchronization page. define the frequency at which you want synchronization to occur between the Enterprise Resource Pool and the Active Directory group. This can be scheduled over a defined period of days. Click OK. in the Scheduling Options section. . or months. you can choose to manually run Active Directory Enterprise Resource Pool synchronization. skip the following step and continue to step 8. you should see the Active Directory group you selected next to Active Directory Group to Synchronize: in the Active Directory Group section. From the Group Name list.Operational Policies Management 215 5. If you want to configure synchronization to occur on a scheduled basis. If you prefer the manual option. Select a start date and time.

The Project Sites page in Server Settings allows you to manage Project Sites for your projects in Project Server 2010. Click Save and Synchronize Now if you want to synchronize your Enterprise Resource Pool immediately. Click Save to save the settings. enabling this option would ensure that if an employee were rehired. you can rerun it manually when needed by returning to this page and clicking Save and Synchronize Now. select Automatically reactivate currently inactive users if found in Active Directory during synchronization. 10. To do so. (For example.216 Project Server 2010 Administrator's Guide 9. If you choose not to schedule Enterprise Resource Pool synchronization. You can do the following through the Project Sites page:  Create a new Project Site  Edit a Project Site Address  Synchronize  Delete a Project Site  Go to Project Site Settings . You can enable inactive accounts to be reactivated if they are found in the Active Directory group during synchronization. Project Sites Project Sites were referred to as Project Workspaces in previous versions of Project Server. It contains information such as when the last successful synchronization occurred. in the Resource Option section. You can check the status of the Enterprise Resource Pool synchronization by returning to the Active Directory Enterprise Resource Pool Synchronization page and reviewing the information in the Synchronization Status section. the employee's user account would be reactivated). 11.

To create a Project site for a project: 1. 2. On the Server Settings page. in the Operational Policies section. From the Project Name list. select a project for which you want to create the project site. Click Create Site. click Project Sites. . All projects without project sites will not have a corresponding URL next to it in the Site Address column. You can view the Project Sites list to determine if a project does not have an existing Project. 3.Operational Policies Management 217 Create Site The Create Site setting allows you to create a new Project Site for your project if you did not originally create one when the project was originally published to Project Server 2010. 4. The Create Project Site message box appears.

Changing the site address information breaks the existing link between the project and the existing Project Site. 5. Note Before changing the Project Site URL for a project. Edit Site Address The Edit Site Address setting allows you to edit the destination URL for a project site to point to a new site address. You can edit the Site URL information if needed. The project site you created will now display next to the project name you selected in step 2.218 Project Server 2010 Administrator's Guide In the Web Application list. To edit a site address for a Project site: 1. verify the site URL for the project site. select a project for which you want to edit the Project site information. In the Site Application field. From the Project Name list. The Edit Site Address dialog box appears. in the Operational Policies section. You can then enter the information to the new Project Site. . select the Web Application you want for the Project Site. 2. click Project Sites. 7. 6. 3. be sure to provision a new Project Site with a new site template. On the Server Settings page. The site URL will be appended to the Web Application to provide you with the Destination URL (as seen in the Destination URL field). 4. Click Edit Site Address. Click OK.

permissions. Note To view a confirmation that Synchronization occurred. On the Server Settings page. Click Synchronize. 6. Change the project site URL information to the new URL. 2. and other Project Server-related information between Project Server 2010 and the Web Server that is running SharePoint Foundation. you can go to the Manage Queue Job Server Settings and verify that the synchronization job completed successfully. Synchronize The Synchronize button allows you to manually synchronize the Project Site’s users. . in the Operational Policies section. From the Project Name list. 3. select a project for which you want to synchronize your Project site information between Project Server 2010 and SharePoint Foundation. Click Test URL to verify if the new project site URL can be opened. If you want to automatically run synchronization for your Project Sites.Operational Policies Management 219 Type a new SharePoint site URL will be selected by default. Click OK. To synchronize your Project Site information between Project Server and SharePoint Foundation Server: 1. see the Project Site Provisioning Settings Automatic Provisioning setting. 5. click Project Sites. 7. The project site URL for the project you selected in step 2 will be changed to the new URL.

Click Cancel if you no longer want to delete the site. Important Verify that you truly want to permanently remove a site and its content before you proceed with this procedure. customize the site’s look and feel. add Web Parts to the site. the Project Site will be deleted and will no longer display next to the project it was associated with in the Project Sites page. From the Site Settings page. 5. and many others. 3. 4. Click Delete Site. click Project Sites. you can make changes to the site. Go to Project Site Settings The Go to Project Site Settings setting allows you to go directly to a Project Site’s site settings page. in the Operational Policies section. Deleted Project Sites are not recoverable. On the Server Settings page. If you clicked OK. From the Project Name list.220 Project Server 2010 Administrator's Guide Delete Site The Delete Site setting allows you to permanently remove a Project Site and its content. To delete a Project site: 1. It will also warn you that Click OK to proceed with deleting the site. such as add or remove users to the site. select a project for which you want to delete a Project Site. . 2. A message box appears that will ask you to confirm if you want to delete the Project Site.

You can make changes to the Project Sites site settings from this page. click Project Sites. You can configure the following settings:  Site URL  Default Site Properties  Automatic Provisioning  Project Site Permissions . The Site Settings page for the selected Project Site will open. From the Project Name list. Project Site Provisioning Settings The Project Site Provisioning Settings page allows you to configure settings for the Project Sites that are created for projects. 3. in the Operational Policies section.Operational Policies Management 221 To go to the Site Settings page for a Project site: 1. 4. select a project for which you want to view the Project Site settings page. Click Go to Project Site Settings. On the Server Settings page. 2.

On the Server Settings page. 5. in the Operational Policies section. On the Project Web App Home page.222 Project Server 2010 Administrator's Guide Site URL The Site URL settings allow you to change the default Web application in which your Project Sites are created. 2. or a template that is derived from it. type the URL path (for example. When selecting a Project Site template. In the Site URL field. in the Site URL section. you can only use the ―Microsoft Project Site‖ template that installs with Project Server 2010. To specify Site URL information: 1. The . Click Save. click Server Settings. click Project Site Provisioning Settings. On the Project Site Provisioning Settings page. The default Site URL information on this page is based on the information provided during the provision of the Project Web App instance. 3. PWA). select the Web application you want to be the default Web Application that your Project Sites will be created in from the Default Web application drop-down menu. Default Site Properties The Default Site Properties settings allow you select the default site template language and the default Project Site template that will be used to create your Project Sites. 4.

if desired. the settings can be configured to allow the Project Server Administrator to create Project Sites manually after projects have been published. On the Server Settings page. 4. In the Default Project Site template drop-down menu. Click Save. select the Project Site template that will be used to create your Project Sites. Alternatively. 3. in the Operational Policies section.com/b/brismith/archive/2010/12/06/project-server-2010-the-fab-40-strikeagain. in the Default Site Properties section. . click Project Site Provisioning Settings. Automatic Provisioning The Automatic Provisioning setting allows you to indicate whether you want to have Project Server 2010 create Project Sites for projects when the projects are newly published to the server.aspx). see Project Server 2010 –The Fab 40 Strikes Again! on the Microsoft Project Support Weblog (http://blogs. Note If you have a group of Project Managers who will not need to create Project sites. To configure default site properties for your Project Sites: 1. On the Project Site Provisioning Settings page. denying this group of users the ―Manage SharePoint Foundation‖ global permission will eliminate the display of a Publish Project Site dialog box that typically displays whenever a project is created.Operational Policies Management 223 Microsoft Project Site template is built to supports features and functionality in SharePoint Server 2010. Important Project Server 2010 and Office Project Server 2007 do not support the use of the Project Tracking Workspace template from the SharePoint Server 2010 ―Fab 40‖ templates to create project sites.msdn. For more details. select the default language for your Project Sites from the Default site template language drop-down menu. 2. you can set the provision mode to Allow users to manually crate project sites in Project Server as noted above. Additionally.

click Project Site Provisioning Settings.224 Project Server 2010 Administrator's Guide To configure the Automatic Provisioning setting: 1.   . under Provisioning Mode select one of the two options:  Automatically create a project site for each project when first published to Project Server  Allow users to manually create project sites in Project Server 3. Click Save. On the Project Site Provisioning Settings page. Team members with assignments in a project are added to the Team Members (Microsoft Project Server) site group. the following occur automatically when any of the circumstances above occur:  Project managers who have published a project or who have Save Project permissions on a project are added to the Project Managers (Microsoft Project Server) site group. This setting allows you to automatically synchronize Project Web App users with Project Sites over the following circumstances:    When Project Sites are created When project managers publish projects When user permissions change in Project Server 2010 When the Project Site Permissions setting is enabled. 2. Project Site Permissions The Project Site Permissions setting allows you to specify access is granted to Project sites in Project Server 2010. On the Server Settings page. in the Automatic Provisioning section. Other Project Server users who have View Project Site permission on a project are added to the Readers (Microsoft Project Server) site group. in the Operational Policies section.

It allows you to break the original links between Project and their corresponding Project Sites in one site collection. 4. click Server Settings. When the check box is cleared. click the Synchronize button on the Project Sites page of the Operational Policies section of Project Web App Server Settings. click Project Site Provisioning Settings. in the Operational Policies section. when migrating). 2. On the Project Web App Home page. in Project Site Permissions section.Operational Policies Management 225 To enable the Project Site Permissions setting: 1. and then relinking to the new Project Sites in the new site collection. On the Server Settings page. On the Project Site Provisioning Settings page. and when user permissions change in Project Server. users are not automatically added to their respective Web sites. Bulk Update Project Sites The Bulk Update Project Sites page allows you to change site path information for Project Sites in one Web application to a different one (for example. click Check to automatically synchronize Project Web App users with Project Sites when they are created. 3.  Update Site Paths  Update Content Types  Project Site Permissions . Project Server users are never synchronized with Project Sites. when project managers publish projects. To add or update users to their sites. Click Save. When the check box is cleared.

in the Update Site Paths section.  In the Site URL field. . in the Operational Policies section. On the Bulk Update Project Sites page.contoso. PWA). http://hr1.226 Project Server 2010 Administrator's Guide Update Site Paths The Update Site Paths setting allows you break links between projects and Project Sites contained in one site collection and relink with the new Project Sites in a different site collection. On the Server Settings page. Click Save.com). type the site URL information (for example. 2. the Web Application you need to select may display as a GUID.  In the Site URL field. click Bulk Update Project Sites. 3. for Previous Site Paths:  Select the Web Application for your Project Sites that you want to break the link to. If you are migrating projects sites from a different server. type the site URL information (for example. To update Project Site paths to a new site collection: 1. 4. the Web Application you need to select may display as a URL. If you are migrating project sites on the same server. PWA). In the New Site Paths:  Select the Web Application that contains the Project Sites that you want to link to (for example.

in the Project Site Permissions section. click Synchronize site permissions. Click Save.Operational Policies Management 227 Update Content Types The Update Content Types setting allows you to ensure that when migrating content from one farm to another. On the Bulk Update Project Sites page. Note For the Project Site Permissions site permissions setting to be enabled. click Bulk Update Project Sites. 2. in the Operational Policies section. that the content types of Project Issues. On the Server Settings page. and Documents are updated in the new location so that item links will remain functional. 3. click Update Content Types. On the Server Settings page. 3. Risks. in the Operational Policies section. click Bulk Update Project Sites. the Project Site Permissions setting must also be enabled on the Project Site Provisioning page. To enable the Synchronize Site Permissions setting: 1. This allows users to immediately access their Project Sites. To enable the Update Content Types setting: 1. 2. . in the Update Content Types section. On the Bulk Update Project Sites page. Project Site Permissions The Project Site Permissions setting allows you to synchronize permissions to the Project Sites while updating the site paths. Click Save.

228 Project Server 2010 Administrator's Guide 8 Workflow and Project Detail Pages This chapter about Project Server 2010 Workflow and Project Detail Pages contains the following sections:       Enterprise Project Types Workflow Phases Workflow Stages Change or Restart Workflows Project Detail Pages Project Workflow Settings .

the EPTs appear in a drop-down list of project types when the user clicks New Project on the Ribbon in Project Web App. On the Server Settings page. click Server Settings. Using project types helps to categorize projects within the same organization that have a similar project life cycle. enter a name for the type. project types are aligned with individual departments. Click New Enterprise Project Type. and PDPs. On the PWA home page. stages. . a single workflow. In the Name box. for example. click Enterprise Project Types 3. and then provide a brief description in the Description box. Normally. under Workflow and Project Detail Pages.Workflow and Project Detail Pages 229 Enterprise Project Types An enterprise project type represents a wrapper that encapsulates phases. or HR projects. marketing projects. For a user. Create New Enterprise Project Type  To create a new enterprise project type 1. Each EPT represents a single project type. IT projects. 2.

or if you want to control its placement in the list. 7. Once you associate a site workflow with a project type and save the type. Click Save to save this enterprise project type to the server. be sure that your server administrator has installed and configured workflows on the Microsoft Project Server 2010 machine. Select a template from the Project Plan Template list. if appropriate. and then click Add to move them to the box on the right. 13. 15. If the enterprise project type that you are creating is the one that all new projects should use by default. Select a template from the Project Site Template list.230 Project Server 2010 Administrator's Guide 4. 5. Click the button next to the Departments field to select the departments you want to associate with this project type. 10. 6. 14. To control the placement of this type in the list. clear the Position this type at the end check box. In the Order section. If you selected No Workflow from the Site Workflow Association list. if appropriate. select the Use this as the default Enterprise Project Type during Project Creation check box. if appropriate. To include this type at the end of the list. 8. you cannot go back and update the type to use a different workflow. 12. The Project Server 2010 workflow platform is built on the SharePoint workflow platform. Note If you're not seeing any workflows in this list. . select the Position this type at the end check box. provide the URL for the image in the Type the URL box. in turn. which. is built on the Windows workflow platform. select the project detail pages that you want to include in this project type from the Available Project Detail Pages box. Select a project detail page from the New Project Page list. choose whether you want this project type to appear at the end of the list of project types. If you want to associate an image with this project type. making it available for new project or proposal creation. 11. Select a workflow from the Site Workflow Association list. 9. and then choose the type that you want to appear just before the type you're creating from the Choose the type before which the current type should be positioned list.

and project management (shown as Create. click Server Settings.Workflow and Project Detail Pages 231 Workflow Phases A phase represents a collection of stages grouped to identify a common set of activities in the project life cycle. Select. Click the New Workflow Phase button on the toolbar. Default Workflow Phases New Workflow Phase  To create a new workflow phase 1. Under Name enter the name of the desired phase and optionally enter a description of the phase in the Description text box. 5. 4. Add Workflow Phase . That is. click Workflow Phases 3. changing the order of phases does not affect how the system reacts. Examples of phases are project creation. and Manage Phases). Click Save. under Workflow and Project Detail Pages. 2. On the Server Settings page. The primary purpose of demand management phases is to provide a smoother user experience where users have the option of organizing stages into logical groups. On the PWA home page. project selection. Phases do not have any direct technical effect on the behavior of an Enterprise Project Type.

under Workflow and Project Detail Pages. click Server Settings. Under Name change the name to the desired phase name and optionally enter a description of the phase in the Description text box. click Workflow Phases 3. 4. 5. Click the existing workflow phase in the Workflow Phases column that you wish to modify. On the Server Settings page. Click Save. 2. .232 Project Server 2010 Administrator's Guide  To edit an existing workflow phase 1. On the PWA home page.

5. 4. modified. At each step. data must be entered. As part of the confirmation dialog shown to users when they click the 'Submit' button in a Project Detail Page 2. As a Tool Tip when users rest the pointer on the 'Submit' button in a Project Detail Page b. this description will be displayed in the following places: a. By default. On the PWA home page. or processed.Workflow and Project Detail Pages 233 Workflow Stages A stage represents one step within a project life cycle. under Workflow and Project Detail Pages. Stages at a user level appear as steps within a project. Under Name enter the name of the desired stage and optionally enter a description of the stage in the Description text box. 3. . On the Server Settings page. Under Description for Submit type the description that will be displayed to end-users when submitting to workflow. click Workflow Stages. A stage is composed of one or more Project Detail Pages linked by common logic or theme. Workflow Stages New Workflow Stages  To create a new workflow stage 1. Click the New Workflow Phase button on the toolbar. reviewed. click Server Settings.

7. This option is typically selected if any project updates occur in this Workflow Stage (which will be blocked if the project is not checked in). Click Save. Note By default no PDPs are visible for workflow stages but at least one page should be selected for a workflow stage. 14. Under Additional Settings for the Visible Project Detail Page you may edit the specific description of the Visible PDPs by selecting them in the right column from the previous step and then editing the description in the text box. You may also check the Project Detail Page requires attention check box to highlight the PDP on the Workflow Status page. If project checkin is required for the current workflow stage. Under Required Custom Fields select the Custom Fields that are required for the Workflow to enter this Workflow Stage and click the Add button. If Strategic Impact behavior is set to Required then a strategic impact value needs to be specified for every business driver. Under Read Only Custom select the Custom Fields that are read only for this Workflow Stage and click the Add button. 6. 10. Under Project Check In Required select whether this Workflow Stage requires the project to be checked in. Read Write or Required in this workflow stage. This page will be displayed as the introduction page when the project enters this workflow stage. This is typically accomplished by using the Strategic Impact Web part on a project detail page. not for all the subsequent Workflow Stages in the Workflow. 11. The Project Workflow Stage is now saved. 9. In Visible Project Detail Pages select the Project Detail Pages you wish to be visible for this workflow stage by selecting them from the Available column and clicking the Add button to put them in the Selected Project Detail Pages column. the user cannot Submit the Project to Workflow without checking in the Project. 13. Under Strategic Impact Behavior select the radio button to specify whether the Strategic Impact values for the project are Read Only. Under Workflow Stage Status Project Detail Page choose the Workflow Stage Status Project Detail Page from the dropdown.234 Project Server 2010 Administrator's Guide Under Workflow Phase choose the Workflow Phase to correspond with this Workflow Stage. 8. . Take note that these Custom Fields are 'Required' just for this Workflow Stage. 12.

Workflow and Project Detail Pages 235 .

click Server Settings. Restart Enterprise Project Type Change or Restart a Workflow  To Change or Restart a Workflow 1.236 Project Server 2010 Administrator's Guide Add a Workflow Stage Details Page Change or Restart Workflows The Change or Restart Workflow section allows you to change a project’s in-progress workflow or change a project’s current stage in a workflow. On the PWA home page. .

Create or Edit Project Detail Pages There are three types of Project Detail Pages that can be created: . Note Only projects that are not checked out or are checked out to you are shown in the Choose Projects section. click Change or Restart a Workflow.Workflow and Project Detail Pages 237 On the Server Settings page. PDPs can be used to display or collect information from the user. Web Parts can make calls to the Project Server Interface (PSI). you must then choose from the drop down menu the new Enterprise Project Type you wish to use. 2. query the Reporting database. If a new Enterprise Project Type is selected. Under Choose Workflow Stage to Skip to you can select the target workflow stage this workflow will skip to. 7. Project Server Web Parts and custom Web Parts used in demand management all contain custom fields. If a project is checked out to another user the workflow cannot be changed or restarted on that project. Under Choose new Enterprise Project Type or restart workflow for current Enterprise Project Type select whether to restart the current workflow for the selected projects or to associate the projects with a new Enterprise Project Type. 3. under Workflow and Project Detail Pages. Under Choose Projects select the project with the workflow instances that need to be changed or restarted and add it to the Target List. 6. 4. Click OK. Under Choose Enterprise Project Type choose the Enterprise Project Type that needs to be changed or restarted. or integrate with external systems. You can add individual Web Parts from the standard Web Part galleries or create custom Web Parts. You can create PDPs in much the same way you create any Web Part Page in a SharePoint site. 5. where you can add Web Parts that provide the experience you want. Choose Workflow Stage to Skip Project Detail Pages Project Detail Pages (PDPs) represent a single Web Part Page in Project Web App.

On the Server Settings page. under Workflow and Project Detail Pages.238 Project Server 2010 Administrator's Guide project template that has a workflow for portfolio analysis. 5. 6. In Categories select Project Web App and then select the web part you would like to add. click Project Detail Pages. On the newly created blank page. Select New Document on the ribbon. select Add a Web Part. click Server Settings. On the PWA home page. 3. 4. 2. . diting  To create a project detail page 1. Click on the Documents tab.

In the Edit Web Part pane under Appearance enter a title and then click OK. Now you must select the project fields used to populate the web part. Select the Page Tools tab on the ribbon and click Stop Editing. 11. . 12. From the top right menu select Edit Web Part. Select the project data you wish the web part you selected to display and then click OK. Now select Edit Properties on the ribbon and update the Display Name and Page Type for your newly created Project Detail Page. The newly selected Web Part is displayed.Workflow and Project Detail Pages 239 7. 8. In the Edit Web Part pane click the Modify button. 9. 10.

which in turn is built off of Windows . The workflows are made up of workflow activities that are objects with code within it. . Project Server 2010 Workflow Hierarchy The Project Workflow Settings page designates the Workflow Proxy User account so that the Project Server Interface (PSI) calls within a workflow can be performed.NET Framework 3. By default.5. For these PSI calls to be successful the Workflow Proxy User Account should have appropriate permissions in Project Server. therefore the only item to be set on this page is to make sure that the Workflow Proxy User account text box contains a logon account with sufficient permissions.240 Project Server 2010 Administrator's Guide Project Workflow Settings Project Server 2010 workflows are built from SharePoint Server 2010 Site Workflows which are built off of Windows Workflow Foundation. all PSI calls within a workflow will be made under the context of the Workflow Proxy User Account.

Workflow and Project Detail Pages 241 Project Workflow Settings .

242 Appendices .

 Dependencies Lists any other permissions (global or category) or requirements to   allow the permission to function. New for Project Server 2010 Displays an X symbol if the permission is new for Project Server 2010. The table includes columns with the following information:  Description Describes what the permission lets you do. Previous name. if renamed from Office Project Server 2007 Specifies the Microsoft Office Project Server 2007 permission name if the permission was renamed from Office Project Server 2007 but provides the same functionality.Project Server 2010 Category Permissions 243 A Project Server 2010 Category Permissions The following is a list of category permissions for Microsoft Project Server 2010. Permission Accept Task Update Requests Description Allows a user to accept updates on projects without requiring that the user have the Save Project to Project Server permission Dependencies Previous name. if renamed from Office Project Server 2007 New for Project Server 2010 .

if renamed from Office Project Server 2007 New for Project Server 2010 Approve Timesheets Allows a user to approve a  team member’s submitted timesheet entries. User must have the View Team Builder global permission in order to use the Build Team page in Project Web App or Project Professional. Dependencies User must have the View Resource Timesheet permission to use this permission. Grant this permission to any member of your organization who requires the ability to approve a resource’s timesheet. User must have the Approve Timesheets permission through a category which contains the resources which they want to approve timesheets on. Assign Resources Allows a user to assign or allocate a given resource to projects. Previous name. This permission controls the list of available resources in Team Builder in both Project Web App and Project Professional. Grant this permission to all project managers and resource managers who  .244 Project Server 2010 Administrator's Guide Permission Adjust Timesheet Description Allows a Project Web App user to adjust a team member’s submitted timesheet entries. Grant this permission to any member of your organization who requires the ability to adjust a resource’s timesheet entry after that resource has submitted the entry.

In addition. or  allocate resources. Or. User must have the Build Team on New Project global permission in order to assign a resource in a new enterprise project.Project Server 2010 Category Permissions 245 Permission Description Dependencies User must have the Build Team on Project category permission in order to assign a resource in an existing enterprise project. then you must have permission to assign resource R (Assign Resources) plus permission to build the team on Project P (Build Team on Project). you must have access to the Team Builder  page through either Project Web App or Project Professional (Assign Resources to Project Team). Build Team On Project Allows a user to 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 they save (and publish) them to the Project Server database. if you want to add resource R to project P. grant this permission to  . User must have the View Enterprise Resource Data and Assign Resources category permissions in order to see resources that are part of the Enterprise Resource Pool in Previous name. manage. For example. if renamed from Office Project Server 2007 New for Project Server 2010 have to assign.

 Create New Task or Assignment Determines which projects are available when you are creating new tasks. this permission enables a user to create. User must have permission (at the category level) to access the specific projects and resources that have to be accessed to build the project team or assign resources. modify. Create Object Links . When allowed. Previous name. Grant this permission to any group of projects that individual users will be able to create new tasks in by using the Create a new task page in Project Web App.246 Project Server 2010 Administrator's Guide Permission Description Dependencies the Build Team feature in Project Professional and Project Web App. if renamed from Office Project Server 2007 New for Project Server 2010 resource managers who want to use the Build Team feature in the Project Center of Project Web App to add resources to a project that has already been saved to the Project Server database. or delete links between Project Tasks User must be granted the New Task Assignment global permission in order to access the New task page in Project Web App.

Dependencies Previous name. deliverables or risks). issues.Project Server 2010 Category Permissions 247 Permission Description and items in the Project Workspace (documents. if you have to do so. if renamed from Office Project Server 2007 New for Project Server 2010 Delete Project 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. Edit Enterprise Resource Data . Allows a project manager to edit enterprise resource data by using Project Professional (checked-out Enterprise Resource Pool) or a resource manager to User must be granted the View Enterprise Resource Data category permission. Grant this permission to members of your organization to enable them to more closely manage the projects he or she has saved to the Project Server database from Project Professional or by using the "Delete Enterprise Objects" link in Project Web App. you should consider how your organization will recover those projects. Before letting users delete projects.

These Dependencies Previous name.248 Project Server 2010 Administrator's Guide Permission Description edit enterprise resources using Project Web App (Resource Center). 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). Resource managers with this permission are able to edit enterprise resource data in the Resource Center in Project Web App. and other static information related to resources. custom field data. Grant this permission to project managers and resource managers who have to make updates to resources that belong to the Enterprise Resource Pool. if renamed from Office Project Server 2007 New for Project Server 2010 . custom outline code data. and they can make updates to cost data. Resource managers cannot add or delete resources from the Enterprise Resource Pool in Project Web App.

but have "Save Project to Project Server" you can still edit project-level fields/custom fields in the project field Web Part. Note The Project Server Interface (PSI) can also be used to create or delete resources in the Enterprise Resource Pool and to edit enterprise resource data. Controls whether a specific Project Permission can be set on a single project through the new Project Permissions feature. Dependencies Previous name.Project Server 2010 Category Permissions 249 Permission Description permissions are required in addition to the Edit Enterprise Resource Data category permission. Allows a user to see other users whom he or she Edit Project Properties in Project Center X Manage Basic Project Security X Manage Resource X . If you do not have this permission. if renamed from Office Project Server 2007 New for Project Server 2010 Edit Project Summary Fields Allows a user to edit only the enterprise project fields shown in the new project fields Web Part.

Allows a user to open a project from the Project Server database in read-only mode using Project Professional. if renamed from Office Project Server 2007 New for Project Server 2010 Publish Project User must be granted the Open Project category permission on any project that has to be checked out from the Project . Allows a user to Publish projects to the Project Server Published database using Project Professional and Project Web App. Allows a user to edit a resource plan. Grant this permission to any member of your organization who has to use the Open from Microsoft Project Server dialog box in Project Professional or in the Project Center in Project Web App to open projects that have been saved to the Project Server database. If users are not assigned the Save Project to Project Server permission. Grant this permission to all Dependencies Previous name.250 Project Server 2010 Administrator's Guide Permission Delegates Manage Resource Plan Open Project Description manages and to set delegates for them. then the project will only be open in read-only mode.

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 or through Server-side projects. Previous name. it will only publish the outdated version. User must be granted the Open Project category permission on any project that has to be checked out from the Project Server database. User must be granted the New Project permission in order to create the project. Dependencies Server database. If not. Allows a user to save a protected baseline or clear a protected baseline Save Protected Baseline User must be granted the Save Project to Project Server . when a publish occurs.Project Server 2010 Category Permissions 251 Permission Description members of your organization who will be publishing projects. If the project has changed since opening. Also gives Project Web App users the permission to save schedules and strategic impact data. if renamed from Office Project Server 2007 New for Project Server 2010 Save Project to Project Server Allows a user to save  projects to the Project Server database using Project Professional. the user will be required to have the Save Project to Project Server permission on that project.

Only users who have Save Unprotected Baseline. Grant this permission to any member of your organization who has to view projects summaries in the Project Users also must be granted the View Project Center View permission in order to see the Project Center. Click the Set Baseline button and then select Save Baseline or Clear Baseline. . Dependencies category permission.252 Project Server 2010 Administrator's Guide Permission Description associated with an enterprise project published to the Project Server database. Open Project and Save Project Category permissions are able to save Baselines in Baseline 6-10. Protected Baselines are in the range of Baseline 0-5 inclusive. Grant this permission to project managers who have to save baselines in their projects. if renamed from Office Project Server 2007 New for Project Server 2010 View Project Summary in Project Center Allows a user to access a specific project in the Project Center from Project Web App. Baselines are saved by using the Set Baseline functionality accessed from the Project Professional ribbon on the Project tab in the Schedule group. Previous name.

Allows users to view Risks. Dependencies Previous name.Project Server 2010 Category Permissions 253 Permission Description Center. Grant this permission to users who have to view project details in the Project Center. Grant this permission to project managers and resource managers who have to view resource assignment details in the Resource Center from Project Professional or Project Web App. Grant this permission to any user who has to view resources and resource data that is stored in the Enterprise Resource Pool. View Project Details in Project Center X View Resource Assignments in Assignment Views View Enterprise Resource Data View Project View X . if renamed from Office Project Server 2007 New for Project Server 2010 View Project Schedule in Project Web App Allows a user to view project information for a specific project from the Project Center in Project Web App. Allows a user to view assignment details using assignment views in the Resource Center. Allows a user to view resources and resource data that is stored in the Enterprise Resource Pool.

Documents. and Documents areas in Project Web App and Project Professional. Issues. if renamed from Office Project Server 2007 Project Workspace New for Project Server 2010 . Dependencies Previous name. Grant this permission to any user of Project Professional who has to select Project site. Documents. or Risks from the Info page in the Backstage or any user of Project Web App who has to access the Project site. or Risks top-level navigation links.254 Project Server 2010 Administrator's Guide Permission Site Description Issues. Issues.

if renamed from Office Project Server 2007 New for Project Server 2010 .  Dependencies Lists any other permissions (global or category) or requirements   necessary for the permission to function. Dependencies Previous name. The columns in the table include the following:  Description Describes what the permission enables you to do. if renamed from Project Server 2007 Specifies the Office Project Server 2007 permission name if the permission was renamed from Office Project Server 2007 but provides the same functionality. Permission About Microsoft Project Server Description Allows a user to access the About Project Server page through Project Web App Server Settings.Project Server 2010 Global Permissions 255 B Project Server 2010 Global Permissions The following is a list of global permissions for Microsoft Project Server 2010. Previous name. New for Project Server 2010 Displays an X symbol if the permission is new for Project Server 2010.

Previous name.256 Project Server 2010 Administrator's Guide Permission Accept Timesheets Description Allows a user to accept but not approve a timesheet. An example would be where an administrative assistant would view the timesheets to make sure that there were no inaccuracies in them. When it is accepted then a manager with Approve Timesheets permission will approve the timesheets. Allows a user to add resources to a project that has not been saved to Project Server. Grant this permission to project managers who want to use the Build Team feature in Microsoft Project Professional to staff their projects before they save (and publish) them to Project Server. Dependencies Users have access to the Approval Center if they have either the Accept Timesheets or the View Approvals permission. Allows a user to change their . X Can be Delegate Change Specifies whether a user can be a delegate. if renamed from Office Project Server 2007 New for Project Server 2010 Build Team On New Project User has to be granted the Assign Resources and View Enterprise Resource Data category permissions in order to see resources that are part of the Enterprise Resource Pool in the Build Team feature in Microsoft Project Professional.

and user delegates from Project Server. Allows a user to close tasks to Time Reporting. resources. Forms-based authentication is provided through a membership provider and individual membership providers may prevent the changing of passwords. if renamed from Office Project Server 2007 New for Project Server 2010 Change Workflow Clean up Project Server database X Close Task to Updates . Allows a user to change a project's Enterprise Project type. (Change Project Type). status reports responses. Allows a user to access the Delete Enterprise Objects page available through the Server Settings page in Project Web App. users. Grant this permission to users who have to delete timesheets. Dependencies Previous name. Please verify this with your membership provider if you intend to use this permission. projects. It gives access to the Close Tasks to Update Project Web App page.Project Server 2010 Global Permissions 257 Permission Password Description Forms user account password from Project Web App.

Grant this permission to any user who is authorized to connect Dependencies Previous name. Allows a user to access the Request a status report link on the Project Web App Status Reports center and to view team reports.258 Project Server 2010 Administrator's Guide Permission Contribute to Project Web App Edit Status Report Requests Description Allows users to edit items within lists in Project Web App project sites. team leads. resource managers. Allows a user to access the Submit a status report link on the Status Reports center in Project Web App. usually project managers. and members of your organization’s PMO. Grant this permission to any member of your organization who has to create status report requests and view team reports. if renamed from Office Project Server 2007 Contribute to Project Web App New for Project Server 2010 Edit Status Report Responses Log on . Allows a user to connect to Project Server from Microsoft Project Professional or to log on to Project Web App. Grant this permission to any user of Project Web App who must be able to submit status reports.

Manage Active Directory Settings . if renamed from Office Project Server 2007 New for Project Server 2010 Log on to Project Server from Project Professional Allows a user to load the Enterprise Global Template when he or she connects Microsoft Project Professional to Project Server. If the user is denied this permission then they cannot modify settings for any of the following:  Enterprise Resource Pool synchronization settings.  Project Web App Security Groups synchronization settings.Project Server 2010 Global Permissions 259 Permission Description to Project Server from Microsoft Project Professional or log on to Project Web App.  Choose an Active Directory Group to synchronize against a specific Security Group within the Add/Modify Group page. Grant this permission to all users in your organization who will be using Microsoft Project Professional to connect to Project Server. Dependencies Previous name. Allows users to modify any Active Directory Synchronization settings within the Project Web App Administration.

Allows a user to the set and modify the settings for OLAP cube creation. calendars. Allows a user to access the Gantt chart and grouping Dependencies Previous name. This page lets users force check-in projects.260 Project Server 2010 Administrator's Guide Permission Manage Check-Ins Description Allows a user to access the Forced Check-in Enterprise Objects page in Project Web App. lookup tables and resource plans. Allows a user to create. if renamed from Office Project Server 2007 New for Project Server 2010 Manage Cube Building Service Manage Drivers Manage Enterprise Calendars Manage Enterprise Custom Fields Manage Exchange Integration Manage Gantt Chart and X X .aspx page to create drivers for Portfolio Analysis. custom fields. modify and delete Enterprise Calendars within Project Web App. resources. Allows a user to modify the definitions of Enterprise Custom Fields and lookup table from Project Web App. Allows a user to access the drivers. Allows administrators to enable the synchronization of project tasks with Exchange Server.

and delete lists within the Project Web App project site. if renamed from Office Project Server 2007 New for Project Server 2010 Manage Lists in Project Web App Manage Notification and Reminders Manage My Delegates X X Manage My Resource Delegates Manage Personal Notifications X . This permission is used when synchronizing a user against the Project Web App project site. Allows users to set a user who requires a substitute on the Add/Modify Delegation page. modify. Allows a user to create. Allows users to see the "Manage Delegates" link and to set a delegate on the "Add/Modify Delegation" page. Allows a user to access the Manage My Alerts and Reminders page in Project Web App. Grant this permission to any user that Dependencies Previous name. Allows a user to manage the Notification and Reminders settings.Project Server 2010 Global Permissions 261 Permission Grouping Formats Description formats customization options in the Project Server Administration page for Project Web App views.

including the following:  Projects  The Enterprise Resource Pool  Calendars  Custom fields  The Enterprise Global template  Views  System settings  Categories  Group settings. read. update. update. Allows a user to schedule the backup or immediately back up several entities on Project Server. Dependencies Previous name.262 Project Server 2010 Administrator's Guide Permission Description you want to be able to sign up for e-mail notifications and reminders related to tasks and status reports. if renamed from Office Project Server 2007 New for Project Server 2010 Manage Portfolio Analyses Manage Prioritizations Manage Project Server Backup Allows a user to create. Allows a user to create. and delete driver prioritizations. read. Allows a user to immediately restore several entities on Project Server. and delete Portfolio analyses. including the X X Manage Project Server Restore .

Grant this permission to project managers. Users with permission to access this page are able to add. Resource Center. Project Center. if renamed from Office Project Server 2007 New for Project Server 2010 Manage Project Web App Views Allows a user to access the Manage Views page in the Server Settings page in Project Web App. or delete Project. . Dependencies Previous name.Project Server 2010 Global Permissions 263 Permission Description following:  Projects  The Enterprise Resource Pool  Calendars  Custom fields  The Enterprise Global template  Views  System settings  Categories  Group settings Note Similar to Server Backup except that the permission does not let you schedule a recovery. and they are able to modify Timesheet views. modify. Assignment. resource managers. or Portfolio Analyzer views.

The number of projects in this kind of environment may be too many for the IT administrator team. Allows a user to access the Alert me about my resources on tasks and status reports link on the Project Web App home page. offloading this work to the people in your organization that work at the project level on a day-to-day basis is one way to distribute the workload of managing views. Grant this permission to Manage Resource Notifications . cancel.264 Project Server 2010 Administrator's Guide Permission Description and members of your organization’s PMO so they can create project data views for users to access in Project Web App and Microsoft Project Professional. Dependencies Previous name. and unblock jobs in the queue. 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. if renamed from Office Project Server 2007 New for Project Server 2010 Manage Queue Allows the user to read or set queue configuration settings and retry.

Project Server 2010 Global Permissions 265 Permission Description 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. or members of your organization’s PMO so they can define how they will automatically receive and accept changes to transactions by their resources. Dependencies Previous name. Grant this permission to project managers. and user authentication settings. resource managers. if renamed from Office Project Server 2007 New for Project Server 2010 Manage Rules Allows a user to access the Rules page from the Approval Center in Project Web App and set rules on how update transactions will be automatically processed. Allows a user to access the Manage security page in Project Web App to define security categories. security templates. Grant this permission to Project Server administrators or a very small and closely managed group of people. This page lets users change Project Server Manage security .

once you have begun using Project Server in your organization. should be carefully managed and (ideally) infrequent. Users with permission to access the Project Web App Permissions page can enable or disable enterprise features. Allows a user to access the Project Web App Permissions page in Project Web App. X Manage Server Configuration .266 Project Server 2010 Administrator's Guide Permission Description security settings. manage organizational permissions. create security categories and security templates. and create custom menus (both top-level and side-pane) in Project Web App. Grant this permission to Project Server administrators or a very small and closely managed group of people. The Manager Server Events page requires the event handler to be registered by the server as defined in the Project Server SDK. if renamed from Office Project Server 2007 New for Project Server 2010 Manage Server Events Allows a user to register event handlers for specific Project Server server-side events. Changes to settings on this page. Dependencies Previous name.

whether or not sites are created on project publish. Grant this permission to members of your organization who are administrators for Project Web App or administrators for the servers that are running SharePoint Server 2010. After reviewing the timesheet. if renamed from Office Project Server 2007 Manage Windows SharePoint Services New for Project Server 2010 X Manage Site Services X Manage Time Reporting and Financial Periods Manage Time Tracking Manage Timesheet and Financial Periods X Allows a user to be forwarded timesheets for review.Project Server 2010 Global Permissions 267 Permission Manage SharePoint Foundation Description Allows a user to create and delete project sites. Dependencies Users with this permission should be granted administrative privileges to all of the servers that are running Project Server 2010 and SharePoint Server 2010 Previous name. permission synchronization settings. Active Directory Synchronization. and site path updates. and Event handlers. the user will be required the following permissions:  Accept Timesheet . Allows users or groups the ability to manage Queue Settings. Allows a user to create and modify Timesheet and Fiscal period definitions.

modify.268 Project Server 2010 Administrator's Guide Permission Description  Dependencies Previous name. Allows a user to add a new project to Project Server using Microsoft Project Professional. Users with this permission will be able to add. or delete Project Server users and manage Project Server security groups. or the Project Server Interface (PSI). Only a small group of people should have permission to access this set of pages. Project Web App. Allows a user to manage and view workflow and Project Detail Pages (PDPs). if renamed from Office Project Server 2007 New for Project Server 2010 Approve Timesheet Manage Users and Groups Allows a user to access the Manage Users and Groups page in the Server Settings page in Project Web App. New functionality in Project Server X Manage Workflow and Project Detail Pages New Project . Grant this permission to members of your organization who are Project Server administrators.

Project Server 2010 Global Permissions 269 Permission Description 2010 for this permission: If you do not also have the Open Project permission. Dependencies Previous name. New Task Assignment Allows users to access the Create a New Task and Add Yourself to a Task links from the Insert Row button found . Note If your organization is using the Active Directory synchronization feature. if renamed from Office Project Server 2007 New for Project Server 2010 New Resource Allows a project manager to add new resources to the Enterprise Resource Pool using Microsoft Project Professional. you are taken back to the Project Center. after you create a project. you may want to consider denying this permission to all non-IT administrators in your organization. Grant this permission to any member of your organization who has to create new enterprise resources in Project Server. or the Project Server Interface (PSI). the Project Web App Resource Center.

A user who has the New Task Assignment permission must also have access to the projects to which they want to assign themselves to a task. . The list of available projects for a user to create new tasks is determined by the Create New Tasks or Assignment category permission.270 Project Server 2010 Administrator's Guide Permission Description on the Tasks page of Project Web App. Dependencies Previous name. Users with this permission will also be able to use the Create a New Task link to create new tasks in Project Web App for any project to which the user has access. Grant this permission to all users in your organization who will be using Microsoft Project Professional User must be granted the New Project global permission in order to save the project to the Project Server database as an actual project. Grant this permission to any member of your organization who has to create new assignments on existing tasks in projects that have been published to Project Server. if renamed from Office Project Server 2007 New for Project Server 2010 Open Project Template Allows a user to open an Enterprise Project Template from Project Server using Microsoft Project Professional.

This example creates an additional layer of task management within the larger organization. A project manager could assign the team leads in the project plan. each with their own team lead. but it can also simplify resource allocation within projects themselves and make it easier for a project manager to manage large projects. a large project may be run by a single project manager. Grant this permission to members of your organization who need the ability to delegate task assignments to other resources. For example. but actually implemented by several teams. Dependencies Previous name. Or. if renamed from Office Project Server 2007 New for Project Server 2010 Reassign Task Allows a user to delegate an assigned task to another (existing) user. and this resource had . and then the team leads could in turn delegate each task to individual members of their teams. if you have a resource that is about to leave on a three-week vacation.Project Server 2010 Global Permissions 271 Permission Description to create and manage projects that are based on Enterprise Project Templates.

either project managers. members of your organization’s PMO.272 Project Server 2010 Administrator's Guide Permission Description this permission. This permission should only be granted to a small group of people in your organization. Grant this permission to members of your organization who are tasked with creating Enterprise Project Templates. Allows a user to create and save a project as an Enterprise Project Template from Microsoft Project Professional to the Project Server database. or Project Server administrators. and save the Enterprise Global Template to the Project Server database from Microsoft Project Professional. if renamed from Office Project Server 2007 New for Project Server 2010 Save Enterprise Global Allows a user to check out. they would be able to assign their tasks directly to other resources instead of having the project manager check out the project and reassign resources. modify. When a user saves a project to Project Server for the first time. the option to select Template (as opposed to User needs to be granted the Assign Resources and View Enterprise Resource Data category permissions in addition to this permission if they are also responsible for adding Generic resources to the Enterprise Project Save Project Template . Dependencies Previous name.

Previous name. which have been assigned to their Team Assignment Pool. Dependencies Template. With this permission. Self-Assign Team Tasks . Unprotected Baselines are in the range of Baseline 6-10 inclusive. Baselines are saved by using the Set Baseline functionality accessed from the Microsoft Project Professional ribbon on the Project tab in the Schedule group. if renamed from Office Project Server 2007 New for Project Server 2010 Save Unprotected Baseline Allows a user to save a nonprotected baseline or clear a non-protected baseline associated with an enterprise project published to the Project Server database. it is possible for users to assign tasks. Click the Set Baseline button and then select Save Baseline or Clear Baseline. Resources can be members of a Team Assignment Pool.Project Server 2010 Global Permissions 273 Permission Description Project) from the Type dropdown list in the Save to Project Server dialog box is enabled. User needs to be granted the Save Project category permission. to themselves through the Team Tasks page in Project Web App.

Allows a user to read from the output for the OLAP cube. Allows a user to view the Approval Center. Dependencies Previous name. User needs to be granted the View Project Summary in Project Center category permission. This permission is only checked when the OLAP cube is built. X View Business Intelligence Link Allows a user to see the Business Intelligence link in Quick Launch.274 Project Server 2010 Administrator's Guide Permission Status Broker Permission View Approvals Description Allows API updates to occur for a user from places like Microsoft Exchange Server. Allows users to access the Project Center from Project Web App or Microsoft Project Professional. View OLAP Data View Project Center View Project View Allows a user to access project views in Project Web App. However. if renamed from Office Project Server 2007 New for Project Server 2010 X Users have access to the Approval Center if they have either the Accept Timesheets or the View Approvals permission. . it has no impact on Report Center Security.

Allows a user to access the View Resource Availability page to view resource allocation data in Project Web App. X X View Resource Center . Grant this permission to users who need User needs to be granted the View Enterprise Resource Data category permission. Allows users to access the Resource Center from Project Web App or Microsoft Project Professional and view resource allocation data.Project Server 2010 Global Permissions 275 Permission Description Grant this permission to users who need to drill down into project details using the Project Center in Project Web App or Microsoft Project Professional. Grant this permission to users in your organization who need to view resource availability in Project Web App. if renamed from Office Project Server 2007 New for Project Server 2010 View Project Schedule Views View Project Timesheet Line Approvals View Resource Availability Allows a user to see the link in the Quick Launch. it has no impact on Report Center Security. However. Dependencies Previous name. Allows a user to approve timesheets on a line-by-line basis.

Allows users to view the timesheets. View Task Center View Team Builder Allows a user to use Build  Team in Project Web App and User needs to be granted the . if renamed from Office Project Server 2007 New for Project Server 2010 View Resource Plan View Resource Timesheet Allows a user to access the Resource Plan page within Project Web App. for resources identified in the category selection criteria. This permission when denied prevents users from seeing the Task Center link on the Project Web App Quick Launch menu. Dependencies Previous name. It is still possible for users to navigate to this page. Note This permission does not lock down access to the Task Center page. regardless of their state or ownership.276 Project Server 2010 Administrator's Guide Permission Description to view the Resource Center in Project Web App by clicking the Resources link in the toplevel navigation. X Users must be granted the Accept Timesheet global permission to use this permission. or in Microsoft Project Professional by selecting Resource Center on the Collaborate menu.

if renamed from Office Project Server 2007 New for Project Server 2010 User needs to be granted the Build Team on Project category permission. Project Managers can also use this permission to allow them to use Build Team in Microsoft Project Professional to add resources to projects. The Build . Dependencies Assign Resources category permission in addition to the View Team Builder global permission. The Assign Resources category permission determines the list of resources available in Build Team in both Microsoft Project Professional and Project Web App. 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 App to add resources to projects that have been saved to the Project Server database.Project Server 2010 Global Permissions 277 Permission Description Microsoft Project Professional.  Previous name.

This applies to using Build Team in both Microsoft Project Professional and Project Web App.278 Project Server 2010 Administrator's Guide Permission Description Dependencies Team on Project permission determines with which projects Build Team can be used. Previous name. if renamed from Office Project Server 2007 New for Project Server 2010 View Timesheets When this permission is denied it prevents users from seeing the Timesheet Center link on the Project Web App Quick Launch menu Note This permission does not lock down access to the Timesheet page. It is still possible for users to navigate to this page View Timesheet Center X .

Project Server 2010 Global Permissions 279 .

Category permissions apply to what users are allowed to do with specific projects. you can then choose to customize the new group to better suit your users by editing the permission for the group. Global permissions differ from category permissions in that they apply to functionality that the user is allowed to use in Project Server 2010.        . For more information about groups and categories.aspx). resources. categories. After using the template to create a new group. and RBS in Project Server 2010‖ (http://technet. and views as defined by the category that the group is associated with. see the Microsoft TechNet article ―Plan groups.microsoft.280 Project Server 2010 Administrator's Guide C Project Server 2010 Default Security Groups This article describes the default permissions that are given to the default templates and user groups in Microsoft Project Server 2010. Templates are also included to allow these default permissions to be assigned to new groups created by the administrator. Project Server 2010 creates seven default groups during installation: Administrators Executives Portfolio Managers Project Managers Resource Managers Team Leads Team Members Each group is given a default set of permissions (global and category).com/enus/library/cc197354.

Permission Name About Microsoft Project Server Accept Timesheets Build Team On New Project Can Be Delegate Change Password Change Workflow Clean Up Project Server Database Close Tasks To Updates Contribute to Project Web App Edit Status Report Requests Edit Status Report Responses Log On Log on to Project Server Administrators X X X X X X X Executives Portfolio Managers Project Managers Resource Managers Team Leads Team Members X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X .Project Server 2010 Default Security Groups 281 Default global permissions The following table contains a list of the default global permissions for each of the default user groups.

282 Project Server 2010 Administrator's Guide Permission Name from Project Professional Manage Active Directory Settings Manage CheckIns Manage Cube Building Service Manage Drivers Manage Enterprise Calendars Manage Enterprise Custom Fields Manage Exchange Integration Manage Gantt Chart and Grouping Formats Manage Lists in Project Web App Manage My Delegates Manage My Resource Delegates Manage Notification and Reminders Administrators Executives Portfolio Managers Project Managers Resource Managers Team Leads Team Members X X X X X X X X X X X X X X X X X X X X X X X X .

Project Server 2010 Default Security Groups 283 Permission Name Manage Personal Notifications Manage Portfolio Analyses Manage Prioritizations Manage Project Server Backup Manage Project Server Restore Manage Project Web App Views Manage Queue Manage Resource Notifications Manage Rules Manage Security Manage Server Configuration Manage Server Events Manage SharePoint Foundation Manage Site Services Manage Time Reporting and Financial Periods Administrators X X Executives X X Portfolio Managers X X Project Managers X Resource Managers X Team Leads X Team Members X X X X X X X X X X X X X X X X X X X X X X .

284 Project Server 2010 Administrator's Guide Permission Name Manage Time Tracking Manage Users and Groups Manage Workflow Project Detail Pages New Project New Resource New Task Assignment Open Project Template Reassign Task Save Enterprise Global Save Project Template Save Unprotected Baseline Self-assign Team Tasks Status Broker Permission View Approvals View Business Intelligence Link View OLAP Data Administrators X X X Executives Portfolio Managers Project Managers Resource Managers Team Leads Team Members X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X .

 My Org = My Organization  My Dir = My Direct Reports  My Proj = My Projects .285 Permission Name View Project Center View Project Schedule Views View Project Timesheet Line Approvals View Resource Availability View Resource Center View Resource Plan View Resource Timesheet View Task Center View Team Builder View Timesheets Administrators X X X Executives X X X Portfolio Managers X X X Project Managers X X X Resource Managers X X Team Leads X X Team Members X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Default category permissions The following table contains a list of the default category permissions for each of the default user groups. Use the following legend for the table below.

microsoft. For more information about groups and categories.286 Project Server 2010 Administrator's Guide  My Res = My Resources  My Tsks = My Tasks For example.aspx). resources. a user in the default Administrators group (who is associated to the My Organization category by default) has permissions allowed in the Administrators column in the table. My Res My Res My Org My Proj My Proj My Proj My Tsks My Org My Org My Org My Proj My Org. My Res My Tsks . This allows you to conveniently set a more or less restrictive set of permissions for different types of users to a group of projects. Permission Name Accept Task Update Requests Adjust Timesheet Approve Timesheets Assign Resource Build Team On Project Create New Task or Assignment Create Object Links Portfolio Project Resource Team Team Administrators Executives Managers Managers Managers Leads Members My Org My Proj My Org My Org My Org My Org My Org My Org My Org My Org My Org My Proj My Proj My Dir. see the Microsoft TechNet article ―Plan groups. resources. and RBS in Project Server 2010‖ (http://technet. and views. My Proj. a user in the default Project Managers group (who is associated to the My Organization and My Projects categories) has a different set of category permissions for the objects in the My Organization category. However. These category permissions only apply to all projects. categories.com/enus/library/cc197354. and views selected for the My Organization category.

287 Permission Name Delete Project Edit Enterprise Resource Data Edit Project Summary Fields Manage Basic Project Security Manage Resource Delegates Manage Resource Plan Open Project Publish Project Save Project to Project Server Save Protected Baseline View Enterprise Resource Portfolio Project Resource Team Team Administrators Executives Managers Managers Managers Leads Members My Org My Org My Org My Org My Proj My Res My Org My Proj My Org My Org My Proj My Org My Res My Org My Org My Org My Res My Org My Org My Org My Org My Org My Org My Proj My Proj My Proj My Tsks My Org My Proj My Org My Org My Org My Org. My Proj My Res .

288 Project Server 2010 Administrator's Guide Permission Name Data View Project Schedule in Project Web App View Project Site View Project Summary in Project Center View Resource Assignments in Assignment Views Portfolio Project Resource Team Team Administrators Executives Managers Managers Managers Leads Members My Or My Org My Org My Proj My Proj My Tsks My Org My Org My Org My Org My Org My Org My Proj My Proj My Proj My Proj My Proj My Proj My Tsks My Tsks My Org My Org My Org My Proj My Res My Proj My Tsks .

The following table shows the default categories and the default groups that can access each of them. Each category has a predefined set of category permissions for default user groups that have access to that category.com/ro-ro/library/cc197354(en-us). Note For more information about the relationship between groups and categories. and RBS in Project Server 2010‖ (http://technet. Category Name My Direct Reports My Portfolio Project Resource Team Team Administrators Executives Managers Managers Managers Leads Members X X X X X X . categories. In this article:   Categories Category permissions Categories Specific default groups are already associated with each of the default categories.microsoft.aspx).Project Server 2010 Default Categories 289 D Project Server 2010 Default Categories Microsoft Project Server 2010 creates seven default categories during installation. The following sections list the default settings for each category for Project Server 2010. see the TechNet article ―Plan groups. Each of the categories is configured to be accessed by specified default user groups.

However. Note For more information about category permissions. a user in the default Administrators group (who is associated to the My Organization category by default) has the permissions allowed in the Administrators column in the table. These category permissions only apply to all projects. For example. Use the following legend for the table below. This allows you to conveniently set a more or less restrictive set of permissions for different types of users to a group of projects. For more information about the relationship between groups and categories.com/ro-ro/library/cc197354(en-us). see the TechNet article ―Plan groups.microsoft. and RBS in Project Server 2010‖ (http://technet. resources. and views selected for the My Organization category. see Appendix A: Project Server 2010 category permissions. and views.aspx).290 Project Server 2010 Administrator's Guide Category Name Organization My Personal Projects My Projects My Resources My Tasks Portfolio Project Resource Team Team Administrators Executives Managers Managers Managers Leads Members X X X X X X X X X X X Category permissions The following table describes the default category permissions for each default group. categories.      My Org = My Organization My Dir = My Direct Reports My Proj = My Projects My Res = My Resources My Tsks = My Tasks . resources. a user in the default Project Managers group (who is associated to the My Organization and My Projects categories) has a different set of category permissions for the objects in the My Organization category.

My Res My Res My Org My Proj My Proj My Proj My Tsks My Org My Org My Org My Proj My Org.Project Server 2010 Default Categories 291 Permission Name Accept Task Update Requests Adjust Timesheet Approve Timesheets Assign Resource Build Team On Project Create New Task or Assignment Create Object Links Delete Project Edit Enterprise Resource Data Edit Project Summary Fields Manage Basic Project Security Portfolio Project Resource Team Team Administrators Executives Managers Managers Managers Leads Members My Org My Proj My Org My Org My Org My Org My Org My Org My Org My Org My Org My Proj My Proj My Dir. My Proj. My Res My Tsks My Org My Org My Org My Org My Proj My Res My Org My Proj My Org My Org My Proj .

292 Project Server 2010 Administrator's Guide Permission Name Manage Resource Delegates Manage Resource Plan Open Project Publish Project Save Project to Project Server Save Protected Baseline View Enterprise Resource Data View Project Schedule in Project Web App View Project Site View Project Summary in Project Center Portfolio Project Resource Team Team Administrators Executives Managers Managers Managers Leads Members My Org My Res My Org My Org My Org My Res My Org My Org My Org My Org My Org My Org My Proj My Proj My Proj My Tsks My Org My Proj My Org My Org My Org My Org. My Proj My Res My Or My Org My Org My Proj My Proj My Tsks My Org My Org My Org My Org My Org My Org My Proj My Proj My Proj My Proj My Proj My Proj My Tsks My Tsks .

Project Server 2010 Default Categories 293 Permission Name View Resource Assignments in Assignment Views Portfolio Project Resource Team Team Administrators Executives Managers Managers Managers Leads Members My Org My Org My Org My Proj My Res My Proj My Tsks .

294 Project Server 2010 Administrator's Guide .

Sign up to vote on this title
UsefulNot useful