01 Product Overview & Setup

Microsoft Project 2002 Training
Courseware
Lesson 1: Product Overview and Setup
Microsoft Corporation
June 2002
Microsoft Project 2002 Training Courseware
Lesson 1: Product Overview and Setup

Published: June 2002
Applies to:
Microsoft Project Standard 2002
Microsoft Project Professional 2002
Microsoft Project Server 2002
Contents
Objectives
Microsoft Project Product Family Overview
Microsoft Project Server Architecture
Supporting Technologies
System Requirements
Functions of Setup.exe
Microsoft Project Desktop Client Setup User Interface
Microsoft Project Server Setup User Interface
Automatic Recovery (Rollback)
Registry Settings
Upgrade Considerations
Enterprise Tools
Installation from a URL
Licensing Architecture
Exercises
Objectives
What You Will Learn

After completing this lesson, you will be able to:
• Describe the new line of products and their key features.
• Understand the difference between Workgroup and Enterprise Mode for Microsoft Project Server.
• Describe the minimum hardware and software requirements for installation.
• Discuss improvements in Windows Installer.
• Discuss the licensing requirements.
• Understand migration, upgrading, and coexistence of multiple versions.
• Identify key registry settings.
• Discuss enterprise tools for deployment.
Microsoft Project 2002 Training Courseware Page 2

Recommended Reading
• Enterprise Installation Recommendations
• Microsoft Project Server Configuration Guidelines White Paper
• Microsoft Project Server Data Migration
• Migration to Microsoft Project Standard 2002
Microsoft Project Product Family Overview

With this release, Microsoft® Project 2002 has expanded its product family to better fit the needs of
its customers. As with earlier versions, Microsoft Project Standard 2002 can be used as a stand-alone
desktop application. Additionally, collaboration between the project manager and the project
resources to receive task information and update that same information can be achieved in two ways;
1) integration with Microsoft Project Web Server application, or 2) by use of a MAPI e-mail client.
Microsoft Project Server 2002 replaces and improves upon Microsoft Project Central and is now sold
separately. A Microsoft Project Web Access client license can also be used to access Microsoft
Project Server. Finally, Microsoft Project Professional 2002 builds on Microsoft Project Standard to
provide enterprise features for managing resources and analyzing company wide project performance
when it is used in tandem with Microsoft Project Server.
These products can be configured and customized to meet the needs of all types and sizes of
businesses and organizations. The following is a listing of the Microsoft Project line of products, target
audiences, and description of the solution.
Table 1. Solution offerings

Description
Product/s Audience
Microsoft Project Standard 2002 Single project manager with 1 to 4 Stand-alone product
projects to manage Robust easy to use project
management tool on the desktop
Microsoft Project Standard with Single project manager with 5 to 20 Workgroup mode collaboration
Microsoft Project Server projects and 5 to 10 resources in
each project Inform and update resources and
projects via the Web
Document and Issue tracking via
SharePoint™ Team Services from
Microsoft
Microsoft Project Server with A resource or Executive Manager Web access
Microsoft Project Web Access
client Inform and update users and
projects via the Web without the
need for a desktop client
Microsoft Project Server with Multiple project managers with 150 Enterprise mode collaboration
Microsoft Project Professional to 1,000 projects and 20 to 50
resources Document and Issue tracking via
SharePoint
Data Modeling and Portfolio
Analysis
Microsoft Project solutions and their features sets are explained in more detail in the following pages.

Microsoft Project Standard Stand-alone New Features
Microsoft Project Standard 2002 helps business and project managers dynamically manage
schedules and resources and analyze project information. Microsoft Project provides a
comprehensive, easy-to-use solution. Based on customer feedback, Microsoft has made significant
improvements to the user interface and added key features that help business managers easily
create and manage project plans and realize the benefits of Microsoft Project.
New! Project Guide. Quickly and easily create and manage project plans with the new Project
Guide. This feature enables users to be productive immediately, step-by-step interactive instructions
walk users through the key areas of project creation and management, Tasks, Resources, Tracking,
and Reporting. In addition, the Project Guide can be customized to include a company's specific
goals and tasks.
New! Wizards. New wizards have been added to Microsoft Project to reduce the time and
complexity of setting up projects. As a new project plan is created, the Project Guide helps users to
select custom fields and templates and facilitates collaboration and the attachment of supporting
documentation when coupled with Microsoft Project Server. When setting up project calendars, a new
wizard simplifies the process of changing working time. A wizard will assist to customize the tracking
view to track projects to suit the user’s needs.
Improved! Microsoft Office interface. A familiar and more intuitive Microsoft Office XP® interface
complete with informative task panes and command bars makes it easy to learn and use Microsoft
Project.
New! Smart tags. Smart tag indicators give feedback when certain changes to the project plan
occur. For example, when a resource is added to a task, a smart tag will ask for clarification and offer
alternate scheduling calculations that may be more appropriate.
New! Microsoft Office integration. Task lists can be converted from Microsoft Excel®, Microsoft
Outlook®, or Microsoft Project Web Access into project plans in Microsoft Project. New import and
export capabilities such as the Microsoft Excel task list template make it easier than ever to switch
between Microsoft Excel and Microsoft Project.
New! Microsoft Visio® integration. Dates and tasks can be exported from Microsoft Project to
create high-level timelines and Gantt Charts in Visio.
New! Multiple baselines. Save and store full baseline data up to 11 times over the course of any
project.
Improved! Project Information Views. A variety of improvements have been made to project data
views including the following:
• Network Diagram view. Grouping summary tasks and displaying standard indicators and custom
fields in the Network Diagram view is now possible.
• Usage views. Group assignments and roll up grouped, time-phased information in Usage views,
even include totals when printing usage views.
• Three-tiered timescales. A third level for timescale labels has been added to Gantt Chart and
other graph and Usage views.

Microsoft Project Standard in Workgroup Mode Features
Microsoft Project Standard can be used in Workgroup mode when used in conjunction with Microsoft
Project Server, similar to how Microsoft Project Central and Microsoft Project 2000 worked together.
Users can collaborate and share data so that team members and stakeholders stay informed and
initiatives are aligned with company goals.
New! Microsoft Project Web Access displayed in Microsoft Project. Project managers can view
Microsoft Project Web Access directly from within Microsoft Project without having to log on to the
service through their Web browser. This feature makes it easier for managers to view information
without having to switch between two application windows.
New! Microsoft SharePoint Team Services Integration. Integration with Microsoft SharePoint
Team Services (STS) and Microsoft Project Server allows users to centrally store and organize
project-related documents and track issues:
• New! Document Sharing. Enhance collaboration throughout the project life cycle with document
sharing. Users can now link supporting project documentation to project plans and tasks.
• New! Issue Tracking. Manage projects more efficiently and effectively and improve team
communications by tracking issues. Users can enter issues associated to tasks or projects,
assign ownership, track progress, and record resolutions.
Improved! E-mail notifications. Keep team members and projects on track and save time with
automated e-mail notifications of project updates, upcoming milestones, issues and more that contain
direct links to project plans. Both project managers and team members can specify the types and
frequency of e-mail notifications and reminders.
New! Support for multiple managers. One manager can create the plan, another manager can
send out task assignments and manage resource progress.
Microsoft Project Server and Web Access Features

