67869084 Testing a Project Server 2010 Deployment

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. You bear the risk of using it.

Some examples depicted herein are provided for illustration only and are fictitious. No real association or

connection is intended or should be inferred.

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.

© 2010 Microsoft Corporation. All rights reserved.

2

This white paper is designed for enterprise project management system administrators and solution

testers as a guide for testing the functionality of a newly deployed Microsoft Project Server 2010

instance.

This guide walks through the various functionalities found in the Server Settings page, plus initial

testing to connect and check server communications with the Microsoft Project Professional 2010 client

application.

3

Table of Contents

Getting started with your Project Server Deployment ......................................................................... 5

Initial use setup ................................................................................................................................ 5

Check access to Project Web App 2010 ........................................................................................ 5

Check connectivity between Project Web App and Project Professional 2010 ................................ 5

Check that you can create a new project schedule, save the project to the server, and publish it to

Project Server ............................................................................................................................... 6

Check that your e-mail address is completed so that you can get notifications ............................ 7

Testing administrative task functionality ............................................................................................ 8

Security ......................................................................................................................................... 8

Configure users ......................................................................................................................... 8

Configure groups ....................................................................................................................... 9

Configure categories ................................................................................................................ 10

Configure security templates .................................................................................................... 11

Configure Project Web App permissions .................................................................................. 11

Enterprise data............................................................................................................................ 12

Configure Enterprise Custom Field definition ............................................................................ 12

Configure Enterprise Global ..................................................................................................... 13

Configure Enterprise Calendars ............................................................................................... 14

View the Resource Center ....................................................................................................... 15

View "About Project Server" ..................................................................................................... 16

Database administration .............................................................................................................. 16

Delete Enterprise Objects ........................................................................................................ 16

Force check-in Enterprise Objects ........................................................................................... 17

Daily schedule backup ............................................................................................................. 18

Administrative backup .............................................................................................................. 18

Administrative Restore ............................................................................................................. 19

OLAP database build settings .................................................................................................. 21

Look and feel .............................................................................................................................. 22

Manage views.......................................................................................................................... 22

Grouping formats ..................................................................................................................... 23

Gantt chart formats .................................................................................................................. 24

Quick Launch .......................................................................................................................... 24

Time and task management ........................................................................................................ 25

Configure fiscal periods ........................................................................................................... 25

Configure time reporting periods .............................................................................................. 26

Timesheet adjustment.............................................................................................................. 27

Configure line classifications .................................................................................................... 28

Timesheet settings and defaults [complex] ............................................................................... 29

Configure administrative time ................................................................................................... 35

4

Task settings and display ......................................................................................................... 35

Close tasks to update .............................................................................................................. 37

Queue ......................................................................................................................................... 38

Manage queue......................................................................................................................... 38

Queue settings ........................................................................................................................ 39

Operational policies ..................................................................................................................... 43

Alerts and reminders ................................................................................................................ 43

Additional server settings ......................................................................................................... 43

Server-side event handler configuration ................................................................................... 44

Active Directory resource pool synchronization ........................................................................ 45

Active Directory Resource Pool Synchronization ...................................................................... 45

Project sites ............................................................................................................................. 47

Project site provisioning settings .............................................................................................. 48

Bulk update project sites .......................................................................................................... 49

Workflow and Project Detail pages .............................................................................................. 50

Enterprise Project Types .......................................................................................................... 50

5

GETTING STARTED WITH YOUR PROJECT SERVER

DEPLOYMENT

Initial use setup

Check access to Project Web App 2010

Overview: This test scenario guides you through the steps to check whether you can open Microsoft Project Web App in your browser.

Prerequisites:

Ask the EPM administrator whether you have been granted the relevant access as permissions to access the Project Server.

Test Step Expected / Desired Results Actual Results (If deviation)

1. Open Internet Explorer 7 or 8.

2. Type the URL http://<ServerName>/PWA/ Project Web App will load.

3. Click the OK button. Project Web App should open, displaying the PWA web pages that you are allowed to see.

4. Add the URL to your list of trusted sites in Internet Explorer.

PWA URL will be added to the list of trusted sites.

Check connectivity between Project Web App and Project Professional 2010

Overview: In order to work with Microsoft Project Server 2010 from Microsoft Project Professional you have to configure your Project Server accounts.

Prerequisites: None


1. Open Project Professional 2010

2. Click File / Info and then Manage Accounts. Opens the Project Server accounts pane.

3. Click Add. Accounts properties page loads.

4. Enter your account name.

5. Enter Project Web Server URL – same as the PWA URL.

http://ServerName/PWA/

6. Select use Windows account.

7. Click set as default account

8. Click OK.

9. Click OK. New account should be added.

10. Close Project Professional.

11. Re-open Project Professional. Project Professional should login

6

to Project Server by using the new account you have configured.

12. To confirm the connection: Click File Open. List of projects on the server should appear.

Check that you can create a new project schedule, save the project to the

server, and publish it to Project Server

Overview: Creating new projects, saving the projects to the server, and publishing the projects to the server is basic to the test scenarios in this document. This test ensures that you are able to perform some of the core actions.

Prerequisites:

Security permissions to Project Server to save new projects.


1. Open Project Professional 2010.

2. Click File / New and then Project Server Templates.

Templates pane should appear.

3. Select a template (example: Infrastructure Deployment) and click OK.

Template selected should load in Project Professional.

4. Click File/Save As. "Save to Project Server" dialog box appears

5. Important: Prefix the name of the project with your name:

Example: RobHoo_Engineering_01

Enter the name of your project and then click Save.

Project will be saved to the server

OR

The system may prompt you with the Enterprise Standard Calendar dialog – Click yes if you accept the changes. The system will save the project to the server.

6. Important: Project Professional saves the project to a local cache – the cache then synchronizes with Project Server after the change.

To view the cache status:

Click Tools, local Project Cache/View Status

Cache Status dialog box will appear with a list of projects.

7. Click File Publish – this will send the request to publish assignment, sync the Published database and Reporting database.

You can add a new column, “Publish,” that governs (at the task level) whether team members assigned to the task will see it under their statusing area.

The project will be published to the server.

You may be asked to create a new PWA site for this project.

7

Check that your e-mail address is completed so that you can get notifications

Overview: When the Enterprise resource pool was migrated, all the e-mail addresses were cleared. This was done to ensure that team members would not get notifications when projects are published. Updating the e-mail address also allows you to see where the administrator configures these settings.

Pre-requisites:

Security permissions in order to edit users details

Test Step Expected / Desired Results Actual Results

(If deviation)

1. Open Project Web App. Project Web App will load.

2. Click Server Settings on the left column under Settings.

Server Settings page appears.

3. Click Manage users. List of users appears.

4. Enter your name in the Search box and then click the search button.

List of users should appear based on the search criteria.

5. Click your user name. Page will display your details in edit mode.

6. Complete the identification information :

