MCTS 70-177 Microsoft Project Server 2010 Configuring CATALYST

Ø  CATALYST training guarantees skills transfer     
            - at the end of the course skills are in place to do the job.

Ø  CATALYST training guarantees certification, and there are no hidden costs to gaining certification - all exam costs are included.

Ø  CATALYST training does not only guarantee the skill set to the individual on the course  
- it guarantees the skill set to the organisation, too. If a delegate leaves his company within six months of attending a course Catalyst guarantees to offer the same course to their replacement at no cost to the company. Our guarantees are in place to reflect that we are prepared to assume the responsibility of our partners' success.

Ø  CATALYST training cuts the downtime used for training by more than 75%          

Ø  CATALYST training solutions lead the market in rapid skills transfer as the approach has been designed to suit to the learning style of most IT professionals. 

Audience Profile

The MCTS: Microsoft Office Project Server 2010, configuring CATALYST is intended for project management and other professionals who have requirements for scheduling, estimating, coordinating, controlling, budgeting, and staffing projects and supporting other users of Office Project. Familiarity with key project management concepts and terminology is recommended particularly those found in the Project Management Institute’s “A Guide to the Project Management Book of Knowledge” (PMBOK Guide). 

Exam 70-177: TS: Microsoft Project Server 2010, Configuring

Installing Project Server 2010 (23 percent)

Configure prerequisites.

This objective may include but is not limited to: domain accounts, SQL Server accounts, preparing servers for Project Server 2010 roles, features, ports, and protocols, configuring SQL for OLAP cubes, configuring SQL roles for Project Server farm administration, configuring analysis services account to read Project Server, configuring SharePoint services (in support of Project Server prerequisites)

Install software required for Project Server 2010 and related technologies.

This objective may include but is not limited to: PSCONFIG, Project Professional 2010 profiles/accounts, installing a new Project Web Access (PWA) instance, configuring Secure Store, configuring Microsoft Office Exchange integration, configuring Project Server 2010 services, configuring Excel Services

Manage a Project Server 2010 upgrade.

This objective may include but is not limited to: migrating data from Project Server 2003 or Project Server 2007 to Project Server 2010, upgrading from Project Server 2003 or Project Server 2007 to Project Server 2010, upgrading from Portfolio Server 2007 to Project Server 2010, configuring backward compatibility with Project 2007 clients

Managing Resources and Security (25 percent)

Configure for time management.

This objective may include but is not limited to: time reporting mode, single entry mode, financial periods, protected actions, administrative time, configuring Status Manager, Timesheet Manager, and Default Assignment owner role, configuring task status updates, configuring timesheets

Configure enterprise resources and organizational structure.

This objective may include but is not limited to: custom fields/lookup tables, calendars, costs, availability, type, department, teams, configuring resource breakdown structure

Manage users and permissions.

This objective may include but is not limited to: Active Directory synchronization, project workspace permissions settings, configuring options and access for a new project, configuring delegation, adding a new user to the system and assigning the correct role, adding groups

Configuring Project Server 2010 (25 percent)

Configure enterprise project types and templates.

This objective may include but is not limited to: configuring a Project Detail Page (PDP), creating an enterprise project type, creating, implementing, and enforcing the use of templates for the enterprise

Configure for Business Intelligence (BI).

This objective may include but is not limited to: BI permissions settings, creating Excel services reports for OLAP, creating analysis cubes for use in BI tasks, configuring OLAP cubes for departments, setting report permissions, adding custom fields to OLAP cubes, updating OLAP cubes on demand, associating a secure store services ID with reporting

Configure metadata and views.

This objective may include but is not limited to: lookup tables, custom fields including formulas and indicators, configuring views, configuring business drivers

Modify the Enterprise Global Template.

This objective may include but is not limited to: standard duration, work types, macros, tables, views, filters, groups

Manage workflows.

This objective may include but is not limited to: visible project pages, configuring phases, configuring stages, deploying a new workflow, restarting workflows, moving projects in a workflow, reassigning a workflow, deploying a new workflow

Administering Project Server 2010 (27 percent)

Configure for data governance.

This objective may include but is not limited to: archiving, retention, forced check-in of enterprise objects, deleting enterprise objects

Backup and restore Project Server 2010.

This objective may include but is not limited to: SharePoint links, farm backup and restore, site backup and restore, backup and restore of enterprise objects, scheduling backups

Administer SharePoint for Project Server 2010 implementation.

This objective may include but is not limited to: changing the default workspace template, creating a new workspace, creating a project web site for an existing project, re-linking a workspace URL, modifying uses of the grid and other Web Parts, configuring and maintaining the site provisioning process

Monitor Project Server health.

This objective may include but is not limited to: event, Unified Logging Service (ULS), and usage logs, active cache management, Health Analyzer, checking the queue for errors, changing history or queue settings, cancelling jobs, configuring the queue, checking the ULS log location, using the Developer Dashboard to assist in farm administration