Microsoft Project Server 2002 serves as the technology platform for workgroup environments when
used with Microsoft Project Standard 2002 and for enterprise environments when used with Microsoft
Project Professional 2002. Through its Microsoft Project Web Access interface, Microsoft Project
Server makes it easy for team members and stakeholders to collaborate and access project
information using only a Web browser. Microsoft Project Server also provides the security, scalability,
and flexibility to adhere to a company's business processes and systems as project and resource
management demands increase.
Microsoft Project Server 2002 is the companion server product for Microsoft Project Standard and
Microsoft Project Professional. Microsoft Project Server stores project and resource information in a
central database, thereby enabling standardized, consistent project planning and reporting across an
organization. A member of the .NET Enterprise Server family, Microsoft Project Server provides the
scalability and security to adhere to a company's business processes and systems as project and
resource management demands increase.
Microsoft Project Server extends project information to team members and stakeholders through the
Microsoft Project Web Access interface. Using just a Web browser, each team member or
stakeholder with a Microsoft Project Server Client Access License (CAL) can access project
information from Microsoft Project Server without having Microsoft Project Standard or Microsoft
Project Professional installed on his or her computer.
Improved! Web Access User Interface. Users can experience the new look of Microsoft Project
Web Access, consistent with other Microsoft Office Web applications. Each team member's home

page displays items pertinent to the current session, such as newly-assigned tasks, action items, and
indicators highlighting items changed since the last session. With Microsoft Project Web Access,
team members and other stakeholders can save a view using sorting, grouping, or filtering options,
making it easy to regularly review and analyze project data pertinent to their role within the
organization.
Improved! Microsoft Project Web Access Views. Improved views in Microsoft Project Web Access
show project and resource information the way users want to see it.
• Improved! Project Center. This feature allows users to view their portfolio of projects in a Gantt
Chart view through either Microsoft Project or the Web browser. The user can drill down into the
project information, group, filter and search on those projects. When Project Center views are
customized with graphical indicators, users can quickly be alerted to problem areas, such as
projects that are behind schedule or over budget.
• New! Resource Center. The new Resource Center lets users view resource information easily.
In addition, resource utilization and availability across the project portfolio can be evaluated
quickly.
• Improved! View settings. Improved view settings allow users to see project information
consistently. When users return to a view in Microsoft Project Web Access, the view looks the
same as when they navigated away from it. Also, modified views can be saved as links in the side
pane for easy access.
• Microsoft Project Web Access components. These allow users to analyze, group, and search
for project information easily. Improved Microsoft Project Web Access components let users
display splits in the Gantt Chart view; search; hierarchically group on outline codes; use more
autofilter conditions, including contains and begins with; and choose from pick lists in custom
fields.
Improved! Timesheets. Improved timesheets provide more flexibility in determining how team
members report progress on their tasks. The project manager or administrator can choose the
tracking method that best suits the current project, so team members can enter their progress in the
timesheet view as hours or as a percentage of work completed. When the timesheet is updated
through the Web, changes are displayed in red for easy visibility.
New! Microsoft Project Web Access to-do lists. Users can create and manage a to-do list
conveniently, maintaining it online in the same format as other task lists. They can then use it for
personal reference or easily convert it into a project plan in Microsoft Project and take advantage of
its full project planning features.
New! Microsoft SharePoint Team Services Integration. Integration of Microsoft STS with
Microsoft Project Server allows users to centrally store and organize project-related documents and
track issues.
• New! Document sharing. Users can enhance collaboration throughout the life cycle of projects
with document sharing. Users can now link supporting project documentation to project plans and
tasks.
• New! Issue tracking. Users can manage projects more efficiently and effectively and improve
team communications by tracking issues. Users can enter issues associated to tasks or projects,
assign ownership, track progress, and record resolutions.
Improved! E-mail notifications. Users can keep team members and projects on track and save
time with automated e-mail notifications of project updates, upcoming milestones, issues and more
that contain direct links to project plans. Both project managers and team members can specify the
types and frequency of e-mail notifications and reminders.
Improved! Project updates. Project updates keep the entire team informed of project status.

• Updates page. Project managers can stay on top of changes with the Update page in Microsoft
Project Web Access. When team members create or delegate tasks, or modify their schedules,
project managers receive the changes in their Update page. From the Update page, project
managers can review and selectively choose which updates to accept, and can set rules for
automatically accepting updates. The Update page also maintains a history of task changes for
easy reference.
• Selectively update tasks. For greater flexibility in project reporting, team members can now pick
tasks when updating task status.
• Updates to actuals. Team members can modify actuals for a task on any day for more flexible
timesheet reporting. These modifications are highlighted on the project manager's Update page,
so the project manager can immediately incorporate the changes into the project plan.
Improved! Task delegation. Workflow can be improved with Microsoft Project Server's support for
top-down and peer-to-peer task delegation. Project managers can define summary tasks and then
direct team leads to create and assign the subtasks to their team members. At the project manager's
discretion, team members have the ability to reject a delegated task.
New! Microsoft Project Server compatibility. Microsoft Project Server 2002 is compatible with
Microsoft Project 2000, which relieves the necessity of upgrading both the server and the client at the
same time across a company.
Improved! Digital dashboards. Microsoft Project Server Web pages have been broken into smaller
components to allow for more opportunities for Web part creation without the need to write ASP
pages.
Improved! Support for industry standards. Utilizing industry standards, Microsoft Project easily
integrates and exchanges schema and data with other line-of-business applications and databases.
The Project Data Service, which utilizes extensible markup language (XML) and Simple Object
Access Protocol (SOAP) as the data transport mechanism, acts as the security schema to filter data
based on the individual user.
Improved! Microsoft Project OLE DB provider. The Microsoft Project Standard OLE DB provider
has been improved to provide support for time-phased data, better support for Office Web
components, and improved scalability and reliability.
Improved! Microsoft Project Web Access components. Users can extend and customize
Microsoft Project Server more easily thanks to improvements to the programmable interfaces of the
controls.
New! Extensible document management integration. Users can integrate Microsoft Project
Server with their organization's document management or issue-tracking solution through an
extensible server-side object.
Improved! Microsoft Project Server user permissions. Users can lower administrative overhead
with improved permission settings. Administrators can create and set permissions for groups and
individual accounts. Permissions can also be applied based on predefined templates.
Microsoft Project Server Features in Enterprise Mode

Microsoft Project Server used in conjunction with Microsoft Project Professional has all the features
listed above plus new enterprise features that are highlighted below.
New! Portfolio Analyzer. With the new Portfolio Analyzer, the user can quickly query information
across his or her portfolio. This tool enables the user to view project and resource information