E-mail address

Identification information should be completed.

7. Click the Save button. E-mail address and other fields that have change will be updated.

8. In the lab: assign yourself to a project task to check that you get the notifications.

8

Testing administrative task functionality

Security

Configure users

Overview: In the event that a user does not exist in the system, the account can be created by using the Add Users functionality. This test scenario describes the steps for creating new resources/users in Project Server 2010. These steps are provided so that the administrator can add the relevant users/resources if they have not been added already.

Pre-requisites:

Security permissions in order to create a new resource.


(If deviation)


2. Click Server Settings. Server settings page appears

3. Click Manage users. List of users displays.

4. Click the new user button New user page displays.

5. Important – Mark the User can be assigned as a resource check box.

This setting will ensure that the resource account is created when the user account is created.

6. Complete the identification information :

Display name [required field]

E-mail address

RBS [Resource Breakdown Structure]

Initials

Hyperlink name

Hyperlink URL

Identification information should be completed.

7. Complete the user authentication information.

Authentication information should be completed.

8. Complete the assignment attribute information:

Check/Uncheck resource can be levelled.

Base Calendar

Default booking type [example: Can set all resources to default to the proposed booking type.]

Timesheet manager [Person who approves timesheets – example: Could be team lead]

Assignment attribute information should be completed.

9. Check/Uncheck Synchronize Tasks in Exchange Server Details information.

Will synchronize project tasks with the resource’s tasks in Exchange Server mailbox.

10. Select the Department:

Click the button to select the resource

Selected Resource Department will appear in the text box.

9

department.

11. Enter Resource Custom Fields:

Select Yes/No on used for placeholder capacity.

Selected custom field will appear in the text box.

12. Complete the security groups. Groups selected should show in the right hand box.

13. Complete the security categories.

Make sure you complete the permissions for the users for the specific category.

Categories should be added to the Categories box with the related permissions.

- Complete the Group fields:

- Group

- Code

- Cost Center

- Cost Type

Group fields should be completed.

14. Complete the team details

- Team Assignment Pool

- Team Name

Team details should be completed.

Configure groups

Overview: When the data is migrated the existing Project Server groups will be created in Project Server 2010. This test scenario allows the administrator to do the following important tasks:

a. Check that the existing groups have been created. [All groups must be checked] b. Check what new features have been added to the groups. [Example: New security features]

Pre-requisites:

Must have security permissions to administer project server groups.

Test Step Expected / Desired Results Actual Results (If

deviation)


2. Click Server Settings. Server settings page appears.

3. Click Manage Groups.

[Located under the security section]

List of Groups displays

4. Click one of the groups. Details of groups will be displayed

5. Check that all the fields for the group are populated.

Group information should confirmed as correct

6. Check that Group information is correct. Group information should confirmed as correct

7. Check that the correct users belong to the group.

Users should be confirmed as correct

8. Check that the correct security categories belong to the group.

Security categories should be confirmed as correct

10

9. Check that the Global Permissions are correct.

IMPORTANT: Take note of all the new permissions.

Example: New Section on Time & Task Management.

Global Permissions should be confirmed as correct.

10. Click the Save button. Changes to the group should be updated to the server – open the group again to confirm that you are satisfied with the changes.

Configure categories

Overview: When the data is migrated, the existing Project Server categories will be created in Project Server 2010. This test scenario allows the administrator to do the following important tasks:

c. Check that the existing categories have been created. [All categories must be checked] d. Check what new features have been added to the categories. [Example: New security

features]

Pre-requisites:

Must have security App administer project server Categories.


(If deviation)



3. Click Manage Categories.


List of Categories will be displayed.

4. Click one of the categories. Details of Categories will be displayed.

5. Check the name and description are correct.

Name and description should be confirmed as correct.

6. Check the users and groups that belong to the category are correct.

NOTE: ―*‖ indicates that it is a group.

Users and groups that belong to the

category should be confirmed as

correct.

7. Check the projects that belong to the group.

Take note of any changes in the security permissions for the project.

Projects that belong to the category

should be confirmed as correct.

8. Check the resources that belong to the group are correct.

Resources that belong to the category

should be confirmed as correct.

9. Check the resource security permissions.

Take note of the new security permissions.

Resource security permissions should

be confirmed as correct.

10. Check the views that belong to the category.

PWA Views belonging to the category

should be confirmed on screen as

correct.

11

Configure security templates

Overview: Security templates are used when you want to allocate permission to groups/users. This is accomplished with dropdown displays which can be used to assign permissions.

Pre-requisites:

Must have security service permissions to administer project server Security templates.

Test Step Expected / Desired

Results Actual Results (If deviation)



3. Click Manage Security templates.


List of Security templates will be displayed.

4. Click one of the security templates.

5. Check the name and description of the template.

Name and description should be confirmed as correct.

6. Check the category permissions.

Take note of the new permissions:

Example: Approve Timesheets

Category

permissions for the

security template

should be confirmed

as correct.

7. Check the global permissions

Take note of the new permissions:

Example: Manage Timesheet and Financial Periods.

Global permissions for the security template should be confirmed as correct.

8. Click Save. Changes are saved to the server.

Configure Project Web App permissions

Overview: Project Web App permissions control which global and category permissions are enabled on Project Server. An administrator can use Project Web App permissions to deny service to all Project Server users for a particular feature in Project Professional or Project Web App. If a Project Web App permission is enabled, the equivalent global or category permission is enabled for users with those permissions. For example, if you deny the Delete Project Web App permission, users cannot delete projects, regardless of whether they have the Delete Project category permission

Pre-requisites:

None

12





3. Click Project Web App Permissions.

[Located under the Security section]

Project Web App Permissions page will appear.

4. Confirm that the PWA permissions migrated correctly.

Take note of the new permissions in the server.

5. Click Save. Changes will be saved to the server.

Enterprise data

Configure Enterprise Custom Field definition

Overview: The following standard custom fields cannot be deleted or renamed:

Cost Type

Health

RBS

State

Team Name In this scenario we walk through the creation of a new custom field.

Pre-requisites:

Must have security permissions to administer Custom Field Definitions.



1. Open Project Web App. Project Web App will load


3. Click Enterprise Custom Field Definition.

[Located under the Enterprise Data section]

Enterprise Custom Field Definition page will appear.

4. Click the new Field button.

[Located under the Enterprise Custom Fields Section]

New Field Web Page will appear.

5. Enter the name of the field.

13

Example:

Project Sponsor

6. Enter the Entity or Type.

Example: It is a project field of type text.

7. Enter the Custom attributes.

Example: We can link the field to a lookup table (which simulates a tree-view/drop-down of the data)

In this example we will create a text field only.

None. Radio button is selected.

8. Select Department to assign the custom field to a specific set of users in the selected department.

Department is displayed in the text box.

9. Enter the values to display.

Example:

If you want the field to display a graphical indicator you can select the graphical indicator option.

