Microsoft project server 2010 administrators guide free
The Microsoft Project Server Administrator’s Guide helps your organization understand the tasks involved with administering and managing Microsoft Project Server Click the Download button in the upper right corner of this page to start the download. Click Save or Save this program to disk. Find the file on your hard disk and double. Mar 01, · I must say that MS active contribution and support so far related to the latest Project Server version must take the product to the next level. The guide consist of mighty number of pages and list down all the administrative activities to be performed by the administrator of the system. Mar 17, · The Microsoft Project Server Administrator’s Guide helps your organization understand these tasks that are involved with administering Project Server It includes many step-by-step procedures and accompanying user-interface screen shots of Project Web App. File size: approximately MB. Download the guide as file.
Project Server Administrator’s Guide – Project Server | Microsoft Docs
Mar 17, · The Microsoft Project Server Administrator’s Guide helps your organization understand these tasks that are involved with administering Project Server It includes many step-by-step procedures and accompanying user-interface screen shots of Project Web App. File size: approximately MB. Download the guide as file. The Microsoft Project Server Administrator’s Guide helps your organization understand the tasks involved with administering and managing Microsoft Project Server Click the Download button in the upper right corner of this page to start the download. Click Save or Save this program to disk. Find the file on your hard disk and double. Jan 07, · Microsoft Download Manager is free and available for download now. Guide for planning, deploying, and maintaining a solution based on Microsoft Project Server Note: There are multiple files available for this download. Once you click on the “Download” button, you will be prompted to select the files you need.
Microsoft Project Server | Five Benefits of Using Microsoft Project Server.
Attribute Single line of text Multiple lines of text Description Select if you want the custom field to be a single line of text. This option is available only for Project Text fields. Select if you want the custom field to be multiple lines of text. The project field created with this option is not visible in project information tab in Project Professional. This field however can be exposed via web based PDP page. You can choose to have a custom lookup table supply the values for a custom field.
This allows you to control the values chosen for the custom field. 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.
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, you will not be able to remove the lookup table relationship.
Therefore, make sure you need the lookup table before making this association. If you want to have a default value included in this custom field in cases where the user does not specify one, select this check box, and then select the default value.
The default value to be used in this field when users do not specify a value. To set the value, click the browse button and select the desired value. Select this option if you want to allow only values in the lookup table that have no subordinate values that is, values at the lowest level of each branch. Select this option if you want to allow users to select more than one value from the lookup table.
Once this selection has been made and saved, it cannot be removed. 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, create the lookup table before creating the custom field. 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.
Formulas cannot be used with all types of Enterprise Custom Fields. The formula option is available with all field types. Note Once a formula is associated with a custom field, it can be edited but it cannot be removed. To use a known formula, type the formula in the Edit formula box. To add a field to the formula, click Pick field, point to a field type, and then click the name of the field that you want to reference.
For example, Baseline Finish and Finish in this example. To reference an existing Enterprise Custom Field, point to a field type, point again to a custom field type such as Custom Date or Custom Finish , and then click the Enterprise Custom Field that you want.
To use a function in the formula, click Pick function, click a function type, and then click the function that you want. Each function includes placeholder arguments that you can replace with the fields and values that you want to use. To build a formula by using a standard set of operators, click Pick operator and choose the operator that you need. The formula can operate by using referenced fields, functions, or literal data. The following table describes the formula options.
Attribute Enter formula Insert field Insert function Insert operator Description Type the formula you want to use in the Enter formula text box. Use Insert field to insert a field cost, date, duration, flag, number, or text into the formula. Use Insert operator to insert an operator mathematical or Boolean into the formula. Department You can select a department to be associated with a custom field. Selecting a department allows you to limit a users ability to see the custom field if they are not a member of that department.
If you do not specify a department, then all users will be able to see the custom field. Calculation for Summary Rows For entity types of Resource and Task, you can select options for the calculation of summary rows. Note that summary row calculation is not available with a field type of Text. The following table describes the options for summary task calculation. 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.
Choose Rollup to roll up the individual rows for the summary row. Choose Use formula to use a specific formula to calculate the summary row. You must specify the formula to use under Custom Attributes. Calculation for Assignment Rows For resource types of Resource and Task, you choose to use a roll down calculation for assignment rows.
Description Choose None if you do not want to roll down assignment rows. 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.
Values to Display You can choose to display raw data or to have the data represented graphically. If you choose Graphical indicators, you can choose different criteria for Non-summary rows, Summary rows, and, if you are using an entity type of Project, Project summary.
When you choose an option, further configurable parameters specific to that option will be displayed. The following table describes the options for graphical indicators. 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. Choose Summary rows to specify criteria for graphical representation of summary rows.
Choose Project summary to specify criteria for graphical representation of the project summary. When you configure graphical indicators, you can specify the exact value and comparison parameters that determine when a particular graphic will be used. The available comparison test parameters are: Equals. These are used to compare the data value with a threshold value that you specify to determine which graphic to display.
For example, 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. You can specify as many different images for different values as required. The following table describes the graphical indicator options for non-summary rows. Attribute Description. Description Choose the operator equals, less than, etc.
Type the field value or a field reference e. Use the move buttons to move a row up or down in the table. Select the Show data values in ToolTips to show the field value in the tool tip associated with the image.
When using graphical indicators for summary rows, you can choose to inherit the graphical indicator settings that you have defined for non-summary rows. If you select the Inherit criteria from non-summary rows check box when configuring graphical indicators for summary rows, the graphical indicator parameters you configured for the non-summary rows will be used.
If you select the Inherit criteria from summary rows check box when configuring graphical indicators for project summary, the graphical indicator parameters you configured for the summary rows will be used.
Behavior You can configure a custom field to be controlled by workflow or to require a value. If you choose to have the custom field controlled by a workflow, the required field option will not be available since that behavior will be controlled by workflow.
The following table describes the options for configuring custom field behavior. 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. Choose whether you want this to be a required field that is, the field cannot be left blank.
This option is not available if the Behavior controlled by workflow option is selected. 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. For example, it might not be a good practice to allow users to enter any integer value in a custom Status field. One project manager might enter Started, and another might enter In-Progress, both indicating that the project has begun and is underway.
Without using lookup tables, it is difficult to standardize terminology in your organization. For example, you might create a custom text field that is associated with Resources. To do this, you click the Resource option, select Text from the list, and rename it Manager. If you do not specify a lookup table for this custom text field, a user can enter any text value in the Manager field. The New Lookup table page allows you to specify the options for a custom lookup table.
Use the following procedure to create a new enterprise custom lookup table. Type a name for the lookup table in the Name box. Type You must specify a data type for each lookup table. It is not possible to mix field types within a table. The table below describes the options for data types within a custom lookup table. Each field in the table will be a date value. Each value in the table will be treated as a duration. Each value in the table will be a number. Each value in the table will be text.
Choosing Text also allows a hierarchy of values to be specified if desired. The code mask allows you to specify what type of text characters will appear in the lookup table, the length of the string, and what characters to use to separate levels in a hierarchy. If you. The following table describes the options available for configuring code masks. Specify the type of text characters to allow. Choose Numbers, Uppercase characters, Lowercase characters, or Characters. Specify the maximum length of the string.
Choose a number from 1 to or Any. Specify from one to three characters to use as a separator between levels of the table hierarchy. Type each that you want in the lookup table in the Value column. Create as many rows as needed to accommodate the values that you want to include.
Optionally, include a description for the value in the Description column. The following table describes the options for creating lookup table values. Description Denotes the level in the hierarchy. This is a read-only field. Select the row and use the Indent and Outdent buttons to change levels.
The value of the field. An optional description of what the field represents. Use the Move buttons to change the position of rows in the table. Select the row and click the Up or Down Move button to move a row. Use the display order options do specify how to sort the lookup table. If you choose By row number, the table will remain sorted as you specify it. If you choose to sort ascending or descending, the table will be sorted based on the values in the Value column.
Departments The Department field is a new feature for Project Server Both projects and resources can have departments. 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 and PWA. Departments allow for different business units to define and make visible their own set of custom fields. Departments are also used to filter OLAP databases so that only the data for that department is loaded.
When configuring a cube, you can specify both the project and resource departments so that the database data is filtered based on these criteria. 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. With Project Server , departmental custom fields help relieve the problem of too much information and too many choices. Departments help you manage the custom field list, and help you define, at a resource, task, or project level, which fields are required or not required.
In Microsoft Office Project Server all custom fields are globally scoped, which means the fields are available to all users. In Project Server , fields can be globally scoped or they can be scoped to a specific department. Departmental fields enable two primary functions: Filtering custom fields so that a user sees, by default, only those fields that are either global to the system or in the department that the user belongs to.
Controlling which fields require input. By default, departments filter the list of custom fields that John Woods and Cindy White see. But the filter does not prevent them from viewing custom fields assigned to the other departments.
Important Departmental fields are not tied into security. You cannot use them with security categories and groups to enable or disable fields and their functions. Instead, 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.
Cubes include assignments for resources in projects that belong to other departments or to no department. This ensures that all data is present when examining data such as a department’s resources full calendar capacity. 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.
Projects with assignments to the departments resources will be included. Task non-timephased: Non-departmental tasks with assignments to the department’s resources will be included. The full non-departmental project will not be included. All tasks for departmental projects will be included. Assignment non-timephased: Non-departmental project assignments for the departments 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.
Deliverables: All deliverables owned by the filtered list of projects will be included. All deliverables offered by non-departmental projects that are subscribed to by departmental projects will be included. Issues: Issues connected to the filtered list of projects and tasks will be included. Risks: Risks connected to the filtered list of projects and tasks will be included.
Resource non-timephased: Resources in the departmental list will be included. Resource timephased: Resources in the departmental list will be included. Timesheet: Timesheets for departmental list resources will be included.
EPM Timesheet: Timesheets for departmental list resources will be included. Task assignments from projects outside the department will be included. Resources are described in three ways in the OLAP databases: Fact focus timesheets, capacity Associated with Facts project task assignments Owning Facts project owner, issue owner, assignment owner The departmental resource list is used to filter facts with focus Timesheets.
Consequently, 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, and will only have the relevant assignment facts. Resources who own things that have separate dimensions that is, Assignment Owner do not have to be in the resource list.
Configuring departments Departments are configured using a built in Enterprise Custom Lookup Table called Departments. By configuring values in this table, you can define a hierarchy of departments for your organization. Use the following procedure to add initial values to the Department custom lookup table or to modify it. To modify the Department lookup table 1. In the Code Mask section, create a code mask for each level of the hierarchy that you plan to have for the Department lookup table: a.
In the Sequence column, choose Characters from the dropdown list. If you are creating a hierarchy with more than one level, use the Indent and Outdent buttons to change the level values for each department as required for you hierarchy.
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.
When you specify an RBS value for each Project Server user, you can take advantage of the dynamic security options that can be defined for each security category. Once you define the structure, you can assign RBS values to individual users by setting the RBS property in the user’s account settings page.
Once the RBS is configured, Categories can use RBS codes to dynamically determine which projects and resources particular users can view or access. 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.
To modify the Resource Breakdown Structure 1. In the Code Mask section, create a code mask for each level of the hierarchy that you plan to have for the Department lookup table: 2. The Enterprise Global file contains all custom enterprise objects that are available to your users for example, views, tables, groups, filters, and reports. When a Project Professional user connects to Project Server , the latest version of the Enterprise Global file is loaded and cached on the client computer.
This allows the user to access all enterprise custom objects available on the server. Through the Enterprise Global file, you are able to enforce standards in your organization that can be applied to all project and resources that work with Project Server data. By using views, tables, filters, and other related elements contains in the Enterprise Global file, you can help to ensure effective standardization in your organization. Decisions regarding what to include in the Enterprise Global file should be made at an organizational level.
To open the Enterprise Global file through the Enterprise Global setting: 1. Project Professional will open the Enterprise Global file. The name of the project in the title bar will be Checked-out Enterprise Global. Make changes to your custom objects through your Enterprise Global file. After you have completed your changes, click File, and then click Save.
After Save has completed successfully, click File, and then click Close. A dialog box will display asking if you would like to check-in the Enterprise Global file. Click Yes. Note If users have Project Professional open when an updated Enterprise Global file is checked in to the server, the changes in the updated Enterprise Global file will not be available until Project Professional is closed and reopened. Important Make sure not to add into the Enterprise Global file any view, table, filter, grouping, reports, etc.
Verify that you give any new enterprise-wide elements a unique name that does not conflict. Enterprise Calendars Enterprise calendars capture the predefined working hours, holidays, and other schedule details within an organization. They are used to standardize the working time for all of an organizations projects. In Project Web App, you can view a list of existing calendars, select a calendar to edit, or begin the process of creating a new calendar.
However, to create or modify a calendar, you must have Project Professional installed on the computer that you are using to access Project Web App. Create a New Calendar Project Server uses a standard enterprise calendar for scheduling, by default. Some organizations may use multiple calendars. For example, if some of your organizations employees work in another country, those workers will likely observe different holidays, and so will need a different enterprise calendar for scheduling project work.
To create a new, blank enterprise calendar 1. On the Enterprise Calendars page, click New Calendar. On the Windows Security dialog box, type your user name and password to connect to Project Server through Project Professional , and then click OK.
Note If you are using integrated Windows authentication and your Internet Explorer settings are set to automatically log you on, or if Project is already connected to the server using the correct profile, then you will not be prompted for credentials. Project Professional opens and displays the Change Working Time dialog box.
Type a name for the new calendar in the For calendar box. Use the calendar with the Exceptions and Work Weeks tabs to modify the working and nonworking times for your organization. For more information, see the Modify Working and Nonworking Times section of this guide.
Close Project Professional 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, you can base a new calendar on an existing calendar.
Copy the existing calendar in Project Web App, and then modify the copy in Project Professional To create a new calendar as a copy of an existing calendar 1. Click the row containing the calendar you want to copy, and then click Copy Calendar.
On the Copy Calendar dialog box, type a name for the new calendar in the Name box, and then click OK. The calendar is added to the list on the Enterprise Calendars page.
If the Windows Security dialog box appears, log on to Project Server. Edit an Existing Calendar As you are initially configuring Project Server, you can modify the default standard enterprise calendar to account for the working and nonworking times observed by your organization. You can modify any enterprise calendar at any time by selecting the calendar in Project Web App, and making changes in Project Professional To modify an existing enterprise calendar 1.
Click the row containing the calendar you want to change, and then click Edit Calendar. Delete a Calendar If you find your organization is not using a specific enterprise calendar, you can easily delete it in Project Web App. To delete an enterprise calendar 1. Click the row containing the calendar you want to delete, and then click Delete Calendar.
When prompted, click OK to delete the selected calendar. Note If the calendar is currently in use, a notification will appear. Modify Working and Nonworking Times When working with calendars in Project Professional , there are a few different things you can do to accurately account for working and nonworking time in your organization.
The following sections provide examples for each type of change, and walk you through the steps involved with making each change. Change a working day into a nonworking day Occasionally, you may need to turn a working day into a nonworking day.
For example, if your organization observes specific days as holidays, you can turn those holidays into nonworking days. Project Server will not schedule work on nonworking days.
To change a working day into a nonworking day 1. Click the date on the calendar that you want to turn into a nonworking day.
On the Exceptions tab, type a name for the nonworking day in the Name column. The Start and Finish columns are automatically populated with the date you clicked in Step 1. Note While you can create multiple exceptions that contain a specific day, only the lowest-level exception will apply on that day.
For example, you might have one exception that changes the standard working times for a month, and another exception that calls out a specific day within that month as a nonworking day.
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. You cannot create multiple single-day exceptions on the same day. 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, say your organization participates in a convention each year that takes place over a weekend.
You can turn the weekend days of the convention into working days, so that Project Server knows to schedule work on those days. To change a nonworking day into a working day 1. Under Set working times for these exceptions, click Working times, and then set the working times for that day by adjusting the times in the From and To columns. If your organization observes these working times on a regular basis for example, once a month or once a year , under Recurrence pattern, choose whether these times should recur Daily, Weekly, Monthly, or Yearly, and then set the following options: Daily Set the frequency for these working times.
For example, every 10 days. Tip If you find that the working day exception is happening very frequently, you may find it easier to change the default calendar options under Schedule on the Project Options dialog box in Project Professional All calendars begin with these default days and times. It may be easier to change the default calendar options than to set up exceptions that recur frequently. Weekly Specify how often you want the working times to recur, and on what day of the week you want them to recur.
For example, every two weeks on Saturday. Monthly Choose what day of the month and at what monthly frequency you want the working times to recur.
For example, day 15 of every 3 months, or the third Saturday of every 6 months. Yearly Choose what day of the year you want the working times to recur. For example, August 21, or the third Saturday of July. Under Range of recurrence, choose the period when you want the recurrence to take place, if appropriate. Start Choose the date when you want the recurrence pattern to begin.
End after If you want the recurrence to happen only a set number of times, choose End after, and then type the number of instances when the working times should occur. End by If you want the recurrence to happen only during a certain time period, choose End by, and then choose when the recurrence should stop. Change the working times for a working day While the specific days on the calendar may be accurately accounted for as working and nonworking, there may be working days that use a different time schedule than the typical 8hour work day.
You can adjust the working times for a specific working day so that work is accurately scheduled on that day. 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, type a name for the changed working day in the Name column, and then press Enter. Note While you can create multiple exceptions that contain a specific day, only the lowestlevel exception will apply on that day. 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 make those changes to the working times for each day in a work week, during a set period of time.
For example, if your organization does not use the default Monday through Friday, 8am to 5pm schedule, you can change the working times for each day in the work week to reflect your organizations accurate schedule. 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. On the Work Weeks tab, type a name for the changed work week s in the Name column, and then press Enter.
Change the date in the Finish column for the row you just added, to reflect the last day that you want to include in the changed work week s. Under Select day s , click the day of the week that you want to use adjusted working times. Press Ctrl and click, or press Shift and click to select multiple days. If you want to change the working times for the selected day s , click Set day s to these specific working times, and then set the working times by typing in the From and To columns.
It can be accessed from the Server Settings page. Create a New Resource When you create a new Project Server user, you can choose to also make that user a resource. However, sometimes you may want to create a resource that cannot log on to Project Server. For example, you may want to add a material resource, such as a conference room, that has no need to be able to log on to Project Server.
Project managers can still assign the resource to work, but if there is not any work to track, and the project manager can account for when the resource is actually used, there is not a need for that resource to also be a user. To create a new resource 1. On the Resources tab, in the Editing group, click New Resource. Budget If the resource is a budget resource, select the Budget check box.
Generic If the resource is generic, meaning that you will use it for planning purposes and replace it with at least one named resource further in the planning process, select the Generic check box. In the Identification Information 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. Display Name Type the resources name in this box. This field is required.
E-mail address If this resource has an e-mail address that he or she wants associated with project work, type the address in this box. RBS If your organization uses a resource breakdown structure RBS , click the button next to this field and choose the appropriate RBS code for this resource from the list.
Initials This field is automatically populated with the resources initials, based on the name typed in the Display Name box. If you want to use different initials to refer to this resource, type them in the Initials box. Hyperlink Name If this resource has an associated Web site, type the name of that site in this box.
In the Assignment Attributes section, complete the following: Resource can be leveled If you want to enable project managers to balance this resources workload based on his or her availability and assignments leveling , select this check box. Base Calendar Choose the calendar that most closely represents this resources overall availability.
For example, if your organization has a base calendar that accounts for specific holidays or events, you can set that as this resources calendar, and work assigned to this resource will be scheduled around the calendars nonworking days. Default Booking Type Choose whether you want this resource to be Committed or Proposed when assigning work.
Timesheet manager Type the name of the person who approves or rejects this resources timesheets, or click Browse to choose the timesheet manager from a list. Resources may not have separate timesheet managers.
Default Assignment Owner Type the name of the person who approves or rejects this resources task progress, or click Browse to choose the assignment owner from a list. Resources may not have separate assignment owners. For example, if the resource is a conference room, and the project manager tracks the amount of time that the conference room is used, the assignment owner may be the project manager. Tip You can set the assignment owner within the project on an assignment-by-assignment basis.
Earliest Available Choose the date when the resource becomes available to assign to tasks, if appropriate. If the resource does not have a set period of availability that is, if he or she is always available , leave this blank.
Note The earliest and latest available dates correspond to the resource availability dates for a resource, as seen in Project Professional. Latest Available Choose the last date that the resource is available to work on tasks, if appropriate.
Standard Rate Type the resources standard pay rate in this box. Overtime Rate Type the resources overtime pay rate in this box. Current Max. For example, a van rental may require a flat fee upfront, with an added standard cost per mile. The flat fee is its cost per use. In the Departments section, click the button next to the Resource Departments box, and choose which department s the resource is associated with. If the resource is not associated with a particular department, leave this blank.
Tip Associating a resource with a department narrows down what the resource sees when using Project Web App. It can help the resource find what he or she is looking for more quickly, by removing things from other departments that do not apply to his or her work. If your organization created codes for grouping and costing purposes, in the Group Fields section, complete the following: Group Type the name of the group in this box.
Code Type the code for the group in this box. Cost Center Type the cost center code for the group in this box. Cost Type Click the button next to the Cost Type field, and then choose the type of cost associated with this group. In the Team Details section, click the button next to the Team Name box, and choose which team the resource belongs to, if appropriate. If the resource will be managing and delegating tasks that are assigned to the team, select the Team Assignment Pool check box.
Tip Some organizations create a generic resource for each team, so that tasks assigned to the team first go to the generic resource. This way, no single resource takes on the task assignment before it is appropriately delegated. If you choose to use a generic resource in this way, set the assignment owner for the resource as the team manager, select the Team Assignment Pool check box, and choose the team from the Team Name list.
By providing that ID number in the External ID box, you identify an association between the resource that you are creating and the HR departments employee data. The External ID box can also be used to facilitate the consolidation of reporting of resource use beyond what Project Server provides.
Tip If you are not sure whether you should be capturing any data in the External ID box, check with other departments in your organization to find out if it would be useful to connect resource data with other systems, or simply leave this box blank. Once a resource is added, you may find that you need to make changes to the resources information. Perhaps the resource had a rate change, or needs to use a different base calendar. To edit a resource 1. Select the check box in the left column for the row containing the resource you are editing.
Tip If your organization has a lot of resources and you cannot easily find the one you want to edit, you can filter the Resource Center. Identify the parameters for the resource you are editing, and then click OK. In some cases, several resources may require the same change. For example, if several resources use the same timesheet manager, and that person takes a job elsewhere, you will need to replace. Project Web App supports bulk editing of several resources at once.
Tip Another good way to edit many resources simultaneously is by using Project Professional By making changes through the Project Professional , you can add fields that you will not see if you make bulk changes through Project Server , and you can also copy and paste from Microsoft Excel or another list. To make the same change to several resources simultaneously 1.
Select the check box in the left column for each row containing a resource you are editing. Project Server permissions are assigned to these group, and they are not editable.
If you must have more control, you can change to the traditional Project Server Permissions Mode. It is important to understand security modes when you are viewing the “Security” chapter. Project Online : Project Online is a hosted version of Project Server in which the service is hosted in the cloud.
Administration will be different for Project Online and Project Server , because many administrative tasks are performed for you and are inaccessible to users. The tasks documented in this guide are intended for Project Server users, and not for Project Online users. A Project Online Administrators Guide will be available to you at a later date.
This guide is divided into two sections, because Project Server administrative settings are now located in Project Web App and in Central Administration. The “Project Web App Settings in SharePoint Central Administration” section is made up of four chapters and contains information that is of more interest to your farm administrator.
Learn skills from picture taking to sushi making. Amazon Explore Browse now. Customer reviews. How customer reviews and ratings work Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them. Learn more how customers reviews work on Amazon. Top reviews Most recent Top reviews. Top review from the United States. There was a problem filtering reviews right now.
Please try again later. This is available for free on TechNet it does have some handy information and I do use it every day. Free MS TechNet why pay for it? See all reviews. Your recently viewed items and featured recommendations.
Back to top. Get to Know Us.