conveniently in a variety of ways as a PivotTable, chart, or both.
New! Portfolio Modeler. What-if scenarios can be created and evaluated with the new Portfolio
Modeler. This tool allows the user to interactively modify project schedules and resource staffing, and
see the impact of the changes on a project portfolio. Modeling what-if scenarios allows users to
identify potential solutions for at-risk projects in a portfolio.
New! Enterprise standards. Standardized data including base calendars, views, and enterprise
fields are stored and shared through the enterprise global file, so project reporting is consistent
across the project portfolio.
New! Enterprise resource pool. The enterprise resource pool provides a central location where
resource information is securely stored and managed, so users can get accurate, up-to-date
information about resources, including assignments, utilization, and availability across the
organization.
New! Enterprise project security. Access to enterprise projects is securely controlled with
Microsoft Project Server's check-in/check-out method. Microsoft Project Server protects the project
portfolio by preventing multiple users from accessing the same information at the same time.
Improved! Scalability. Microsoft Project Server can be installed on one machine or on a dedicated
Web server with a separate server for the Microsoft Project Server database. Microsoft Project Server
accommodates performance and scalability needs through load balancing for the servers and clusters
for the database server.
Microsoft Project Professional Features

Microsoft Project Professional 2002 helps professional project managers manage their portfolio and
resources, collaborate on projects, and analyze project information. Working with Microsoft Project
Server, Microsoft Project Professional's powerful project planning, reporting, scenario analysis, and
resource management capabilities provide organizations with a scalable and customizable solution.
To enable the enterprise and resource management features, Microsoft Project Professional must be
used with Microsoft Project Server.
In addition to the features and functionality in Microsoft Project Standard, with Microsoft Project
Professional, customers will have access to the following features:
New! Build team from enterprise. This feature assists in the selection of resources from the
enterprise resource database, allowing users to find resources that have the right skills and
availability to work on their project. Users can filter and query the enterprise resource database to
fine-tune their project resource assignments.
New! Resource Substitution Wizard. This wizard staffs projects using local and enterprise
resources, based on the skill project tasks require and the skills and availability of resources.
New! Generic resources. Generic resources support skills-based resource assignment and
replacement by allowing managers to define and save frequently used skill and code profiles as
generic resources. These are of particular use when setting up a new project. The Resource
Substitution Wizard will recognize the generic resource skill profiles and match them to the skills of
resources in the enterprise resource pool, based on their availability.
In addition, Microsoft Project Professional through its user interface has the ability to access the
following Microsoft Project Server features:
New! Enterprise standards. The Enterprise Global file holds the items such as reports, views, and

calendars that enforce enterprise standards. The Enterprise Global can only be opened, new items
created, defined, and modified in Microsoft Project Professional by a user with the appropriate
permissions.
New! Enterprise resource pool. Enterprise resources are imported into the Enterprise resource
pool through Microsoft Project Professional; the same resources' details can be defined and modified
by a user with the appropriate permissions in Microsoft Project Professional.
The following features are described in the Microsoft Project Server section. They are available and
can be accessed through the Microsoft Project Professional Collaboration menu.
• Portfolio Analyzer
• Portfolio Modeler
• Project Center
• Resource Center
Microsoft Project Server Architecture

When Microsoft Project Server is paired with Microsoft Project Standard the resulting feature set is
referred to as Workgroup mode and when the server is paired with Microsoft Project Professional it
is called Enterprise mode. The modes have slightly different architectures that enable the differences
in feature sets.
A major improvement in the architecture that affects both server modes is the addition of view tables.
These tables hold all the information necessary to drilldown in the Project Center as well as display
data for resource availability views in the Resource Center. This change eliminates the extra work
that was required in Microsoft Project Central 2000 for storing project plans.
The view tables are updated in Workgroup mode whenever a project plan is published.
The tables are updated in Enterprise mode when:

• A project is checked-in.
• A resource is checked-in.
• A forced update of resource availability tables occurs via the Admin pages.
The view tables are also used in Enterprise mode when viewing Portfolio Analyzer views, resource
availability and when building a team in Microsoft Project Professional.
Workgroup Mode Architecture

Figure 1 shows the Web client and the desktop client, Microsoft Project Standard on the left gaining
access to Microsoft Project Server through Internet Information Services (IIS). Then using hypertext
transfer protocol (HTTP) and XML the request, storage, and retrieval of data is handled.

Figure 1. Workgroup mode architecture
View tables. The view tables store the project and resource data. These tables all begin with the
prefix MSP_VIEW, such as MSP_VIEW_PROJ in the Microsoft SQL Server database.
Project Business Object (PBO) (PJBUSOBJ.DLL). Processes requests and filters data based on
the user's verified permissions.
OLEDB Provider. Retrieves and posts data to the project file.
Project server tables. These tables hold the backend information about Project Server, such as
account info, views, site customization, file locations, etc. These tables all begin with the prefix of
MSP_WEB_, such as MSP_WEB_PROJECTS.
Project data tables. These tables hold project data and begin with the prefix of MSP_, such as
MSP_CALENDARS.
Stored procedures. To improve the performance when writing and retrieving data, common SQL
queries have been complied and stored on the server.
Temporary directory. Project data storage area used for transaction processing to ensure data
integrity, in case of errors a transaction can be rolled back.
How it all works together
When publishing a project file from Microsoft Project Standard a copy of the project (.mpp) file is sent
to the PBO and stored in a temporary directory. The PBO gets a unique Project ID from the Project
Server tables, if the ID exists then the ID is passed back, otherwise a unique ID is assigned. The PBO
then opens a connection to OLEDB provider. The OLEDB provider then publishes a set of tables to
the view tables overwriting any existing tables for that project. The temporary directory is then
deleted. The Project Server and Project Data tables are updated by OLEDB as well.
Enterprise Mode Architecture

The first difference between the two modes is the addition of the Portfolio Data Service (PDS) in
enterprise mode. The PDS provides a high level of security to the SQL tables and will allow the
owners of the system to take advantage of the PDS standard interface and security features when

creating extensions in order to add custom functionality. Secondly, the OLAP cube is created and
updated by SQL Analysis Services and used to create Portfolio Analyzer views and generate
resource availability information. The data used to create the cube is stored in the Enterprise tables,
the third difference.
Components exclusive to the Enterprise architecture are:
Project Data Service. All requests for data go through the PDS, which checks the user's access to
the data stored in the SQL tables.
Enterprise tables. These tables hold all the enterprise outline codes from which the OLAP cube is
generated. These tables have the prefix of MSP_CUBE.
OLAP Cube. Created by SQL Server Analysis Service, contains the field and dimension information
to be used in Portfolio Analysis views.
Figure 2. Enterprise mode architecture
How it all works
When publishing an enterprise project plan Microsoft Project Professional sends a project summary
record to the server and makes a request to the PDS to check-in the project file. The PDS makes a
request to the PBO to publish the Project Summary Record to the Project Server Tables. The PBO
gets the unique Project ID from the Project Server Tables, if the ID exits then the ID is passed;
otherwise a unique ID is assigned. PBO publishes the summary record and returns a success to
PDS. PDS makes a request to the PBO to publish the project file to the Project tables. PBO makes a
request to OLEDB to open a connection with the Project tables and publishes the new data. Finally,
the OLEDB refreshes data in the view tables and enterprise tables.
Additional Architectural Components