Select the Data option only

Data option selected

10. Check/uncheck whether the behavior will be controlled by workflow, and whether this field is required to have information.

Box is checked/unchecked.

Radio button for No/Yes is selected.

11. Click Save. Field will be created.

Configure Enterprise Global

Overview: Certain enterprise customizations are made from within the Project Professional desktop client by checking out the Enterprise Global template. Settings made in this way affect all users who connect to this server. Customizations of the following items are made from within Project Professional: •Grouping •Maps •Tables •Filters •Views •Reports •Modules When you click the Configure Project Professional button, Project Pro opens, and the enterprise global is automatically checked out. You cannot check whether your enterprise global configurations are correct.

Pre-requisites:

Permissions to modify the enterprise global.

Test Step Expected / Desired Actual Results (If deviation)

14

Results



3. Click Enterprise Global.

[Located under the Enterprise Data]

4. Click the Configure Project Professional button.

Project Professional will be opened, enterprise global will automatically be checked out.

5. Check that the specific enterprise global configurations are correct.

Confirmed that the Specific Configurations are correct.

Configure Enterprise Calendars

Overview: Enterprise Calendars can be created for the working/non-working times of resources. In this scenario we want to create an IT Department Calendar that specifies that there are 24x7 working times. Fifteen exceptions can be created per calendar.

Pre-requisites:

None





3. Click Enterprise Calendars.


Enterprise Calendars page appears.

4. Click New Calendar. Project Professional opens, displaying the Change Working Time pane.

5. Enter a name for the new enterprise calendar.

6. Click the Exceptions tab.

7. IMPORTANT: If you define it and mark it as an exception, we indicate that it is a non-working day.

15

Example : a Public Holiday

Type in a name of the exception.

Example:

National Public Holiday

8. Enter the start date and end date of the exception.

Example:

Start: 2010/01/01

End: 2010/01/01

9. Click the Work Weeks tab.

NOTE: Using this feature you can set the working and non-working time defaults.

Click the Details tab.

Details for the default will show.

10. Select the days – Sunday to Saturday Days will be selected.

11. Click the Set days to these specific working times button.

Input the ―from‖ & ―to times.‖

12. Click the OK button. Dialog box will close.

13. Click the OK button. Working times dialog box will close.

14. Click the Save button in Project Professional to save the details to the server.

Calendar details will be saved to the server.

View the Resource Center

Overview: The Resource Center contains all resources for enterprise projects.

Pre-requisites:

None





3. Click Resource Center.


Resource Center page will appear.

4. Verify that the expected resources are displayed.

The number of resources is confirmed as correct.

16

View "About Project Server"

Overview: This web page is for information purposes. It allows you to view the number of active Project Server users and the number of Project Professional users. The number of Project Server users is calculated by counting the number of active Project Server user accounts that have permissions to log on. The number of Project Professional users is calculated by counting the number of active Project Server user accounts that have permissions to log on as well as the permission 'Log on to Project Server from Project Professional'.

Pre-requisites:

None





3. Click About Project Server.


About Project Server dialog box appears.

4. Check that the number of Project Server and Project Professional users is correct.

The number of users is confirmed as correct.

Database administration

Delete Enterprise Objects

Overview: This page allows the administrator to delete: Projects, proposals, and activities Resources and users Status Report responses Timesheets There are four databases in Project Server 2010:

Draft: when opening/saving projects from Project Professional it is done to/from the Draft database

Published: When the publish option is selected in Project Professional the data gets saved in the Published database.

Reporting: When published a copy of the data is stored in the Reporting database – all reports run from the reporting database

Archive: When projects are archived they are stored in the Archive database In this scenario we delete a project From the Draft database and its associated SharePoint site.

Pre-requisites:

None




17


3. Click Delete enterprise objects.

[Located under the Database Administration section]

Delete enterprise objects page appears.

4. Click Projects. List of projects will appear in the grid below.

5. Check: Delete the associated SharePoint Foundation Sites option.

6. Select the projects you would like to delete from the grid below.

NOTE : You are able to select Multiple projects for delete

7. Click the Delete button. List of projects will be deleted.

Force check-in Enterprise Objects

Overview: Sometimes enterprise objects do not get checked back into the system. This feature allows the administrators to perform a force check-in operation on the object. The following objects can be checked-in:

Enterprise Projects

Enterprise Resources

Enterprise Custom Fields

Enterprise Calendars

Lookup Tables for Enterprise Custom Fields

Resource plans.

Pre-requisites:

Security App to Check-in Enterprise Objects





3. Click Force Check-in Enterprise Objects

[Located under the Database Administration]

Force Check-in Enterprise Objects page appears.

4. Select the type of object you want to check in.

List of the selected type will display.

5. Click the Check-in button. Object will be checked back in to Project Server.

18

Daily schedule backup

Overview: Use this page to define your daily backup schedule to support item-level restoration. Increasing the project retention policy affects your archive database. The more versions you keep, the more space is required. Item-level backup is designed to work with, not instead of, SQL Server database backups. The following items can be backed up:

Projects

Enterprise Resource Pool and Calendars


Enterprise Global

View Definitions

System Settings

Category and Group Settings

Pre-requisites:

None





3. Click Schedule Backup.

[Located under the Database Administration section]

Schedule Backup web page appears.

4. Set the Project Retention Policy [versions].

5. Next to the projects item, set the option drop-down to Schedule.

6. Allocate a time.

7. Click Save. Project Server will create a backup of the item selected according to the schedule.

Administrative backup

Overview: Item-level backup is designed to work with, not instead of, SQL Server database backups. The following items can be backed up:

Projects

Enterprise Resource Pool and Calendars

19


Enterprise Global

View Definitions

System Settings

Category and Group settings

Pre-requisites:

None





3. Click Administrative Backup.


Backup web page will appear.

4. Select the object you would like to back up. In this example we will back up projects.

Check Projects

5. Click the Backup button. Request will be sent to the queue for processing.

6. Open the queue:

Server settings/queue

Queue should display details of the backup request.

Administrative Restore

Overview: Restore individual item-level objects stored in your archive database.

Pre-requisites:

None





3. Click Administrative Restore


Restore Web Page will appear.

4. Select the item type you would like to restore.

List of objects will refresh based on the item type selected.

5. Click the item and then click the Restore button.

The system will send the item to the queue

20

to be restored.

21

OLAP database build settings

Overview: The cube build setting page allows the administrator to schedule when the cube should be built and the date ranges used when building. The date ranges are important because they affect the following:

1. Time the cube takes to build 2. Amount of data that can be analyzed. For example: You may only want to build a cube for 2009

data only. By using the data range options. you can select to run it from 1/1/2009 to 12/31/2009

In this scenario we create a new build.

Pre-requisites:

None





3. Click OLAP Database Build Settings [Located under the Database Administration section]

OLAP Database Management page will appear.

4. Click New. OLAP Database Build Settings page will appear.

