01 Product Overview & Setup

8/8/2019 01 Product Overview & Setup

1/37

Microsoft Project 2002 TrainingCourseware

Lesson 1: Product Overview and Setup

Microsoft Corporation

June 2002


2/37

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

ObjectivesMicrosoft Project Product Family OverviewMicrosoft Project Server Architecture

Supporting TechnologiesSystem RequirementsFunctions of Setup.exeMicrosoft Project Desktop Client Setup User InterfaceMicrosoft Project Server Setup User InterfaceAutomatic Recovery (Rollback)Registry SettingsUpgrade ConsiderationsEnterprise ToolsInstallation from a URLLicensing ArchitectureExercises

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


3/37

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 ofits customers. As with earlier versions, Microsoft Project Standard 2002 can be used as a stand-alonedesktop application. Additionally, collaboration between the project manager and the projectresources 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 soldseparately. A Microsoft Project Web Access client license can also be used to access MicrosoftProject Server. Finally, Microsoft Project Professional 2002 builds on Microsoft Project Standard toprovide enterprise features for managing resources and analyzing company wide project performancewhen 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 ofbusinesses and organizations. The following is a listing of the Microsoft Project line of products, targetaudiences, and description of the solution.

Table 1. Solution offerings

Product/s Audience

Description

Microsoft Project Standard 2002 Single project manager with 1 to 4projects to manage

Stand-alone productRobust easy to use projectmanagement tool on the desktop

Microsoft Project Standard withMicrosoft Project Server

Single project manager with 5 to 20projects and 5 to 10 resources ineach project

Workgroup mode collaboration

Inform and update resources andprojects via the WebDocument and Issue tracking viaSharePoint Team Services fromMicrosoft

Microsoft Project Server withMicrosoft Project Web Accessclient

A resource or Executive Manager Web access

Inform and update users andprojects via the Web without theneed for a desktop client

Microsoft Project Server with

Microsoft Project Professional

Multiple project managers with 150

to 1,000 projects and 20 to 50resources

Enterprise mode collaboration

Document and Issue tracking viaSharePoint

Data Modeling and PortfolioAnalysis

Microsoft Project solutions and their features sets are explained in more detail in the following pages.



4/37

Microsoft Project Standard Stand-alone New Features

Microsoft Project Standard 2002 helps business and project managers dynamically manageschedules and resources and analyze project information. Microsoft Project provides acomprehensive, easy-to-use solution. Based on customer feedback, Microsoft has made significantimprovements to the user interface and added key features that help business managers easilycreate 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 ProjectGuide. This feature enables users to be productive immediately, step-by-step interactive instructionswalk 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 specificgoals and tasks.

New! Wizards. New wizards have been added to Microsoft Project to reduce the time andcomplexity of setting up projects. As a new project plan is created, the Project Guide helps users toselect custom fields and templates and facilitates collaboration and the attachment of supportingdocumentation when coupled with Microsoft Project Server. When setting up project calendars, a newwizard simplifies the process of changing working time. A wizard will assist to customize the trackingview to track projects to suit the users needs.

Improved! Microsoft Office interface. A familiar and more intuitive Microsoft Office XP interfacecomplete with informative task panes and command bars makes it easy to learn and use MicrosoftProject.

New! Smart tags. Smart tag indicators give feedback when certain changes to the project planoccur. For example, when a resource is added to a task, a smart tag will ask for clarification and offeralternate scheduling calculations that may be more appropriate.

New! Microsoft Office integration. Task lists can be converted from Microsoft Excel, MicrosoftOutlook, or Microsoft Project Web Access into project plans in Microsoft Project. New import andexport capabilities such as the Microsoft Excel task list template make it easier than ever to switchbetween Microsoft Excel and Microsoft Project.

New! Microsoft Visio integration. Dates and tasks can be exported from Microsoft Project tocreate 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 anyproject.

Improved! Project Information Views. A variety of improvements have been made to project dataviews including the following:

Network Diagram view. Grouping summary tasks and displaying standard indicators and customfields 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 andother graph and Usage views.



5/37

Microsoft Project Standard in Workgroup Mode Features

Microsoft Project Standard can be used in Workgroup mode when used in conjunction with MicrosoftProject 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 andinitiatives are aligned with company goals.