Not shown in the architectural figures above are two more components that run on the IIS server in
both server modes. SharePoint Team Services enable greater collaboration with the ability to link
documents and issues to project plans. The Notification Process Engine polls the server for
messages that need to be sent and then uses IIS Simple Mail Transport Protocol (SMTP) services to

send out those notifications and reminders.
Supporting Technologies
The technologies that support the server modes and their feature sets are listed below.
Database applications:
• Microsoft Desktop Engine 2000 (MSDE) - MSDE can be used as the backend database for
Microsoft Project Server in workgroup mode. MSDE is installed when the Install Now option is
selected for setup and only if Microsoft Project SQL is not already installed on the system. MSDE
supports 10 to 15 users and does not install with tools to administer the database.
• MSDE or SQL must be used as the backend database for SharePoint Team Services. SharePoint
enables document and issues tracking in both server modes.
• Microsoft SQL Server 2000 SPI or later must be used as the database backend when Microsoft
Project Server is run in enterprise mode or in workgroup mode when there will be more than 10
users.
• Microsoft SQL Server Analysis Services is required to enable the features that use the OLAP
cube in enterprise mode only.
• Optionally, Microsoft SQL Server 7.0 or Oracle 8.0 can be used to store projects in database
format.
Microsoft Project Server should be setup using Mixed Authentication; this is because SQL accounts
are used to access the database tables by default.
Internet Information Services 5.0 or later
IIS will host the Microsoft Project Server Web site, Notification Process Engine, and STS Web site.
SharePoint Team Services
Microsoft Project Server ships with the SharePoint Configuration Wizard, an executable
(STSWIZ.exe) that will install STS and custom ASP pages. However, if STS is already installed the
executable is smart enough to just install the custom pages. STS can be installed to a different IIS
server from Microsoft Project Server. Indexing Services in IIS should be turned on to enable
searching of STS sites.
Office Web Components
Office Web Components (OWC) ships with Microsoft Project Server and must be installed to create a
Portfolio Analyzer view. In order to receive the full interactive functionality of a Portfolio Analyzer
view OWC must be installed on the client machine otherwise the view will be a static one. A Microsoft
Office XP license is required to install OWC.
System Requirements
The requirements listed below are minimum requirements. Processor, memory, and hard disk
requirements depend on the number of services installed on the computer. Minimum requirements
assume only Microsoft Project components (for example, Microsoft SQL Server and other services
run on separate computers). A thorough evaluation of the number of users, other services and

applications running, and the feature set to be used, must be considered before installation. More
detailed information on enterprise considerations can be found in Lesson 41: Enterprise Installation
Recommendations.
Microsoft Project Standard 2002

Use of Microsoft Project Standard version 2002 requires the following:
• Processor. PC with Pentium 133 MHz or higher processor
• Operating system. Microsoft Windows® 98, Windows 98 Second Edition, Windows Millennium
Edition, Windows NT® 4.0 with Service Pack 6 or later, or Windows 2000 Professional or later
• Memory.
For Windows 98 and Windows 98 Second Edition - 24 MB of RAM for the operating system plus
an additional 48 MB of RAM for Microsoft Project
For Windows Me, Windows NT Workstation 4.0, or Windows NT Server 4.0 - 32 MB of RAM for
the operating system plus an additional 48 MB of RAM for Microsoft Project
For Windows 2000 Professional - 64 MB of RAM for the operating system plus an additional 48
MB of RAM for Microsoft Project
• Hard disk space. 30-204 MB of available hard disk space with 115 MB on the hard disk where
the operating system is installed (55 MB for typical installation on system with Microsoft Office XP
installed; 310 MB for full installation on similar system without Office XP installed)
Users without Windows 2000, Windows Me, Office 2000 SR-1, or Microsoft Project 2000 will
require an extra 50 MB of hard disk space for System Files Update (hard disk usage will vary
depending on configuration)
• CD-ROM drive
• Super VGA or higher-resolution monitor
• Microsoft Mouse, Microsoft IntelliMouse®, or compatible pointing device
• Microsoft Internet Explorer® 5.0 or later (Internet Explorer 5.5 or later recommended)
Additional items or services required to use certain features:

• 14.4Kbps or higher modem
• Multimedia computer to access sound and other multimedia effects
• Some Internet functionality may require Internet access and payment of a separate fee to a
service provider; local and/or long distance telephone toll charges may apply
• Windows-compatible network and MAPI compliant mail systems required for e-mail project
collaboration
• Microsoft SQL Server 7.0 or later, or Oracle 8.x or later, for projects stored in databases
• Microsoft Project Server 2002 required for workgroup project collaboration

Microsoft Project Web Access
Use of Microsoft Project Web Access requires the following:
• Memory
an additional 8 MB of RAM for Microsoft Project Web Access
For Windows Me, Windows NT Workstation, or Windows NT Server 4.0 - 32 MB of RAM for the
operating system plus an additional 8 MB of RAM for Microsoft Project Web Access
For Windows 2000 Professional - 64 MB of RAM for the operating system plus an additional 8 MB
of RAM for Microsoft Project Web Access
• Hard disk space. 10-20 MB of available hard disk space
Microsoft Project Server 2002

Use of Microsoft Project Server 2002 requires the following:
• Processor. PC with Pentium III 500 MHz or higher processor; 700 MHz recommended
• Operating system. Microsoft Windows® 2000 Server with Service Pack 1 or later, or Windows
2000 Advanced Server with Service Pack 1 or later
• Memory. 128 MB of RAM minimum (512 MB of RAM recommended)
Users with Microsoft SQL Server 2000 installed on the same machine require an additional 32
MB of RAM minimum for SQL Server (additional 64 MB recommended); additional services
installed require more RAM
• Hard disk space - 70 MB of available hard disk space
Users with Microsoft SQL Server 2000 installed on the same machine require an additional 170
MB for the typical installation of SQL Server, plus hard disk space required for the database (1
GB minimum); additional services installed will require more hard disk space
• Microsoft IIS 5.0 or later
• Microsoft SQL Server 2000 Desktop Engine (MSDE), included, or Microsoft SQL Server 2000 or
later (required for enterprise project and resource management)
• CD-ROM drive
• Microsoft Mouse, Microsoft IntelliMouse, or compatible pointing device
Additional items or services are required to use certain features:

• STS (included with Microsoft Project Server) required for project collaboration
• Microsoft SQL Server Analysis Services for Portfolio Analyzer (OLAP reporting)
• Microsoft Exchange, Internet SMTP/POP3, IMAP4 or MAPI-compliant messaging software for e-
mail notifications
• 14.4Kbps or faster modem

service provider; local and/or long-distance telephone toll charges may apply
Note Processor, RAM, and hard disk requirements depend on the number of services installed on
the computer. Minimum requirements assume only Microsoft Project Server components (for
instance, Microsoft SQL Server and other services run on separate computers).
Microsoft Project Professional 2002