5. Enter Analysis Services Server and the Analysis Services database to be created.

6. Enter the Project Department for the OLAP database.

7. Enter the Resource Department to be used for the OLAP database.

8. In Database Date Range settings select the Use the fixed date range specified below:

Select the start date: 1/1/2009

Select the end date: 12/31/2009

9. In the OLAP Database Update Frequency section: Do not select the update periodically option. The reason is this: In this example we only want to build the 2009 OLAP database once – there is no need to rebuild it periodically as it is in the past.

Immediately retry the cube update if scheduled time fails because of queue down time.

10. Click Save. You return to the OLAP Database Management

22

page with the newly created OLAP Database name.

11. Click Build Now. Your OLAP Database is built.

Look and feel

Manage views

Overview: Take note of all the different types of views that can be created/modified.

Project

Project Center

Resource Assignments

Resource Center

My Work

Resource Plans

Team Tasks

Team Builder

Timesheet

Portfolio Analysis

Portfolio Analysis Project Selection

Pre-requisites:

None

Test Step Expected / Desired Results Actual Results (If

deviation)



3. Click Manage Views.

[Located under the Look and Feel]

Manage views web page will appear.

4. Click the new view button.

5. Select the view type Project.

6. Select Task.

7. Select the fields you want to add : Example: Task Name, Start Date

8. Set the width of each field by typing the width value.

Width of field will change according to the width input.

9. Input the format settings for the view:

Example:

Gantt Chart View

Grouping: Group 1 then by group 2

Sorting: Task Name: Ascending

23

10. Click the Filter button to build filter criteria for the view.

The dialog box will appear, allowing you to build filter criteria for the view.

11. Select the security categories that can see the view.

12. Click the Save button.

13. Open Project Center, select the new view you have created, and check that the view is built according to the criteria selected.

Grouping formats

Overview: You can select a grouping format for the Tasks section and up to 10 grouping formats for views. The grouping formats for views apply to Project Center, Resource Center, Project, and Assignment views. Important: When you are creating a view you can link it to the grouping format.

Pre-requisites:

None





3. Click Grouping Formats.

[Located under the Look and Feel section]

Grouping Formats web page will display

4. Select Grouping 1. Level 1-4 will show for the selected view.

5. Change the colors of the groupings.

Example:

Level 1 – Yellow

Level 2 – Blue

Level 3 – Green

Level 4 – Purple

6. Click Save.

7. Open a view in Project Center and select Grouping 1: Note that the view selected needs to be linked to Grouping 1.

When the view is selected and the grouping is applied, the colors for levels 1-4 should be displayed in the groupings.

24

Gantt chart formats

Overview: Project Web App can display a Personal Gantt Chart on the Tasks page and can display up to 19 different types of Gantt Chart views in the Views section.

Pre-requisites:

None





3. Click Gantt Chart Formats.


Gantt Chart Formats web page will appear.

4. Select Gantt 1 from the Gantt Chart drop-down list.

Gantt Chart 1 items will appear in the grid.

5. Change the color of the summary task from black to green.

6. Click the Save button.

7. Open Project Center in PWA. List of projects will appear.

8. Click one of the projects — one that you know has summary tasks.

Project detail will appear with the summary tasks showing in green and not black.

Quick Launch

Overview: The left hand menu in Project Web App is dynamically built when loaded. The quick launch admin feature allows the administrator to add links to the page with ease. A parent menu and child menu can be created. In this scenario we add a link for the PMO FAQ.

Pre-requisites:

None





3. Click Quick Launch. Quick Launch web

25

[Located under the Look and Feel] page will appear.

4. Select the expand menu items for all sections option.

5. Click the new link button.

6. Select the new heading option, which allows you to create a parent level menu.

7. Enter the name of the new parent menu.

8. Enter in the URL of the heading – paste your PWA web page home page in the URL if you do not have one.

[This will ensure the page always navigates back to itself.]

9. Select yes – to display the menu in the quick launch.

10. Click the new Link button again – this is so we can create the child menu option.

11. Enter the name of the child menu.

Example: FAQ

12. Enter the URL of the SharePoint list where the PMO FAQs are stored.

13. Select the heading PMO – this was the parent menu previously created.

14. Select yes to display the link.

15. Click the OK button to save.

16. Look in the left hand menu bar — you should see the new parent & child menus created.

Click the FAQ link.

A new web page will be loaded with the FAQ SharePoint list

Time and task management

Configure fiscal periods

Overview:

Fiscal periods are primarily used in timesheet adjustments and enterprise reporting. You can create, modify, and delete financial period definitions in this section.

Pre-requisites:

Permissions: Manage Timesheet and Financial Periods



26



3. Click Financial Periods.

[Located under the Time and Task Management section]

Financial Periods web page will appear.

4. Select an undefined fiscal period to manage – example: 2012.

5. Click the Define button. Page will refresh with detailed sections.

6. Select a Fiscal Year Creation model.

Example:

4,5,4 method.

7. Define Period Naming conventions.

Examples:

Enter the Prefix: FY

Enter Numbering Sequence: 01

Enter Suffix: FP

8. Optional: If you want to change the end date for a specific month, click the end date cell for a specific month.

Date picker should be available for you to select a specific date.

9. Click the ―save to create‖ button. Page will refresh with the list of fiscal periods that have been created in the system,

10. 10 NOTE: You can click the Delete button to delete the defined fiscal period.

Configure time reporting periods

Overview: Timesheet periods can be created in bulk, which saves time for the administrator. It is important that the timesheet periods are correctly defined to begin with as they affect many aspects of the solution.

Pre-requisites:

Permissions: Manage Timesheet and Financial Periods




2. Click Server Settings. Server settings page

27

appears.

3. Click Time Reporting Periods.


Timesheet Periods web page will appear.

4. Define Bulk Period Parameters:

Example: Create 52 periods.

Enter the start date as : 1/1/2010 – this way we create periods for a full year

Define the period length: 7 Days – example: If no one in the organization works /reports time on Saturdays/Sundays you can set it to 5 days.

After you click Save the changes will be saved to the server.

5. Define Batch Naming Convention:

For multiple reporting periods you can set a unique name for each period.

After you click Save the changes will be saved to the server.

Timesheet adjustment

Overview: You can duplicate timesheet lines for business purposes or accounting reasons. To do this, define timesheet line classifications, which will become the unique identifiers for a timesheet line. By default the system creates a standard classification. In this example: We will create three timesheet classifications to help identify timesheet line items.

Pre-requisites:

None





3. Click Timesheet Adjustment.


Timesheet approval page will appear, allowing you to view approved timesheets, available timesheets, and unsubmitted timesheets.

28

Configure line classifications

Overview: You can duplicate timesheet lines for business purposes or accounting reasons. To do this, define timesheet line classifications, which will become the unique identifiers for a timesheet line. By default, the system creates a standard classification. In this example, we create three timesheet classifications to help identify timesheet line items.