New! Microsoft Project Web Access displayed in Microsoft Project. Project managers can viewMicrosoft Project Web Access directly from within Microsoft Project without having to log on to theservice through their Web browser. This feature makes it easier for managers to view informationwithout having to switch between two application windows.

New! Microsoft SharePoint Team Services Integration. Integration with Microsoft SharePointTeam Services (STS) and Microsoft Project Server allows users to centrally store and organizeproject-related documents and track issues:

New! Document Sharing. Enhance collaboration throughout the project life cycle with documentsharing. Users can now link supporting project documentation to project plans and tasks.

New! Issue Tracking. Manage projects more efficiently and effectively and improve teamcommunications 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 withautomated e-mail notifications of project updates, upcoming milestones, issues and more that containdirect links to project plans. Both project managers and team members can specify the types andfrequency of e-mail notifications and reminders.

New! Support for multiple managers. One manager can create the plan, another manager cansend 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 whenused with Microsoft Project Standard 2002 and for enterprise environments when used with MicrosoftProject Professional 2002. Through its Microsoft Project Web Access interface, Microsoft ProjectServer makes it easy for team members and stakeholders to collaborate and access projectinformation 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 resourcemanagement demands increase.

Microsoft Project Server 2002 is the companion server product for Microsoft Project Standard andMicrosoft Project Professional. Microsoft Project Server stores project and resource information in acentral database, thereby enabling standardized, consistent project planning and reporting across anorganization. A member of the .NET Enterprise Server family, Microsoft Project Server provides thescalability and security to adhere to a company's business processes and systems as project andresource management demands increase.

Microsoft Project Server extends project information to team members and stakeholders through theMicrosoft Project Web Access interface. Using just a Web browser, each team member orstakeholder with a Microsoft Project Server Client Access License (CAL) can access projectinformation from Microsoft Project Server without having Microsoft Project Standard or MicrosoftProject Professional installed on his or her computer.

Improved! Web Access User Interface. Users can experience the new look of Microsoft ProjectWeb Access, consistent with other Microsoft Office Web applications. Each team member's home



6/37

page displays items pertinent to the current session, such as newly-assigned tasks, action items, andindicators highlighting items changed since the last session. With Microsoft Project Web Access,team members and other stakeholders can save a view using sorting, grouping, orfiltering options,making it easy to regularly review and analyze project data pertinent to their role within theorganization.

Improved! Microsoft Project Web Access Views. Improved views in Microsoft Project Web Accessshow 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 GanttChart view through either Microsoft Project or the Web browser. The user can drill down into theproject information, group, filter and search on those projects. When Project Centerviews arecustomized with graphical indicators, users can quickly be alerted to problem areas, such asprojects that are behind schedule or over budget.

New! Resource Center. The new Resource Centerlets users view resource information easily.In addition, resource utilization and availability across the project portfolio can be evaluatedquickly.

Improved! View settings. Improved view settings allow users to see project informationconsistently. When users return to a view in Microsoft Project Web Access, the view looks thesame 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 searchfor project information easily. Improved Microsoft Project Web Access components let usersdisplay splits in the Gantt Chart view; search; hierarchically group on outline codes; use moreautofilter conditions, including contains and begins with; and choose from pick lists in customfields.

Improved! Timesheets. Improved timesheets provide more flexibility in determining how teammembers report progress on their tasks. The project manager or administrator can choose thetracking method that best suits the current project, so team members can enter their progress in thetimesheet view as hours or as a percentage of work completed. When the timesheet is updatedthrough 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 listconveniently, maintaining it online in the same format as other task lists. They can then use it forpersonal reference or easily convert it into a project plan in Microsoft Project and take advantage ofits full project planning features.

New! Microsoft SharePoint Team Services Integration. Integration of Microsoft STS withMicrosoft Project Server allows users to centrally store and organize project-related documents andtrack issues.

New! Document sharing. Users can enhance collaboration throughout the life cycle of projectswith document sharing. Users can now link supporting project documentation to project plans andtasks.

New! Issue tracking. Users can manage projects more efficiently and effectively and improveteam 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 savetime with automated e-mail notifications of project updates, upcoming milestones, issues and morethat contain direct links to project plans. Both project managers and team members can specify thetypes and frequency of e-mail notifications and reminders.