Use of Microsoft Project Professional 2002 requires the following:
• Operating system. Microsoft Windows® 98, Windows 98 Second Edition, Windows Millennium
Edition, Windows NT® 4.0 with Service Pack 6 or later, or Windows 2000 Professional or later
• Memory.
an additional 48 MB of RAM for Microsoft Project
For Windows Me, Windows NT Workstation 4.0, or Windows NT Server 4.0 - 32 MB of RAM for
the operating system plus an additional 48 MB of RAM for Microsoft Project
For Windows 2000 Professional - 64 MB of RAM for the operating system plus an additional 48
MB of RAM for Microsoft Project
• Hard disk space. 30-204 MB of available hard disk space with 115 MB on the hard disk where
the operating system is installed (55 MB for typical installation on system with Microsoft Office XP
installed; 310 MB for full installation on similar system without Office XP installed)
Users without Windows 2000, Windows Me, Office 2000 SR-1, or Microsoft Project 2000 will
require an extra 50 MB of hard disk space for System Files Update (hard disk usage will vary
depending on configuration)
• CD-ROM drive
• Microsoft Mouse, Microsoft IntelliMouse, or compatible pointing device
• Microsoft Internet Explorer 5.0 or later (Internet Explorer 5.5 or later recommended)
Additional items or services required to use certain features:

• 14.4Kbps or higher modem
service provider; local and/or long distance telephone toll charges may apply
• Windows-compatible network and MAPI compliant mail systems required for e-mail project
collaboration
• Microsoft SQL Server 7.0 or later, or Oracle 8.x or later, for projects stored in databases
• Microsoft Project Server 2002 required for workgroup project collaboration

Overview - Setup Enhancements
The installation process for Microsoft Project 2002 is much the same as it is for Microsoft Project
2000. However, in response to customer feedback, accessibility studies, known issues in the product,
and usability studies on all Microsoft Office products, the overall setup experience has been improved
in 2002 applications. The changes made to the setup process were done primarily to incorporate the
following items:
• User interface has a sharp, professional appearance.
• Microsoft Windows Installer version 1.1 required.
• Unique .msi filenames used for each SKU.
• Verbose logging is on by default.
• Reboot requirement is minimized.
• Installation from a Web URL is supported.
The setup process and thus the user experience is the same across all SKUs, including products like
the Microsoft Project Multi-Lingual User Interface Packs. Consistency across all of these products
lends itself to familiarity with the setup user interface, providing a better user experience each time a
product is installed.
Functions of Setup.exe
Setup.exe has been updated to add new functionality, handle Office System Pack requirement
detection/installation, and chain additional Windows Installer products. The following items outline the
complete life cycle and objectives of Setup.exe for Microsoft Project 2002:
• Can be started by means of AutoRun on the CD or from a command line, including a Web URL.
• Detection of a supported operating system.
• Detection and installation of the Windows Installer.
• Detection and installation of the Office System Pack.
• Installation of the Microsoft Project core files.
• Installation of additional packages specified by an administrator.
The most important point to remember is that each of the above items can be done manually,
bypassing Setup.exe, and the end result is exactly the same.
Note Setup.exe installs the Tahoma font if it is not present. This is the one item that does not occur
with Microsoft Windows 2000 application deployment.
Detection of Windows Components

Whether Setup.exe is started by means of the AutoRun on the CD or from a command line, the first
dialog box displayed depends on the version of Windows, whether or not the Windows Installer needs
to be installed/updated, and whether or not System Files Update needs to be installed.

Support Operating System
If the operating system is unsupported, for example Windows 95 or Windows NT 4.0, an error
message will display.
Windows Installer
If the Windows Installer Version 1.1 is not installed before Setup is run, it is automatically installed. In
a scenario where the Windows Installer is not yet installed, the following dialog box is displayed
during the installation of the Windows Installer.
Figure 3. Installation of the Windows Installer
Note If you are installing by means of a URL (HTTP), Instmsi.exe or Instmsiw.exe is cached locally
and then run by Setup using the /q switch.
If Windows Installer 1.0 is installed, then the user does not immediately see the dialog box from
Figure 3. Instead, setup skips this part of the setup process and updates the Windows Installer when
the System Files Update is installed. In this scenario, the dialog box from Figure 3 is displayed after
the computer is forced to reboot by the installation of the System Files Update.
Tip To verify the version of the Windows Installer on the system, check the version of Msi.dll.
To manually install the Windows Installer, double-click Instmsi.exe for Windows 98, or Instmsiw.exe
for Windows NT 4.0.
Note Do not run either of these two .exe files on Windows Me or Windows 2000. These versions of
Windows already have the Windows Installer installed and cannot be updated this way.
Microsoft Office System Files Update
If the core Windows files on the computer are not at a specific level/version, Setup.exe automatically
launches the installation of the System Files Update.
This core set of system files is included by default on computers with one of the following
configurations, so users should not see the System Files Update installation if:
• Any version of Windows with Office 2000 SR-1 installed
• Windows 2000
• Windows Me
The System Files Update is a Windows Installer installation controlled by the OSP.MSI Windows
Installer package that is found in the \FILES\OSP\1033 folder.
When the System Files Update installation is finished, it is required that the computer be restarted.
After the restart, the installation of the core Microsoft Project files automatically continues. At this
point, the first Setup dialog box is displayed.

Microsoft Project Core File Installation
After the Windows Installer and the System Files Update have been installed, Setup.exe calls the
Windows Installer to install the .msi for Microsoft Project. The following table outlines the different
.msi files used in Microsoft Project 2002.
Table 2 - Windows Installer .Msi Files for Microsoft Project SKUs

.Msi
Microsoft Project Edition Market
PRJSvr.msi
Server Retail
PRJSvrE.msi
Server Enterprise
PRJSvrT.msi
Server Trial
PRJStd.msi
Standard Retail
PRJStdE.msi
Standard Enterprise
PRJStdT.msi
Standard Trial
PRJPro.msi
Professional Retail
PRJProE.msi
Professional Enterprise
PRJProT.msi
Professional Trial
SQLRun01.msi
MSDE All
OSP.msi
Office System Pack All
OWS.msi
SharePoint Team Services All
Microsoft Project Desktop Client Setup User Interface

The user interface in Microsoft Project 2002, for both Standard and Professional editions share many
features with the user interface in Microsoft Project 2000. However, there are some new dialog boxes
and many of the existing dialog boxes are improved to ease the installation. Only Microsoft Project
Standard will be shown here as the Setup dialog boxes are the same for Microsoft Project
Professional.
Microsoft Project Client Core File Installation

If it was not required to install the System Files Update, or the computer has just restarted after the
installation of the System Files Update, the first Project Setup dialog box, as shown in Figure 4, is
displayed. In the User Information dialog box, the user information and the Product key, otherwise
known as the CD key, is entered.

Figure 4. User information
The next step in the installation is to accept the license agreement (Figure 5).
Figure 5. License agreement
The Next button is not available until the License Agreement is accepted. If it is not accepted, click