Pre-requisites:

None





3. Click Line Classifications.


Line Classifications web page will appear.

4. Click the new classification button A new row is highlighted

5. Input the name and description of the line classifications.

Example:

Custom Classification 1



6. Click Save. New timesheet classifications will be created.

29

Timesheet settings and defaults [complex]

Due to the complexity of this admin setting, it has been divided into a number of sub-test scenarios.

How timesheets are displayed in Project Web App

Overview: Timesheets can display planned work, overtime, and non-billable time. To disable the overtime and non-billable timesheet types, clear the check box to the right.

Pre-requisites:

None





3. Click Timesheet Settings and defaults.


Settings and defaults page will load.

4. Open another Internet Explorer PWA session, and then click the My Timesheet menu.

My Timesheet view will open.

5. Click the Create button to create a new timesheet.

New timesheet page will appear.

Note: The overtime and non-Billable time tracking sections will appear if the check box is selected.

6. Toggle the setting on the admin page and then refresh the timesheet view.

Note: The overtime and non-Billable time tracking sections will be displayed or not be displayed.

7. IMPORTANT: If you don’t see the toggle taking place, then you need to check the actions bar on the My Timesheet page to check that the user has not chosen to hide this as a personal setting.

Click the actions bar, select the show billable work. If the menu is greyed out then the admin has cleared the display setting.

30

Default timesheet creation mode

Overview: Users can enter data on their timesheets against projects or current assignments. This setting allows site-level consistency for the type of default timesheet users see. Example 1: When you create a new timesheet it defaults to using the current task assignments. This way the user does not have to select the current task assignments when creating a new timesheet. Example: 2: Users start with a blank timesheet because they prefer that no pre-population be done.

Pre-requisites:

None





3. Click Timesheet Settings and Defaults.



4. Locate the section – Default timesheet creation mode.

Check the No – Population option

5. Click Save.

6. Open another instance of Project Web App.

7. Click the My Timesheets menu.

8. Click Create. The system will create a new timesheet.

9. If no pre-population is selected then non-project task assignments will appear on the timesheet.

IMPORTANT: Administrative Time will still show as default line items if the administrator has set them to show.

This feature is for project-related items.

31

Timesheet grid column units

Overview: Timesheets support weekly or daily tracking. When Weekly is specified, each column in the timesheet represents seven days, and the date in the column displays the first day of the week.

Pre-requisites:

None








4. Navigate to the Timesheet Grid Column Units.

5. Change the unit to weeks.

6. Click Save.

7. Open the ―My Timesheet‖ page.

8. Look at the date ranges; they will show as weeks and not days.

9. Change the setting back to days and then click Save.


11. Look at the date ranges; they will show as days and not weeks.

Default reporting units

Overview: Timesheets support viewing and reporting in either hours or parts of a day. You can specify here which units are used.

Pre-requisites:

None








4. Navigate to the Default reporting Units

32

Page.

5. Update the :

Days

Standard timesheet day = 8

Number of hours in a standard work week = 40

6. Click Save.


8. Try to capture a timesheet outside of the ranges specified and submit it.

The system should prevent submission of a timesheet outside the defined settings.

Hourly reporting units

Overview: Accounting systems, customers, or internal business policies might restrict how time can be entered. If you use team resources, be sure to consider such restrictions when you set these values.

Pre-requisites:

None

#No Test Step Expected / Desired







4. Navigate to the Default reporting Units Page.

5. Update the :

Maximum Hours per Timesheet: 50 Minimum Hours per Timesheet: 40

Maximum hours per day: 15

6. Click Save.


8. Try to capture a timesheet outside of the ranges specified and submit it.

The system should prevent the TM from submitting a timesheet outside the settings.

33

Timesheet policies

Overview: The administrator can use settings in this section to help you comply with accounting and regulatory policies. You can restrict users from reporting time in future timesheet periods. Example: Contoso may want to restrict all users from capturing time for future periods. You can restrict users from specifying timesheet lines that cannot be verified against Project Server items. Example: Will you allow TMs to add lines not associated to any kind of project to a timesheet?

Pre-requisites:

None








4. Navigate to the Timesheet Policies page.

5. Update the :

Allow Future Time Reporting = Uncheck

Allow Unverified line items = uncheck

6. Click Save.


8. Try to capture future time.

The system should prevent the reporting resource from capturing future time.

9. Try to add line items by clicking on the Add Lines button.

System should prevent submitting unverified line items.

Auditing

Overview: You can use timesheet auditing to record changes saved to timesheets during creation, approval, and later adjustments. We recommend that this is turned on from the start of the implementation so that a full history is maintained. Important: this data could consume large amounts of space in SQL Server, so you need to work with IT to ensure that enough disk space has been allocated.

Pre-requisites:

None

#No Test Step Expected / Desired


1. Open Project Web App. Project Web App will

34

load.





4. Navigate to the Auditing section.

5. Check the Enable Timesheet auditing item.

6. Click Save. The system will log creation, approval, and adjustments to timesheets.

7. Use the purge log feature with caution as you may not want to lose this data.

Purge is permanent

Approval routing

Overview: Fixed Approval routing disables the ability to change the next approval during timesheet submission. The transaction comment is also disabled for timesheet submitting; therefore users should use the timesheet header comment instead.

Pre-requisites:

None








4. Navigate to the Approval Routing section.

5. Clear the fixed approval routing check box.

6. Click Save. The system will prevent the timesheet App rover from being changed.

35

Configure administrative time

Overview: Administrative time allows you to track exception time as well as any other categorized non-project time spent by employees and tracked by your company. Each category can be set to require managerial approval before employees commit time. Additionally, each category can be set to display by default on each user's timesheet. To specify this setting, select the Always Display option. By default, the following administrative time options are made available. [Clear the Always Display option if you do not want the options to always be displayed on the timesheet.]

1. Administrative 2. Jury Duty 3. Sick Time 4. Vacation

In this example we create maintenance time.

Pre-requisites:

None





3. Click Administrative time.


Administrative time web page will appear.

4. Click the New Category option.

5. Enter the name of the new category.

Example: Maintenance Work_Don’t Always Display

Training_Always Display

6. Click Save. Admin time categories will be created.

These will now be available on the ―My timesheets‖ page.

Task settings and display

Overview: Note: This is a global configuration for the instance of Project Server being configured.

36

Pre-requisites:

None





3. Click Administrative time.


Administrative time web page will appear.

4. Tracking method options:

% of work complete. Resources report the percentage of work they have completed, from 0 through 100%.

Actual work done and work remaining. Resources report the actual work done and the work remaining to be done on each task.

Hours of work done per period. Resources report their hours worked on each task per period.

In this example:

1. Select Percentage of work complete.

2. Check the form project managers to use the progress reporting method for all Projects.

5. Reporting Display:

Resources should report their hours worked every day.