Improved! Project updates. Project updates keep the entire team informed of project status.



7/37

Updates page. Project managers can stay on top of changes with the Update page in MicrosoftProject Web Access. When team members create or delegate tasks, or modify their schedules,project managers receive the changes in theirUpdate page. From the Update page, projectmanagers can review and selectively choose which updates to accept, and can set rules forautomatically accepting updates. The Update page also maintains a history of task changes foreasy 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 flexibletimesheet 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 fortop-down and peer-to-peer task delegation. Project managers can define summary tasks and thendirect team leads to create and assign the subtasks to their team members. At the project manager'sdiscretion, team members have the ability to reject a delegated task.

New!Microsoft Project Server compatibility.Microsoft Project Server 2002 is compatible withMicrosoft Project 2000, which relieves the necessity of upgrading both the server and the client at thesame time across a company.

Improved! Digital dashboards. Microsoft Project Server Web pages have been broken into smallercomponents to allow for more opportunities for Web part creation without the need to write ASPpages.

Improved! Support for industry standards. Utilizing industry standards, Microsoft Project easilyintegrates 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 ObjectAccess Protocol (SOAP) as the data transport mechanism, acts as the security schema to filter databased on the individual user.

Improved! Microsoft Project OLE DB provider. The Microsoft Project Standard OLE DB providerhas 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 customizeMicrosoft Project Server more easily thanks to improvements to the programmable interfaces of thecontrols.

New! Extensible document management integration. Users can integrate Microsoft ProjectServer with their organization's document management or issue-tracking solution through anextensible server-side object.

Improved! Microsoft Project Server user permissions. Users can lower administrative overheadwith improved permission settings. Administrators can create and set permissions for groups andindividual 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 featureslisted above plus new enterprise features that are highlighted below.

New! Portfolio Analyzer. With the new Portfolio Analyzer, the user can quickly query informationacross his or her portfolio. This tool enables the user to view project and resource information



8/37

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 PortfolioModeler. This tool allows the user to interactively modify project schedules and resource staffing, andsee the impact of the changes on a project portfolio. Modeling what-if scenarios allows users toidentify 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 consistentacross the project portfolio.

New! Enterprise resource pool. The enterprise resource pool provides a central location whereresource information is securely stored and managed, so users can get accurate, up-to-dateinformation about resources, including assignments, utilization, and availability across theorganization.

New! Enterprise project security.Access to enterprise projects is securely controlled withMicrosoft Project Server's check-in/check-out method. Microsoft Project Server protects the projectportfolio 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 Serveraccommodates performance and scalability needs through load balancing for the servers and clustersfor the database server.

Microsoft Project Professional Features

Microsoft Project Professional 2002 helps professional project managers manage their portfolio andresources, collaborate on projects, and analyze project information. Working with Microsoft ProjectServer, Microsoft Project Professional's powerful project planning, reporting, scenario analysis, andresource 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 ProjectProfessional, customers will have access to the following features:

New! Build team from enterprise. This feature assists in the selection of resources from theenterprise resource database, allowing users to find resources that have the right skills andavailability to work on their project. Users can filter and query the enterprise resource database tofine-tune their project resource assignments.

New! Resource Substitution Wizard. This wizard staffs projects using local and enterpriseresources, based on the skill project tasks require and the skills and availability of resources.

New! Generic resources. Generic resources support skills-based resource assignment andreplacement by allowing managers to define and save frequently used skill and code profiles asgeneric resources. These are of particular use when setting up a new project. The ResourceSubstitution Wizard will recognize the generic resource skill profiles and match them to the skills ofresources in the enterprise resource pool, based on their availability.

In addition, Microsoft Project Professional through its user interface has the ability to access thefollowing Microsoft Project Server features:

New! Enterprise standards. The Enterprise Global file holds the items such as reports, views, and



9/37

calendars that enforce enterprise standards. The Enterprise Global can only be opened, new itemscreated, defined, and modified in Microsoft Project Professional by a user with the appropriatepermissions.

New! Enterprise resource pool. Enterprise resources are imported into the Enterprise resourcepool through Microsoft Project Professional; the same resources' details can be defined and modifiedby a user with the appropriate permissions in Microsoft Project Professional.