Cancel to stop the installation of Microsoft Project 2002.
The first dialog box after accepting the License Agreement, as shown in Figure 6, includes the
following three options:
• Install Now
• Complete
• Custom
Figure 6. Installation type
Note If Setup is running from administrative installation, the Run from Network option will also be
available. If this option is selected, it is equivalent to setting the top Microsoft Office feature Run all
from Network.
Depending on the option you select, the user interface is slightly different to allow for the different
features offered by each option.
Tip The dialog box shown in Figure 6 allows you to change the installation location for Microsoft
Office.
Install Now
Clicking Install Now installs all of the files used to run the Microsoft Project and shared tools.
When Next is clicked, the Begin Installation dialog box is displayed (Figure 7) with a summary of the
programs to be installed.

Figure 7. Begin installation
Click Install to finish the Microsoft Project desktop client installation.
Figure 8. Installation Progress bar
When installation is complete the following message will display as shown in Figure 9.

Figure 9. Successful installation
If the operating system was updated by the System Files Update or was already at the requisite level,
there is no need to restart the computer when the Microsoft Project installation is finished. This is an
added advantage for customers with large rollouts of Microsoft Project.
Complete Installation
Clicking the Complete option installs all of Microsoft Project and tools. Because a Complete
installation is being performed, the program is set to Run from My Computer.
Custom Installation
If the user wants to customize the features installed with Microsoft Project, the Custom option should
be selected. Figure 10 shows the dialog box that will be presented to the user with the Office Tools
menu expanded. Clicking the + next to the feature displays its sub-features and clicking the icon next
to the feature allows the user to modify its installation state to one of the following options:
• Run from My Computer
• Run all from My Computer
• Run from Network (if you are installing from a network source)
• Run all from Network (if you are installing from a network source)
• Installed on First Use
• Not Available

Figure 10. Custom option selection
Microsoft Project Server Setup User Interface

There are two setup modes to select from when installing Microsoft Project Server, there are Install
Now and Custom.
Install Now can only be used under the following circumstances:

• Microsoft Project Server will be used in Workgroup mode,
• And less than 15 users will be accessing the Web site,
• And Microsoft Project SQL is not installed on the machine.
Custom must be used in the following circumstances:

• Microsoft Project Server will be used in enterprise mode.
• Microsoft Project SQL or MSDE already exist on the system where Microsoft Project Server is to
be installed.
• Microsoft Project Server will connect to an existing database. In the case of upgrading from
Microsoft Project Central 2000 the database must be upgraded before setup can be run. For
more information see the section in this lesson on upgrading.
In this section the Install Now option for setting up the server to use in workgroup mode is discussed.
When setting up a Microsoft Project Server for use in enterprise mode there are many considerations
and preparations that need to be made before installation. For a complete discussion see Lesson 41:
Enterprise Installation Recommendations.

Microsoft Project Server File Installation
The first screen to display after inserting the CD or clicking setup.exe or setupsvr.exe is the Auto-
play screen shown in Figure 11. There are a number of reference materials that will be discussed
later, for now assume that Server Installation was selected.
Figure 11. Auto-play screen from the Microsoft Project Server CD
As with the setup for the client, the Windows System files are checked to see if they need updating, if
not then the installation will begin. The next Setup dialog box displayed is shown in Figure 4. In the
User Information dialog box, the user information and Product key, otherwise known as the CD key,
are entered. The next step in the installation is to accept the license agreement as seen in Figure 5,
and this is where the similarities end.
To install MSDE, the radio button next to or install now must be selected. The install folder can be
changed by clicking on the Browse button (see Figure 12).

Figure 12. Installation type
Clicking Next will bring up the dialog box shown in Figure 13.
Figure 13. Database password
A password for use with MSDE must be entered here and confirmed. The password must meet the
password requirements specified for the domain. Take note of this password as it may be used later
during STS installation. Then next screen (Figure 14) displays the components that will be installed
when the Install button is clicked.

Figure 14. Begin installation
A screen with the progress will be presented next. If no errors are encountered a message that the
Microsoft Project Server has been successfully installed will display. If an error is encountered an
error message should display and setup will rollback.
SharePoint Team Services Installation

The installation of STS can be done before or after the installation of Microsoft Project Server. STS
can be installed from Microsoft Office XP® CD or when the STS Configuration Wizard is run from the
Microsoft Project Server CD. The Configuration Wizard accomplishes a couple of tasks that include:
• Detecting if STS is already on the system, if it not then STS is installed.
• Copying a number of templates and custom ASP pages to the STS server.
• Provisioning a subweb used for public documents.
The auto-play screen of the Microsoft Project Server CD is shown in Figure 15. Selecting SharePoint
Configuration Wizard launches STSWIZ.exe or the same file can be found in the \support folder on
the CD and double clicked.
Note The template is copied to \\Program Files\Common Files\Microsoft Shared\Web Server

Extensions\50\template\1033.

Figure 15. Auto-play screen for Microsoft Project Server CD
Figure 16. End-User License Agreement
Accept the End-User License Agreement (ULA) and the Next button will be available.
In Figure 17 the user is asked to select a Web site to provision with STS. It is important to select a
Web site that is not an administrative Web site; STS cannot provision an administration Web site.

Figure 17. Select a Web site where STS will be provisioned
In Figure 18 the user must provide the name of the server where the SQL database that will be used
as the STS backend is installed. This does not need to be the same server that is hosting STS or
Microsoft Project Server.
Figure 18. Enter SQL database information
The next screen begins the installation when the user clicks the Next button. The following screen
presented will warn the user that the provisioning process may take some time. The final screen is
most important because it contains information necessary to completing the configuration between
Microsoft Project Server and STS (Figure 19).

Figure 19. SharePoint configuration data
This information will be used to add a SharePoint Server to Microsoft Project Server.
To Add a STS Server in Microsoft Project Server

1. Log into Microsoft Project Web Access as Administrator and select the Admin menu.
2. Select Manage SharePoint Team Services, which displays the Connect to Servers page.
3. Click Add Server the page in Figure 20 will display.
Figure 20. Add Server page

4. Enter the information received from the STS configuration wizard and click Save Changes.

The SharePoint Customization Wizard can also be run prior to the installation of Microsoft Project
Server. The advantage is that when a custom installation is run for Microsoft Project Server, the
information about the SharePoint site can be entered at the time of installation and the above steps
are not necessary.
Automatic Recovery (Rollback)