Resources should report their total hours worked for a week.

In this example:

Hours worked each day option.

6. Select the Only allow task updates via Tasks and Timesheets check box if your business requires that the project manager not be able to change actual time worked.

7. Select the Time entry by Timesheet only check box if you want to ensure that your users always report the same timesheet hours as task progress. Users must then import from a timesheet to update task progress and submit.

8. Define Near Future Planning Window:

Specify the number of reporting periods to include in the Near Future Planning

37

Window on the Tasks page.

In this example: set it to 5 days.

9. Click Save. Changes will be saved to the server.

Close tasks to update

Overview: The "Close tasks to update" feature lets you select the project for which you want to lock down tasks. These changes will not take effect until the next time this project is published. Publishing a project will publish all applied task updates and any other changes that were made to the plan. To preview all pending changes you can open the project in Microsoft Project Professional 2010 before publishing.

Pre-requisites:

None



1. Open Project Professional.

2. Create a new project.

3. Assign yourself to all the tasks on the schedule

4. Save the project. The project will be saved to the server.

5. Publish the project. The project will be published. The Task assignments will be available on your My work page.

6. Open PWA.

7. Click the My Tasks link [left menu]. List of task assignments will appear.

8. Update some of the fields. The system will allow you to edit the fields.

Next we CLOSE the task to updates, preventing future updates to the task being made.

NOTE: The task will still appear on the timesheet view. However, it will be in a read-only state.



11. Click Close tasks to update.


Close tasks to update web page will appear.

12. Select a project from the list. Lists of tasks for the

38

project will appear.

13. Check the tasks that you want to close.

14. Click the update/save button.

15. Tasks will now be closed to updates. IMPORTANT: take note of the rules described in the summary of this test scenario.

16. Open the My Work / Tasks Page again and try to edit some of the values for the tasks that you know have been closed to updates.

The system will prevent you from capturing time against a closed task – the task will be read-only.

IMPORTANT: The task will still appear on the timesheet.

Queue

Manage queue

Overview: See Project Server 2010 documentation on TechNet for details on how the queue works from a technical perspective. Example; When a save transaction is performed, the request is sent to the queue and the client side cache and queue will ensure the transactions are completed. Example: When a new resource is created, the request will be sent to the queue, the queue will create the resource. Example: When you are publishing, the queue manages the synchronization transactions between the Draft database, Published database, and Reporting database. The queue is read-only. Only Applications like Project Professional and Project Web App can make entries into the queue.

Pre-requisites:

None





3. Click Manage Queue.

[Located under the Queue section]

Manage Queue Page will appear.

4. Open Project Professional and publish a project.

5. Refresh the queue page. Page should display the list of items in the queue including the

http://technet.microsoft.com/en-us/library/cc197746.aspx

39

project publish transaction.

6. Open the Delete enterprise objects page and then delete a timesheet.

7. Open the queue page again after issuing the timesheet delete transaction.

Page will display the timesheet delete transaction.

8. Take note of the following:

Progress of the queue – % complete is shown for each transaction in the queue.

Job State – example if the queue transaction fails it will provide the details of why.

If an error occurs, click the link in the error column – this will load a web page with a detailed page about the error.

Queue settings

Overview: There are two queues in Project Server 2010.

1. A Timesheet queue – processed transactions related to Timesheets 2. A Project queue– processed transactions related to Projects/Resources

Pre-requisites:

None





3. Click Queue Settings.

[Located under the Queue section]

Queue Settings page will appear.

Below is an explanation of each:

4. Queue Type

Choose the Queue to which the settings will apply. The options are either the Project Queue (which processes job types such as Project Save and Publish) or the Timesheet Queue (which processes job types such as Timesheet Save and Notifications). Note that all the Queue Settings are per PWA site, and per Queue Type.

5. Maximum Number Of Job Processor Threads

The Queue is multi-threaded, which enables multiple jobs to be processed at the same time. If the number of current job processor threads equals the limit, no more threads are created. Note that this setting is per PWA site, and per Queue Type.

40

Minimum: 1

Maximum: 20

Default: 4

6. Polling Interval (in milliseconds)

This is the time interval at which the Queue polls the database for new jobs.

Minimum: 500 (.5 second)

Maximum: 300000 (5 minutes)

Default: 1000 (1 second).

7. Retry Interval (in milliseconds)

If job processing fails due to transient issues (like a SQL Deadlock), instead of failing the job, the Queue will wait for the Retry Interval to elapse and then retry the job.

Minimum: 0 (immediately retry)


Default: 1000 (1 second)

8. Retry limit

If job processing fails due to transient issues (like a SQL Deadlock), instead of failing the job, the Queue will retry the job. The number of retries is bound by the Retry Limit.

Minimum: 0 (no retries)

Maximum: 100

Default: 5

9. SQL retry interval (in milliseconds)

The Queue polls the database at regular intervals to retrieve jobs that need processing. If this query fails due to a transient SQL problem (like a SQL Deadlock), the Queue will wait for the SQL Retry Interval to elapse and then retry the query.

Minimum: 0 (immediately retry)

Maximum: 60000 (1 minute)


10. SQL retry limit

The Queue polls the database at regular intervals to retrieve jobs that need processing. If this query fails due to a transient SQL problem (like a SQL Deadlock), the Queue will retry the query after the SQL Retry Interval has elapsed. The number of retries is bound by the SQL Retry Limit.

Minimum: 0 (no retries)

Maximum: 100

Default: 5

11. SQL Timeout (in seconds)

The Queue makes SQL calls for retrieving and executing jobs. This setting controls the timeout value for all such calls. If any job fails due to a SQL Timeout error, administrators can increase this setting and retry the job.

Minimum: 30

Maximum: 86400 (1 day)

41

Default: 300 (5 minutes)

12. Clean-up Interval (in hours)

This setting determines the frequency with which the Queue Cleanup job runs. The time of day at which the Queue Cleanup job runs is determined by the Cleanup Interval Offset setting.

Minimum: 1

Maximum: 100000

Default: 24 (1 day) Cleanup Interval (in hours)


Minimum: 1

Maximum: 100000



Minimum: 1

Maximum: 100000



Minimum: 1

Maximum: 100000

Default: 24 (1 day)

13. Clean-up Interval (in hours)


Minimum: 1

Maximum: 100000

Default: 24 (1 day)

14. Clean-up Interval Offset (in minutes)

This setting is the number of minutes after 12:00 a.m. (midnight) at which the Queue Cleanup job will run. The frequency with which the Queue Cleanup job runs is determined by the Cleanup Interval setting.

Minimum: 0 (cleanup 12:00 a.m.)

Maximum: 1439 (cleanup at 11:59 p.m.)

Default: 0 (cleanup at 12:00 a.m.).

15. Clean-up Age Limit For Successful Jobs (in hours)

