Sei sulla pagina 1di 259
Microsoft Office Project Server 2003 Installation Guide

Microsoft Office Project Server 2003 Installation Guide

Microsoft Office Project Server 2003 Installation Guide
Microsoft Office Project Server 2003 Installation Guide

Microsoft Office Project Server 2003 Installation Guide

Microsoft Office Project Server 2003 Installation Guide

Copyright

Information in this document, including URL and other Internet Web site references, is subject to change without notice. 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, e-mail address, logo, person, place or event is intended or should be inferred. 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.

© 2003 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows NT, Windows Server, and SharePoint 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.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Published: October 19, 2003 Updated: January 30, 2004; March 2, 2004; August 13, 2004; September 2004 Applies To: Microsoft Office Project Server 2003, Microsoft Office Project Professional 2003, Microsoft Office Project Web Access 2003 Authors: Mike Plumley; Roy Riley; Efren Edwards; James Scott Editors: Kerry Landen; Laura Graham; David Longmuir Reviewed By: Project Product Development

Microsoft Office Project Server 2003 Installation Guide

i

Table of Contents

Introduction

1

Introduction

1

Microsoft Office Project Server 2003 Online Books Series

1

What Can You Learn from This Book?

2

Who Should Read This Book?

3

Revision History

3

Chapter 1

5

Overview of Project Server 2003

5

Project Server 2003 Components

5

EPM Solution Architecture

7

Client Tier

7

Application Tier

7

Database Tier

8

Chapter 2

9

Installation Roadmaps

9

Single Computer Installation Roadmap

10

Small-Scale Installation Roadmap

13

Medium-Scale Installation Roadmap

16

Large-Scale Installation Roadmap

21

Chapter 3

25

Upgrading to Project Server 2003 from Earlier Versions of Microsoft Project

25

Upgrading from Microsoft Project Central or Microsoft Project Server 2002

26

Upgrading from Microsoft Project Server 2002 and MSDE

27

Migrating from SharePoint Team Services

30

Requirements for Migrating from SharePoint Team Services

31

Limitations to Migrating to Windows SharePoint Services

32

Migrating a SharePoint Team Services Site to Windows SharePoint Services

34

ii

Microsoft Office Project Server 2003 Installation Guide

Chapter 4

37

Prepare the Servers

37

Create User Accounts

37

Configure SQL Server Authentication

42

Install Decision Support Objects

43

Create an OLAP Administrator

45

Configure Internet Information Services

46

Configure Internet Explorer Enhanced Security

48

Chapter 5

50

Configure Windows SharePoint Services

50

Installing Windows SharePoint Services with a New Database

51

Install Windows SharePoint Services

51

Configure the Administrative Virtual Server

52

Set the Configuration Database Server

54

Extend the Virtual Server

56

Run the Windows SharePoint Services Configuration Wizard

57

Create a Windows SharePoint Services Administrator

59

Installing Windows SharePoint Services with an Existing Database

60

Install Windows SharePoint Services

60

Configure the Administrative Virtual Server

61

Set the Configuration Database Server

63

Extend the Virtual Server

65

Run the Windows SharePoint Services Configuration Wizard

66

Create a Windows SharePoint Services Administrator

67

Installing Windows SharePoint Services with WMSDE

68

Install Windows SharePoint Services

68

Run the Windows SharePoint Services Configuration Wizard

69

Chapter 6

71

Deploy the Database

71

Creating the Project Server Database Manually

71

Partitioning the Database

72

Partitioning the Database for New Deployments

74

Partitioning the View Tables

74

Partitioning the Project Tables

78

Using Three-Way Partitioning

82

Deploying Project Server 2003 with MSDE

88

Microsoft Office Project Server 2003 Installation Guide

iii

Chapter 7

90

Install Project Server 2003

90

Starting Project Server Setup

91

Project Server Setup Welcome Page

91

Product Key

92

User Information

92

End-User License Agreement

93

Select a Location for Installation

94

Choosing the Services to Install

96

Choose the Services That You Want to Install on This Server

96

Create the View Processing Share

98

Enter the Session Manager Server Name

99

Enter the View Processing Server Information

99

Choosing Database Options

101

Connecting to an Existing Database

101

Connect to an Existing Database

101

Enter Connection Information for View Tables

102

Enter Database Account Information

103

Creating a New Database That Uses Windows Authentication

104

Enter Connection Information for View Tables

105

Create Database Account Information

106

Creating a New Database That Uses SQL Server Authentication

107

Enter Connection Information for View Tables

109

Create Database Account Information

110

Configuring the Front-End Components

111

Enter Analysis Services Connection Information

111

Select a Web Site

112

Enter Web Server Address Information

113

Enter SMTP Mail Server Information

115

Connect to a Web Server Running Windows SharePoint Services

116

Enter Windows SharePoint Services Account Information

117

Connect to SharePoint Portal Server

118

Choose an Installation Environment

119

Enter the Administrator Password

120

Complete the Installation

121

Chapter 8

123

Post-Installation Tasks

123

Configure Items Bypassed During Setup

123

Configuring Analysis Services Settings

123

Downloading ActiveX Controls

125

Configuring Web Server Address Settings

126

iv

Microsoft Office Project Server 2003 Installation Guide

Configuring Windows SharePoint Services Settings 127

128

Configuring SMTP Mail Server Settings 129 Synchronize the Public Document Site 130

Migrate the Analysis Services Repository to a SQL Server Database 130

131

Add Users to Cube Database Roles in Analysis Services

Enable Users to Log on By Using a Different Windows User Account 132 Configuring Project Professional for Project Server 2003 134

Configuring SharePoint Portal Server Settings

Deploy Project Professional

134

Using the Office Resource Kit

134

Set Up Connection Information for Project Server 2003

135

Add Project Server and Windows SharePoint Services as Trusted Sites in Internet Explorer

136

Updating the MSP_WEB_ADMIN Table for Hosted Deployments By Using Windows SharePoint Services

137

Chapter 9

138

Extranet and Non-Trusted Domain Scenarios

138

Configuring Project Server 2003 for the Extranet

138

Set up Analysis Services to Be Accessible By Means of HTTP

138

Configure Your Deployment

140

Configuring a Non-Trusted Domain Deployment 142

Chapter 10

144

System Optimization

144

Database Optimization Scripts

144

Master Stored Procedures

145

MSP_UTIL_EXEC_MOVE_DATABASE_OBJECTS 145

145

MSP_UTIL_EXEC_MOVE_TABLES_TO_FILEGROUP 145

MSP_UTIL_EXEC_MOVE_INDEXES_TO_FILEGROUP 146

146

Database Partitioning 147 Preparing to Partition the Database 148 Migrating Existing Deployments 149 Partitioning the View Tables 149 Partitioning the Project Tables 152 Using Three-Way Partitioning 155 Migrating from View Tables Partition to Three-Way Partition 161

Migrating from Project Tables Partition to Three-Way Partition 164 Load Balancing the Project Server Views Notification Service 167 Configuring the Computers Running

169

MSP_UTIL_EXEC_MOVE_DATABASE_FILES

Component Utility Stored Procedures

the Project Server Views Notification Service

Microsoft Office Project Server 2003 Installation Guide

v

Configuring the Front-End Application Server to Support Load-Balancing of the Project Server Views Notification Service

170

Chapter 11

172

International Deployment Considerations

172

Planning an International Deployment

173

Installing Project Server Multilingual User Interface Packs

174

Project Server Installation Language

175

Project Server Code Page Limitations

176

Using Windows SharePoint Services in an International Deployment

176

Ensuring that Windows SharePoint Services URLs Are in Unicode