Another change in Microsoft Project is the way costing of available drive space is performed. By
default, the Space Required value displayed in the Begin Installation dialog box does not include
Rollback space requirements. This is to reduce customer confusion with the space requirement
numbers generated by setup.
Even though the value for Space Available is higher than the value for Space Required the user
may still not be able to install without disabling the Rollback feature. If they click Install in this
scenario, they may be prompted to disable Rollback to allow the installation to continue.
Registry Settings
The Windows Registry holds information important to the execution of Microsoft Project Server and its
clients as well as customized option settings for the applications. When all applications are running as
expected there is no need to go into the registry to view or modify any values, however when
problems do arise it is sometimes useful to know where these settings are. It is important to always
backup the registry before making any changes.
Below is a list of registry locations where settings for Microsoft Project Server and clients are stored.
HKey_Current_User\Software\Microsoft\Office\MS Project
\Addins - list of available addins
\Profiles - connection accounts to Server from Pro
\Settings - application settings
HKey_Current_User\Software\Microsoft\Office\10.0\MS Project
\HTML -default template to be used when saving as HTML
\Options - a folder for each tab and the settings for that option
tab
\Recent file list - list of most recently used files
\User Info - binary data
\Workgroup customization - changes to the default workgroup message
HKey_Current_User\Software\Microsoft\Office\10.0\Web Server
\OWS Collaboration objects - information
HKey_Local_Machine\ Software\Microsoft\Office\10.0\Common\MS Project
\Messaging - managers and senders
HKey_Local_Machine\ Software\Microsoft\Office\10.0\MS Project
\OLE DB Provider - timeouts
\Services\Configuration - SessionMgr and Views Notification
\Web Client Server - Languages
\Web Client Server\Project Server
\Datasets - connection information to databases such as username and
password
Application
EnterpriseDatabase
STS
ViewsFileDrop
ViewsSchedulingDatabase
\Services\SessionMgr

HKey_Local_Machine\ Software\Microsoft\Office\10.0\Web Server
OWS Collaboration Objects
Upgrade Considerations
The database schema has changed for Microsoft Project Server 2002. The complete instructions are
included on the Microsoft Project Server CD. To locate the information load the CD and from the
Auto-play screen select Upgrading and Database Configuration, then select Database Upgrade
Information or select the Installation Guide from the Auto-play screen. The information can also be
found on the CD under the DOCS folder double click on PJSVR10.CHM.
Upgrading from Microsoft Project Central 2000 to Microsoft Project

Server 2002
Workgroup mode
Upgrading from Microsoft Project Central 2000 to Microsoft Project Server 2002 Workgroup mode
requires several SQL scripts to be run against the database. It is a recommended that the Microsoft
Project Central database be backed up before proceeding with the upgrade. Any project files stored
in the database will be lost as well as customizations to ASP pages, status reports, and messages.
Customized Views will be retained, as will assignment, resource and project summary records. Once
all the required scripts are run the data will be accessible via the Web access client.
Enterprise mode
Upgrading from Microsoft Project Central 2000 to Enterprise mode requires that Microsoft Project
Server be installed to a different server and a new database be created for use with Microsoft Project
Server. Then the data from the 2000 database is migrated to 2002. See the white paper “Microsoft
Project Server Data Migration” for detailed information. Basically data from 2000 will be imported via
Microsoft Project Professional to the new 2002 database. That means resource and project plan data
only.
Enterprise Tools
The Microsoft Project 2002 Resource Kit (PRK) is located on the Microsoft TechNet Website and
contains tools and instructions on how to deploy Microsoft Project, the database maintenance tools
and information and more. Some of the more frequently-used items are listed below.
Administrative install. Can be done from a command prompt using the /a switch, more information
can be found in the PRK.
Custom Installation Wizard (CIW). To create a transform that will aid in the customization of an
install to multiple desktops can be found in the PRK.
Multi-Lingual User Interface. To view application menus and dialog boxes in a language other than
the localized version, a language pack is installed, multiple language packs are also available. In
order to enter foreign language data into Microsoft Project the Input Method Editor (IME) is available
from the PRK.

Installation from a URL
Microsoft Project supports installation from a mapped drive, a UNC connection, or from a CD-ROM
drive. In addition to these three installation sources, Microsoft Project allows you to install from the
following sources.
• HTTP
• HTTPS
• FTP
With corporations becoming more and more Intranet/Internet-centric, adding installations from a Web
server as a feature in Microsoft Office XP is a great advantage.
Installation Details
When setup is run for Microsoft Project from a Web server, Setup.exe detects the source by one of
two methods.
• If installing from a link in Internet Explorer, Setup.exe detects it is running from the Internet cache
and asks the operating system for the source location. This sets the URLPATH property to this
location.
• If not using a link from within Internet Explorer, then use the /webinstall switch to alert Setup.exe
that the source location is a Web server.
Because the installation is from a Web server, all of the Microsoft Project files are first copied into
the \Temporary Internet Files folder and then copied from this location into the specified installation
folder.
Tip After the installation is finished, the files in the \Temporary internet files folder are not
automatically deleted. One possible workaround is to lower the amount of disk space used for
temporary Internet files before the installation.
After Setup.exe knows it is running from a Web server, it uses the Web server URL as the path to the
installation files, rather than the path to Setup.exe itself. This is because Setup.exe is downloaded to
the local Internet cache and the rest of the setup files, including Setup.ini, are left on the Web server.
Windows Installer Installation
If the user is installing Microsoft Office from a Web server and they do not have the Windows Installer
installed, or it needs to be updated, the Instmsi.exe (or Instmsiw.exe on Windows NT 4.0) package is
cached locally and then installed from the local cache.
Licensing Architecture
The following items outline the different licensing methods for Microsoft Project.
Mandatory. Uses the Office Activation Wizard (OAW) to activate Microsoft Project. After it is
activated, the user has a perpetual license to use the product. If Microsoft Project is not activated
within 50 launches of the program, the program goes into Reduced Functionality Mode (RFM). In this
mode changes to files or new files cannot be saved. This applies to retail reversions.
Bypass. Does not require activation of the product. The CD key provided with the product

automatically bypasses the OAW. Bypass CD keys are included with large volume SKUs such as
Select Licenses.
Trial. Microsoft Project trials have a license with a finite time span under which the user can use the
program. In order to continue the use of the program after this license has expired, the user cannot
convert it to a perpetual license with a Mandatory activation. They must uninstall the trial version and
then install a retail version of the product. A warning will display starting 3 days before the trial time
period will expire.
Migration Paths
Volume Licensing
On October 1, 2001, Software Assurance replaced one-time upgrade paths (Version Upgrade,
Product Upgrade, Competitive Upgrade, and Language Upgrade). Upgrade Advantage, which is
available until July 31, 2002, will be automatically rolled into Software Assurance.
The following three scenarios provide the migration paths for the Microsoft Project 2002 product line:
• If the customer is licensed for Microsoft Project 95 or Microsoft Project 98, through 31 July
2002, for each license of Microsoft Project 95 or Microsoft Project 98, the customer is eligible to
purchase Upgrade Advantage. The customer will receive rights to Microsoft Project Server and
can migrate to either Microsoft Project Standard version 2002 or Microsoft Project Professional
version 2002.
• If the customer is licensed for Microsoft Project 2000, through 31 July 2002, for each license
of Microsoft Project 2000, the customer is eligible to purchase Software Assurance or Upgrade
Advantage. The customer will receive rights to Microsoft Project Server 2002 and can migrate to
either Microsoft Project Standard 2002 or Microsoft Project Professional 2002.
• If the customer is already maintained via Software Assurance or Upgrade Advantage for
Microsoft Project, for each Software Assurance or Upgrade Advantage license that is active at
the time Microsoft Project 2002 appears on the Product List, the customer will receive rights to
Microsoft Project Server 2002 and can migrate to either Microsoft Project Standard 2002 or
Microsoft Project Professional 2002.
• If the customer is licensed for Microsoft Project Central, through 31 July 2002, for each
license of Microsoft Project Central, the customer is eligible to purchase Microsoft Project Central
Software Assurance and migrate to Microsoft Project Server CAL.
Note Customers who do not purchase Software Assurance or Upgrade Advantage by 31 July 2002
can purchase License or License and Software Assurance for Microsoft Project Server 2002,
Microsoft Project Standard version 2002 or Microsoft Project 2002 Professional version 2002.
For more information on License and Software Assurance, visit www.microsoft.com/licensing.
Retail Licensing
There is no version or product upgrade for retail customers; they need to purchase the full package
product. The only exception is if Microsoft Project 2000 is purchased before the end of June, these
users then qualify for a Technology Guarantee (free upgrade) to get Microsoft Project (Standard)
2002.
Activation