This setting determines the age threshold at which successful jobs can be purged when the Queue Cleanup job runs. The age of each job is determined by the completed date and time. For example: If a job succeeded at 2/1/2007 10:41 p.m. and the Queue Cleanup job runs at 2/2/2007 11:55 p.m., then the job will be purged (assuming the Cleanup Age Limit For Successful Jobs was 1 day). Because the number of successful jobs is usually high, the Cleanup Age Limit For Successful Jobs setting is

42

usually set to a low value of 24 (1 day).

Minimum: 1

Maximum: 100000

Default: 24 (1 day)

16. Clean-up Age Limit For Non-Successful Jobs (in hours)

This setting determines the age threshold at which any job in a completed, non-successful state (example: Failed But Not Blocking Correlation) can be purged when the Queue Cleanup job runs. The age of each job is determined by the completed date and time. For example: If a job was cancelled at 2/1/2007 10:41 p.m. and the Queue Cleanup job runs at 2/2/2007 11:55 p.m., then the job will not be purged (assuming the Cleanup Age Limit For Non-successful Jobs was 7 days). Because the number of completed, non-successful jobs is usually not high, the Cleanup Age Limit For Non-successful Jobs setting is usually set to a high value of 168 (7 days).

Minimum: 1

Maximum: 100000

Default: 168 (7 days)

17. Bookkeeping Interval (in milliseconds)

There are a number of Bookkeeping tasks executed by the Queue System. Some examples are: awakening jobs in 'Sleeping' state, updating the heartbeat timestamp, checking whether Queue Cleanup needs to be executed, and so on. This setting controls the time interval at which these tasks run.

Minimum: 500 (1/2 second)



18. Queue Timeout (in minutes)

The Queue System has a failover recovery feature: if the farm contains multiple servers running the Project Application Service, and the Queue Service fails on one server, jobs are automatically redistributed to other servers on which the Queue Service is online. A Queue Service is considered to have timed out if it has not updated its heartbeat for more than the 'Queue Timeout' interval. The heartbeat is updated by the Queue in all the PWA databases that it handles.

Minimum: 2

Maximum: 20

Default: 3

(Note that Queue Timeout cannot be less than 4 times the Bookkeeping Interval at any time. For example, if the Queue Timeout is 3 minutes and the Bookkeeping Interval is changed to 60000 (60 seconds), then the Queue Timeout will automatically be changed to 4 minutes.)

19. Fast Polling

By default, this setting is enabled and the queue processes all 'waiting to be processed' jobs as soon as possible. But if this fast processing overwhelms the server and you need the queue to slow down, administrators can turn off "Fast Polling'". If the setting is off, the queue does the following: Check if there are any free threads to process jobs, if so load all the free threads with the 'waiting to be processed' jobs, wait for the polling interval and do the whole thing again. If the setting is on, the queue does not wait for the polling interval if there are pending jobs. As jobs get processed, the pending jobs are processed immediately.

43

Operational policies

Alerts and reminders

Overview: Allows you to define notification e-mail settings and schedule e-mail reminder service.

Pre-requisites:

None





3. Click Alerts and Reminders.

[Located under the Operational Policies section]

Alerts and Reminders page will appear.

4. Enter the name of the SMTP Server.

5. Enter the From address.

6. Enter the company domain name.

7. Enter the e-mail footer.

Example:

Please contact the PMO if you have any further questions or need assistance regarding the Project Server notifications.

8. Schedule e-mail reminder service.

The e-mail reminder service scans the Project Server database at the scheduled time each day, and sends e-mail messages to remind users about their upcoming or overdue tasks and status reports.

Enter 11am

9. Publish a project: add yourself as one of the team members.

10. Open Outlook and check for new mail. Project Server should have sent you a notification regarding the new assignment.

Additional server settings

Overview: This page allows the administrator to set additional global settings for the server instance. Examples: 1 – Allow master projects to be published

44

Pre-requisites:

None





3. Click Additional Server Settings.

[Located under the Operational Policies Section]

Additional Server Settings page will appear.

Server-side event handler configuration

Overview: This page is used to manage custom server-side events. Example: Once a developer has written a server-side event, the EPM administrator can view summary details of the event handler on the server. There are several standard events that happen on the server already. Example: Project: Create – each time a project is created on the server, the event is triggered.

Pre-requisites:

None





3. Click Server-Side event handler configuration.


Server-Side event handler configuration page will appear.

4. Click the event source. Event handlers will refresh at the bottom of the page based on the event source selected.

5. Click new event handler. Page will display, allowing you to capture the details of the event handler.

6. Enter the Display and System information of the event and then click Save.

Event details will be saved to the server.

7. IMPORTANT: This is only used when a developer has created custom event handlers that should be registered with Project Server.

45

Active Directory resource pool synchronization

Overview: The Active Directory resource pool synchronization allows you to add/remove resources in the Enterprise Resource Pool based on who is added / removed from a single Active Directory Group. Example:

1. A new employee joins Contoso. 2. A process is in place to add new users to the Project 2010 Active Directory Group. 3. The system synchronizes on a nightly basis with the Active Directory group. 4. If new users have been added to the group, they will be added to the Project 2010 ERP. 5. If users are removed from the group they will be flagged as inactive.

Pre-requisites:





3. Click Active Directory Resource Pool Synchronization.


Active Directory Resource Pool Synchronization page will appear.

4. Click the Find Group button. Dialog will display allowing you to select a group from active directory.

5. Select a Valid Active Directory Group.

6. Set the scheduling option. Set it to update on a nightly basis at 10 PM.

7. Set the resource options. Set the group to automatically reactivate inactive users.

8. Click Save and synchronize now.

9. Project Server Group should synchronise with the Active Directory group.

10. NOTE:

Add new people to the Active Directory group who are not in the EPM resource Pool: Run the sync and then check whether they are resources in the enterprise resource pool.

Users added to the Active Directory Group will be added to the Project Server ERP.

Active Directory Resource Pool Synchronization

Overview: The Active Directory ERP synchronization only adds the resource to the ERP and the Team Member Security Group. This test scenario explains how you can use Active Directory groups to grant users additional permissions to project data. Example:

46

Contoso may want to grant Project Managers "create project" permissions as soon as they start or it may want to allow executives automatic authentication in Project Web App for certain management reports in Project Server by default.

Pre-requisites: Active Directory ERP Sync must have the same users as the groups indicated in the custom groups below.



1. Contact the Active Directory administration and request that a new group be created.

Example:

PMOProjectManagers

PMOExecutives

Request the Active Directory admin to add some users into the groups for testing purposes.

NOTE: Try using the same user names that were used in the Active Directory ERP Sync Test scenario.

2. Open Project Web App. PWA opens.

3. Click Server Settings. The admin menu will display.

4. Click Manage Group. List of Groups will display

5. Click the group to place it in edit mode.

6. Click the find group button – locate the Active Directory group that the admin created. Example: PMOProjectManagers

7. Click Save. Changes will be made permanent.