177

Using Input Method Editor

177

Choosing an Operating System for Project Web Access Users

178

Viewing Project Web Access in Other Languages

178

Appendix A

182

Additional Resources

182

Microsoft Office Project Server 2003 Online Books Series

182

Project Server–Related Web Sites

183

Appendix B

184

Project Server Service Accounts

184

Analysis Services Account

184

Windows SharePoint Services Administrator Account

185

Project Server Database Account

185

Windows SharePoint Services Database Account

186

Project Server User Database Account

186

Project User Database Account

187

View Administrator Account

187

Appendix C

188

Project Server Installation Tools

188

Connection Information Tool 188

EditSite Tool

190

Site Information Tab

193

Database Information Tab

194

Windows SharePoint Services Information Tab

196

Completing Site Setup 197

198

Project Server COM+ Settings Tool 200

Windows SharePoint Services Backup and Restore Tool 201

202

Project Server Data Migration Tool

Running the EditSite Tool from the Command Line

vi

Microsoft Office Project Server 2003 Installation Guide

Windows SharePoint Services Site Migration Tool

204

Hosted Deployment Migration

204

Single Project Restore

204

Running the Tool 205 WinHTTP Proxy Configuration Tool 208 WinHTTP Proxy Configuration Tool Options 208 Examples 210

Appendix D

212

Configuring the Sample Database

212

Installing Project Server 2003 with the Sample Database

212

User Accounts

213

Sample Data Installation and Configuration

214

Configuring Windows SharePoint Services for Project Server 2003

215

Installing Multiple Copies of the Windows SharePoint Services Data

218

Building the OLAP Cube

220

Verifying the Resource Availability Tables

222

Granting Users Permission to Access the OLAP Cube

223

Creating Project Server Accounts for Project Professional Users

223

Configuring Internet Explorer

225

Setting Up Outlook Integration

225

Backing Up Custom Databases

226

Appendix E

229

Uninstalling Project Server 2003

229

Appendix F

230

Installing Project Server 2003 From the Command Line

230

Command-Line Parameters for Installing Project Server 2003

230

Select a Location for Installation

231

Choose the Services You Want to Install on This Server

231

Installing the Session Manager Service Without the Front-End Service

232

Create the View Processing Share

232

Enter the Session Manager Server Name

233

Enter the View Processing Server Information

233

Enter Database Server Information

234

Enter Connection Information for Views Tables

234

Enter Database Account Information

236

Enter Analysis Services Connection Information

236

Select a Web Site

237

Enter Web Server Address Information

237

Enter SMTP Mail Server Information

238

Microsoft Office Project Server 2003 Installation Guide

vii

Connect to a Web Server Running Windows SharePoint Services

238

Connect to a Web Site Running SharePoint Portal Server 2003

239

Choose an Installation Environment

240

Enter the Administrator Password

240

Appendix G

242

Working with the Outlook Add-in

242

Installing the Outlook Add-in

242

Security Settings Required for Installation 242

Connecting to the Computer Running Project Server 2003 243

243

Removing the Outlook Add-in from Outlook

Appendix H

244

Installing Project Web Access ActiveX Controls

244

Appendix I

246

Service Packs for Project Server Components

246

Microsoft Office Project Server 2003 Installation Guide

1

Introduction

The Microsoft Office Project Server 2003 Installation Guide is designed to help your organization understand the tasks involved in installing Microsoft® Office Project Server 2003.

The Microsoft Office Project Server 2003 Installation Guide is a comprehensive guide that covers various types of installations, including a single computer installation and small-scale, medium-scale, and large-scale installations. For a step-by-step guide for single computer, small-scale, and medium-scale installations, see the following resources:

Microsoft Office Project Server 2003 Single Computer Installation Guide

http://go.microsoft.com/fwlink/?LinkId=34499

Microsoft Office Project Server 2003 Small-Scale Installation Guide

http://go.microsoft.com/fwlink/?LinkId=34500

Microsoft Office Project Server 2003 Medium-Scale Installation Guide

http://go.microsoft.com/fwlink/?LinkId=34501

Send us your feedback. Please let us know what you think about the quality of this content. If this text does not meet your needs, let us know how we can improve it. If this text was helpful to you, let us know how it helped.

Microsoft Office Project Server 2003 Online Books Series

The Microsoft Office Project Server 2003 Online Books series documents the Microsoft Office Enterprise Project Management (EPM) Solution and provides a detailed reference for all phases of deploying Project Server 2003, including planning, installation, configuration, and administration. Each book is designed to stand alone and can be referred to on an as-needed basis. You can also read these books in the order listed below for a complete guide to deploying Project Server 2003:

Microsoft Office Project Server 2003 Solution Planning Guide

Microsoft Office Project Server 2003 Configuration Planning Guide

2

Microsoft Office Project Server 2003 Installation Guide

Microsoft Office Project Server 2003 Disaster Recovery Guide

Microsoft Office Project Server 2003 Installation Guide

This includes the following resources:

Microsoft Office Project Server 2003 Single Computer Installation Guide

Microsoft Office Project Server 2003 Small-Scale Installation Guide

Microsoft Office Project Server 2003 Medium-Scale Installation Guide

Microsoft Office Project Server 2003 Application Configuration Guide

Microsoft Office Project Server 2003 Administrator’s Guide

Microsoft Office Project Server 2003 Security Group Guide

http://go.microsoft.com/fwlink/?LinkID=33554

This includes the following resources:

Microsoft Office Project Server 2003 Portfolio Managers Guide

Microsoft Office Project Server 2003 Project Managers Guide

Microsoft Office Project Server 2003 Resource Managers Guide

Microsoft Office Project Server 2003 Team Leads Guide

Microsoft Office Project Server 2003 Team Members Guide

Microsoft Office Project Server 2003 Executives Guide

A key part of deploying Project Server 2003 as part of a Microsoft Office Enterprise Project Management (EPM) Solution is proper planning. These books will help your organization plan for deployment by explaining Project Server 2003 in detail, highlighting the questions you should ask throughout the planning phase, and providing a reference for the requirements during each phase of deployment. These books are not intended to be a substitute for proper planning within your organization as to what your EPM Solution should be. The Microsoft Office Project Server 2003 Online Books series will help you succeed in deploying your organization’s project management solution.

What Can You Learn from This Book?

This guide covers the installation of Microsoft Office Project Server 2003 and its related components. The following topics are covered:

Migrating to Project Server 2003 from Microsoft Project Server 2002 and Project Central.

Microsoft Office Project Server 2003 Installation Guide

3

Preparing your servers for installation of Project Server 2003, Microsoft Windows® SharePoint® Services, and other related components.

Deploying your Project Server 2003 database, both manually and automatically, by means of the Project Server Setup program.

Database optimization and partitioning.

Project Server 2003 installation tools.

Who Should Read This Book?

This guide is designed to benefit the following professionals:

IT administrators

Those individuals who are responsible for installing Project Server 2003 and its related components.

Database administrators

Those individuals who are responsible for database maintenance.

Deployment planners

Those individuals who plan the deployment of Project Server 2003 within your organization.

Revision History

The following table provides the revision history for this document.

Date

Revision

October 2003

Initial Publication.

January 2004

Added Chapter 9, Extranet and Non- Trusted Domain Scenarios.

Added Chapter 11, International Deployment Considerations.

Added Appendix F, Installing Project Server 2003 from the Command Line.

Added Appendix G, Working with the Outlook Add-In.

Added Appendix H, Installing Project Web Access ActiveX Controls.

Updated Appendix C, Project Server Installation Tools.