Activation can be done either via the Internet or telephone.
When Microsoft Project is launched for the first time after installing, the OAW automatically appears.
The first dialog box presents three options:
• Activate by using the Internet
• Activate by using the Telephone
• Activate Later
The only required field the customer needs to provide is the Country/Region. The information is sent
to the Microsoft licensing servers. If the information is validated, the Activation Complete dialog box
is displayed.
Coexistence of Multiple Versions

It is strongly recommended to remove earlier versions of Microsoft Project before installing Microsoft
Project 2002 or let the setup program upgrade the existing program files. However it is possible to
install both versions on the same machine by taking care to install each into its own directory. The
Global files for each version are stored in separate locations.
2000 - <drive>:\Documents and Settings\<profile name>\Application Data\Microsoft\MS Project\1033
2002 - <drive>:\:\Documents and Settings\<profile name>\Application Data\Microsoft\MS

Project\10\1033

Lesson 1: Exercises
Exercises
1. Can Microsoft Project Server be load balanced?
2. Name the four products in the Microsoft Project 2002 product family.
3. What are the two server modes?
4. What products together enable each server mode?
5. List the technologies involved in the operation of Microsoft Project Server.
6. What is OAW? Which SKUs use OAW?
7. Microsoft Project Installation is supported from what installation sources?
8. What factors contribute to the server's performance?

Answers to Exercises
1. Yes, Microsoft Project Server can be load balanced.
2. The four products in the Microsoft Project 2002 product family are Microsoft Project Standard,
Microsoft Project Server, Microsoft Project Professional, and Microsoft Project Web Access.
3. The two server modes are Workgroup and Enterprise.
4. Microsoft Project Standard and Microsoft Project Server together operate in Workgroup mode.
Microsoft Project Professional and Microsoft Project Server operate in Enterprise Mode.
5. The technologies involved in the operation of Microsoft Project Server are:
• IIS
• SQL
• SharePoint Team Services
• SMTP for Notifications and Reminders
• Office Web Components
6. OAW stands for Office Activation Wizard. All retail SKUs need to be activated.
7. Microsoft Project supports installation from:
• mapped drive
• UNC connection
• CD-ROM drive
• HTTP
• HTTPS
• FTP
8. Factors that contribute to the server's performance are:
• Total number of users.
• Number of concurrent users.
• Number and size of the project plans.
• Kinds of actions preformed in Microsoft Project Web Access.
• General network performance.
• Other applications running on the same server.
###
This is a preliminary document and may be changed substantially prior to final commercial release of the software described
herein.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of
the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a
commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date
of publication.

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR
STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part
of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any
means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written
permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject
matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this
document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people,
places and events depicted herein are fictitious, and no association with any real company, organization, product, domain
name, email address, logo, person, place or event is intended or should be inferred.
@ 2002 Microsoft Corporation. All rights reserved.
Microsoft, SQL, SharePoint, Outlook, Visio, Intellimouse, Internet Explorer, and Windows are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

01 Product Overview &amp; Setup

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

01 Product Overview &amp; Setup

Загружено:

Авторское право:

Доступные форматы

Microsoft Project 2002 Training

Lesson 1: Product Overview and Setup

Lesson 1: Product Overview and Setup

What You Will Learn

Microsoft Project 2002 Training Courseware Page 2

Microsoft Project Product Family Overview

Table 1. Solution offerings

Microsoft Project 2002 Training Courseware Page 3

Microsoft Project 2002 Training Courseware Page 4

Microsoft Project Server and Web Access Features

Microsoft Project 2002 Training Courseware Page 5

Microsoft Project 2002 Training Courseware Page 6

Microsoft Project Server Features in Enterprise Mode

Microsoft Project 2002 Training Courseware Page 7

Microsoft Project Professional Features

Microsoft Project 2002 Training Courseware Page 8

Microsoft Project Server Architecture

The tables are updated in Enterprise mode when:

Workgroup Mode Architecture

Microsoft Project 2002 Training Courseware Page 9

OLEDB Provider. Retrieves and posts data to the project file.

How it all works together

Enterprise Mode Architecture

Microsoft Project 2002 Training Courseware Page 10

Components exclusive to the Enterprise architecture are:

Figure 2. Enterprise mode architecture

How it all works

Additional Architectural Components

Microsoft Project 2002 Training Courseware Page 11

Internet Information Services 5.0 or later

SharePoint Team Services

Office Web Components

Microsoft Project 2002 Training Courseware Page 12

Microsoft Project Standard 2002

Additional items or services required to use certain features:

Microsoft Project 2002 Training Courseware Page 13

Microsoft Project Server 2002

Additional items or services are required to use certain features:

Microsoft Project 2002 Training Courseware Page 14

Microsoft Project Professional 2002

Additional items or services required to use certain features:

Microsoft Project 2002 Training Courseware Page 15

Detection of Windows Components

Microsoft Project 2002 Training Courseware Page 16

Figure 3. Installation of the Windows Installer

Microsoft Office System Files Update

Microsoft Project 2002 Training Courseware Page 17

Table 2 - Windows Installer .Msi Files for Microsoft Project SKUs

Microsoft Project Desktop Client Setup User Interface

Microsoft Project Client Core File Installation

Microsoft Project 2002 Training Courseware Page 18

Figure 5. License agreement

Microsoft Project 2002 Training Courseware Page 19

Figure 6. Installation type

Microsoft Project 2002 Training Courseware Page 20

Click Install to finish the Microsoft Project desktop client installation.

Figure 8. Installation Progress bar

Microsoft Project 2002 Training Courseware Page 21

Microsoft Project 2002 Training Courseware Page 22

Microsoft Project Server Setup User Interface

Install Now can only be used under the following circumstances:

Custom must be used in the following circumstances:

Microsoft Project 2002 Training Courseware Page 23

01 Product Overview & Setup

01 Product Overview & Setup