The following features are described in the Microsoft Project Server section. They are available andcan 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 isreferred to as Workgroup mode and when the server is paired with Microsoft Project Professional itis called Enterprise mode. The modes have slightly different architectures that enable the differencesin 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 Centeras well as displaydata for resource availability views in the Resource Center. This change eliminates the extra workthat 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 Analyzerviews, resourceavailability 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 hypertexttransfer protocol (HTTP) and XML the request, storage, and retrieval of data is handled.



10/37

Figure 1. Workgroup mode architecture

View tables. The view tables store the project and resource data. These tables all begin with theprefix 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 onthe 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 asaccount info, views, site customization, file locations, etc. These tables all begin with the prefix ofMSP_WEB_, such as MSP_WEB_PROJECTS.

Project data tables. These tables hold project data and begin with the prefix of MSP_, such asMSP_CALENDARS.

Stored procedures. To improve the performance when writing and retrieving data, common SQLqueries have been complied and stored on the server.

Temporary directory. Project data storage area used for transaction processing to ensure dataintegrity, 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 sentto the PBO and stored in a temporary directory. The PBO gets a unique Project ID from the ProjectServer tables, if the ID exists then the ID is passed back, otherwise a unique ID is assigned. The PBOthen opens a connection to OLEDB provider. The OLEDB provider then publishes a set of tables tothe view tables overwriting any existing tables for that project. The temporary directory is thendeleted. 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) inenterprise mode. The PDS provides a high level of security to the SQL tables and will allow theowners of the system to take advantage of the PDS standard interface and security features when



11/37

creating extensions in order to add custom functionality. Secondly, the OLAP cube is created andupdated by SQL Analysis Services and used to create Portfolio Analyzerviews and generateresource 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 isgenerated. These tables have the prefix of MSP_CUBE.

OLAP Cube. Created by SQL Server Analysis Service, contains the field and dimension informationto 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 summaryrecord to the server and makes a request to the PDS to check-in the project file. The PDS makes arequest to the PBO to publish the Project Summary Record to the Project Server Tables. The PBOgets 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 toPDS. PDS makes a request to the PBO to publish the project file to the Project tables. PBO makes arequest 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 inboth server modes. SharePoint Team Services enable greater collaboration with the ability to linkdocuments and issues to project plans. TheNotification Process Engine polls the server formessages that need to be sent and then uses IIS Simple Mail Transport Protocol (SMTP) services to



12/37

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 forMicrosoft Project Server in workgroup mode. MSDE is installed when the Install Now option isselected for setup and only if Microsoft Project SQL is not already installed on the system. MSDEsupports 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. SharePointenables document and issues tracking in both server modes.

Microsoft SQL Server 2000 SPI or latermust be used as the database backend when MicrosoftProject Server is run in enterprise mode or in workgroup mode when there will be more than 10users.

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 databaseformat.

Microsoft Project Server should be setup using Mixed Authentication; this is because SQL accountsare 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 theexecutable is smart enough to just install the custom pages. STS can be installed to a different IISserver from Microsoft Project Server. Indexing Services in IIS should be turned on to enablesearching of STS sites.

Office Web Components

Office Web Components (OWC) ships with Microsoft Project Server and must be installed to create aPortfolio Analyzerview. In order to receive the full interactive functionality of a Portfolio Analyzerview 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 diskrequirements depend on the number of services installed on the computer. Minimum requirementsassume only Microsoft Project components (for example, Microsoft SQL Server and other servicesrun on separate computers). A thorough evaluation of the number of users, other services and



13/37

applications running, and the feature set to be used, must be considered before installation. Moredetailed information on enterprise considerations can be found in Lesson 41: Enterprise InstallationRecommendations.

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 MillenniumEdition, 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 plusan 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 forthe 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 wherethe operating system is installed (55 MB for typical installation on system with Microsoft Office XPinstalled; 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 willrequire an extra 50 MB of hard disk space for System Files Update (hard disk usage will varydepending 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 aservice provider; local and/or long distance telephone toll charges may apply

Windows-compatible network and MAPI compliant mail systems required for e-mail projectcollaboration

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



14/37

Microsoft Project Web Access

Use of Microsoft Project Web Access requires the following:


Memory

For Windows 98 and Windows 98 Second Edition - 24 MB of RAM for the operating system plusan 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 theoperating 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 MBof 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 Windows2000 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 32MB of RAM minimum for SQL Server (additional 64 MB recommended); additional servicesinstalled 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 (1GB 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 orlater (required for enterprise project and resource management)

CD-ROM drive



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

Some Internet functionality may require Internet access and payment of a separate fee to a



15/37

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 onthe computer. Minimum requirements assume only Microsoft Project Server components (forinstance, 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 MillenniumEdition, 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 plusan 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 forthe 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 48MB of RAM for Microsoft Project

Hard disk space. 30-204 MB of available hard disk space with 115 MB on the hard disk wherethe operating system is installed (55 MB for typical installation on system with Microsoft Office XPinstalled; 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 willrequire an extra 50 MB of hard disk space for System Files Update (hard disk usage will varydepending on configuration)

CD-ROM drive



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


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 projectcollaboration

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



16/37

Overview - Setup Enhancements

The installation process for Microsoft Project 2002 is much the same as it is for Microsoft Project2000. 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 improvedin 2002 applications. The changes made to the setup process were done primarily to incorporate thefollowing 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 likethe 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 aproduct is installed.

Functions of Setup.exe

Setup.exe has been updated to add new functionality, handle Office System Pack requirementdetection/installation, and chain additional Windows Installer products. The following items outline thecomplete life cycle and objectives of Setup.exe for Microsoft Project 2002:

Can be started by means ofAutoRun 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 occurwith 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 firstdialog box displayed depends on the version of Windows, whether or not the Windows Installer needsto be installed/updated, and whether or not System Files Update needs to be installed.



17/37

Support Operating System

If the operating system is unsupported, for example Windows 95 or Windows NT 4.0, an errormessage will display.

Windows Installer

If the Windows Installer Version 1.1 is not installed before Setup is run, it is automatically installed. Ina scenario where the Windows Installer is not yet installed, the following dialog box is displayedduring 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 locallyand 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 fromFigure 3. Instead, setup skips this part of the setup process and updates the Windows Installer whenthe System Files Update is installed. In this scenario, the dialog box from Figure 3 is displayed afterthe 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, orInstmsiw.exefor Windows NT 4.0.

Note Do not run either of these two .exe files on Windows Me or Windows 2000. These versions ofWindows 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 automaticallylaunches the installation of the System Files Update.

This core set of system files is included by default on computers with one of the followingconfigurations, 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 WindowsInstaller 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 thispoint, the first Setup dialog box is displayed.



18/37

Microsoft Project Core File Installation

After the Windows Installer and the System Files Update have been installed, Setup.exe calls theWindows 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

Microsoft Project Edition Market

.Msi

Server RetailPRJSvr.msi

Server EnterprisePRJSvrE.msi

Server TrialPRJSvrT.msi

Standard RetailPRJStd.msi

Standard EnterprisePRJStdE.msi

Standard TrialPRJStdT.msi

Professional RetailPRJPro.msi

Professional EnterprisePRJProE.msi

Professional Trial PRJProT.msi

MSDE AllSQLRun01.msi

Office System Pack AllOSP.msi

SharePoint Team Services AllOWS.msi

Microsoft Project Desktop Client Setup User Interface

The user interface in Microsoft Project 2002, for both Standard and Professional editions share manyfeatures with the user interface in Microsoft Project 2000. However, there are some new dialog boxesand 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 ProjectProfessional.

Microsoft Project Client Core File Installation

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



19/37

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



20/37

Cancel to stop the installation of Microsoft Project 2002.

The first dialog box after accepting the License Agreement, as shown in Figure 6, includes thefollowing 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 beavailable. If this option is selected, it is equivalent to setting the top Microsoft Office feature Run allfrom Network.

Depending on the option you select, the user interface is slightly different to allow for the differentfeatures offered by each option.

Tip The dialog box shown in Figure 6 allows you to change the installation location for MicrosoftOffice.

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 theprograms to be installed.



21/37

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.



22/37

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 anadded advantage for customers with large rollouts of Microsoft Project.

Complete Installation

Clicking the Complete option installs all of Microsoft Project and tools. Because a Completeinstallation 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 shouldbe selected. Figure 10 shows the dialog box that will be presented to the user with the Office Toolsmenu expanded. Clicking the + next to the feature displays its sub-features and clicking the icon nextto 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



23/37

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 InstallNow 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 tobe 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. Formore 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 considerationsand preparations that need to be made before installation. For a complete discussion see Lesson 41:Enterprise Installation Recommendations.



24/37

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 discussedlater, 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, ifnot then the installation will begin. The next Setup dialog box displayed is shown in Figure 4. In theUser 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 bechanged by clicking on the Browse button (see Figure 12).



25/37

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 thepassword requirements specified for the domain. Take note of this password as it may be used laterduring STS installation. Then next screen (Figure 14) displays the components that will be installedwhen the Install button is clicked.



26/37

Figure 14. Begin installation

A screen with the progress will be presented next. If no errors are encountered a message that theMicrosoft Project Server has been successfully installed will display. If an error is encountered anerror 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. STScan be installed from Microsoft Office XP CD or when the STS Configuration Wizard is run from theMicrosoft 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 SharePointConfiguration Wizard launches STSWIZ.exe or the same file can be found in the \support folder onthe CD and double clicked.

Note The template is copied to \\Program Files\Common Files\Microsoft Shared\Web ServerExtensions\50\template\1033.



27/37

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 aWeb site that is not an administrative Web site; STS cannot provision an administration Web site.



28/37

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 usedas the STS backend is installed. This does not need to be the same server that is hosting STS orMicrosoft Project Server.

Figure 18. Enter SQL database information

The next screen begins the installation when the user clicks the Next button. The following screenpresented will warn the user that the provisioning process may take some time. The final screen ismost important because it contains information necessary to completing the configuration betweenMicrosoft Project Server and STS (Figure 19).



29/37

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 Serverthe 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.



30/37

The SharePoint Customization Wizard can also be run prior to the installation of Microsoft ProjectServer. The advantage is that when a custom installation is run for Microsoft Project Server, theinformation about the SharePoint site can be entered at the time of installation and the above stepsare not necessary.

Automatic Recovery (Rollback)

Another change in Microsoft Project is the way costing of available drive space is performed. Bydefault, the Space Required value displayed in the Begin Installation dialog box does not includeRollback space requirements. This is to reduce customer confusion with the space requirementnumbers generated by setup.

Even though the value forSpace Available is higher than the value forSpace Required the usermay still not be able to install without disabling the Rollback feature. If they click Install in thisscenario, 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 itsclients as well as customized option settings for the applications. When all applications are running asexpected there is no need to go into the registry to view or modify any values, however whenproblems do arise it is sometimes useful to know where these settings are. It is important to alwaysbackup 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 messageHKey_Current_User\Software\Microsoft\Office\10.0\Web Server

\OWS Collaboration objects - informationHKey_Local_Machine\ Software\Microsoft\Office\10.0\Common\MS Project

\Messaging - managers and sendersHKey_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 andpassword

ApplicationEnterpriseDatabaseSTSViewsFileDropViewsSchedulingDatabase

\Services\SessionMgr



31/37

HKey_Local_Machine\ Software\Microsoft\Office\10.0\Web ServerOWS 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 theAuto-play screen select Upgrading and Database Configuration, then select Database UpgradeInformation or select the Installation Guide from the Auto-play screen. The information can also befound on the CD under the DOCS folder double click on PJSVR10.CHM.

Upgrading from Microsoft Project Central 2000 to Microsoft ProjectServer 2002

Workgroup mode

Upgrading from Microsoft Project Central 2000 to Microsoft Project Server 2002 Workgroup moderequires 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 storedin 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. Onceall 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 ProjectServer be installed to a different server and a new database be created for use with Microsoft ProjectServer. Then the data from the 2000 database is migrated to 2002. See the white paper MicrosoftProject Server Data Migration for detailed information. Basically data from 2000 will be imported viaMicrosoft Project Professional to the new 2002 database. That means resource and project plan dataonly.

Enterprise Tools

The Microsoft Project 2002 Resource Kit (PRK) is located on the Microsoft TechNet Website andcontains tools and instructions on how to deploy Microsoft Project, the database maintenance toolsand 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 informationcan 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 thanthe localized version, a language pack is installed, multiple language packs are also available. Inorder to enter foreign language data into Microsoft Project the Input Method Editor (IME) is availablefrom the PRK.



32/37

Installation from a URL

Microsoft Project supports installation from a mapped drive, a UNC connection, or from a CD-ROMdrive. In addition to these three installation sources, Microsoft Project allows you to install from thefollowing sources.

HTTP

HTTPS

FTP

With corporations becoming more and more Intranet/Internet-centric, adding installations from a Webserver 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 oftwo 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 thislocation.

If not using a link from within Internet Explorer, then use the/webinstall switch to alert Setup.exethat the source location is a Web server.

Because the installation is from a Web server, all of the Microsoft Project files are first copied intothe \Temporary Internet Files folder and then copied from this location into the specified installationfolder.

Tip After the installation is finished, the files in the \Temporary internet files folder are notautomatically deleted. One possible workaround is to lower the amount of disk space used fortemporary 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 theinstallation files, rather than the path to Setup.exe itself. This is because Setup.exe is downloaded tothe 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 Installerinstalled, or it needs to be updated, the Instmsi.exe (or Instmsiw.exe on Windows NT 4.0) package iscached 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 isactivated, the user has a perpetual license to use the product. If Microsoft Project is not activatedwithin 50 launches of the program, the program goes into Reduced Functionality Mode (RFM). In thismode 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



33/37

automatically bypasses the OAW. Bypass CD keys are included with large volume SKUs such asSelect Licenses.

Trial. Microsoft Project trials have a license with a finite time span under which the user can use theprogram. In order to continue the use of the program after this license has expired, the user cannotconvert it to a perpetual license with a Mandatory activation. They must uninstall the trial version andthen install a retail version of the product. A warning will display starting 3 days before the trial timeperiod 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 isavailable 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 topurchase Upgrade Advantage. The customer will receive rights to Microsoft Project Server andcan migrate to either Microsoft Project Standard version 2002 or Microsoft Project Professionalversion 2002.

If the customer is licensed for Microsoft Project 2000, through 31 July 2002, for each licenseof Microsoft Project 2000, the customer is eligible to purchase Software Assurance or UpgradeAdvantage. The customer will receive rights to Microsoft Project Server 2002 and can migrate toeither Microsoft Project Standard 2002 or Microsoft Project Professional 2002.

If the customer is already maintained via Software Assurance or Upgrade Advantage forMicrosoft Project, for each Software Assurance or Upgrade Advantage license that is active atthe time Microsoft Project 2002 appears on the Product List, the customer will receive rights toMicrosoft 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 eachlicense of Microsoft Project Central, the customer is eligible to purchase Microsoft Project CentralSoftware Assurance and migrate to Microsoft Project Server CAL.

Note Customers who do not purchase Software Assurance or Upgrade Advantage by 31 July 2002can 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 packageproduct. The only exception is if Microsoft Project 2000 is purchased before the end of June, theseusers then qualify for a Technology Guarantee (free upgrade) to get Microsoft Project (Standard)2002.

Activation



34/37

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 sentto the Microsoft licensing servers. If the information is validated, the Activation Complete dialog boxis displayed.

Coexistence of Multiple Versions

It is strongly recommended to remove earlier versions of Microsoft Project before installing MicrosoftProject 2002 or let the setup program upgrade the existing program files. However it is possible toinstall both versions on the same machine by taking care to install each into its own directory. TheGlobal files for each version are stored in separate locations.

2000 - :\Documents and Settings\\Application Data\Microsoft\MS Project\1033

2002 - :\:\Documents and Settings\\Application Data\Microsoft\MSProject\10\1033



35/37

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?



36/37

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

FTP8. 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 describedherein.

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as ofthe date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be acommitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the dateof publication.



37/37

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED ORSTATUTORY, 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 partof this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by anymeans (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 subjectmatter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of thisdocument 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, domainname, 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 ortrademarks 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.

Date post:	10-Apr-2018
Category:	Documents
Upload:	sagar-aliasjackey
View:	220 times
Download:	0 times