4

Microsoft Office Project Server 2003 Installation Guide

Date

Revision

March 2004

Updated Chapter 5, Configure Windows SharePoint Services.

Updated Appendix H, Installing Project Web Access ActiveX Controls.

August 2004

Added Appendix B, Project Server Service Accounts.

Added Appendix I, Service Packs for Project Server Components.

September 2004

Updated the section Database Partitioning in Chapter 10, System Optimization.

Added the section Load Balancing the Project Server Views Notification Service to Chapter 10, System Optimization.

5

Microsoft Office Project Server 2003 Installation Guide

1

Overview of Project Server 2003

Microsoft® Office Project Server 2003 is designed to support collaboration between project managers who are using Microsoft Office Project Professional 2003 and team members who are using Microsoft Office Project Web Access 2003. The Microsoft Office Enterprise Project Management (EPM) Solution is an integrated system that includes Project Professional 2003, Project Web Access 2003, and Project Server 2003.

Project Server 2003 provides timesheets, status reports, portfolio analysis and modeling, enterprise resources, and enterprise templates. When integrated with Microsoft Windows® SharePoint® Services, Project Server 2003 provides document management and issues and risk tracking features.

Users access Project Server 2003 by means of Project Web Access, a browser-based client that enables team members, resource managers, and executives to enter and view timesheet information and view portfolio reports. Project managers can create projects or create or modify the Enterprise Resource Pool by using Project Professional and save that data to the Project Server database.

Project Server 2003 is flexible and is designed to enable you to extend your EPM Solution. You can begin by using a limited number of enterprise features and then add additional features as needed.

Project Server 2003 Components

Project Server 2003 consists of the following software components:

Project Server Front-End service Service requests.

View Processing

Handles all Project Web Access and Project Data

Generates static views of published data for Project Web Access.

6

Microsoft Office Project Server 2003 Installation Guide

Session Manager

Handles the session-state information for each client that is

connecting to Project Server 2003 from Project Web Access.

Project Server 2003 requires the services and support of the following Microsoft applications:

Internet Information Services (IIS) 5.0 or later

Provides the foundation for secure

and scalable Web-based solutions. IIS is included as part of the Microsoft

Windows 2000 Server and Microsoft Windows Server™ 2003 operating systems.

Microsoft SQL Server™ 2000

Provides database management for users who want

to take advantage of all enterprise functionality that is built in to Project Server 2003 in a scalable environment. Both SQL Server 2000 Standard Edition and SQL Server 2000 Enterprise Edition support the enterprise functionality of Project Server 2003, but only SQL Server 2000 Enterprise Edition supports advanced deployment features such as failover or HTTP Internet support. You must install SQL Server 2000 before you can install Project Server 2003 or configure Windows SharePoint Services for Project

Server 2003.

SQL Server 2000 Analysis Services

Provides online analytical processing (OLAP)

services, which are required for the Portfolio Analyzer feature of Project Server 2003.

The Portfolio Analyzer feature is only available as an enterprise feature of Project Server 2003.

Windows SharePoint Services

Provides document library and issues and risks

tracking services when properly configured for Project Server 2003. You can download

Windows SharePoint Services from the Microsoft Web site