8. The Active Directory column should have the group name you selected in it.

Run the Sync:

The synchronization can be scheduled to run at night; however we want to test if it is working in this test scenario.

9. Hover the group

10. Click the Active Directory Sync Options button.

11. A dialog box will appear with options.

12. Schedule the sync to run a few minutes AFTER you scheduled the ERP Active Directory Sync to run.

13. Click the save and synchronize now button.

The Active Directory Sync will run; wait a

47

few minutes.

14. After the Sync has run, check the Project Server groups details: Example Edit Project managers Group

The same list of users that were added to the Active Directory group should be added to the Project 2010 group.

Project sites

Overview:

This page allows the administrator to perform the following functions:

Create a SharePoint site for a Project

Edit the SharePoint site address

Synchronize the security between the sites

Delete a site

Open the project's SharePoint site

Pre-requisites:

None





3. Click Project Sites.


Project Site page will appear.

Create a site for the project

1. Click a project. Toolbar will be enabled.

2. Click the Create site button. A site will be provisioned for the project, and the URL will be updated.

Edit the site address

If a site already exists and the URL is incorrect, the administrator can edit the URL


2. Click the Edit Site Address button. Edit Site Address dialog box will appear.

3. Select the Web Application and enter the desired site URL.

4. Click the Test URL button. Site should open.

5. Click the OK button. Changes should be

48

saved to the server.

Synchronize the security between the sites

Each site that gets created has custom security permission levels that synchronize with security groups in Project Server.

Example : Each site has the following security permission levels

Web Administrators (Microsoft Office Project Server)

Project Managers (Microsoft Office Project Server)

Team Members (Microsoft Office Project Server)

Readers (Microsoft Office Project Server)


2. Click the Synchronize button Dialog box will appear.

3. Open the site as the administrator.

4. Click Site settings.

5. Click the advanced permissions menu [Located under the users and permissions section]

6. List of users/groups will display.

Important: Click the settings/permission levels sub menu in order to view the permission levels that have been created.

After the synchronization has been done, the list of users should be added with related security permissions.

7. Try Again: Delete all the users from the Project site. Click the synchronize button again.

Refresh the list of users

The users should be displayed in the relevant Project site.

Delete a site

NOTE: The delete action is a permanent action and should be used with caution.


2. Click the Synchronise button. Dialog box will appear.

3. Click the Delete button. System will prompt you for confirmation

4. Click the OK button. Site will be deleted.

Open the projects site


6. Click the Go to Project Workspace site settings button.

Site will open.

Project site provisioning settings

Overview: This page is used by the administrator to define the configuration settings used when new sites are created.

49

Example: 1. Should the site be automatically provisioned when a project is published by project managers? 2. Which instance of SharePoint Server will be used when doing the provisioning?

Pre-requisites:

None





3. Click Project Site provisioning settings.


Project Site provisioning settings page will appear.

4. Select the default Web Application:

http://ServerName/

Enter in the site URL:

Example:

If you want all the sites to be provisioned under the Project Server then enter in Project Server.

Thus when sites are created there URL will look as follows

http://ServerName/PWA/Site1



5. Select the automatic provisioning setting – this will prevent the PMs from having to decide if they want to create a SharePoint site or not.

6. Check the automatically synchronize option – this will ensure that the team members/project managers can service the project's SharePoint site.

7. Click save Configuration settings should be saved to the server. When new sites are created the settings in this page will be used.

Bulk update project sites

Overview: Use this page to update the URL path to one or more project sites. You may need to run this tool after restoring or migrating a site or content database containing project sites.

50

Pre-requisites:

None





10. Click Bulk Update Project Sites.


Bulk Update Project Sites page will appear.

11. Select the previous site path and URL and set the new set path and URL.

Check / Uncheck the Update Content Types box.

Check / Uncheck the Synchronize site permissions box.

12. Click Save. Configuration settings should be saved to the server and site paths will change according to the above entries.

Workflow and Project Detail pages

Enterprise Project Types

Overview:

Enterprise Project Types are a way of grouping phases, stages, a single workflow, business drivers, and project

detail pages. In order for project managers to use enterprise project types when creating a project or proposal, a

site administrator must first define them in Project Web App.

Pre-requisites:

None





3. Click Enterprise Project Types.

[Located under the Workflow and Project Detail Pages section]

Enterprise Project Types will appear.

4. Select New Enterprise Project Type. Will navigate to Add Enterprise Project

51

Type Page.

5. In the Name field specify a name for the Enterprise Project Type. This is the name users will see while you are creating new projects in Project Center.

6. In the Description field Specify a description for the Enterprise Project Type. This information will display in the tool tip when users rest the pointer on the name while creating new projects in Project Center.

7. In the Site Workflow Association field choose a site workflow association for this Project Workflow.

For the 'Site Workflow' to appear in the drop down, it has to be installed and configured on the Project Server machine.

Note: Once you select an association it cannot be changed"

8. Choose the ―New Project Page‖ for this enterprise project type. This is the first Project Detail Page that users will see when you create new projects in the Project Center.

If the 'No Workflow' option is selected as the Site Workflow Association, then choose the Project Detail Pages that users will see once the project is created.

The 'New Project Page' may also be visible after project creation. If any other option is selected as the Site Workflow Association, then the Project Detail Pages are determined dynamically by the associated workflow.

9. Click the checkbox to Choose whether this is the default Enterprise Project Type for Project creation.

If no type is specified during Project Creation, the default Enterprise Project Type will be used.

Note: Making this default will automatically unselect all the departments. The default Enterprise Project Type cannot have a Project Plan Template associated with it

52

10. Choose the Department association for this Enterprise Project Type. Note that this department association is used only for filtering the Enterprise Project Types on the Project Center and not for security.

Pressing will display the departments to choose from.

11. Specify an image for the Enterprise Project Type. This is the image users will see next to the Enterprise Project Type while you are creating new projects in the Project Center.

Note: If you have an image on your computer, you have to first upload the image to an online document library (for example, 'Shared Documents' library in PWA) and then specify the image URL from here.

12. Select the Order to determine the position in which Enterprise Project Types display in the 'New' button in the Project Center.

13. Choose a template that will be used when creating any project with this Enterprise Project Type. If the drop down list just shows 'None', then there are no templates available - you can create project plan templates using Project Professional connected to the server

Note 1: Avoid having non-generic assignments in the project plan template. This is because all assigned tasks will be published when a project is being created

Note 2: The default Enterprise Project Type cannot have a Project Plan Template associated with it.

Note 3: This list is not filtered by department

14. Choose a Project Site Template that will be used when the project site is created

15. Click Save. The page will navigate back to the Enterprise Project Types list where the newly saved Enterprise Project Type will appear.

67869084 Testing a Project Server 2010 Deployment

Documents

project web app

operational policies section

project detail pages

transient sql problem

enterprise resource pool

active directory group

mail reminder service

duplicate timesheet lines