(http://go.microsoft.com/fwlink/?linkid=23448), or you can configure an existing

installation of Windows SharePoint Services for Project Server 2003.

Note

Project Server 2003 is not compatible with SharePoint® Team Services.

Microsoft Office SharePoint Portal Server 2003 searching of Project Server 2003 document libraries.

Project Professional

Enables the indexing and

Provides enterprise-wide project and resource management

capabilities, collaboration functionality, and scenario analysis tools for organizations that require an enterprise project management solution. To access Project Server 2003,

Project Professional 2003 has the following Internet browser requirements:

o

Internet Explorer 5.01 with SP3 or later

o

Internet Explorer 5.5 with SP2 or later

o

Internet Explorer 6 with SP1 or later (recommended)

The Microsoft Office Project Add-in for Outlook®

Enables users to keep track of

tasks that are assigned to them in projects. Tasks can be tracked in Microsoft

Microsoft Office Project Server 2003 Installation Guide

7

Outlook 2000 or later (or Outlook Web Access in a limited capacity). The Outlook Integration add-in is available from the Project Web Access Home page.

Microsoft Internet Explorer version 5.01 (or later)

Enables access to the Project

Web Access user interface (UI). Internet Explorer 5.5 or later is required in order to

use all available Project Web Access features.

EPM Solution Architecture

The Microsoft EPM Solution is based on a common three-tiered architecture, consisting of a client tier, an application tier, and a database tier.

Note

EPM Solution Architecture, in the Microsoft Office Project Server 2003 Configuration Planning Guide (http://go.microsoft.com/fwlink/?LinkID=20235).

For more information about the EPM Solution architecture, see Chapter 5, Planning Your

Client Tier

The client tier of the Microsoft EPM Solution includes Project Web Access and Project Professional. Project Web Access provides access to timesheets, project views, status reports, administration pages, and the Build Team feature. It also provides access to the document library and risk and issue tracking by means of Windows SharePoint Services integration. Project Web Access consists of a set of Microsoft ActiveX® controls (primarily a grid control) and Hypertext Markup Language (HTML) pages provided by Active Server Pages (ASPs). The ActiveX controls are downloaded the first time you access Project Web Access. Project Web Access requires Internet Explorer 5.01 or later.

Project Professional 2003 runs on Windows 2000 and later. Project managers can use Project Professional 2003 to publish projects to the Project Server database and manage updates to the project information that is stored on the server. You can also use Project Professional 2003 to open, modify, and save enterprise projects and resources.

Application Tier

The application tier is made up of Web-based front-end applications that are integrated with Internet Information Services (IIS). These applications include Project Server 2003 and Windows SharePoint Services.

Project Server 2003 is the central component of an EPM Solution and is a robust and highly scalable Web-based server application. Project Server 2003 runs on Windows 2000 Server or later and requires Internet Information Services (IIS) version 5.0 or later.

8

Microsoft Office Project Server 2003 Installation Guide

Windows SharePoint Services is an optional component that integrates with Project Server 2003 to provide document management and risk and issue tracking. Windows SharePoint Services is available as a free download from Microsoft at www.microsoft.com and is only supported on a computer running Windows Server 2003, IIS 6.0, and ASP.NET.

Database Tier

SQL Server provides the database tier of the EPM Solution. Project Professional and Project Web Access work with both the non-enterprise and enterprise tables in the SQL Server database. Project Server 2003 uses View tables that contain time-phased data for all projects that are published to the server to reduce the load on the computer running SQL Server and to allow for greater scalability. Project Server 2003 provides the primary means of access to the database, although Project Professional can save projects directly to the database by means of Open Database Connectivity (ODBC).

9

Microsoft Office Project Server 2003 Installation Guide

2

Installation Roadmaps

This chapter describes four examples of hardware deployments for Microsoft® Office Project Server 2003. Each example includes a roadmap of, or high-level steps for, the installation process to assist you in planning your deployment. Identify the deployment roadmap in this chapter that most closely matches the architecture that you require for your organization, and then follow the procedures in that topic to complete your installation.

Before you install Project Server 2003, read the Microsoft Office Project Server 2003

Configuration Planning Guide (http://go.microsoft.com/fwlink/?LinkID=20235). The Microsoft Office Project Server 2003 Configuration Planning Guide includes hardware recommendations for various tested configuration scenarios. When you are planning your hardware requirements, be sure to consider the type of hardware that was used to test the configurations and compare it against the hardware that you intend to use. If you are using different hardware, you will see different performance results.

Note

The procedures in this chapter assume that you have the required hardware for your deployment, and that you have installed an appropriate version of Microsoft Windows®, along with Microsoft SQL Server™ 2000, Analysis Services (if applicable), and the required service packs.

If you are upgrading or migrating from an earlier version of Microsoft Project Server, see Chapter 3, Upgrading to Project Server 2003 from Earlier Versions of Microsoft Project in the Microsoft Office Project Server 2003 Installation Guide before beginning your deployment. You will need to follow the steps in this chapter when you deploy Project Server 2003.

Important

from a system failure or disaster. Keep track of the accounts that you create, computer names, passwords, and setup options. Be sure you keep a copy of this documentation with your disaster recovery materials, preferably in an off-site location.

Document your installation thoroughly, in case you need to duplicate it when recovering

10

Microsoft Office Project Server 2003 Installation Guide

Single Computer Installation Roadmap

A single computer deployment can support a small- to medium-sized organization and can be used by a large organization to test Project Server 2003. A single computer deployment supports up to 500 users, but is not ideal for a large-scale production environment. For information about single computer deployments, including sample hardware sets and performance numbers, see the topic Configuration Scenario 1 in Chapter 6, selecting a Project Server Configuration, of the Microsoft Office Project Server 2003 Configuration Planning

Note

Sample database.

You must use a single computer deployment if you are installing the Project Server 2003

deployment if you are installing the Project Server 2003 Example of a single computer deployment. Follow

Example of a single computer deployment.

Follow the procedures in this topic to install Project Server 2003 on a single computer. This topic assumes that you are not upgrading from a previous deployment of Microsoft Project Server.

Note

If you are installing Project Server 2003 and Microsoft Windows SharePoint® Services on a

Terminal Server, or if you install Windows SharePoint Services after you install Project Server 2003, you will need to add the Project Server URL to the Excluded Path list in Windows SharePoint Services. For more information, see the Microsoft Windows SharePoint Services Administrator’s Guide on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=12860).

To get started

1. Acquire the necessary hardware for your deployment.

2. Install the operating system and SQL Server 2000.

Note

Configure SQL Server 2000 to use mixed-mode authentication.

3. Install SQL Server 2000 Service Pack 3 (SP3).

Note

For more information about SQL Server 2000 SP3, see Appendix I, Service Packs for

Project Server Components, in the Microsoft Office Project Server 2003 Installation Guide.

Microsoft Office Project Server 2003 Installation Guide

11

4. If you plan to use online analytical processing (OLAP) functionality, install Analysis Services and SQL Server 2000 Analysis Services Service Pack 3a (SP3a).

Note

For more information about SQL Server 2000 Analysis Services SP3, see Appendix I,

Service Packs for Project Server Components, in the Microsoft Office Project Server 2003 Installation Guide.

5. Verify network and domain connectivity.

To prepare the servers

1. Create the following user accounts:

A Windows domain user account or local user account. This account allows Project Server to access SQL Server Analysis Services and Windows SharePoint Services.

A SQL Server account that belongs to the Database Creators and Security Administrators roles. This account will be used to create the database during the setup process. You can also use your system administrator (sa) account for this purpose.

Create these accounts by using the procedures in the topic Create User Accounts in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

2. Create an OLAP administrator by using the procedure in the topic Create an OLAP Administrator in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

3. If your implementation of SQL Server is not configured to use mixed-mode authentication, configure it to use mixed-mode authentication by using the procedures in the topic Configure SQL Server Authentication in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

4. Configure Internet Information Services by using the procedures in the topic Configure Internet Information Services in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

5. Configure Microsoft Internet Explorer security on Microsoft Windows Server™ 2003 by using the procedure in the topic Configure Internet Explorer Enhanced Security in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

To install Windows SharePoint Services

1. Install Windows SharePoint Services on your server by using the procedure in the topic Install Windows SharePoint Services in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

12

Microsoft Office Project Server 2003 Installation Guide

2. Configure the administrative virtual server for Windows SharePoint Services by using the procedure in the topic Configure the Administrative Virtual Server in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

3. Configure the Windows SharePoint Services configuration database by using the procedure in the topic Set the Configuration Database Server in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

4. Extend the virtual server by using the procedure in the topic Extend the Virtual Server in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

5. Create a Windows SharePoint Administrator by following the procedure in the topic Create a Windows SharePoint Services Administrator in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

6. Run the Windows SharePoint Service Configuration Wizard by following the procedure in the topic Run the Windows SharePoint Services Configuration Wizard in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

To install Project Server 2003

1. If you want to create the database in SQL Server manually, follow the procedure in the topic Creating the Project Server Database Manually in Chapter 6, Deploy the Database of the Microsoft Office Project Server 2003 Installation Guide. This step is not required, because Project Server Setup can create the database for you during installation.

2. Run the Project Server Setup program by using the procedures in Chapter 7, Install Project Server 2003 of the Microsoft Office Project Server 2003 Installation Guide.

To perform post-installation tasks

1. Configure any items that you bypassed when running Project Server Setup by using the procedures in the topic Configure Items Bypassed During Setup in Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

2. To enable users to use the Log on using a different Microsoft Windows user account link on the Logon page, follow the procedures in the topic Enable Users to Log On By Using a Different Windows User Account in Chapter 8, Post- Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

3. To give users access to the OLAP cube, follow the procedure in the topic Add Users to Cube Database Roles in Analysis Services in Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

Microsoft Office Project Server 2003 Installation Guide

13

4. To ensure proper connectivity to Analysis Services, migrate the Analysis Services repository to a SQL Server database by using the procedure in the topic Migrate the Analysis Services Repository to a SQL Server Database in Chapter 8, Post- Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

Small-Scale Installation Roadmap

Follow the procedures in this topic to install Project Server 2003 in a small-scale deployment such as the one shown in the following figure.

deployment such as the one shown in the following figure. Example of a small-scale deployment. To

Example of a small-scale deployment.

To get started

1. Acquire the necessary hardware for your deployment.

2. Install the operating system on each computer.

3. Install SQL Server 2000 on the appropriate computer.

Note

Configure SQL Server 2000 to use mixed-mode authentication.

4. Install SQL Server 2000 Service Pack 3 (SP3).

Note

For more information about SQL Server 2000 SP3, see Appendix I, Service Packs for

Project Server Components, in the Microsoft Office Project Server 2003 Installation Guide.

5. If you plan to use online analytical processing (OLAP) functionality, install Analysis Services and SQL Server 2000 Analysis Services Service Pack 3 (SP3) on the appropriate computer.

14

Microsoft Office Project Server 2003 Installation Guide

Note

For more information about SQL Server 2000 Analysis Services SP3, see Appendix I,

Service Packs for Project Server Components, in the Microsoft Office Project Server 2003 Installation Guide.

6. Verify network and domain connectivity.

To prepare the servers

1. Create the following user accounts:

A Windows domain user account or local user account on the Analysis Services server, to allow Project Server 2003 to access Microsoft SQL Server 2000 Analysis Services.

A Windows domain user account or local user account on the server running Windows SharePoint Services, to allow Project Server 2003 to access Windows SharePoint Services.

A SQL Server account that belongs to the Database Creators and Security Administrators roles. This account will be used to create the database during the setup process. You can also use your sa account for this purpose.

Create these accounts by using the procedures in the topic Create User Accounts in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

2. Create an OLAP Administrator by using the procedure in the topic Create an OLAP Administrator in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

3. If your implementation of SQL Server is not configured to use mixed-mode authentication, configure it to use mixed-mode authentication by using the procedures in the topic Configure SQL Server Authentication in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

4. Install the Analysis Services Decision Support Objects by using the procedure in the topic Install Decision Support Objects in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

5. Configure Internet Information Services on the computer on which you will install Project Server by using the procedures in the topic Configure Internet Information Services in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

6. Configure Internet Explorer security on Windows Server 2003 by using the procedures in the topic Configure Internet Explorer Enhanced Security in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

Microsoft Office Project Server 2003 Installation Guide

15

To install Windows SharePoint Services

1. Install Windows SharePoint Services on your server by using the procedure in the topic Install Windows SharePoint Services in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

2. Configure the administrative virtual server for Windows SharePoint Services by using the procedure in the topic Configure the Administrative Virtual Server in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

3. Configure the Windows SharePoint Services configuration database by using the procedure in the topic Set the Configuration Database Server in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

4. Extend the virtual server by using the procedure in the topic Extend the Virtual Server in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

5. Create a Windows SharePoint Administrator by following the procedure in the topic Create a Windows SharePoint Services Administrator in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

6. Run the Windows SharePoint Service Configuration Wizard by following the procedure in the topic Run the Windows SharePoint Services Configuration Wizard in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

7. If you are upgrading from a SharePoint Team Services installation, and you want to migrate your data, follow the procedures in the topic Migrating from SharePoint Team Services in Chapter 3, Upgrading to Project Server 2003 from Earlier Versions of Microsoft Project of the Microsoft Office Project Server 2003 Installation Guide.

To install Project Server 2003

1. If you want to create the database in SQL Server manually, follow the procedure in the topic Creating the Project Server Database Manually in Chapter 6, Deploy the Database of the Microsoft Office Project Server 2003 Installation Guide. This step is not required, because Project Server Setup can create the database for you during installation.

2. Run the Project Server Setup program on the computer on which you want to install Project Server by using the procedures in Chapter 7, Install Project Server 2003 of the Microsoft Office Project Server 2003 Installation Guide.

16

Microsoft Office Project Server 2003 Installation Guide

To perform post-installation tasks

1. Configure any items that you bypassed when running Project Server Setup by using the procedures in the topic Configure Items Bypassed During Setup in Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

2. To enable users to use the Log on using a different Microsoft Windows user account link on the Logon page, follow the procedures in the topic Enable Users to Log On By Using a Different Windows User Account in Chapter 8, Post- Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

3. To give users access to the OLAP cube, follow the procedure in the topic Add Users to Cube Database Roles in Analysis Services in Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

4. To ensure proper connectivity to Analysis Services, migrate the Analysis Services repository to a SQL Server database by using the procedure in the topic Migrate the Analysis Services Repository to a SQL Server Database in Chapter 8, Post- Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

5. If you are using Project Server 2003 in a hosted deployment with Windows SharePoint Services, use the procedures in the topic Updating the MSP_WEB_ADMIN Table for Hosted Deployments By Using Windows SharePoint Services in Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

Medium-Scale Installation Roadmap

Follow the procedures in this topic to install Project Server 2003 in a medium-scale deployment such as the one shown in the following figure.

Microsoft Office Project Server 2003 Installation Guide

17

Microsoft Office Project Server 2003 Installation Guide 17 Example of a medium-scale deployment. To get started

Example of a medium-scale deployment.

To get started

1. Acquire the necessary hardware for your deployment.

2. Install the operating system on each computer.

3. Install SQL Server 2000 on the appropriate computer.

Note

Configure SQL Server 2000 to use mixed-mode authentication.

4. Install SQL Server 2000 Service Pack 3 (SP3).

Note

For more information about SQL Server 2000 SP3, see Appendix I, Service Packs for

Project Server Components, in the Microsoft Office Project Server 2003 Installation Guide.

5. If you plan to use online analytical processing (OLAP) functionality, install Analysis Services and SQL Server 2000 Analysis Services Service Pack 3 (SP3) on the appropriate computer.

Note

For more information about SQL Server 2000 Analysis Services SP3, see Appendix I,

Service Packs for Project Server Components, in the Microsoft Office Project Server 2003 Installation Guide.

6. Verify network and domain connectivity.

18

Microsoft Office Project Server 2003 Installation Guide

To prepare the servers

 

1. Create the following user accounts:

 

A Windows domain user account or local user account on the Analysis Services server, to allow Project Server 2003 to access Microsoft SQL Server 2000 Analysis Services.

A Windows domain user account or local user account on the server running Windows SharePoint Services, to allow Project Server 2003 to access Windows SharePoint Services.

A SQL Server account that belongs to the Database Creators and Security Administrators roles. This account will be used to create the database during the setup process. You can also use your sa account for this purpose.

Create these accounts by using the procedures in the topic Create User Accounts in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

2. Create an OLAP Administrator by using the procedure in the topic Create an OLAP Administrator in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

3. If your implementation of SQL Server is not configured to use mixed-mode authentication, configure it to use mixed-mode authentication by using the procedures in the topic Configure SQL Server Authentication in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

4. Install the Analysis Services Decision Support Objects using the procedure in the topic Install Decision Support Objects in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

 

Note

If you are installing the View Processing service on a different computer from the

Front-End service, you must install the Decision Support Objects on both computers.

 

5. Configure Internet Information Services on the computer on which you will install Project Server by using the procedures in the topic Configure Internet Information Services in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

6. Configure Internet Explorer security on Windows Server 2003 by using the procedures in the topic Configure Internet Explorer Enhanced Security in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

To install Windows SharePoint Services

 

1. Install Windows SharePoint Services on your server by using the procedure in the topic Install Windows SharePoint Services in Chapter 5, Configuring Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

Microsoft Office Project Server 2003 Installation Guide

19

2. Configure the administrative virtual server for Windows SharePoint Services by using the procedure in the topic Configure the Administrative Virtual Server in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

3. Configure the Windows SharePoint Services configuration database by using the procedure in the topic Set the Configuration Database Server in Chapter 5, Configuring Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

4. Extend the virtual server by using the procedure in the topic Extend the Virtual Server in Chapter 5, Configuring Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

5. Create a Windows SharePoint Administrator by using the procedure in the topic Create a Windows SharePoint Services Administrator in Chapter 5, Configuring Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

6. Run the Windows SharePoint Service Configuration Wizard by using the procedure in the topic Run the Windows SharePoint Services Configuration Wizard in Chapter 5, Configuring Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

7. If you are upgrading from a SharePoint Team Services installation, and you want to migrate your data, follow the procedures in the topic Migrating from SharePoint Team Services in Chapter 3, Upgrading to Project Server from Earlier Versions of Microsoft Project of the Microsoft Office Project Server 2003 Installation Guide.

To install Project Server 2003

1. If you want to create the database in SQL Server manually, follow the procedure in the topic Creating the Project Server Database Manually in Chapter 6, Deploy the Database of the Microsoft Office Project Server 2003 Installation Guide. This step is not required, because Project Server Setup can create the database for you during installation.

2. Run the Project Server Setup program on the computer on which you want to install Project Server by using the procedures in Chapter 7, Install Project Server 2003 of the Microsoft Office Project Server 2003 Installation Guide.

To perform post-installation tasks

1. Configure any items that you bypassed when running Project Server Setup by using the procedures in the topic Configure Items Bypassed During Setup in Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

2. To enable users to use the Log on using a different Microsoft Windows user account link on the Logon page, follow the procedures in the topic Enable Users to

20

Microsoft Office Project Server 2003 Installation Guide

Log On By Using a Different Windows User Account in Chapter 8, Post- Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

3. To give users access to the OLAP cube, follow the procedure in the topic Add Users to Cube Database Roles in Analysis Services in Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

4. To ensure proper connectivity to Analysis Services, migrate the Analysis Services repository to a SQL Server database by using the procedure in the topic Migrate the Analysis Services Repository to a SQL Server Database in Chapter 8, Post- Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

5. If you are using Project Server 2003 in a hosted deployment with Windows SharePoint Services, use the procedures in the topic Updating the MSP_WEB_ADMIN Table for Hosted Deployments By Using Windows SharePoint Services in Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

Microsoft Office Project Server 2003 Installation Guide

21

Large-Scale Installation Roadmap

Follow the procedures in this topic to install Project Server 2003 in a large-scale deployment such as the one shown in the following figure.

deployment such as the one shown in the following figure. Example of a large-scale deployment. To

Example of a large-scale deployment.

To get started

1. Acquire the necessary hardware for your deployment.

2. Install the operating system on each computer.

22

Microsoft Office Project Server 2003 Installation Guide

3. Install SQL Server 2000 on the appropriate computer.

Note

Configure SQL Server 2000 to use mixed-mode authentication.

4. Install SQL Server 2000 Service Pack 3 (SP3).

Note

For more information about SQL Server 2000 SP3, see Appendix I, Service Packs for

Project Server Components, in the Microsoft Office Project Server 2003 Installation Guide.

5. If you plan to use online analytical processing (OLAP) functionality, install Analysis Services and the SQL Server Analysis Services Service Pack 3 (SP3) on the appropriate computer.

Note

For more information about SQL Server 2000 Analysis Services SP3, see Appendix I,

Service Packs for Project Server Components, in the Microsoft Office Project Server 2003 Installation Guide.

6. Verify network and domain connectivity.

7. Configure clustering if you are using failover clusters or network load–balancing clusters as part of your deployment.

8. Verify network and domain connectivity.

To prepare the servers

1. Create the following user accounts:

A Windows domain user account or local user account on the Analysis Services server, to allow Project Server 2003 to access Microsoft SQL Server 2000 Analysis Services.

A Windows domain user account or local user account on the server running Windows SharePoint Services, to allow Project Server 2003 to access Windows SharePoint Services.

A SQL Server account that belongs to the Database Creators and Security Administrators roles. This account will be used to create the database during the setup process. You can also use your sa account for this purpose.

Create these accounts by using the procedures in the topic Create User Accounts in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

2. Create an OLAP Administrator by using the procedure in the topic Create an OLAP Administrator in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

3. If your implementation of SQL Server is not configured to use mixed-mode authentication, configure it to use mixed-mode authentication by using the procedures

Microsoft Office Project Server 2003 Installation Guide

23

in the topic Configure SQL Server Authentication in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

4. Install the Analysis Services Decision Support Objects by using the procedure in the topic Install Decision Support Objects in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

Note

Front-End service, you must install the Decision Support Objects on both computers.

If you are installing the View Processing service on a different computer from the

5. Configure Internet Information Services on the computer on which you will install Project Server by using the procedures in the topic Configure Internet Information Services in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

6. Configure Internet Explorer security on Windows Server 2003 by using the procedures in the topic Configure Internet Explorer Enhanced Security in Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Installation Guide.

To install Windows SharePoint Services

1. Install Windows SharePoint Services on your server by using the procedure in the topic Install Windows SharePoint Services in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

2. Configure the administrative virtual server for Windows SharePoint Services by using the procedure in the topic Configure the Administrative Virtual Server in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

3. Configure the Windows SharePoint Services configuration database by using the procedure in the topic Setting the Configuration Database Server in Chapter 5, Configuring Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

4. Extend the virtual server by using the procedure in the topic Extend the Virtual Server in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

5. Create a Windows SharePoint Administrator by using the procedure in the topic Create a Windows SharePoint Services Administrator in Chapter 5, Configuring Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

6. Run the Windows SharePoint Service Configuration Wizard by using the procedure in the topic Run the Windows SharePoint Services Configuration Wizard in Chapter 5, Configure Windows SharePoint Services of the Microsoft Office Project Server 2003 Installation Guide.

24

Microsoft Office Project Server 2003 Installation Guide

7. If you are upgrading from a SharePoint Team Services installation, and you want to migrate your data, follow the procedures in the topic Migrating from SharePoint Team Services in Chapter 3, Upgrading to Project Server from Earlier Versions of Microsoft Project of the Microsoft Office Project Server 2003 Installation Guide.

To install Project Server 2003

1. If you want to create the database in SQL Server manually, follow the procedure in the topic Creating the Project Server 2003 Database Manually in Chapter 6, Deploy the Database of the Microsoft Office Project Server 2003 Installation Guide. This step is not required, because Project Server Setup can create the database for you during installation.

2. Run the Project Server Setup program on the computer on which you want to install Project Server by using the procedures in Chapter 7, Install Project Server 2003 of the Microsoft Office Project Server 2003 Installation Guide.

If you are installing Project Server services on separate computers, run Setup on each computer on which you want to install a service. The Front-End service must be installed last, as you will be prompted to specify the location of the other services at that time.

To perform post-installation tasks

1. Configure any items that you bypassed when running Project Server Setup by using the procedures in the topic Configure Items Bypassed During Setup in Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

2. To enable users to use the Log on using a different Microsoft Windows user account link on the Logon page, follow the procedures in the topic Enable Users to Log On Using a Different Windows User Account in Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

3. To give users access to the OLAP cube, follow the procedure in the topic Add Users to Cube Database Roles in Analysis Services in Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

4. To ensure proper connectivity to Analysis Services, migrate the Analysis Services repository to a SQL Server database by using the procedure in the topic Migrate the Analysis Services Repository to a SQL Server Database in Chapter 8, Post- Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

5. If you are using Project Server in a hosted deployment with Windows SharePoint Services, use the procedures in the topic Updating the MSP_WEB_ADMIN Table for Hosted Deployments By Using Windows SharePoint Services in Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation Guide.

Microsoft Office Project Server 2003 Installation Guide

25

3

Upgrading to Project Server 2003 from Earlier Versions of Microsoft Project

If you want to use Microsoft® Office Project Server 2003 with data that you have stored in Microsoft Project Central, Microsoft Project Server 2002, or SharePoint® Team Services from Microsoft, then you will need to migrate the existing data for use with your Project Server 2003 deployment. You must migrate data from an existing deployment before you install Project Server 2003.

Upgrading to Project Server 2003 from earlier versions involves completing one or more of the following processes:

Upgrading from Microsoft Project Central or Microsoft Project

Server 2002

Central or Microsoft Project Server 2002 deployment and you want to prepare it for

use with Project Server 2003.

Complete this process if you have data in an existing Microsoft Project

Upgrading from Microsoft Project Server 2002 and MSDE

Complete this process

if you have Project Central or Microsoft Project Server 2002 data in Microsoft Desktop Engine (MSDE) and you want to upgrade your MSDE database for use with

Project Server 2003.

Migrating from SharePoint Team Services

Complete this process if you have

Microsoft Project Server 2002 documents and issues stored in SharePoint Team

Services and you want to migrate that data for use with Project Server 2003.

26

Microsoft Office Project Server 2003 Installation Guide

Upgrading from Microsoft Project Central or Microsoft Project Server 2002

If you are upgrading from Microsoft Project Central or Microsoft Project Server 2002 to Project Server 2003, you can migrate your data for use with Project Server 2003. Complete this migration process before you install Project Server 2003.

When you migrate Project Central or Microsoft Project Server 2002 data, the Microsoft SQL Server™ 2000 database schema is upgraded for Project Server 2003. After you migrate, it is no longer possible to use the database with Project Central or Microsoft Project Server 2002. If you want to continue using Project Central or Microsoft Project Server 2002, back up the database and restore it with a new name, and then perform the migration steps on the new database.

Note

If your Microsoft Project Server 2002 deployment has outline codes that use a comma as the

list separator, you need to change the separator to a different character so that the outline codes will work with Project Server 2003. If your outline codes contain leading or trailing white spaces, you need to remove the white spaces so that the outline codes will work with Project Server 2003. You can perform these steps before or after you upgrade.

It is recommended that you run the migration scripts on the computer on which the database that you are migrating is installed.

To prepare to upgrade from Microsoft Project Central or Microsoft Project Server 2002

1. Create a full backup of the Microsoft Project Central or Microsoft Project Server 2002 database that you want to upgrade.

2. In Microsoft Windows® Explorer, browse to the Support folder on the Project Server 2003 CD.

3. In the Support folder, copy the Database folder to the local disk.

If you are upgrading from Microsoft Project Central, you must first upgrade the database from Microsoft Project Central to Microsoft Project Server 2002. After you upgrade the database to Microsoft Project Server 2002, you can run the scripts to upgrade to Project Server 2003.

To upgrade from Microsoft Project Central

1. Open a command prompt window, and then browse to the Database folder.

2. Copy the file osql.exe to the PC2PS02 folder.

3. Open the PC2PS02 folder.

4. Run UPG09DB.cmd by using the following syntax:

UPG09DB.CMD <ServerName> <DatabaseName> <UserName> <Password>

For example:

Microsoft Office Project Server 2003 Installation Guide

27

UPG09DB.CMD PROJSQL2000 ProjectCentral sa hello

5. When the script finishes successfully, follow the procedure To upgrade from Microsoft Project Server 2002.

6. In SQL Server 2000 Enterprise Manager, create the following two logins by using SQL Server Authentication in the database: MSProjectServerUser and MSProjectUser.

7. Create the two database roles that are needed by the Project Server logins:

MSProjectServerRole and MSProjectRole.

8. Grant each role that you created in the previous step login access to the Project Server database.

9. Assign the MSProjectServerRole role to the MSProjectServerUser login, and then assign the MSProjectRole role to the MSProjectUser login.

To upgrade from Microsoft Project Server 2002

1.

Open a command prompt window, and then browse to the Database folder.

2.

Run UPG10DB.cmd by using the following syntax:

UPG10DB.cmd <ServerName> <DatabaseName> <UserName> <Password>

For example:

UPG10DB.cmd PROJSQL2002 ProjectServer sa hello

3.

When the script finishes successfully, install Project Server 2003 and connect to the upgraded database from the Enter database account information page of Project Server Setup.

Note

When you set up Microsoft Project Server 2002, random passwords are assigned to the

ProjectUser and ProjectServerUser accounts. If you do not know the passwords for these accounts, you will need to reset them with new passwords before you install Project Server 2003. You must provide the password information for these accounts when you run Project Server Setup. To reset the password, in SQL Server Enterprise Manager, right-click the login, click Properties, and then type the new password in the Password box.

Upgrading from Microsoft Project Server 2002 and MSDE

To upgrade to Microsoft Office Project Server 2003 from a Microsoft Project Server 2002 installation that is configured to use the Microsoft Desktop Engine (MSDE) 2000, you must do the following:

1. Disconnect your Microsoft Project Server 2002 database from MSDE 2000.

Important

If you do not disconnect your Microsoft Project Server 2002 database from

MSDE, your data will be lost when you uninstall Microsoft Project Server 2002.

28

Microsoft Office Project Server 2003 Installation Guide

2.

Uninstall Microsoft Project Server 2002 and MSDE 2000.

3.

Install a new instance of MSDE 2000 and reconnect to your Microsoft Project Server 2002 database.

4.

Upgrade your database for Project Server 2003 and then install Project Server 2003.

Note

Microsoft Project Server 2002 is configured to use MSDE when you choose the Install Now

option in Microsoft Project Server 2002 Setup.

To upgrade from Microsoft Project Server 2002 and MSDE 2000

1. Detach your Microsoft Project Server 2002 database from MSDE 2000:

a. Click Start, click Run, type osql -U sa in the Open box, and then click OK.

This connects you to the local, default instance of MSDE 2000 by using the System Administrator (sa) account.

b. At the Password prompt, type the sa password, and then press ENTER.

c. Retrieve the names of the database (.mdf) and log (.ldf) files for the Microsoft Project Server 2002 database by typing the following text on separate lines, and then pressing ENTER after each line of text:

select a.filename as Filename from sysaltfiles a, sysdatabases b where a.dbid = b.dbid and b.name = N'ProjectServer'

go

This returns two rows, one that ends in .mdf, indicating the full path of the database file, and one that ends in .ldf, indicating the full path of the log file.

d. Close any running transactions, detach the database, and detach the log files by typing the following text on separate lines and pressing ENTER after each line:

EXEC sp_detach_db N'ProjectServer', N'true'

go

Note

There might be a long delay after running this command.

2. After the database is detached, back up the .mdf file and the .ldf file from the directories that were identified in step 1.c by copying them to an alternate directory.

3. Remove Microsoft Project Server 2002 by doing the following:

a. Click Start, click Control Panel, and then click Add or Remove Programs.

b. In the Add or Remove Programs box, click Microsoft Project Server 2002, and then click Remove.

c. Follow the on-screen instructions to remove Microsoft Project Server 2002.

d. Restart your computer regardless of whether or not you are prompted to do so.

Microsoft Office Project Server 2003 Installation Guide

29

4. Install MSDE 2000 SP3 or higher by doing the following:

a. Go to the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=19683).

b. Select the language that matches your version of Microsoft Project Server 2002 from the Full Download box on the right side of your screen, and then click Go.

c. Locate the download link to the SQL2KDeskSP3.exe file, and then click the download link to start the download.

Note

Non-English versions of the download are listed as

language_SQL2KDeskSP3.exe where language represents the language version of the download.

d. When prompted, save the file to your Windows desktop.

e. In Windows Explorer, double-click the file that you previously saved to your desktop.

f. Click I Agree to accept the End-User License Agreement (EULA).

g. In the Installation Folder box, type C:\sql2ksp3 and then click Continue.

h. Click Start, click Run, and then type the following command in the Open box:

C:\sql2ksp3\msde\setup.exe sapwd=<strong_pwd> securitymode=sql disablenetworkprotocols=0

where strong_pwd is your System Administrator (sa) password.

i. Click OK.

j. Restart your computer.

5. Attach your Microsoft Project Server 2002 databases to MSDE 2000 by doing the following:

a. Click Start, click Run, type osql -U sa in the Open box, and then click OK.

This connects you to the local, default instance of MSDE 2000 by using the sa account.

b. At the password prompt, type the sa password that you set in step 4.h, and then press ENTER.

c. Attach the Project Server .mdf and .ldf files by typing the following text on separate lines, and then pressing ENTER after each line:

EXEC sp_attach_db @dbname=N'ProjectServer', @filename1=N'

<mdf_path>',@filename2=N'<ldf_path>’

go

where mdf_path and ldf_path are the paths to the .mdf file and the .ldf file that you previously backed up to a safe location in step 2.

30

Microsoft Office Project Server 2003 Installation Guide

Note

There might be a long delay after running this command.

6. Create the MSProjectUser and MSProjectServerUser SQL logins. To do this, type the following text on separate lines, and then press ENTER after each line:

EXEC sp_addlogin N'MSProjectServerUser', N'<newpassword1 > ', N'ProjectServer'

EXEC sp_addlogin N'MSProjectUser', N'<newpassword2>', N'ProjectServer'

go

where newpassword1 is the new password for the MSProjectServerUser account, and newpassword2 is the new password for the MSProjectUser account.

7. Add the MSProjectServerUser account and the MSProjectUser account to the MSProjectRole role and MSProjectServerRole role by typing the following text on separate lines, and then pressing ENTER after each line:

USE ProjectServer

go

EXEC sp_dropuser N'MSProjectServerUser’

EXEC sp_dropuser N'MSProjectUser’

go

EXEC sp_adduser N'MSProjectServerUser', N'MSProjectServerUser', N'MSProjectServerRole'

EXEC sp_adduser N'MSProjectUser', N'MSProjectUser', N'MSProjectRole'

go

quit

8. Upgrade your database for Project Server 2003 by following the steps in Migrating Data from Project Central or Microsoft Project Server 2002 earlier in this chapter.

9. Install Project Server 2003 and connect to the upgraded MSDE 2000 database from the Enter database server information page of the installation wizard.

Migrating from SharePoint Team Services

SharePoint Team Services does not run with Project Server 2003. If you plan to upgrade Microsoft Project Server 2002 to Project Server 2003, you must migrate SharePoint Team Services to Microsoft Windows SharePoint Services.

Microsoft Office Project Server 2003 Installation Guide

31

You can use the Project Server Data Migration tool (PSMigrat.exe) to migrate Project Server data from SharePoint Team Services to Windows SharePoint Services. PSMigrat.exe extracts the subweb information from SharePoint Team Services into one or more FrontPage Web Package (.fwp) archive files. For each site, PSMigrat.exe packages all of the site content (including documents and issues) into a .cab file and expands the file to perform additional operations. Then PSMigrat.exe runs the Windows SharePoint Services Backup and Restore tool (SMigrate.exe) to add this information to the server running Windows SharePoint Services. You can download PSMigrat.exe from the Microsoft

Windows SharePoint Services is more robust than SharePoint Team Services and provides for detailed progress reporting and error logging. Windows SharePoint Services is also easier for administrators to maintain, because much of the application is controlled by automated settings, and easier to install than SharePoint Team Services.

Windows SharePoint Services stores all data related to documents, issues, and risks in a database. Backup and recovery for Windows SharePoint Services data is based on the backup and recovery principles that apply to SQL Server 2000, which makes disaster avoidance and disaster recovery easier to manage.

Requirements for Migrating from SharePoint Team Services

The following are the requirements for migrating from SharePoint Team Services:

The administrator running PSMigrat.exe must be an administrator on both the server running SharePoint Team Services and the server running Windows SharePoint Services.

The administrator must provide an account (Windows or SQL Server) that has read/write permissions to the Project Server 2003 database.

The administrator must first run the Project Server 2003 database upgrade scripts to upgrade the Microsoft Project Server 2002 database to the Project Server 2003 database format.

The server that you are migrating to must be local (the path must be in the form //server/site).

If you are migrating to a Secure Sockets Layer (SSL) site, the host name provided when you run PSMigrate.exe must match the hostname on the SSL certificate. If the host name on the SSL certificate is not a local name, you will need to use a non-SSL connection to the server for the migration.

Migration to Windows SharePoint Services can be a time-consuming process. To migrate SharePoint Team Services to Windows SharePoint Services, you must use PSMigrat.exe to extract the subweb information from SharePoint Team Services into one or more .fwp

32

Microsoft Office Project Server 2003 Installation Guide

files. PSMigrat.exe then runs SMigrate.exe to add this information to the server running Windows SharePoint Services.

Be sure that you have sufficient disk space for the work directories of PSMigrat.exe, especially if you are migrating all the subwebs at once. For each site, PSMigrat.exe packages all of the site content (including documents and issues) into a .cab file and expands the file to perform additional operations.

PSMigrat.exe logging includes:

A text description of all major operations, including the output of SMigrate.exe.

A silent mode option, whereby progress is written to a log file.

Limitations to Migrating to Windows SharePoint Services

You must be running the version of SharePoint Team Services that was included as part of the Microsoft Office XP Service Pack 2 release to be able to migrate a site from SharePoint Team Services to Windows SharePoint Services. The site migration process is optimized for use with standard team Web sites. This means that many types of customizations will not migrate properly or will not work in a migrated site. Also, because the feature set and architecture is significantly different in SharePoint Team Services and Windows SharePoint Services, several features that you can use in these environments will not work after migration.

The following customizations and features will not migrate when you migrate from SharePoint Team Services to Windows SharePoint Services:

Home pages that you customized by means of a Windows

SharePoint Services–compatible Web page editor, such as Microsoft FrontPage® 2002, will revert to the standard team Web site home page. Home pages that you customized in the browser will retain their customizations, including views that you added and

Customized home pages

changes that you made to the Quick Launch bar.

Customized link bars

Link bars, such as the top link bar, that you customized by

means of a Windows SharePoint Services–compatible Web page editor, such as FrontPage 2002, will revert to the standard link bars.

Custom Active Server Pages (ASP) included in the site

By default, the Internet

Server Application Programming Interface (ISAPI) filter for Windows SharePoint Services blocks the use of any ASP pages that are not part of the Windows SharePoint Services installation. If you want to use custom ASP pages with your upgraded Windows SharePoint Services sites, you must put the ASP pages in a separate virtual directory and create an excluded path for the directory in Windows SharePoint Services. This allows IIS— rather than Windows SharePoint Services—to control the

directory, and allows the ASP pages to run.

Microsoft Office Project Server 2003 Installation Guide

33

Custom pages that link to SharePoint Team Services lists

The SMigrate.exe tool

does not include an automatic fix-up tool. After migration, any links that you created to point to specific lists will be broken. You can update the links to refer to the current

list location after migration.

Subsites that have the same name as a wildcard inclusion or exclusion

If you

have set up included and excluded paths for the server that will host the migrated sites, be sure that the names of those paths do not conflict with the names of the sites to be migrated. For example, if you had a subsite named http://servername/sitename, and the /sites path on the new server is a wildcard inclusion, the http://servername/sitename subsite will not be migrated.

Windows SharePoint Services does

not support leading or trailing spaces (“ filename.doc”, or “filename .doc”). You must

change the file name and then add the file manually to your site.

Files or folders with leading or trailing spaces

Files with file extensions that are blocked in Windows SharePoint Services

A

new feature enables server administrators to control whether specific file types can be

uploaded or downloaded to the server. If a file in your site uses one of these file extensions (for example, .exe), the file will not be migrated to the new site.

Long file and folder names (more than 255 characters)

File and folder names that

are longer than 255 characters are not supported in Windows SharePoint Services. You can rename the files or folders that have long names before migrating a site or rename

them after migration and add them manually to the new site.

Links with long URLs (more than 255 characters)

URLs that are longer than 255

characters are not supported in Windows SharePoint Services.

User account limits Services.

Local user accounts

User account limits are not supported in Windows SharePoint

Local user accounts are not supported when running Windows

SharePoint Services with Microsoft Office Project Server 2003.

Security permissions

Security permissions do not translate directly from SharePoint

Team Services to Windows SharePoint Services. The SMigrate.exe tool will apply the

same or greater permissions.

Folders under an Attachments subfolder of a list

If your original site contains a

list with an Attachments subfolder, with files or subfolders inside it, the Attachments folder will not be migrated. The attachments feature in Windows SharePoint Services is enabled for that list, so that you can copy the related files or subfolders over and add

them as attachments to items in the list.

Custom fields with specific names fields with the following names: