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
Configure the Administrative Virtual Server .................................................... 61
Set the Configuration Database Server........................................................... 63
Extend the Virtual Server.................................................................................. 65
Create a Windows SharePoint Services Administrator................................... 67
Installing Windows SharePoint Services with WMSDE .......................................... 68
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
Create Database Account Information ...................................................106
Creating a New Database That Uses SQL Server Authentication ................107
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

Configuring SharePoint Portal Server Settings .............................................128
Configuring SMTP Mail Server Settings.........................................................129
Synchronize the Public Document Site.................................................................130
Migrate the Analysis Services Repository to a SQL Server Database.................130
Add Users to Cube Database Roles in Analysis Services ....................................131
Enable Users to Log on By Using a Different Windows User Account.................132
Configuring Project Professional for Project Server 2003...................................134
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
MSP_UTIL_EXEC_MOVE_DATABASE_FILES ...........................................145
MSP_UTIL_EXEC_MOVE_TABLES_TO_FILEGROUP................................145
MSP_UTIL_EXEC_MOVE_INDEXES_TO_FILEGROUP..............................146
Component Utility Stored Procedures ...........................................................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
the Project Server Views Notification Service ..........................................169
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
Running the EditSite Tool from the Command Line .....................................198
Project Server COM+ Settings Tool.......................................................................200
Windows SharePoint Services Backup and Restore Tool....................................201
Project Server Data Migration Tool .......................................................................202
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
Removing the Outlook Add-in from Outlook .........................................................243
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
• Microsoft Office Project Server 2003 Medium-Scale Installation Guide
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.
mailto:projdocs@microsoft.com?subject=Feedback: Microsoft Office Project Server 2003 Installation
Guide
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
http://go.microsoft.com/fwlink/?LinkID=20235
• 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 Small-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
• 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.
• 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.
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.
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 Handles all Project Web Access and Project Data
Service requests.
• View Processing Generates static views of published data for Project Web Access.
• 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 Enables the indexing and
searching of Project Server 2003 document libraries.
• Project Professional 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
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 For more information about the EPM Solution architecture, see Chapter 5, Planning Your
EPM Solution Architecture, in the Microsoft Office Project Server 2003 Configuration Planning
Guide (http://go.microsoft.com/fwlink/?LinkID=20235).
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.
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).
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.
Note 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.
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 Document your installation thoroughly, in case you need to duplicate it when recovering
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.
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
Guide (http://go.microsoft.com/fwlink/?LinkID=20235).
Note You must use a single computer deployment if you are installing the Project Server 2003
Sample database.
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).
X 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.
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.

X 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.
X 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
X 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.
X 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-
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.
Example of a small-scale deployment.
X To get started
2. Install the operating system on each computer.
3. Install SQL Server 2000 on the appropriate computer.

Services and SQL Server 2000 Analysis Services Service Pack 3 (SP3) on the
appropriate computer.
Installation Guide.

• 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
setup process. You can also use your sa account for this purpose.
Guide.
2. Create an OLAP Administrator by using the procedure in the topic Create an OLAP
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
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.

Installation Guide.
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
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
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.
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.

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,
Medium-Scale Installation Roadmap

Follow the procedures in this topic to install Project Server 2003 in a medium-scale
Example of a medium-scale deployment.
X To get started

Services and SQL Server 2000 Analysis Services Service Pack 3 (SP3) on the
appropriate computer.
Installation Guide.


Services.
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.
Installation Guide.
Install Windows SharePoint Services in Chapter 5, Configuring Windows
Installation Guide.
Configuring Windows SharePoint Services of the Microsoft Office Project Server 2003
Installation Guide.
Server in Chapter 5, Configuring Windows SharePoint Services of the Microsoft
5. Create a Windows SharePoint Administrator by using the procedure in the topic
Create a Windows SharePoint Services Administrator in Chapter 5, Configuring
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.
Team Services in Chapter 3, Upgrading to Project Server from Earlier Versions
of Microsoft Project of the Microsoft Office Project Server 2003 Installation Guide.
installation.

5. If you are using Project Server 2003 in a hosted deployment with Windows SharePoint
Large-Scale Installation Roadmap

Follow the procedures in this topic to install Project Server 2003 in a large-scale
Example of a large-scale deployment.

X To get started


Services and the SQL Server Analysis Services Service Pack 3 (SP3) on the appropriate
computer.
Installation Guide.

7. Configure clustering if you are using failover clusters or network load–balancing
clusters as part of your deployment.
Services.
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
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.
Installation Guide.
Installation Guide.
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.
5. Create a Windows SharePoint Administrator by using the procedure in the topic
Create a Windows SharePoint Services Administrator in Chapter 5, Configuring
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
Installation Guide.
Team Services in Chapter 3, Upgrading to Project Server from Earlier Versions
of Microsoft Project of the Microsoft Office Project Server 2003 Installation Guide.
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
installation.
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.
Log On Using a Different Windows User Account in Chapter 8, Post-Installation
5. If you are using Project Server in a hosted deployment with Windows SharePoint
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 Complete this process if you have data in an existing Microsoft Project
Central or Microsoft Project Server 2002 deployment and you want to prepare it for
use with Project Server 2003.
• 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.
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.
X 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.
X 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:
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.
X 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.
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.
X 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.
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.
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.
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
Download Center (http://go.microsoft.com/fwlink/?LinkId=20877).
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
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:
• Customized home pages 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
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.
• 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.
• Files or folders with leading or trailing spaces 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 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 User account limits are not supported in Windows SharePoint
Services.
• Local user accounts 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 Smigrate.exe will not properly migrate custom
fields with the following names:
• Assigned By
• Assigned To
• Assigned Date
• Approval Level
• Approval Date
• Approved By
• Categories
If you have fields with these names, change the names before you migrate to Windows
Migrating a SharePoint Team Services Site to Windows

SharePoint Services
Follow the procedure in this topic to migrate your SharePoint Team Services data to a
server running Windows SharePoint Services.
Note It is recommended that you migrate the public documents site last.
X To migrate a SharePoint Team Services site to Windows SharePoint Services

1. Install Windows SharePoint Services on a different computer from SharePoint Team
Services by using the procedures in the topic Installing Windows SharePoint
Services with a New Database in Chapter 5, Configure Windows SharePoint
Services of the Microsoft Office Project Server 2003 Installation Guide.
Note When you run the Windows SharePoint Services Configuration Wizard, run it from the
command line (WSSWiz.exe) with the –f switch. This will copy the Project Server templates
to the server running Windows SharePoint Services without setting up a new site.
2. On the server running SharePoint Team Services, be sure that you have installed
Microsoft Office XP Service Pack 3 (SP3).
Note Office XP SP3 contains the OWS1002.exe update file that is required for migrating
SharePoint Team Services to Windows SharePoint Services. This enables SharePoint Team
Services to export additional schema information about SharePoint Team Services subwebs
and is required by the Windows SharePoint Services Backup and Restore tool
(SMigrate.exe) during the migration process.
For more information about Office XP SP3, see Appendix I, Service Packs for Project Server
Components, in the Microsoft Office Project Server 2003 Installation Guide.
3. Run STSWiz.exe on the server running SharePoint Team Services. STSWiz.exe can be
found in the Support folder on the Microsoft Project Server 2002 CD.
4. Run PSMigrat.exe. Insert your Office Project Server 2003 CD into your CD-ROM
drive. Click Start and then click Run. Type CMD and click OK. At the command
prompt, change to your CD-ROM drive and change to the \SUPPORT\PSMIGRAT

folder. This tool requires the following information:
• The Windows SharePoint Services managed path under which the newly migrated
sites will be created.
• The folder where all the backup files will be stored.
• The connection information for the Project Server 2003 database.
• The range of project IDs (optional).
• The location of the log file (optional).
Note To view parameter options that can be run with PSMigrate.exe, see the topic Project
Server Data Migration Tool in Appendix B, Project Server Installation Tools of the Microsoft
For example, you can run the following:

PSMigrat.exe –w http://wss_svr/projects
-f \\<serverName>\<path to server> -dbserver <serverName>
-dblogin <loginName> -dbpassword <password> -p <prefix>
Note You must run PSMigrat.exe from the computer running Windows SharePoint Services.
For each subweb, PSMigrat.exe does the following:

1. Verifies that the OWS1002.exe update is installed on the server running SharePoint
Team Services.
2. Backs up each subweb on the server running SharePoint Team Services by performing
the following steps:
a. Creating a working folder in the same file directory, and then extracting the file
manifest.xml.
b. Modifying the file manifest.xml and does the following:
• Inserting a new template ID (6215).
• Changing the Comments field types to Note field types for Documents and Issues.
• Changing the issue list type to 101 so that it can be migrated into a custom list.
c. Renaming the issues list to avoid naming conflicts.
d. Rebuilding the .cab file and names it after the project ID.
e. Deleting the working directory (unless –bo is specified).
3. Runs the SMigrate.exe tool to migrate SharePoint Team Services information to the
new server running Windows SharePoint Services.
4. Updates the list global universal identifications (GUIDs) and new site addresses in the
Project Server 2003 database.
5. Migrates Issues from the custom list type in SharePoint Team Services to the Windows
SharePoint Services Issues list type.
6. Updates site properties in the server running Windows SharePoint Services.
7. Updates the Project Server 2003 database with the new site address and the new list
GUIDs.
4
Prepare the Servers
This chapter describes how to prepare your servers prior to installing Microsoft® Office
Project Server 2003. Follow these steps in conjunction with one of the installation
roadmaps in Chapter 2, Installation Roadmaps in the Microsoft Office Project Server 2003
Installation Guide.
Create User Accounts

To install Project Server 2003, you must create the following user accounts:
Note These accounts will only be used by Project Server 2003.
• A Microsoft Windows® domain user account or local user account to allow Project
Server 2003 to access Microsoft SQL Server™ 2000 Analysis Services. Use this
account when you create an OLAP administrator later in this chapter.
If you create a local user account, you must create identical accounts with identical
passwords on each of the following computers in your deployment:
• The computer running Analysis Services.
• The computer running the Project Server Front-End service.
• The computer running the Project Server View Processing service.
Note Some deployments do not have separate computers for each of the components
listed.
Microsoft Windows SharePoint® Services, to allow Project Server 2003 to access
Windows SharePoint Services. You can use a generic name for this account, such as
MSProjServ, and set the password to never expire. You will use this account when you
create a Windows SharePoint Services administrator, and you will specify this account
on the Enter account information for Microsoft Windows SharePoint Services
(continued) page in Project Server Setup.
• A Windows domain user or local user account to allow the Project Server Front-End
service to access the Views Staging shared folder on the computer on which the View
Processing service is located. This account must be located on both the computer
running the Project Server Front-End service and the computer running the Project
Server View Processing service. During Project Server Views Processing Setup, a
Views Staging folder is specified and created. The Windows account that you specify is
then assigned the required permissions to the folder.
Note This account is only required if you plan to install the View Processing service on a
different computer than the computer on which you install the Project Server Front-End
service.
• A SQL Server account on the instance of SQL Server 2000 where the Project Server
database will be located. This account must belong to the Database Creators and
Security Administrators roles. This account will only be used for the purposes of
creating the Project Server database. It will not be stored and used after installation.
Note You can use your system administrator (sa) account or an existing account that is a
member of the same roles. If your Windows account belongs to the appropriate SQL Server
roles, you can use Windows authentication as long as you are not partitioning your
database.
• A SQL Server login for the computer on which Windows SharePoint Services is
installed. This account must belong to the Database Creators and Security
Administrators roles. Windows authentication is the preferred authentication method,
although you can also select SQL Server authentication. This account will be used to
create the Windows SharePoint Services database on the computer running SQL
Server.
Note For more information about accounts needed to install and configure Project
Server 2003, see Appendix B, Project Server Service Accounts, in the Microsoft Office Project
X To create a Windows domain user account

1. Open Active Directory Users and Computers.
2. In the console tree, right-click the folder in which you want to add a user account.
3. Point to New, and then click User.
4. On the New Object – User page, type the user’s first name, initial, last name, and user
logon name, and then click Next.
5. In the Password box, type a password, and in the Confirm Password box, retype the
password.
6. Clear the User must change password at next logon check box.
Note You must clear this check box or the account will not work properly with Project
Server 2003.
7. Select the Password Never Expires check box, and then click Next.
8. Click Finish.
Note To perform this procedure, you must be a member of the Account Operators group, Domain
Admins group, or the Enterprise Admins group in Active Directory® directory service, or you must
have been delegated the appropriate authority.
X To create a local user account

1. On the computer on which you want to create the account, open Computer
Management.
2. Expand Local Users and Groups.
3. Right-click Users and click New User.
4. In User name, type a name for the user (for example, ProjServ).
5. In Description, type a description for the user account.

6. In Password and Confirm password, type the user's password.
Note You must clear this check box or the account will not work properly with Project
Server 2003.
8. Click Create.
X To create a SQL Server 2000 account
1. Open SQL Server Enterprise Manager.
2. Expand the server group containing the server on which you want to add the account,
and then expand the server.
3. Expand Security, right-click Logins, and then click New Login.
4. In the Name box, type a name for the SQL Server login (for example, ProjServSQL).
5. Under Authentication, select SQL Server Authentication.

6. In the Password box, type a password.
7. On the Server Roles tab, select the Security Administrators and Database Creators
check boxes.
8. On the Confirm Password page, in the Confirm New Password box, reenter the
password, and then click OK.
9. Click OK.
X To create a SQL Server login for the computer running Windows SharePoint Services
2. Expand the server group containing the server on which you want to add the account,
and then expand the server.
3. Expand Security, right-click Logins, and then click New Login.
4. In the Name box, type a name for the SQL Server login. Use the form
domain\username; for example, XABYTE2\ProjServ.
5. Under Authentication, select Windows Authentication.

6. From the Domain list, select the domain in which the computer is located.
7. On the Server Roles tab, select the Security Administrators and Database Creators
check boxes, and click OK.
Note You can also configure this account to use SQL Server authentication, although Windows
authentication is recommended. To configure this account using SQL Server Authentication, see
the previous procedure: To create a SQL Server 2000 account.
Configure SQL Server Authentication

SQL Server mixed-mode authentication enables users to connect to an instance of SQL
Server that is using either Windows authentication or SQL Server authentication. You must
configure the instance of SQL Server 2000 that you will use with Project Server 2003 to use
mixed-mode authentication.
X To configure SQL Server authentication

2. Expand the server group that contains the database server that you will use with
3. Right-click the server, and then click Properties.
4. Click the Security tab.
5. Under Authentication, click SQL Server and Windows.

6. Under Audit level, select the level at which user accesses to SQL Server are recorded
in the SQL Server error log.
7. Click OK.
Install Decision Support Objects

SQL Server Analysis Services is required in order to use the Portfolio Analyzer feature of
Project Server 2003. When Analysis Services is installed on a different computer than the
computer on which Project Server 2003 is installed, the Decision Support Objects (DSO)
component of Analysis Services must be installed on the computer running Project

Server 2003.
If you install the Project Server 2003 View Processing service on a different computer than
the computer on which the Project Server 2003 Front-End service is installed, you must
install DSO on both computers.
Note You must also install SQL Server 2000 Analysis Services Service Pack 3 (SP3) on the
computers on which you install the DSO component of Analysis Services. 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.
X To install the Analysis Services Decision Support Objects

1. On the computer on which you will install Project Server 2003, insert the SQL
Server 2000 CD into the CD-ROM drive, or connect to a network installation point.
2. If you are installing from the SQL Server 2000 CD with AutoPlay enabled, click SQL
Server 2000 Components in the SQL Server 2000 Setup program. Otherwise, on the
SQL Server CD (or network installation point), browse for and run the file named
Autorun.exe.
3. On the Install Components page, click Install Analysis Services.
4. Read and accept the End-User License Agreement.
5. In the Analysis Services Setup program, on the Select Components page, clear all the
components except Decision Support Objects and Client components, and then
follow the wizard to install DSO.
6. Install SQL Server 2000 Analysis Services Service Pack 3 (SP3).

Note Installing DSO separately from Analysis Services does not require an additional license. For
more information, see SQL Server Books Online and your licensing information.
Create an OLAP Administrator

In order for Project Server 2003 to access Analysis Services, you must create an OLAP
Administrator. To do this, add the account that you created for this purpose to the OLAP
Administrators group on the following computers:
• The computer running Analysis Services.
• The computer running the Project Server 2003 Front-End service.
• The computer running the Project Server 2003 View Processing service.
Note Some deployments do not have separate computers for each of the components listed.
X To create an OLAP Administrator

1. On the computer on which you want to create an OLAP Administrator, open
Computer Management.
2. In the console tree, under System Tools, expand Local Users and Groups.
3. Click Groups.
4. Right-click the OLAP Administrators group and then click Properties.
5. Click Add.
6. In Enter the object names to select, type the name of the Windows account that you
want to add to the group, and then click OK.
7. Click OK.
Note The OLAP Administrators user group to which you want to add the account will not
exist unless you have Analysis Services or DSO on your computer. If Analysis Services is not
installed on the computer on which Project Server 2003 is installed, you must install DSO
on that computer. For more information about DSO, see the topic Install Decision Support
Objects, in Chapter 4, Prepare the Servers, of the Microsoft Office Project Server 2003
Installation Guide.
Configure Internet Information Services

Both Project Server 2003 and Windows SharePoint Services require Internet Information
Services (IIS). Enable IIS on the computer on which you will install Project Server 2003
and Windows SharePoint Services.
It is recommended that you configure IIS to use Secure Sockets Layer (SSL) for increased
security. If you do not configure IIS to use SSL, potentially sensitive data will be sent in
plaintext between the clients and servers in your deployment. For example:
• If you are using Project Server 2003 accounts, user names and passwords are sent from
client to server in plaintext.
• All information exposed through the Project Data Service (PDS) is transmitted in
plaintext, including a SQL Server username and password.
• Microsoft Office Project Web Access users can transmit potentially sensitive company
data between client and server.
For more information about configuring IIS to use SSL, see your IIS documentation.
X To enable IIS on a computer running Windows 2000 Server
1. Click Start, click Settings, and then click Control Panel.
2. Double-click Add/Remove Programs.
3. Select Configure Windows, click the Components button, and then follow the on-
screen instructions to install, remove, or add components to IIS.
X To enable IIS on a computer running Windows Server 2003
1. Open Manage Your Server.
Note Manage Your Server is located in Administrative Tools in Control Panel.
2. On the Manage Your Server page, click Add or remove a role.

3. On the Preliminary Steps pane, click Next.
4. On the Server Role pane, click Application server (IIS, ASP.NET), and then click
Next.
5. For computers on which you will install Windows SharePoint Services, in the
Application Server Options pane, select the Enable ASP.NET check box.
6. Click Next, and then click Next again to begin the installation.
7. When the installation is complete, on the This Server is Now an Application server
page, click Finish.
8. Close the Manage Your Server application.
9. Click Start, point to Administrative Tools, and then click Internet Information
Services (IIS) Manager.
10. In Internet Information Services Manager, click the plus (+) sign next to the server
name, and then right-click the Web Sites folder and select Properties.
11. Click the Service tab.
12. In the Isolation mode section, clear the Run WWW service in IIS 5.0 isolation
mode check box, and then click OK.
Note The Run WWW service in IIS 5.0 isolation mode check box is only selected if you
upgraded to IIS 6.0 on Windows Server 2003 from IIS 5.0 on Windows 2000 Server. New
installations of IIS 6.0 default to IIS 6.0 worker process isolation mode.
Configure Internet Explorer Enhanced Security

By default, Microsoft Windows Server™ 2003 provides a set of security settings called
Internet Explorer Enhanced Security Configuration. These settings limit the types of
content that a user at the server can view by using Microsoft Internet Explorer, except for
sites listed in the Local intranet and Trusted sites zones. For example, by default,
scripting on Internet pages will not run. The goal of these settings is to help ensure that a
local user on a computer that is also running as a server will not download a virus or other
harmful files from the Internet and infect the server. Internet Explorer Enhanced Security
Configuration does not affect remote users who view content on the server; it affects only
users running Internet Explorer on the server itself.
Using Internet Explorer Enhanced Security Configuration on a Web server running Project
Server 2003 or Windows SharePoint Services prevents some code that is necessary for
viewing site pages or Administration pages from running. Remote users with proper access
rights can still view the pages correctly, but a user running Internet Explorer on the server
will be unable to view or administer the site. The user at the server will also be unable to
view and administer a remote SharePoint or Project Server site, because of the security
settings.
To help ensure that Windows SharePoint Services and Project Server 2003 work properly
in your environment, you can do one of the following:
• Uninstall Internet Explorer Enhanced Security Configuration. If you are not
concerned about users working locally at the Web server, an administrator can uninstall
Internet Explorer Enhanced Security Configuration by using Add or Remove
Programs.
• Add the SharePoint and Project Server sites to the list of Local intranet sites.
This is a more time-consuming solution, but potentially more secure. A server
administrator can add the URLs of all virtual servers that are being hosted to the
Internet Explorer Local intranet zone.
X To uninstall Internet Explorer Enhanced Security Configuration
1. On the computer on which you will install Windows SharePoint Services, click Start,
click Settings, and then click Control Panel.
2. Double-click Add/Remove Programs.
3. Click Add/Remove Windows Components.
4. In the Components list, clear the Internet Explorer Enhanced Security
Configuration check box, and then click Next.
The Internet Explorer Enhanced Security Configuration component is removed.

5. Click Finish.
X To add the SharePoint and Project Server sites to the list of Local intranet sites
1. On the computers on which you will install Windows SharePoint Services and Project
Server, open Internet Explorer.
2. On the Tools menu, select Internet Options.
3. Click the Security tab, and then click the Local intranet icon.
4. Click Sites.
5. Click Advanced.
6. Type the URL for the site that you want to add, and then click Add.
7. Repeat step 6 for each site that you want to add. When you are finished adding sites,
click Close, and then click OK.
5
Configure Windows SharePoint
Services
You can install Microsoft® Windows® SharePoint® Services in one of the following
configurations:
• New database If you are installing the first instance of Windows SharePoint Services
in your Microsoft Office Project Server 2003 deployment, and you are using Microsoft
SQL Server™ 2000 for your Windows SharePoint Services database, follow the
procedures for installing Windows SharePoint Services with a new database.
• Existing database If you are installing a second copy of Windows SharePoint
Services for use on a network load–balancing cluster, or if you need to reinstall
Windows SharePoint Services and connect to your existing Windows SharePoint
Services content database, follow the procedures for installing Windows SharePoint
Services with an existing database.
• WMSDE If you are installing Windows SharePoint Services to use Microsoft
Desktop Engine (Windows) (WMSDE), follow the procedures for installing Windows
SharePoint Services with WMSDE.
If you choose to install Windows SharePoint Services later, you must use Project Web
Access to configure Project Server 2003 to connect to Windows SharePoint Services. For
more information, see the topic Configuring Windows SharePoint Services Settings in
Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 Installation
Guide.
Note If you configure Windows SharePoint Services to use Secure Sockets Layer (SSL), you must
use SSL for both the Administration site and the virtual server. The virtual server must be
configured to use the default port of 443.
If you do not have Windows SharePoint Services, you can download it from the Microsoft
Web site (http://go.microsoft.com/fwlink/?LinkId=23448).
Installing Windows SharePoint Services with a New Database

If you are installing the first instance of Windows SharePoint Services in your deployment,
follow the procedures in this topic.
Install Windows SharePoint Services

Install Windows SharePoint Services by using the following procedure.
1. Go to the Windows SharePoint Services Technology Center on the Microsoft Web site
(http://go.microsoft.com/fwlink/?LinkId=23448).
2. Download the Windows SharePoint Services installation files to your computer and
start the Windows SharePoint Services Setup program. When selecting the Windows
SharePoint Services file to download, select the language pack that matches the Project
Server 2003 default installation language.
Note If you selected to Open the file on the File Download page, the Windows SharePoint
Services Setup program will start automatically after the file is downloaded. If you selected
to Save the file on the File Download page, after the download completes, click the file to
start the Windows SharePoint Services Setup program.
3. In the End-User License Agreement (EULA) dialog box, review the terms, select
the I accept the terms in the License Agreement check box, and then click Next.
4. In the Type of Installation dialog box, select the Server Farm option, and then click
Next.
5. In the Summary dialog box, verify that only Windows SharePoint Services will be
installed, and then click Install.
Setup runs and installs Windows SharePoint Services. When Setup completes, a browser
opens and the Configure Admin Virtual Server page is displayed.
Note If you receive a Page cannot be displayed error, in the Internet Explorer address bar, replace
localhost with the name of the computer on which you installed Windows SharePoint Services.
Configure the Administrative Virtual Server

After Windows SharePoint Services Setup is complete, you can configure your
administrative virtual server, including specifying an application pool to use for the virtual
server processes, by using the Configure Administrative Virtual Server page.
Application pools are an Internet Information Services 6.0 feature that enables you to use
an isolated process to run Web applications. Each pool is uniquely identified on the Web
server, so you know which applications are performing which actions. If an application
fails, it will not affect other applications that are also running. Each application pool must
be configured with a security account that the application pool will run under.
When configuring Windows SharePoint Services to work with Project Server 2003, it is
suggested to create a new application pool and to select the predefined Network Services
account (NT AUTHORITY\Network Services) that is available on the local computer.
Note The Configure Administrative Virtual Server page opens automatically when the Windows
SharePoint Services installation is complete. You can also access the Configure Administrative
Virtual Server page by selecting SharePoint Central Administration in Administrative Tools.
The Configure Administrative Virtual Server page.
X To configure the administrative virtual server

1. Open Windows SharePoint Services Central Administration. Click Start, point to All
Programs, then Administrative Tools, and then select SharePoint Central
Administration.
2. On the Central Administration page, under Server Configuration, select Configure
virtual server for central administration.
3. On the Configure Administrative Virtual Server page, select the Create a new
application pool option.
4. In the Application pool name box, type a name for the application pool (for
example, SharePoint).
5. Select the Predefined option, and select Network Service from the list.
6. Click OK.
The Application Pool Changed page appears.

Note On the Application Pool Changed page, do not click OK until you complete the
following steps for restarting Internet Information Services.
7. On your Windows desktop, click Start, and then click Run.

8. In the Open box, type CMD and then click OK.
9. At the command prompt, type iisreset and then press ENTER.
10. When Internet Information Services (IIS) restarts, close the command prompt window
and return to your browser.
11. On the Application Pool Changed page, click OK.
Set the Configuration Database Server

By following the procedure to set the configuration database server, you configure
Windows SharePoint Services to work with SQL Server.
The Set Configuration Database Server page.
X To set the configuration database server

Administration.
2. On the Central Administration page, under Server Configuration, select Set
configuration database server.
3. In the Database server box, type the name of the instance of SQL Server that you
want to connect to.
4. In the SQL Server database name box, type a name for the configuration database
that you want to create (for example, WSSConfigDB).
5. Select the Use Windows authentication option.
6. If presented with the Active Directory Account Creation area, select the Users
already have domain accounts option.
Note Do not choose the Automatically create active directory accounts for users of this site
option. This option is not compatible with Microsoft Office Project Server 2003.
7. Click OK.
Extend the Virtual Server

After you set up the connection to SQL Server, you are ready to extend your virtual servers
by using Windows SharePoint Services. When you extend a virtual server, Windows
SharePoint Services is applied to the virtual server, and a top-level Web site is created.
The Extend Virtual Server page.
X To extend the virtual server

Administration.
2. On the Central Administration page, under Virtual Server Configuration, click
Extend or upgrade virtual server.
3. On the Virtual Server List page, click Default Web Site or another Web site if you
created one for this purpose.
4. On the Extend Virtual Server page, click Extend and create a content database.
5. On the Extend and Create Content Database page, in the Application Pool
section, select the Use existing application pool option.
6. Under Site Owner, in the User name box, type the Windows domain account name
of the owner for this virtual server.
This user will receive any quota or auto-deletion notices, and is automatically granted
Windows SharePoint Services administrator rights. You can use any Windows domain
account for this purpose.
7. In the E-mail box, type the e-mail address for the owner of this virtual server.
8. Click OK.
Run the Windows SharePoint Services Configuration Wizard

The Windows SharePoint Services Configuration wizard installs a basic Project Workspace
template and other program files on the server running Windows SharePoint Services. This
enables Windows SharePoint Services to be integrated with Project Server 2003. The
wizard also provisions a site called MS_ProjectServer_PublicDocuments for the public
document library feature in Microsoft Office Project Web Access 2003.
X To run the Windows SharePoint Services Configuration wizard
1. Insert the Project Server 2003 CD into the CD-ROM drive, or connect to a network
installation point.
2. If you are installing from the Project Server 2003 CD with AutoPlay enabled, click
Server installation in the Project Server Setup program. Otherwise, on the Project
Server 2003 CD or network installation point, browse for and run the file Setup.exe.
Note If you are installing from a network installation point, you must adjust the
Microsoft .NET Framework security settings to trust the Local intranet zone. To do this, in
Administrative Tools, open the Microsoft .NET Framework 1.1 Wizards, and use the
Adjust .NET Security Wizard to configure the Local intranet zone for full trust.
Project Server Setup starts.

3. Click Microsoft Windows SharePoint Services.
4. On the next page, click Windows SharePoint Services Configuration Wizard.
5. On the next page, click Next.
6. On the next page, click Default Web Site or select a previously provisioned site, and
then click Next.
7. On the next page, in the Select the managed path under which project sites will
be created list, click sites, and then click Next.
Note If you created a different managed path for use with Project Server sites, you can
select that path here.
8. On the next page, in the Site Owner User Name box, type the Windows account
name for the site owner.
For more information about Windows SharePoint Services site owners, see the
Microsoft Windows SharePoint Services Administrator’s Guide
9. In the Site Owner E-mail address box, type the e-mail address for the site owner,
and then click Next.

11. On the next page, write down the information under SharePoint Central
Administration URL and Create a top-level Web site under this URL. You will
need this information when you install Project Server 2003.
12. Click Finish.
Create a Windows SharePoint Services Administrator

In order for Project Server 2003 to access Windows SharePoint Services, you must create a
Windows SharePoint Services administrator on the computer running Windows SharePoint
Services. To do this, add the account that you created for this purpose to the
Administrators group on the computer running Windows SharePoint Services.
X To create a Windows SharePoint Services administrator
1. On the computer running Windows SharePoint Services, open Computer
Management.
2. In the console tree, expand Local Users and Groups and click Groups.
3. Right-click the Administrators group and then click Properties.
4. Click Add.
6. Click OK.
Windows SharePoint Services is now configured to work with Project Server 2003.
Installing Windows SharePoint Services with an Existing

Database
If you are installing a second copy of Windows SharePoint Services for use on a network
load–balancing cluster, or if you need to reinstall Windows SharePoint Services and
connect to your existing database, follow the steps in this topic.

Note If you selected to Open the file on the File Download page, the Windows SharePoint
Services Setup program will start automatically after the file is downloaded. If you selected
to Save the file on the File Download page, after the download completes, click the file to
start the Windows SharePoint Services Setup program.
4. In the Type of Installation dialog box, select the Server Farm option, and then click
Next.
5. In the Summary dialog box, verify that only Windows SharePoint Services will be
installed, and then click Install.
Setup runs and installs Windows SharePoint Services. When Setup completes, a browser
opens and the Configure Admin Virtual Server page is displayed.
Configure the Administrative Virtual Server

After the setup process is complete, you can configure your administrative virtual server—
including specifying an application pool to use for the virtual server processes—by using
the Configure Administrative Virtual Server page.
Application pools are an Internet Information Services 6.0 feature that enables you to use
an isolated process to run Web applications. Each pool is uniquely identified on the Web
server, so you know which applications are performing which actions. If an application
fails, it will not affect other applications that are also running. Each application pool must
be configured with a security account that the application pool will run under.
When configuring Windows SharePoint Services to work with Project Server 2003, it is
suggested to create a new application pool and to select the predefined Network Services
account (NT AUTHORITY\Network Services) that is available on the local computer.
Note The Configure Administrative Virtual Server page opens automatically when the Windows
SharePoint Services installation is complete. You can also access the Configure Administrative
Virtual Server page by selecting SharePoint Central Administration in Administrative Tools.
The Configure Administrative Virtual Server page
X To configure the administrative virtual server

1. On the Configure Administrative Virtual Server page, select the Create a new
2. In the Application pool name box, type a name for the application pool.
3. Select the Predefined option, and then choose Network Service from the list.
4. Click OK.
The Application Pool Changed page will appear.
Note On the Application Pool Changed page, do not click OK until you have completed the
following steps for restarting Internet Information Services.
5. In the Open box, type CMD and then click OK.

6. At the command prompt, type iisreset and then press ENTER.
7. When IIS restarts, close the command prompt window and return to your browser.
8. On the Application Pool Changed page, click OK.
Set the Configuration Database Server

Set the configuration database server to connect your new Windows SharePoint Services
installation to an existing configuration database.
The Set Configuration Database Server page.
X To set the configuration database server

want to connect to.
2. In the SQL Server database name box, type the name of the existing configuration
database.
3. Select the Use Windows authentication option.
4. Select the Connect to existing configuration database check box.
5. In the Active Directory Account Creation area, select the Users already have
domain accounts option.
Note Do not choose the Automatically create active directory accounts for users of this site
option. This option is not compatible with Project Server 2003.
6. Click OK.
The Refresh Config Cache on Other Web Servers page is displayed.
Extend the Virtual Server

After you set up the connection to SQL Server, you are ready to extend your virtual servers
by using Windows SharePoint Services. When you extend a virtual server, Windows
SharePoint Services is applied to the virtual server and a top-level Web site is created.
The Extend Virtual Server page.
X To extend the virtual server

1. On the Refresh Config Cache on Other Web Servers page, click OK.
2. On the Central Administration page, click Extend or upgrade virtual server.
3. On the Virtual Server List page, click Default Web Site or another Web site if you
have created one for this purpose.
4. On the Central Administration page, click Extend and map to another virtual
server.
5. On the Virtual Server List page, click Default Web Site.
6. On the Extend and Map to Another Virtual Server page, click the Create a new
7. In the Application pool name box, type a name for the application pool.
8. Select the Predefined option, and then choose Network Service from the list.
9. Click OK.

The Windows SharePoint Services Configuration Wizard installs a basic Microsoft Project
Workspace template and other program files on the server running Windows SharePoint
Services. This enables Windows SharePoint Services to be integrated with Project
Server 2003. When you configure Windows SharePoint Services to run in a load-balancing
cluster, you must run the Windows SharePoint Services Configuration Wizard on each
node in the cluster. Additionally, for each node in the cluster subsequent to the first, you
must run the wizard from a command line with the -f switch. This will copy just the
template files, without attempting to re-register the template.
X To run the Windows SharePoint Services Configuration Wizard
1. Insert the Project Server 2003 CD into your CD-ROM drive, or connect to a network
installation point.
Server 2003 CD or network installation point, browse to and run the file Setup.exe.
Administrative Tools, open the Microsoft .NET Framework 1.1 Wizards, and use the

3. Click Windows SharePoint Services.
then click Next.
7. On the next page, in the Select the URL path to create project sites under list, click
sites, and then click Next.
Microsoft Windows SharePoint Services Administrator’s Guide on the Microsoft Web site

12. Click Finish.
Create a Windows SharePoint Services Administrator

In order for Project Server 2003 to access Microsoft Windows SharePoint Services, you
must create a Windows SharePoint Services administrator on the computer running
Windows SharePoint Services. To do this, add the account that you created for this
purpose to the Administrators group on the computer running Windows SharePoint
Services.
X To create a Windows SharePoint Services administrator
1. On the computer running Windows SharePoint Services, open Computer
Management.
2. In the console tree, click Groups.
3. Right-click the Administrators group and then click Properties.

4. Click Add.
6. Click OK.
Installing Windows SharePoint Services with WMSDE

You can install Windows SharePoint Services to use the Microsoft Desktop Engine
(Windows) (WMSDE). WMSDE does not have the performance limitations that the
version of MSDE that can be used with Project Server 2003 has. WMSDE only works with
Windows SharePoint Services.
If you want to install Windows SharePoint Services to use WMSDE, follow the procedures
in this topic.

Note If you selected Open on the File Download page, the Windows SharePoint Services
Setup program will start automatically after the file is downloaded. If you selected Save on
the File Download page, after the download completes, click the saved file to start the
Windows SharePoint Services Setup program.
4. In the Type of Installation dialog box, select the Typical Installation option, and
then click Next.
5. In the Summary dialog box, click Install.

Setup runs and installs Windows SharePoint Services and WMSDE.

The Windows SharePoint Services Configuration Wizard installs a basic Microsoft Project
Workspace template and other program files on the server running Windows SharePoint
Services. This enables Windows SharePoint Services to be integrated with Project
Server 2003. The wizard also provisions a site called MS_ProjectServer_PublicDocuments
for the public document library feature in Microsoft Office Project Web Access 2003.
X To run the Windows SharePoint Services Configuration Wizard
1. Insert the Project Server 2003 CD into your CD-ROM drive, or connect to a network
installation point.
Server 2003 CD or network installation point, browse for and run the file Setup.exe.
Administrative Tools, open the Microsoft .NET Framework 1.1 Wizards and use the

3. Click Windows SharePoint Services.
then click Next.
7. On the next page, in the Select the URL path to create project sites under list, click
sites, and then click Next.
Microsoft Windows SharePoint Services Administrator’s Guide

12. Click Finish.

6
Deploy the Database
Project Server Setup in Microsoft® Office Project Server 2003 can automatically create the
Project Server database. Allowing Project Server Setup to create the database for you
automatically is the best option for most deployment scenarios.
This chapter describes how to manually deploy your Project Server database prior to
installing Project Server 2003. Use the procedures in this chapter if you want to create the
database prior to installing Project Server 2003, or if you are using database partitioning
options or Microsoft Desktop Engine (MSDE).
Creating the Project Server Database Manually

You can create the Project Server database manually by using a Microsoft
SQL Server™ 2000 script provided on the Project Server 2003 CD. Use this procedure if
you do not want the database to be created by the Project Server Setup program.
Running this script requires a SQL Server login that is a member of the Systems
Administrator role on the computer on which you are creating the database. It is also
possible to use the SQL Server sa account for this purpose.
Note It is recommended that you run the scripts on the computer on which you are creating the
database.
X To create the Project Server database

1. In SQL Server 2000 Enterprise Manager, create a new database for use with Project
Server 2003.
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 a location on your database server.
4. Open a command prompt window, and then browse to the Database folder where you
copied it locally.
5. Run Setupdb.cmd by using the following syntax:
SETUPDB.cmd <SQL ServerName> <DatabaseName> <UserName> <Password>

NOPAUSE
For example,
Setupdb.cmd PROJSQL2003 ProjectServer MyAccount hello NOPAUSE
Notes
If you omit the UserName and Password parameters, the script will use NTLM
authentication.
NOPAUSE is an optional parameter that will cause setupdb.cmd to return to the command
prompt after completion.
6. Using SQL Server Query Analyzer and connecting with your login account, run
PSRoles.sql from within the Project Server database context.
This script creates the two database roles needed by the Project Server logins:
7. Using SQL Server Enterprise Manager, go to the Security folder, select Login, and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure to
use SQL Server authentication and to select the new database on the Database
Access tab.
8. On the Database Access tab, assign the MSProjectServerRole role to the
MSProjectServerUser login, and then assign the MSProjectRole role to the
MSProjectUser login.
When the script finishes successfully, partition the database if necessary, and then install
Project Server 2003 and connect to the new database during Project Server Setup.
Partitioning the Database

If you created the Project Server database manually and you want to partition it prior to
installing Project Server 2003, you can use the procedures in this topic to partition the
Project Server databases and then connect to these databases during Project Server Setup.
These procedures require you run the partition scripts with a SQL Server login that is a
member of the Systems Administrator role on each instance of SQL Server in your
deployment. When you create this account, it will require the same password on each
server. It is recommended that you delete these logins when you are finished partitioning
the database. It is also possible to use the SQL Server sa account, so long as the password
is the same on each server. The sa account cannot be deleted.
Important
SQL Server uses the Microsoft Distributed Transaction Coordinator (MSDTC) automatically with
Project Server database partitioning. Be sure that MSDTC is installed on each computer running
SQL Server in your deployment. If you are also running SQL Server in a cluster, some database
transactions will fail unless you use the COM+ Wizard (Comclust.exe) to configure the cluster. Using
this tool routes all MSDTC requests to the computer in the cluster that is running MSDTC for the
cluster. For information about configuring the cluster by using Comclust.exe, see the Microsoft Web
site (http://go.microsoft.com/fwlink/?LinkId=19684). If MSDTC is not installed on your computer,
you can install it from the SQL Server 2000 CD.
By default, the network access settings of MSDTC are disabled on new installations of SQL
Server 2000 on computers running Microsoft Windows Server™ 2003. If you are partitioning on a
computer running Windows Server 2003, follow the procedure in Microsoft Knowledge Base article
329332 (http://go.microsoft.com/fwlink/?LinkId=19685) to be sure that your MSDTC settings are
correct. After you complete the procedure, restart your computer.
Partitioning the Database for New Deployments

Use the procedures in this topic to set up database partitioning as part of a new Project
Server deployment. Complete these procedures assume before you install Project
Server 2003 and its associated components. You can also partition your database after you
install Project Server 2003. For more information, see the topic Database Partitioning in
Chapter 10, System Optimization of the Microsoft Office Project Server 2003 Installation Guide.
You can partition your database in of the following three ways:
• By partitioning the View tables to move the View tables to a separate database server.
• By partitioning the Project tables to move the Project tables to a separate database
server.
• By using three-way partitioning to move both the Project tables and the View tables to
separate database servers.
Important These procedures should only be used by someone who is familiar with SQL
Server 2000 and experienced with the database creation process, security, and editing and
executing scripts across a multi-server environment. All steps listed in these procedures must be
performed in the order in which they are listed.
The files required for the procedures in this topic can be found on the Project Server 2003
CD in the Support/Database folder. It is recommended that you copy this folder to each
of the database computers in your deployment.
Partitioning the View Tables

You can move the Project Server 2003 View tables to a separate database server. This
configures the databases as follows:
• Main database server Contains the Web tables, Cube tables, Project tables, and
Security views.
• View Tables database server Contains the View tables.
Project Server Setup can partition the View tables for you when you are installing Project
Server 2003. If you prefer to do so manually before running Project Server Setup, complete
the following procedures.
X To configure the View Tables database server
1. In SQL Server 2000 Enterprise Manager, create a new Project Server database for the
View tables (for example, ProjectServerVIEW).
Access tab.
ViewTbls.sql from within the Project Server View database context.
X To configure the Main database server
1. In SQL Server 2000 Enterprise Manager, create a new Project Server database (for
example, ProjectServerMAIN).
Access tab.
Important Be sure that the user names and passwords for these database logins are the
same on both your Main database server and your View Tables database server.

5. Using SQL Server Query Analyzer and connecting with your login account, run the
following scripts from within the Project Server database context:
a. ProjTbls.sql
b. WebTbls.sql
c. CubeTbls.sql
d. SecViews.sql
e. ProjSPS.Sql
f. WebSPS.Sql
6. Using the Osql tool (on the Project Server 2003 CD in the /Support/Database folder)
and connecting to the main database with your login account, run PjcrtSPS.sql.
Important You must run this script with Osql. SQL Server Query Analyzer will not open this
script file because of the line length of the binary data in the last UPDATE command. The
Osql command must be in the following format and must be run from the command line on
the server. You can run this command-line tool from either database server.
osql –S <MainDatabaseServerName> -d <MainDatabaseName> -U <Login>

-P <Password> -i <Input File>
For example:
osql –S PSMain –d ProjectServerMAIN –U MyAccount –P hello –i
PjcrtSPS.sql
7. Using SQL Server Query Analyzer and connecting with your login account, create a
linked server by using the following command:
EXEC sp_addlinkedserver <ViewTablesDatabaseServerName>, N'SQL
Server'
For example:
EXEC sp_addlinkedserver PSView, N'SQL Server'
LnkViews.sql from within the Project Server database context.
9. Using SQL Server Query Analyzer and connecting with your login account, execute the
ExecLinkedViewsSP stored procedure as follows:
EXEC ExecLinkedViewsSP <ViewTablesDatabaseServerName>,
<ViewTablesDatabaseName>
For example:
EXEC ExecLinkedViewsSP PSView, ProjectServerVIEW
following scripts in order listed:
Note These files can be found in the Database\1033 folder.
a. LocData.sql
b. EGlobal.sql
Important You must run this script with Osql. For more information about using Osql,
see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=20509).
c. InsDef.sql
d. InsDefLP.sql
X To connect to the new databases
1. Run Project Server Setup.
2. On the Enter database server information page, select the Connect to another
existing database option.
3. In the Database server box, type the name of the SQL Server instance that you will
use for the Main database server.
4. In the Database name box, type the name of the Project Server database that you
created on the server, and then click Next.
5. On the Enter connection information for View tables page, clear the Connect to
the main Project Server 2003 database check box.
6. In the Database server box, type the name of the View Tables database server.
7. In the Database name box, type the name of the Project Server View database that
you created on that server.
8. Complete Project Server Setup.
Partitioning the Project Tables

You can move the Project Server database tables that are used by Project Professional on a
separate database server. This configures the databases as follows:
• Main database server Contains the Web tables, Cube tables, and View tables.
• Project Tables database server Contains the Project tables and Security views.
Project Server Setup cannot create this database configuration when you are installing
Project Server 2003. If you want to partition the Project tables, follow the procedures in
this topic before you run Project Server Setup.
X To configure the Project Tables database server
Project Tables (for example, ProjectServerPROJ).
Access tab.
following scripts in the listed order from within the Project Tables database context:
a. ProjTbls.sql
b. ProjSPS.sql
c. SecViews.sql
and connecting to the ProjectServerPROJ database with your login account, run
PjcrtSP1.sql.
osql –S <DatabaseServerName> -d <DatabaseName> -U <Login> -P

<Password> -i <Input File>
For example:
osql –S PSProj –d ProjectServerPROJ –U MyAccount –P hello –i
PJCRTSP1.SQL

example, ProjectServerMAIN).
Access tab.
same on both your Main database server and your Project Tables database server.

following scripts from within the Project Server Main database context:
a. WebTbls.sql
b. CubeTbls.sql
c. ViewTbls.sql
d. ViewSPS.sql
e. WebSPS.sql
EXEC sp_addlinkedserver <ProjectTablesDatabaseServerName>, N'SQL
Server'
For example:
EXEC sp_addlinkedserver PSProj, N'SQL Server'
LNKPROJ.SQL from within the Project Server Main database context.
EXEC ExecLinkedViewsSP <ProjectTablesDatabaseServerName>,
<ProjectTablesDatabaseName>
For example:
EXEC ExecLinkedViewsSP PSProj, ProjectServerPROJ
following scripts in the order listed:
a. LocData.sql
b. EGlobal.sql
c. InsDef.sql
d. InsDefLP.sql
10. Modify the PjcrtSP2.sql script and change the <WinProjServerName> and
<WinProjDatabaseName> parameters on the line where the
MSP_PDS_SP_INSERT_PROJECT_BINARY stored procedure is called, to the
name of the Project Tables SQL Server and the Project Server database respectively.
PjcrtSP2.sql from within the Project Server Main database context.
3. In the Database server box, type the name of the instance of SQL Server that you will
use for the Main database server.
created on the server, and then click Next.
5. On the Enter Connection Information for View Tables page, select the Connect to

X To update the registry for a two-way partition
1. Run the Connection Information tool (ConnInfo.exe) on the computer on which
Project Server 2003 is installed.
Note For more information about ConnInfo.exe, see the topic Connection Information Tool
in Appendix C, Project Server Installation Tools of the Microsoft Office Project Server 2003
Installation Guide.
2. Select the Partitioned database configuration option, and then select the Custom
Deployment option.
3. From the list, select Project Tables.
4. In the SQL Server box, type the name of the Project Tables database server.
5. In the Database box, type the name of the Project Server database that you created on
that server.
6. In the MSProjectServer Role Member section, type MSProjectServerUser for the

user name and the password that you chose for that account.
7. In the MSProject Role Member section, type MSProjectUser for the user name and
the password that you chose for that account.
8. Click Save, and then click Exit.
Using Three-Way Partitioning

You can install the Web tables, Project tables, and View tables onto three different
database servers. This configures the databases as follows:
• Main database server Contains the Web tables and Cube tables.
• Project Tables database server Contains the Project tables and Security views.
• View Tables database server Contains the View tables.
The Project Server Setup program cannot create this database configuration when you run
Setup. If you want to create a three-way partition, follow the procedures in this topic
before you run Project Server Setup.
1. Create a new Project Server database (for example, ProjectServerPROJ).
Access tab.
following scripts in the listed order from within the Project Tables database context.
a. ProjTbls.sql
b.ProjSPS.sql
c. SecViews.sql
and connecting to the Project Tables database with your login account, run
PjcrtSP1.sql.
osql –S <MainDatabaseServerName> -d <MainDatabaseName> -U <Login>

-P <Password> -i <Input File>
For example:
osql –S PSMain –d ProjectServerMAIN –U MyAccount –P hello –i
PJCRTSP1.SQL

1. Create a new Project Server database (for example, ProjectServerVIEW).
use SQL Server authentication and to select the View Tables database on the
Database Access tab.

ViewTbls.sql from within the Project Server database context.
ViewSPS.sql from within the View Tables database context.
1. Create a new Project Server database (for example, ProjectServerMAIN).
use SQL Server authentication and to select the Project Server database on the

following scripts from within the Project Server Main database context:
a. WebTbls.sql
b. CubeTbls.sql
c. WebSPS.sql
Server'
For example:
7. Using SQL Server Query Analyzer and connected with your login account, create a
Server'
For example:
LnkProj.sql from within the Project Server Main database context.
For example:
LnkViews.sql from within the Project Server database context.
following stored procedure as follows:
For example:
following scripts from in the listed order:
a. LocData.sql
b. EGlobal.sql
c. InsDef.sql
d. InsDefLP.sql
13. Modify the PjcrtSP2.sql script and change the WinProjServerName and
WinProjDatabaseName parameters on the line where the
name of the Project Tables SQL Server and the Project Tables database respectively.
PjcrtSP2.sql from within the Project Server database context.
used for the Main database server.
created on that server, and then click Next.
5. On the Enter connection information for Views tables page, clear the Connect to
6. In the Database server box, type the name of the View Tables database server.
7. In the Database name box, type the name of the View Tables database that you
created on that server.

X To update the registry for a three-way partition
Installation Guide.
Deployment option.
that server.

8. From the list, select View Tables.

9. In the SQL Server box, type the name of the View Tables database server.
10. In the Database box, type the name of the View Tables database that you created on
that server.
13. From the list, select Web Tables.
14. In the SQL Server box, type the name of the Project Server Main database server.
15. In the Database box, type the name of the Project Server Main database.
the password you that chose for that account.
Deploying Project Server 2003 with MSDE

You can use MSDE 2000 to host your Project Server database. However, MSDE has
significant performance limitations and is not recommended for anything beyond the most
basic test deployment.
The limitations to using MSDE instead of SQL Server as the repository for the Project
Server database include:
• Maximum number of connections MSDE has a managed concurrency workload
governor that limits up to five concurrent batch workloads for optimal performance.
As batch workloads are added that increase the number past five, the concurrency
governor slows down the system. However, MSDE 2000 has no limitations on the
number of users who can be connected to the database.
• Maximum database size MSDE supports up to a 2 gigabyte (GB) database. A
single computer can host multiple instances of MSDE, with each instance supporting
up to a 2 GB database.
• Maximum memory usage MSDE is limited to 1 GB of memory, regardless of how
much memory is available on the computer.
• Administration tools MSDE does not come with the administration tools that are
provided with SQL Server, including SQL Server Enterprise Manager, SQL Server
Query Analyzer, and SQL Server Profiler. All administration must be performed by
using the Osql command-line tool or by using the administration tools that are
installed with a separate instance of SQL Server.
X To install MSDE SP3
1. Go to the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=19683).
2. 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.
3. 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 will be listed as language_SQL2KDeskSP3.exe
where language represents the language version of the download.
4. When prompted, save the file to your Windows desktop.

5. In Windows Explorer, double-click the file that you previously saved to your desktop.
6. Click I Agree to accept the End-User License Agreement (EULA).
7. In the Installation Folder box, type C:\sql2ksp3 and then click Continue.
8. 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.

9. Click OK.
7
Install Project Server 2003
Microsoft® Office Project Server 2003 is composed of three services:
• Project Server Front-End service The Project Server Front-End service runs on the
computer running Internet Information Services (IIS).
• Session Manager service The Session Manager service manages user session state in
Microsoft Office Project Web Access 2003. When used in a clustered environment, the
Session Manager service should be deployed on its own server outside the cluster. This
enables users to be directed to any one of the clustered application servers.
• View Processing service The View Processing service creates the project views for
Project Web Access. Each time a resource or project is checked in to Project Server,
the View tables are updated. Because this can be extremely processor-intensive,
moving this service to a separate server can greatly reduce the workload for the
computer running Project Server 2003.
Project Server Setup installs these services. You can install all services on the same
computer, or you can distribute the services across multiple computers.
If you distribute Project Server services across multiple computers, you must run Project
Server Setup on each computer on which you want to run a service.
For more information about when to install Project Server services on separate computers,
see the Microsoft Office Project Server 2003 Configuration Planning Guide
(http://go.microsoft.com/fwlink/?LinkID=20235).
To see a visual representation of the relationships between the various Project Server Setup
steps, see the Project Server Setup Flow Diagram on the Microsoft Web site
Note Do not install Project Server 2003 on a computer running Project Professional 2002.
Starting Project Server Setup

Use the following procedure to start Project Server Setup.
X To start Project Server Setup
1. On the computer on which you want to install Project Server 2003, insert the Project
Server 2003 CD into the CD-ROM drive, or connect to a network installation point.
2. If you are installing from the Project Server 2003 CD with AutoPlay enabled, Setup
starts automatically. Otherwise, on the Project Server 2003 CD (or network installation
point), browse for and run the file Setup.exe.
Project Server Setup Welcome Page

The Project Server Setup welcome page provides links to various documents as well as a
link to start Project Server Setup.
The Project Server Setup welcome page.
X To start Project Server Setup

• Click Server installation.
Product Key
If the Product Key page appears, enter your 25-character product key.
The Product Key page.
Note This page appears if your licensing agreement requires you to have a product key.
X To enter the product key

1. In the Product Key boxes, type the product key provided with your Project
Server 2003 CD.
2. Click Next.
User Information
You can use the User Information page to enter your user information. This information
is not required by Project Server 2003.
The User Information page.
Note This page appears for all installations.
X To enter user information

1. In the User name box, type your name.
2. In the Initials box, type your initials.
3. In the Organization box, type the name of your organization.
4. Click Next.
End-User License Agreement

The End-User License Agreement page displays the End-User License Agreement for
The End-User License Agreement page.
X To accept the End-User License Agreement

1. Read the End-User License Agreement.
2. If you agree to the End-User License Agreement, select I accept the terms of the
License Agreement, and then click Next.
Select a Location for Installation

Use the Select a location for installation page to select an installation location for Project
Server 2003. The default location is shown in the Install to box.
The Select a location for installation page.
X To select an installation location

1. Type a location in the Install to box, or click Browse to browse for a new path.
2. After you have specified the path for Project Server 2003 installation, click Next.
Choosing the Services to Install

You must install all three Project Server services in order for Project Server 2003 to work.
Run Setup on each computer on which you want to install a Project Server service.
Choose the Services That You Want to Install on This Server

By default, all Project Server services are installed, but the Project Server Sample Data is
not. Use the Choose the services you want to install on this server page to choose the
Project Server services that you want to install on this computer.
The Choose the services you want to install on this server page.

If you are installing the View Processing service or the Session Manager service on a
different computer than the Project Server Front-End service, you must install the Project
Server Front-End service after you have installed the View Processing and Session Manager
services. Setup will require you to specify the location of the View Processing and Session
Manager services when you install the Front-End service.
If you are installing the Project Server Sample Data, all Project Server services must be
installed on the same computer along with Microsoft SQL Server™ 2000, Microsoft
Windows® SharePoint® Services, and SQL Server Analysis Services (if applicable). For
information about configuring the sample data after installation, see Appendix D,
Configuring the Sample Database in the Microsoft Office Project Server 2003 Installation
Guide.
Note You cannot install the Project Server Sample Data on a domain controller.
If you are not installing all of the Project Server services on this computer, clear the service
options that you do not want to install.
X To clear an option
• Click the arrow next to the option name, and then click Not Available.
X To select an option
• Click the arrow next to the option name, and then click Run from My Computer.
When you are finished selecting the options that you want to install, click Next.
Create the View Processing Share

When projects are published to Project Server 2003, a copy of the project is used to create
project view data. When you install the View Processing service on a different computer
than the computer on which the Project Server Front-End service is installed, Setup creates
a shared folder (also called a share) where Project Server will stage updated view
information that is generated when projects are published from Microsoft Office Project
Professional 2003.
Use the Enter the Views Processing server information page to specify the name of this
share, as well as a computer account that has sufficient rights to create it.
The Enter the Views Processing server information page.
Note This page appears when you are installing the View Processing service but not the Project
Server Front-End service.
X To enter the View Processing server information

1. Type a name for the share that you want to create in the Share name box.
2. In the Logon name box, type the user name of an account that has sufficient
permissions to create the share.
3. In the Password box, type the password for the user account.
4. Click Next.
Enter the Session Manager Server Name

When you install the Project Server Front-End service but not the Session Manager service,
Project Server Setup displays the Enter the Session Manager server name page. Use this
page to specify the server on which you installed the Session Manager service.
The Enter the Session Manager server name page.
Note This page appears when you are installing the Project Server Front-End service but not the
Session Manager service.
X To enter the Session Manager server name

1. In the Server name box, type the name of the server on which the Session Manager
service is installed.
2. Click Next.
Enter the View Processing Server Information

When you install the Project Server Front-End service but not the View Processing service,
Project Server Setup displays the Enter the Views Processing server information page.
Use this page to specify the server on which the View Processing service was installed and
the share that you created for the View Staging folder on that server. The account that you
choose must have read/change permissions on the share.
The Enter the Views Processing server information page.
Note This page appears when you are installing the Project Server Front-End service but not the
View Processing service.
X To enter the View Processing server information

1. In the Path box, type the computer name and share name for the views staging share
that you created when you installed the View Processing service.
2. In the Logon name box, type the domain and user name of the account that you want
Project Server 2003 to use to connect to the View Staging share.
4. Click Next.
Note If the Views Staging share is located in a non-trusted domain, Setup might not be able to
validate the Windows user account that you specified. If Setup is not able to validate your user
account, use Windows Explorer to log on to the share and then try again.
Choosing Database Options

If you are running Project Server 2003 more than once in order to install services on more
than one computer, be sure to create a new database only once, and connect to that
database on subsequent installations.
Connecting to an Existing Database

If you have already created your Project Server database, or if you are connecting to an
upgraded Microsoft Project Server 2002 or Microsoft Project Central database, choose the
Connect to another existing database option on the Enter database server
information page.
Connect to an Existing Database

When you are connecting to an existing database, the Enter database server information
page prompts you for the name of the database and the server on which it is located.
The Enter database server information page.
Note This page appears for all installations when you choose to connect to an existing database.
X To enter the database server information

1. Select the Connect to another existing database option.
2. In the Database server box, type the name of the instance of SQL Server on which
the Project Server database is located.
want to connect to.
4. Click Next.
Enter Connection Information for View Tables

If the View tables are not part of your main Project Sever database, use the Enter
connection information for Views tables page to specify where the Project Server View
tables are located.
The Enter connection information for Views tables page.
X To connect to View tables on the main Project Server 2003 database

1. Select the Connect to the main Project Server 2003 database check box.
2. Click Next.
X To connect to View tables on a different server
1. Clear the Connect to the main Project Server 2003 database check box.
2. In the Database server box, type the name of the SQL Server instance on which the
View tables are located.
3. In the Database name box, type the name of the View Tables database.
4. Click Next.
Enter Database Account Information

Use the Enter database account information page to specify the account name and
password that Project Professional 2003 and Project Server 2003 will use to access the
Project Server database.
The Enter database account information page.
X To specify the database account for Project Server 2003 to use

1. In the top Logon name box, type the name of the SQL Server account for Project
Server 2003 to use to connect to the database.
2. In the top Password box, type the password for the account.
X To specify the database account for Project Professional 2003 to use

1. In the bottom Logon name box, type the name of the SQL Server account for Project
Professional to use to connect to the database.
2. In the bottom Password box, type the password for the account you typed in the
previous step.
Creating a New Database That Uses Windows Authentication

If you are creating a new database and you want to access the computer running SQL
Server by using Windows authentication and the account that you are currently logged in
with, select the Create a new database and Windows Authentication (currently logged
in user) options on the Enter Database Server Information page. This will use your
current Windows account to access the computer running SQL Server and create the
database. The account information is not saved and will not be used at any time after Setup
completes.
If you are deploying the View tables to a different server by using Project Server Setup, you
cannot use the Windows authentication option. You must use SQL Server authentication.
For more information, see the topic Creating a New Database That Uses SQL Server
Authentication in Chapter 7, Installing Project Server 2003 of the Microsoft Office Project
Note Windows authentication will not work if you are installing Project Server 2003 on a Terminal
Server. If you are installing Project Server 2003 on a Terminal Server, choose the SQL Server
Authentication option.
When you are creating a new database to use with Project Server 2003, the Enter database
server information page will prompt you for the database server name and the type of
authentication that you want to use.
Note This page appears for all installations when you choose to create a new database that uses
Windows authentication.
X To create a new database that uses Windows authentication

1. Select the Create a new database option.
2. In the Database server box, type the name of the SQL Server instance on which you
want to create the database.
3. Select the Windows Authentication (currently logged in user) option.
4. Click Next.

When you create a new database by using Windows authentication, it is not possible to
install the View tables on a different server. In this case, the Enter connection
information for Views tables page is preset to connect to the main Project Server
database. Click Next to create the database account information.
Create Database Account Information

When Setup creates a new database for use with Project Server 2003, the accounts used by
Project Server 2003 and Project Professional to access the database are created
automatically. Use the Create database account information page to specify the
password to use with these accounts. Record the passwords that you choose in your system
documentation for future reference.
The Create database account information page.
X To specify a password for Project Server 2003 to use to connect to the database
1. In the top Password box, type the password that you want to use.
2. In the top Confirm password box, type the password again.
X To specify a password for Project Professional 2003 to use to connect to the database
1. In the bottom Password box, type the password that you want to use.
2. In the bottom Confirm password box, type the password again, and then click Next.
Creating a New Database That Uses SQL Server Authentication

If you are creating a new database and you want to access the computer running SQL
Server by using SQL Server authentication, select the Create a new database and SQL
Server Authentication options on the Enter database server information page. The
Enter database server information page prompts you for the database server name and
the type of authentication that you want to use.
SQL Server authentication.
X To create a new database that uses SQL Server authentication

1. Select the Create a new database option.
want to create the new database.
3. Select the SQL Server Authentication option.
4. In the Logon name box, type the name of the SQL Server account that you want to
use to create the new database.
Note This account information is used only by Project Server Setup. The information is not
saved and will not be used after Setup completes.
5. In the Password box, type the password for the account.

6. Click Next.

If you are deploying the View tables on a different server from your main Project Sever
database, use the Enter connection information for Views tables page to specify where
the Project Server View tables are created.
X To create View tables as part of the main Project Server 2003 database
1. Select the Connect to the main Project Server 2003 database check box.
2. Click Next.
X To create View tables on a different server from the main Project Server 2003 database
1. Clear the Connect to the main Project Server 2003 database check box.
want to create the View tables.
3. In the Logon name box, type the name of the SQL Server account that you want to
use to create the database.
4. In the Password box, type the password for the SQL Server account.
5. Click Next.
Create Database Account Information

When Setup creates a new database for use with Project Server 2003, the accounts used by
Project Server 2003 and Project Professional 2003 to access the database are created
automatically. Use the Create database account information page to specify the
password to use with these accounts.
The Create database account information page.
X To specify a password for Project Server 2003 to use to connect to the database
1. In the top Password box, type the password that you want to use.
2. In the top Confirm password box, type the password again, and then click Next.
X To specify a password for Project Professional 2003 to use to connect to the database
1. In the bottom Password box, type the password that you want to use.
2. In the bottom Confirm password box, type the password again, and then click Next.
Configuring the Front-End Components

When you are installing the Project Server 2003 Front-End service, the following pages
appear in the Project Server 2003 Setup Wizard:
• Enter Analysis Services Connection Information
• Select a Web Site
• Enter Web Server Address Information
• Connect to a Web Server Running Windows SharePoint Services
• Enter Account Information for Windows SharePoint Services
• Choose an Installation Environment
• Enter Administrator Password
Enter Analysis Services Connection Information

If you are deploying Analysis Services, use the Enter Analysis Services connection
information page to specify the analysis server to be used with Project Server 2003, and
the connection account information for the analysis server.
The Enter Analysis Services connection information page.
Note This page appears when you are installing the Project Server Front-End service or View
Processing service.
X To enter Analysis Services connection information

1. In the Analysis server box, type the name of the analysis server to use with Project
Server 2003.
2. In the Logon name box, type the domain and user name for the account that you
want to use to access the analysis server. Use the account that you created for Analysis
Services in the topic Create User Accounts in Chapter 4, Prepare the Servers of the
It is recommended that you enter this information when you install Project Server 2003,
unless the analysis server is in a non-trusted domain. If the analysis server is in a non-
trusted domain, choose the Enter this information later option.
If you choose the Enter this information later option, you need to run the Project Server
COM+ Settings tool (PSCOMPlus.exe) and update the analysis server information in
Project Web Access 2003. For more information, see the topic Configuring Analysis
Services Settings in Chapter 8, Post-Installation Tasks of the Microsoft Office Project
Select a Web Site

Use the Select a Web site page to select the Web site on which the Internet Information
Service (IIS) virtual directory for Project Server 2003 is to be installed. You can choose the
default Web site or another site that you have created for the purpose.
The Select a Web site page.
Note This page appears when you are installing the Project Server Front-End service.
X To select a Web site

• Click the Web site that you want, and then click Next.
Enter Web Server Address Information

Use the Enter Web server address information page to specify an intranet and extranet
address for Project Server 2003. This information will be used to provide links to Project
Server 2003 from notifications and reminders.
The Enter Web server address information page.
X To enter Web server address information

1. Under Intranet protocol and server name for accessing Project Server, select a
protocol from the drop-down list, and then type the server name in the box.
2. Optionally, under Extranet protocol and domain name for accessing Project
Server, select a protocol from the drop-down list, and then type the extranet address in
the box.
3. Click Next.
If you choose the Enter this information later option, you need to enter this information
after Project Server Setup finishes. For more information, see the topic Configuring Web
Server Address Settings in Chapter 8, Post-Installation Tasks of the Microsoft Office
Note If you upgraded your database from Microsoft Project Server 2002 and you choose the Enter
this information later option, Microsoft Project Server 2002 Web server address information might
remain in the database. It is strongly recommended that you enter this information when you are
installing Project Server 2003.
Enter SMTP Mail Server Information

Use the Enter SMTP mail server information page to specify the Simple Mail Transfer
Protocol (SMTP) mail server that you want to use for Project Server notifications and
reminders.
The Enter SMTP mail server information page.
X To enter SMTP mail server information

1. In the SMTP mail server box, type the server name or IP address of the mail server
that you want to use with Project Server 2003.
2. In the Port box, type the port for the mail server.
3. In the From address box, type the e-mail address that you want to appear in the From
field of e-mail messages sent by Project Server 2003.
It is recommended that you enter this information when you install Project Server 2003. If
you choose the Enter this information later option, you need to enter this information
after Project Server Setup completes. For more information, see the topic Configuring
SMTP Mail Server Settings in Chapter 8, Post-Installation Tasks of the Microsoft Office
Connect to a Web Server Running Windows SharePoint Services

Use the Connect to a Web server running Microsoft Windows SharePoint Services
page to specify the connection information for your Windows SharePoint Services
deployment. This information was displayed when you completed the Windows SharePoint
Services Configuration Wizard.
The Connect to a Web server running Microsoft Windows SharePoint Services page.
X To connect to a server running Windows SharePoint Services

1. Under Microsoft Windows SharePoint Services administration URL, select a
protocol from the drop-down list, and then type the computer name and port number
in the box.
2. Under Create sites under this Microsoft Windows SharePoint Services URL,
select a protocol from the drop-down list, and then type the URL for the Project
Server sites in the box.
3. Click Next.
Important If you use a fully qualified domain name (FQDN) for the Windows SharePoint Services
administration URL, you must use a FQDN for the Windows SharePoint Services URL as well.
It is recommended that you enter this information when you install Project Server 2003. If
you choose the Enter this information later option, you need to enter this information
after Project Server Setup completes. For more information, see the topic Configuring
Windows SharePoint Services Settings in Chapter 8, Post-Installation Tasks of the
Enter Windows SharePoint Services Account Information

Use the Enter account information for Microsoft Windows SharePoint Services
(continued) page to specify the Windows SharePoint Services administrator account.
The Enter account information for Microsoft Windows SharePoint Services (continued)
page.
Note This page appears when you are installing the Project Server Front-End service. This page will
not appear if you chose the Enter this information later option on the Connect to a Web server
running Microsoft Windows SharePoint Services page.
X To specify the Windows SharePoint Services administrator account

1. In the Logon name box, type the domain and user account of the Windows
SharePoint Services administrator. Use the account that you created for Windows
SharePoint Services in the topic Create User Accounts in Chapter 4, Prepare the
Connect to SharePoint Portal Server

Use the Connect to a Web server running Microsoft SharePoint Portal Server 2003
page to specify the connection information for Microsoft Office SharePoint Portal
Server 2003.
The Connect to a Web server running Microsoft SharePoint Portal Server 2003 page.
Note This page appears when you are installing the Project Server Front-End service. This page will
not appear if you chose the Enter this information later option on the Connect to a Web server
running Microsoft Windows SharePoint Services page.
X To connect to a server running SharePoint Portal Server

1. Under Web address for accessing Microsoft SharePoint Portal Server, choose a
protocol from the drop-down list, and type the URL of the SharePoint Portal Server in
the box.
2. In the Portal name box, type the portal name.
Important You must include a trailing slash (/) at the end of the Portal Server Web
address. For example, portalserver/myportal/. The Portal Server Web address is not
validated by Project Server Setup.
3. Click Next.
If you will be using SharePoint Portal Server as part of your deployment, it is
recommended that you enter this information when you install Project Server 2003. If you
choose the Enter this information later option, you need to enter this information after
Project Server Setup completes. For more information, see the topic Configuring
SharePoint Portal Server Settings in Chapter 8, Post-Installation Tasks of the Microsoft
Choose an Installation Environment

Use the Choose an installation environment page to specify whether to configure
Project Server 2003 in Enterprise or Non-enterprise mode.
The Choose an installation environment page.
X To select an installation environment

• Select the Enterprise or Non-enterprise option, and then click Next.
Enter the Administrator Password

Use the Enter the Administrator password page to specify the password used to access
the Project Web Access administrator account. Remember the password that you choose;
you will need it to log on to Project Web Access by using the administrator account.
The Enter the Administrator password page.
X To specify the Administrator password

1. In the Password box, type the password that you want to use.
2. In the Confirm password box, retype the password.
3. Click Next.
Complete the Installation

The Summary page is the last page displayed by the Setup Wizard before Setup begins
installing Project Server 2003 on your server.
The Summary page.
X To change a setting that you entered previously

• Click Back.
X To start the installation
• Click Install.
8
Post-Installation Tasks
After you finish running Microsoft® Office Project Server 2003 Setup, follow the
procedures in this chapter to complete your Project Server 2003 deployment.
Configure Items Bypassed During Setup

If you chose the Enter this information later option for any Microsoft Office Project
Server 2003 setup options, use the following procedures to configure these options after
Project Server Setup finishes.
Configuring Analysis Services Settings

If you did not enter Analysis Services connection information when you ran Project Server
Setup, you will need to configure the COM+ settings with the user name and password for
the Analysis Services administrator and configure the Analysis Services settings in
Microsoft Office Project Web Access 2003. You will also need to verify your Internet
Explorer security settings if the Microsoft ActiveX® controls for Project Web Access do
not download and install when you use Project Web Access to connect to the computer
running Project Server 2003.
Note Follow the steps in the topic Create an OLAP Administrator in Chapter 4, Prepare the Servers
of the Microsoft Office Project Server 2003 Installation Guide if you have not already done so.
Configure the COM+ settings on the following computers:

• The computer running the Front-End service.
• The computer running the View Processing service if you installed it on a computer
other than the computer on which you installed the Front-End service.
X To configure COM+ settings

1. Start the Project Server COM+ Settings tool (PSCOMPlus.exe). You can find this tool
in the BIN\1033 folder of your Project Server installation.
Note For information about running the PSCOMPlus.exe tool, see the topic Project Server
COM+ Settings Tool in Appendix C, Project Server Installation Tools of the Microsoft Office
2. Under Analysis Services (OLAP) Access Identity:

a. Select the Process this identity update check box.
b. In the Username box, type the user name for the account that you are using as
the Analysis Services administrator.
c. In the Password box, type the password for the account.
3. Under Windows SharePoint Services Administration Identity, clear the Process

this identity update check box.
4. Click Create/Update COM+ Apps.
X To configure Project Web Access Analysis Service settings
Notes
Before configuring these settings, migrate the Analysis Services repository to a SQL Server
database. For more information about migrating the Analysis Services repository, see the
topic Migrate the Analysis Services Repository to a SQL Server Database in Chapter 8, Post-
You must publish a project to the Project Server database before building the OLAP cube in
order to see data in the cube.
1. Log on to Project Web Access as an administrator.

To view the Project Web Access logon page, open Internet Explorer and point to
http://servername/projectserver, where servername is the name of the computer running
2. Click the Admin tab.
3. In the right pane, click Manage enterprise features.
4. Under Build the OLAP cube, select the Yes, I want to update resource
availability information and build an OLAP cube option.
5. In the Analysis Server box, type the name of the computer running Analysis Services.
6. In the Cube Name box, type the name for the OLAP cube you want to build.
7. Click Save Changes.

Note If the Yes, I want to update resource availability information and build an OLAP cube
option is selected, the OLAP cube will be built when you click Save Changes.
Downloading ActiveX Controls

ActiveX controls for Project Web Access are installed by default when you connect to
Project Server 2003. If ActiveX controls cannot be installed, verify that the Internet
Explorer security settings are configured correctly.
X To verify Internet Explorer security settings
1. On the Internet Explorer main menu, click Tools, and then select Internet Options.
2. In the Security tab, select Trusted Sites and then click Custom Level.
3. Verify that the following setting are properly configured:
• Download signed ActiveX controls Set to Prompt or Enable.
• Run ActiveX controls and plugins Set to Prompt, Enable, or Administrator
Approval.
• Script ActiveX controls marked safe for scripting Set to Prompt or Enable.
• Access data sources across domains Set to Prompt or Enable.
4. Click OK.
Note You can install Project Web Access ActiveX controls on client workstations manually
in cases where your organization operates in a locked-down environment in which users
cannot install OCX controls. For more information about manually installing Project Web
Access ActiveX controls, see Appendix H, Installing Project Web Access ActiveX Controls, in
Configuring Web Server Address Settings

When you enter Web server address information during Project Server Setup, the Setup
program modifies the Pds.wsdl file to enable communication with the Project Data Service
and configures the hyperlink to be sent out in Project Server e-mail notifications. If you do
not enter Web server information during Project Server Setup, you need to edit the
Pds.wsdl file manually and configure Web server address settings in Project Web Access.
X To update pds.wsdl
1. On the computer running the Project Server Front-End service, using Notepad, edit
install path\IIS Virtual Root\Pds.wsdl.
2. Replace servername with the name of the server running Project Server 2003 in the
following line:
<soap:address
location="http://servername/ProjectServer/PDS.WSDL"/>
3. Save the file and close Notepad.

X To configure Project Web Access settings

3. In the side pane, click Server Configuration.
4. Under Enter the intranet and/or extranet addresses of Project Server, type the
server Intranet and Extranet addresses that you want Project Server 2003 to display in
e-mail notifications and reminders.
Configuring Windows SharePoint Services Settings

If you have installed Microsoft Windows® SharePoint® Services for use with Project
Server 2003, and if you did not enter Windows SharePoint Services connection information
when you ran Project Server Setup, you must configure the COM+ settings with the user
name and password for the Windows SharePoint administrator and configure the Windows
SharePoint Services settings in Project Web Access.
X To configure COM+ settings
1. On the computer running the Project Server Front-End service, start the Project
Server COM+ Settings tool (PSCOMPlus.exe). You can find this tool in the BIN\1033
folder of your Project Server installation.
Note For information about running the PSCOMPlus.exe tool, see the topic Project Server
COM+ Settings Tool in Appendix C, Project Server Installation Tools of the Microsoft Office
2. Under Windows SharePoint Services Administration Identity, do the following:

b. In the Username box, type the user name for the account that you are using as
the Analysis Services administrator.
c. In the Password box, type the password for the account.
3. Under Analysis Services (OLAP) Access Identity, clear the Process this identity
update check box.
4. Click Create/Update COM+ Apps.
3. In the side pane, click Manage Windows SharePoint Services.
4. In the SharePoint Central Administration URL box, type the URL for the
SharePoint Central Administration page, including the port number.
5. In the Create a site under this SharePoint URL box, type the URL for the Project
Server 2003 site on the computer running Windows SharePoint Services.
Configuring SharePoint Portal Server Settings

If you are using Microsoft Office SharePoint Portal Server 2003 as part of your Project
Server deployment and you did not enter SharePoint Portal Server connection information
when you ran Project Server Setup, you can specify that information in Project Web
Access.

3. In the side pane, click Manage Windows SharePoint Services.
4. In the side pane, under Options, click Connect to SharePoint Portal Server.
5. Select the Connect to a portal site option and type the Portal Web Address (for
example, http://PortalServerName/portal/) and Portal Name.
Important When you enter the Portal Web Address, be sure to include a slash character (/)
at the end. If the slash is not included, the Portal Web Address property will be set
incorrectly and Windows SharePoint Services might not be able to connect to the
SharePoint Portal Server.
Configuring SMTP Mail Server Settings

If you want to use an SMTP mail server for reminders and notifications as part of your
Project Server deployment and you did not enter SMTP Mail Server connection
information when you ran Project Server Setup, you can specify SMTP Mail Server
connection information in Project Web Access.
3. In the side pane, click Customize Project Web Access.
4. In the side pane, under Customization options, click Notifications and reminders.
5. In the SMTP mail server box, type the name of your SMTP server. Verify the port
number in the Port box.
6. In the From address box, type the default e-mail address. This address is the reply-to
address for all notification and reminder e-mails.
7. In the Company e-mail address box, type the host and domain portion of your
organization’s default e-mail address. The company e-mail address is appended to user
e-mail addresses where a host and domain are not specified.
8. Optionally, in the Default e-mail message box, type the default message that you
want to be appended to all notification e-mails.
Synchronize the Public Document Site

If you have installed Windows SharePoint Services for use with Project Server 2003, you
must synchronize the public document site after Project Server 2003 is installed. When you
install Project Server 2003, the Setup program is not able to set the site properties on the
Windows SharePoint Services public documents site.
X To synchronize the public document site
3. On the side pane, click Manage Windows SharePoint Services.
4. On the Connect to SharePoint server page, click Save Changes. This synchronizes
the public document site.
Migrate the Analysis Services Repository to a SQL Server

Database
Each server running Microsoft SQL Server™ 2000 Analysis Services has a repository to
store metadata for the objects of the computer running Analysis Services (for example,
cubes and dimensions). By default, this repository is a Microsoft Access (.mdb) database on
the server on which Analysis Services is installed. Migrate the repository to a Microsoft
SQL Server 2000 (.mdf) database to avoid permissions issues for users accessing the Access
database from another computer.
Notes
You can migrate the repository at any time after installing Analysis Services as long as SQL Server is
installed and a database for the repository exists.
The OLAP administrators group on the computer running SQL Server needs to be granted
DB_OWNER permission for the repository. To do this, add a user in the repository database to the
OLAP Administrators group, and then give that group DB_OWNER permissions on the repository
database. This ensures that any user in the OLAP Administrators group is granted the permissions
that are listed.
X To migrate the Analysis Services repository

1. In SQL Server, create a new database and name it Analysis Services Repository.
2. Under Security, right-click Logins and then click New Login.
3. For the name of the login, click ... and select the OLAP Administrators group for this
computer.
4. On the Database Access tab, select the Analysis Services Repository database.
5. Under Permit in Database Role, select db_owner.
6. Log on to the computer running Analysis Services by using a user account that has
permissions that are equivalent to either the Administrators group or OLAP
Administrators group, and start Analysis Manager.
7. In the left pane, expand Analysis Servers.
8. Right-click the name of your server, and then click Migrate Repository to start the
Migrate Repository Wizard. Migrate the repository to the database that you created.
Note It is recommended that you choose the Analysis Services native format when
migrating the repository.
9. After you migrate the repository to a SQL Server database, you can safely delete the
old repository. By default, this database is \Program Files\Microsoft Analysis
Services\Bin\msmdrep.mdb.
Add Users to Cube Database Roles in Analysis Services

SQL Server Analysis Services uses Windows authentication to control access to OLAP
cubes—for example, when using Portfolio Analyzer. By default, the OLAP cube database
created by Project Server 2003 has no database roles defined so that only users or groups
that are specifically added have access to the cubes.
Note This procedure cannot be performed until you build an OLAP cube database. To determine
the status of the cube database, open Project Web Access, and then click Admin in the top link bar
to go to the Admin Center. In the side pane, click Manage enterprise features, and then click
Update resource tables and OLAP cube. The status of the OLAP cube database is shown under
Current Cube Status.
X To add users to cube database roles

1. Log on to the Analysis Services computer by using a user account that has permissions
equivalent to either of the Administrators or OLAP Administrators groups, and start
Analysis Manager.
2. Expand the name of your server under Analysis Servers to see the cube databases on
that computer.
3. Right-click the name of the database (as shown in the Cube name box of the Update
Resource Tables and OLAP Cubes page in Project Web Access), and then click
Manage Roles.
4. Click New, and type a name for the new database role in the Role name box.
5. On the Membership tab, click Add to add users and groups to the role, and then click
OK.
6. On the Cubes tab, click Check All to enable access to all three cubes in the database.
7. Click OK to add the role.
Enable Users to Log on By Using a Different Windows User

Account
When Project Server 2003 attempts to use Windows authentication to authenticate a user,
the default assumption is that the user is using a computer with which he or she has already
logged on to the network using a Windows user account (Integrated Windows
authentication). However, this might not always be the case. For example, a user might
want to view Project Server information from someone else's computer or by using a
common computer that is shared by several people and from which the user has not logged
on with his or her Windows user account.
In this case, when the user goes to a Project Server site, the Logon page opens instead of
the Home page. The user must then click the Log on using a different Microsoft
Windows user account link on the left side of the page. After entering his or her
Windows user account information, the user is authenticated by means of Basic
authentication and is then directed to the Home page.
To enable users to use the Log on using a different Microsoft Windows user account
link on the Logon page, the administrator must perform the following steps on the
computer running Project Server 2003:
1. Enable Basic authentication for the Project Server virtual directory and for the Remote
Data Services ISAPI Library (msadcs.dll) by using the Microsoft Management Console
(MMC) snap-in for Internet Information Services (IIS).
2. Set up the Secure Sockets Layer (SSL) features of IIS for greater security.
For more information about SSL, see your IIS documentation.
For more information about the Windows administrative tools, see your Microsoft
Windows 2000 Server or Microsoft Windows Server™ 2003 documentation.
X To enable Basic authentication for the Project Server virtual directory
1. On the left pane of the Internet Information Services window, right-click the virtual
directory, and then click Properties.
2. Click the Directory Security tab and then click Edit in the Authentication Control
section.
3. Select the Basic authentication check box, and then click Yes when asked if you
want to continue.
4. Click OK to apply your changes, and then click OK to close the dialog box.
5. Click OK to close the Inheritance Overrides dialog box without making any changes.
X To enable Basic authentication for msadcs.dll
1. Select the MSADC virtual directory in the left pane of the Internet Information
Services window.
2. Right-click msadcs.dll in the right pane and then click Properties.
3. Click the Directory Security tab, and then click Edit in the Anonymous Access and
Authentication Control section.
4. Select the Basic authentication check box, and then click Yes when asked if you
want to continue.
5. Click OK to apply your changes, and then click OK to close the dialog box.
Configuring Project Professional for Project Server 2003

Project Professional is required in order for you to customize the Enterprise Resource Pool
and the Enterprise Global Template, and to publish enterprise projects to the Project
Server database. After you install Project Professional, you can enter the connection
information for Project Server 2003 in Project Professional by typing the URL for the
computer running Project Server 2003 and the user account information for the individual
who will be using this installation of Project Professional, and then connect to the server.
Note If you do not want to use the Administrator account to use Project Professional to connect to
the Project Server database, you must create a user account when you install Project Professional.
For more information about creating user accounts, see the topic Managing Users in Chapter 2,
Managing Users and Groups of the Microsoft Office Project Server 2003 Administrator’s Guide
(http://go.microsoft.com/fwlink/?LinkID=20236).
Deploy Project Professional

To deploy Project Professional to your users, you can create an administrative installation
point or copy the Microsoft Office 2003 CD to create a compressed installation image.
Users can run Setup from the administrative installation point or the compressed CD
image, or you can use other distribution tools that capture or reference the installation
source.
Note For information about deploying Project Professional in an enterprise environment, see the
Microsoft Office 2003 Editions Resource Kit (http://go.microsoft.com/fwlink/?LinkId=31582).
Using the Office Resource Kit

For larger rollouts of Microsoft Office Project Professional 2003, the Microsoft Office 2003
Editions Resource Kit provides detailed documentation about the various deployment
methods that are available. The Microsoft Office 2003 Editions Resource Kit provides
information about how to customize, deploy, and maintain Microsoft Office in your
organization and offers the technical information required for installing Office to a
networked user base.
The Microsoft Office 2003 Editions Resource Kit provides information about the following
deployment methods:
• Hard Disk Image A method that involves installing software on a test computer,
and then creating an image of the hard disk to copy to users' computers.
• Windows Installer Transform (MST file) A method that involves using the Office
Custom Installation Wizard to customize the Office configuration that is installed on
users' computers.
• Installation Scripts A method that involves creating and distributing a batch file that
runs the Setup program by means of your command-line options.
• Group Policy Software Installation Feature A tool included with Windows 2000
or later operating systems that enables you to install and maintain software applications
based on Group Policy along with Custom Installation Wizard and Office 2003 policy
template files (ADM files).
• Microsoft Systems Management Server (SMS) A software distribution tool
designed for medium- and large-sized organizations that manage large numbers of
clients in a complex and rapidly changing business environment.
Note For more information about these deployment methods, see the topic Installing Office 2003
in the Microsoft Office 2003 Resource Kit (http://go.microsoft.com/fwlink/?LinkId=31582).
Set Up Connection Information for Project Server 2003

In order for you to connect Project Professional to Project Server 2003, the user’s account
name and connection information must be entered in the Account Properties dialog box
in Project Professional. This information must specify a valid user name that can
authenticate to the computer running Project Server 2003 as well as specify the URL for
the computer running Project Server 2003.
X To set up connection information
1. In Project Professional, click Tools, point to Enterprise Options, and then select
Microsoft Office Project Server Accounts.
2. In the Project Server Accounts dialog box, click Add to open the Account
Properties dialog box.
3. In the Account Properties dialog box, enter the user account name, the URL for the
computer running Project Server 2003, and the type of user account, and indicate
whether this is the default account. If Use Windows user account is selected under
When connecting, Project Professional will authenticate by using the user’s
Windows NT user account.
4. Click Test Connection to verify that the URL for the computer running Project
Server 2003 enables you to connect to the server properly. When you are finished, click
OK twice to save the user account information.
5. Close and restart Project Professional.
Add Project Server and Windows SharePoint Services as Trusted

Sites in Internet Explorer
In order to access data stored in Project Server 2003 by using Project Web Access, the
Project Server and Windows SharePoint Services URLs must be listed as trusted sites in
Internet Explorer. The first time you connect to Project Server 2003 from Project
Professional, the Project Server Security Login dialog box will add the URL for Project
Server 2003 to the list of trusted sites when you click Make Server Trusted. If you are
using Windows SharePoint Services, you need to manually add the Windows SharePoint
Services URL as a trusted site.
X To manually add a trusted site in Internet Explorer
1. Open Microsoft Internet Explorer.
2. On the Tools menu, select Internet Options, and then click the Security tab.
3. Click Trusted Sites, and then click Sites.
4. Clear the Require Server Verification (https:) for all sites in this zone option.
5. In the Add This Web site to the zone box, enter the URL.
6. Click Add.
7. Click OK twice to exit the Internet Options menu.
Updating the MSP_WEB_ADMIN Table for Hosted

Deployments By Using Windows SharePoint Services
A hosted deployment is a large installation of Project Server 2003 that hosts Project Server
site collections for departments or divisions within the organization. The host can also be
an application service provider that hosts Project Server site collections for other
companies, similar to the way that an Internet service provider (ISP) hosts Web sites.
In a Project Server hosted deployment, a single installation of Project Server 2003 hosts
multiple instances of Project Web Access, each with its own SQL Server database.
Typically, in a hosted deployment, multiple Project Server sites share a single Windows
SharePoint Services content database. When this occurs, it is imperative to manually
configure a column in the MSP_WEB_ADMIN table of the Project database. In this table,
the WADMIN_IS_HOSTED_ORG column must be set to a value of 1 (default is 0).
Configuring this value to 1 in a hosted environment prevents groups within your
organization from accessing Windows SharePoint Services data from other groups.
9
Extranet and Non-Trusted Domain
Scenarios
This chapter provides information about implementing a Microsoft® Office Project
Server 2003 extranet and about configuring your deployment for a non-trusted domain.
Configuring Project Server 2003 for the Extranet

You can provide connectivity to Project Server 2003 by means of the Internet by deploying
an additional Project Server installation outside your firewall. In this scenario, authorized
non-domain users and users from other domains can access Project Server 2003 over the
Internet or through a virtual private network.
After you install Project Server 2003, you can implement a Project Server extranet to
expand your deployment to include extranet access.
For the Web site that is hosting the external-facing Project Server virtual directory, it is
recommended that you use Secure Sockets Layer (SSL). The Web site should also have
anonymous access and Integrated Windows® authentication enabled.
Set up Analysis Services to Be Accessible By Means of

HTTP
Project Server 2003 uses Microsoft Office Web Components to bind directly to the server
running Analysis Services. In order for this to work over the extranet, you must configure it
correctly. For information about configuring Analysis Services to be accessible over the
Internet, see Knowledge Base article 279489: “How to Connect to Analysis Server 2000 By
Using HTTP Connection” on the Microsoft Web site

Note You must be running SQL Server 2000 Enterprise Edition in order to enable Portfolio
Analyzer to be available over the Internet. Internet Information Services (IIS) must also be installed
on the Analysis Services server.
X To set up the server running Analysis Services for HTTP

1. On the server running Analysis Services, copy the file Msolap.asp from Program
Files\Microsoft Analysis Services\Bin to either Inetpub\Wwwroot or to a subfolder
under wwwroot.
2. To ensure that Msolap.asp is installed and working properly, in the Address bar in
Internet Explorer, type the following URL:
http://Analysis_Services_Server_Name/Msolap.asp
3. If everything is working properly, you will see a blank page instead of an error message
indicating that the page cannot be displayed.
Note This URL must be accessible by means of the Internet, or you will receive an error
message.
4. Set the new copy of Msolap.asp to use Basic authentication and Integrated Windows®
authentication by doing the following:
a. Open Internet Information Services (IIS) Manager.
b. Expand Web Sites and find the Web site on which you placed the copy of
Msolap.asp.
c. Right-click Msolap.asp and then click Properties.
d. Click the File Security tab and then make changes in the Anonymous Access
and Authentication Control dialog box.
e. Be sure that both the Basic authentication and Integrated Windows
authentication check boxes are selected.
Note It is strongly recommended that SSL be used on the server running Analysis
Services so that data is encrypted when it is sent between client and server. It is
particularly important that Microsoft Windows passwords are encrypted by means of
SSL.
5. Set up connection strings in the Portfolio Analyzer view. After the server running
Analysis Services is configured to be available over the Internet, you must complete the
following steps for all Portfolio Analyzer views that will be available over the Internet::
a. On a computer that is within the intranet, log on to Microsoft Office Project Web
Access 2003 as an administrator.
b. Click Admin.
c. On the Administration overview page, click Manage enterprise features.

d. In the OLAP cube name and description section, in the Analysis Server
extranet address box, type the extranet address for the server running Analysis
Services. This will be used later when a user tries to view a Portfolio Analyzer view
that is built on the intranet from the extranet. This enables the administrator to
create views that are accessible from the intranet as well as the extranet.
Optionally, you can create views that are accessible only by means of the extranet by
doing the following:
a. On the Administration overview page, click Manage views.
b. Click Add View.
c. Select the Portfolio Analyzer option.
d. In the Analysis Server box, type the extranet address for the analysis server, and
then click Apply to bind to the cube over the extranet.
When you save this view, it will be accessible only by means of the extranet.
When users try to access this extranet-enabled view from Microsoft Project or from the
Resource Center of Microsoft Project Web Access, they will be prompted to enter their
Windows user account name and password before they can see the view. Because the
Windows user account name and password are sent in plaintext, you should be sure to
configure Project Web Access to use SSL so that information will be sent encrypted.
Configure Your Deployment

To configure your Project Server deployment for extranet access, complete the following
procedure.
X To configure Project Server 2003 for the extranet
1. Install Project Server 2003.
Note For information about installing Project Server 2003, see Chapter 7, Install Project
Server 2003, in the Microsoft Office Project Server 2003 Installation Guide.
2. Set up the server running Analysis Services to be accessible by means of HTTP.

3. If you are using Microsoft Windows SharePoint® Services, deploy a second Windows
SharePoint Services installation outside your firewall. Connect to the content database
for your existing deployment. For more information, see the topic Installing
Windows SharePoint Services with an Existing Database in Chapter 5,
Configuring Windows SharePoint Services, of the Microsoft Office Project 2003
Installation Guide.
4. Deploy a second Project Server installation outside your firewall. When you run
Project Server Setup, choose to connect to an existing database on the Enter
Database Server Information page. For more information, see the topic Choosing
Database Options in Chapter 7, Install Project Server 2003, of the Microsoft Office
Project 2003 Installation Guide.
5. On the Project Server installation that is located outside your firewall, add the
following registry key under HKLM\Software\Microsoft\Office\11.0\MS
Project\Webclient Server\ProjectServer\Datasets\STS:
Name Type Data

IsExtranet REG_DWORD 1
6. On the Project Server installation that is located outside your firewall, add the
following registry keys under HKLM\Software\Microsoft\Office\11.0\MS
Project\Webclient Server\ProjectServer\Datasets\Application:
Name Type Data

ExtranetServerName REG_SZ Server name; for example,
example.com.
ExtranetServerProtocol REG_SZ Http or https.
ExtranetServerPort REG_SZ Extranet port number.
7. On the computer running Windows SharePoint Services, edit the web.config file in the
home directory of the Web site on which Windows SharePoint Services is installed
(C:\Inetpub\WWWRoot if Windows SharePoint Services is extended on the Default
Web Site) by doing the following:
a. Open Web.Config in Notepad.
b. Search for the Section called <appSettings>. It might or might not exist.
c. If it does not exist, search for </Sharepoint>. The next section is <system.web>
d. Just after </Sharepoint>, and just before <system.web>, add the following lines:
<appSettings>
<add key="PWANetwork" value="EXTRANET" />
</appSettings>
e.Save web.config.
f. Reset Internet Information Services.
8. In Project Web Access:
a. Click the Admin tab.
b.In the left pane, click Server configuration.

c. In the Server extranet address box, type the Internet address for the computer
running Project Server 2003 that you deployed outside the firewall.
d. Click Save Changes.
9. Deploy Terminal Server for use with Project Professional, if needed.
Configuring a Non-Trusted Domain Deployment

When you are working in a non-trusted domain or a workgroup or Novell environment,
you need to enable Anonymous Access to the Project Server virtual directory and to
msadcs.dll in the MSADC virtual directory.
Additionally, if you are using Windows authentication in your deployment, you need to do
the following:
• Create identical local Windows accounts that have identical passwords on the
computer running Project Server 2003 and on the computer running Project
Professional or Project Web Access. The Project Professional or Project Web Access
user will use this account to log on to the client workstation.
For example, if the user Peter J. Krebs wants to use Project Web Access on a
computer named client01 to access Project Server 2003 on a computer called server01,
create the account client01\PJKrebs on the computer client01 and the account
server01\PJKrebs on the computer server01. Give both accounts the same password.
The user Peter J. Krebs can then use the PJKrebs account to log on to the computer
client01 and can use Project Web Access to access Project Server 2003 on the
computer server01.
• If you are using Windows SharePoint Services, create identical local Windows accounts
that have identical passwords for the Windows SharePoint Services administrator on
the computer running Project Server 2003 and on the computer running Windows
• If you are using Analysis Services, create identical local Windows accounts that have
identical passwords for the Analysis Services administrator on the computer running
Project Server 2003 and on the computer running Analysis Services.
Note In a Novell environment, Project Server 2003 does not support the synchronization of users
with the Novell Directory Service (NDS). Project Server 2003 can only synchronize users with Active
Directory® directory service.
X To create a local user account

1. On the computer on which you want to create the account, open Computer
Management.
2. Expand Local Users and Groups.

3. Right-click Users and click New User.
4. In the User name box, type a name for the user.
5. In the Description box, type a description for the user account.
6. In the Password and Confirm password boxes, type the user's password.
8. Click Create.
X To allow anonymous access to the Project Server virtual directory
1. On the computer running Project Server 2003, open Internet Information Services
(IIS) Manager.
2. Expand the local computer node, and then expand Web Sites.
3. Expand the Web site on which you installed Project Server 2003.
4. Right-click the ProjectServer directory, and then click Properties.
5. On the Directory Security tab, click Edit.
6. Select the Enable Anonymous Access check box, and then click OK twice.
X To allow anonymous access to msadcs.dll

1. On the computer running Project Server 2003, open Internet Information Services
(IIS) Manager.
2. Expand the local computer node, and then expand Web Sites.
3. Expand the Web site on which you installed Project Server 2003, and click the
MSADC directory.
4. In the right pane, right-click msadcs.dll, and then click Properties.
5. On the File Security tab, click Edit.
6. Select the Enable Anonymous Access check box, and then click OK twice.
10
System Optimization
This chapter describes how to optimize system performance for your Microsoft® Office
Project Server 2003 deployment by modifying your database configuration. You can do this
in two ways:
• By using the database optimization scripts to move your database and log file to a
random array of independent disks (RAID) for increased input and output (I/O)
performance and availability.
• By partitioning the database onto multiple computers running Microsoft SQL Server™
to provide better network performance for the database.
• Your organization should make the decision to optimize Project Server 2003 carefully
because the benefits are specific to certain types of configuration and deployment
scenarios. In general, only a small percentage of overall Project Server 2003 customers
should use either of these approaches.
Database Optimization Scripts

Microsoft SQL Server 2000 provides for database performance optimization by means of
data and log file placement at a detailed level. The data centers at most medium and large
organizations apply a standard data and log file definition and placement that are different
from the default data and log file placement for SQL Server. For example, it is common to
locate data files on a four-disk RAID10 array and log files on a two-disk mirrored RAID1
drive that are separate from the drive on which the operating system is installed. In most
cases, this configuration provides significant I/O improvement over the default data and
log file placement for SQL Server.
Many data centers isolate data from indexes, optimizing I/O even further. Microsoft Office
Project Server 2003 provides Transact-SQL scripts that enable a database administrator to
optimize the physical database layout as usage rates and data sizes grow after the initial
deployment. These scripts can be found in the file DDBSPS.SQL on the Project
Server 2003 CD.
Master Stored Procedures

Project Server 2003 provides four master stored procedures (each of which calls
component utility stored procedures) to enable database administrators to more easily
optimize Project Server database performance by changing the physical layout of the
database.
MSP_UTIL_EXEC_MOVE_DATABASE_OBJECTS
This master stored procedure can be used to move all of the database objects from the
default SQL Server file group to a new file group. This is the most basic optimization of
the four scripts, which moves the database objects created in the SQL Server default file
group to a new file group. The new file group must be created in advance. You can create
the new file group by using the MSP_UTIL_ADD_FILEGROUP_AND_DATAFILES
stored procedure provided in this script file.
This master stored procedure calls the following component utility stored procedures:
• MSP_UTIL_ADD_CLUSTERED_IDENTITY_TO_BLOBS
• MSP_UTIL_MOVE_CLUSTERED_INDEXES
• MSP_UTIL_MOVE_NONCLUSTERED_INDEXES
• MSP_UTIL_DROP_TEMP_CLUSTERED_IDENTITY
MSP_UTIL_EXEC_MOVE_DATABASE_FILES
This stored procedure moves the default (or current) data file and log file to a new location
(for example, it can move .mdf and .ldf files from drive C to drives D and E, respectively).
The new data and log files do not need to be created ahead of time. If the database has
more than one data or log file, the stored procedure can be edited accordingly.
This stored procedure is self-contained and calls no component utility stored procedures.
MSP_UTIL_EXEC_MOVE_TABLES_TO_FILEGROUP
This stored procedure moves tables from the default (or current) file group to a new file
group. You must create the file group ahead of time. You can choose to move all tables in
the database, or you can move tables of a particular type. The types of tables include:
• MSP_PROJ_n (Microsoft Office Project tables)
• MSP_PROJ_WEB_n (Microsoft Office Project Web Access online transaction
tables)
• MSP_VIEW_n (Project Web Access View tables)

• MSP_CUBE_n (Microsoft Office Project Server OLAP staging tables)
The new file group must be created ahead of time. You can create the new file group by
using the stored procedure MSP_UTIL_ADD_FILEGROUP_AND_DATAFILES
provided in the script file. If you want to move an explicit list of tables, the associated
component utility stored procedures must be updated. The master stored procedure calls
the following component utility stored procedures:
• MSP_UTIL_ADD_CLUSTERED_IDENTITY_TO_BLOBS
• MSP_UTIL_MOVE_CLUSTERED_INDEXES
• MSP_UTIL_DROP_TEMP_CLUSTERED_IDENTITY
MSP_UTIL_EXEC_MOVE_INDEXES_TO_FILEGROUP
This stored procedure moves non-clustered indexes from the default (or current) file group
to a new file group. The file group must be created ahead of time. You can move all non-
clustered indexes in the database, or indexes of a particular type. The types include:
• MSP_PROJ_n (Microsoft Office Project tables)
• MSP_PROJ_WEB_n (Project Web Access online transaction tables)
• MSP_VIEW_n (Project Web Access View tables)
• MSP_CUBE_n (Microsoft Office Project Server OLAP staging tables)
You can create the new file group by using the
MSP_UTIL_ADD_FILEGROUP_AND_DATAFILES stored procedure provided in
this script file. If you want to move an explicit list of indexes, the associated component
utility stored procedures must be updated. This stored procedure calls the following
component utility stored procedures:
• MSP_UTIL_MOVE_NONCLUSTERED_INDEXES
Component Utility Stored Procedures

The following component utility stored procedures are called by the master stored
procedures:
• MSP_UTIL_ADD_FILEGROUP_AND_DATAFILES is not called by any of the
master stored procedures, but can be used to create file groups for those master stored
procedures that require that a new file group be created ahead of time.
• MSP_UTIL_CREATE_CLUSTERED_IDENTITY ensures that a specified table
has an identify column (or creates a temporary one if necessary) and creates a clustered
index on that identity column.
• MSP_UTIL_ADD_CLUSTERED_IDENTITY_TO_BLOBS locates all (or
specific category) blobs (tables without a clustered index) and calls
MSP_UTIL_CREATE_CLUSTERED_IDENTITY to add a temporary identity

column (if necessary) and clustered index.
• MSP_UTIL_DROP_TEMP_CLUSTERED_IDENTITY drops the temporary
identity column and its clustered index on all tables previously created by using
MSP_UTIL_ADD_CLUSTERED_IDENTITY_TO_BLOBS.
• MSP_UTIL_MOVE_CLUSTERED_INDEXES moves all tables (or specified
category) that have clustered indexes to the specified file group.
• MSP_UTIL_MOVE_NONCLUSTERED_INDEXES moves all non-clustered
indexes (or specified category) that have clustered indexes to the specified file group.
• MSP_UTIL_REBUILD_INDEX rebuilds a specified index on a table.
Database Partitioning
As the number of users who access the computer running Project Server 2003 increases,
performance can degrade. During the Project Server Setup process, you can choose to use
a different instance of SQL Server for the View tables than you use for the rest of the
database. You can also manually partition databases after installation to create two- and
three-way partitions. When the database is partitioned, additional SQL views are created in
each database to enable access to the tables that are located in the other servers. Separate
registry keys are created that include the connection information for each server.
Database partitioning for Project Server 2003 improves the performance of open, save, and
publish operations. It is important to note, however, that a partitioned database
configuration is beneficial for only a small percentage of Project Server deployments, and
can negatively impact some aspects of the performance of a Project Server deployment..
Before using database partitioning, explore ways to improve the performance of SQL
Server 2000. Most organizations can find ways to improve the performance of their system
without partitioning the database.
Before applying a partitioned database configuration to your Project Server deployment,
consider the following:
• Partitioning the database does not improve the overall performance of the Project
Server database. A partitioned database configuration is beneficial for the following
types of Project Server deployments:
• Deployments that include several thousand Project Web Access users and with a
high ratio of project managers to team members (Project Web Access users).
• Deployments for which projects require frequent updates, and the average project
contains a large number of tasks and assignments.
• Deployments in which the open, save, and publish operations are used at a high
frequency throughout the day.
• A partitioned database configuration includes the following possible disadvantages:

• Increased administrative overhead required for the maintenance of the computer
running Project Server 2003, including a proportional increase of backup and
restore procedures and a greater number of servers that need to be maintained in a
failover scenario.
• Increased sensitivity to server downtime; organizations are required to maintain
more servers for a single installation of Project Server 2003.
• Slower performance of certain types of Project Web Access views, including the
Resource Center (potentially a significant decrease in performance), Timesheets,
and the Project Center. These views require the retrieval of large amounts of data
across all partitioned databases. Do not partition the Project Server database if
your organization must use the Resource Center frequently; for example, if your
organization includes several thousand users and is planning to use the Timesheets
feature in Project Web Access to track and record actual work against project
tasks.
Preparing to Partition the Database

To partition the database, you must run the partition scripts with a SQL Server login that is
a member of the Systems Administrator role on each instance of SQL Server in your
deployment. When you create this account, it will require the same password on each
server. It is recommended that you delete these logins when you are finish partitioning the
database. It is also possible to use the SQL Server sa account, as long as the password is the
same on each server. The sa account cannot be deleted.
Important
SQL Server uses the Microsoft Distributed Transaction Coordinator (MSDTC) automatically with
Project Server database partitioning. Be sure MSDTC is installed on each computer running SQL
Server in your deployment. If you are also running SQL Server in a cluster, some database
transactions will fail unless you use ComClust.exe to configure the cluster. Using this tool routes all
MSDTC requests to the computer in the cluster that is running MSDTC for the cluster. For
information about using ComClust.exe to configure the cluster, see the Microsoft Web site
(http://go.microsoft.com/fwlink/?LinkId=19684). If MSDTC is not installed on your computer, you
can install it from the SQL Server 2000 CD.
By default, the network access settings of MSDTC are disabled on new installations of SQL
Server 2000 on computers running Microsoft Windows Server™ 2003. If you are partitioning on a
computer running Windows Server 2003, follow the procedure in Microsoft Knowledge Base article
329332 (http://go.microsoft.com/fwlink/?LinkId=19685) to be sure that your MSDTC settings are
correct. After you complete the procedure, restart your computer.
Migrating Existing Deployments

Use the procedures in this topic to set up database partitioning after you install Project
Server 2003.
The files required for the procedures in this topic can be found on the Project Server 2003
CD in the Support/Database folder. It is recommended that you copy this folder to each
of the database computers in your deployment.
Important An updated version of the file Migrate.sql is available. Download the latest copy of the
Migrate.sql file from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=22648). Use
the updated version of Migrate.sql instead of the version in the Support/Database folder on the
Project Server 2003 CD.
You can partition your database in one of the following ways:

• By partitioning the View tables.
• By partitioning the Project tables.
• By using three-way partitioning to move both the Project tables and the View tables to
separate database servers.
• By migrating from View tables partition to a three-way partition, if you have already
partitioned the View tables and you want to move to a three-way partition.
• By migrating from a Project tables partition to three-way partition, if you have already
partitioned the Project tables and you want to move to a three-way partition.
Important These procedures should only be used by someone who is familiar with SQL
Server 2000 and experienced with database creation, security, and editing and executing scripts
across a multi-server environment. All steps in these procedures must be performed in the order
listed. Always create full database backups before attempting any database partitioning.
Partitioning the View Tables

If your deployment is configured with all the Project Server database tables in one
database, you can move the Project Server View tables to a separate database server. The
databases are configured as follows:
• Main database server Contains the Web tables, Cube tables, Project tables, and
Security views.
• View database server Contains the View tables.
Important Always create full database backups before attempting any database partitioning.

View tables (for example, ProjectServerVIEW).
PSRoles.sql from within the View Tables database context.
same on both your Main database server and your View tables database server.

ViewTbls.sql from within the View Tables database context.
Migrate.sql, from within the Project Server Main database context.
This creates several stored procedures that are needed for the data migration.
Server'
For example:
following command:
EXEC MigrateViewTablesSP <MainDatabaseServerName>,
<MainDatabaseName>, <MainDatabaseServer Account Login Name>,
<MainDatabaseServer Account Password>,
<ViewTablesDatabaseServerName>, <ViewTablesDatabaseName>,
<ViewTablesDatabaseServer Account Login Name>,
<ViewTablesDatabaseServer Account Password>, <Local File Path to
Temporarily Hold BCP Files>
For example:
EXEC MigrateViewTablesSP PSMain, ProjectServer, MyAccount, hello,
PSView, ProjectServerVIEW, MyAccount, hello, c:\temp
LnkView.sql, from within the Project Server database context.
5. Verify that the View tables were successfully created and populated on the new View
Table database server.
6. On the Main database server, using SQL Server Query Analyzer and connected with
your login account, execute the ExecLinkedViewsSP stored procedure as follows:
For example:
EXEC ExecLinkedViewsSP PSView, ProjectServerVIEW.
The local View table will no longer be used and database views pointing to the View
table on the new View Table database server will be created.
Installation Guide.
2. Select the Partitioned database configuration option, and then select the Standard
2-Way Deployment option.
5. In the Database box, type the name of the Project Server View database that you
created on that server.

Partitioning the Project Tables

If your deployment is configured with all Project Server database tables in one database,
you can deploy the Project Server 2003 database tables that are used by Project
Professional on a separate database server. This configures the databases as follows:
• Server running the Main database Contains the Web tables, Cube tables, and View
tables.
• Server running the Project Tables database Contains the Project tables and
Security views.

Project tables (for example, ProjectServerPROJ).
PSROLES.SQL from within the Project Server database context.

following scripts in the listed order from within the Project Server database context:
a. ProjTbls.sql
b. ProjSPS.sql
c. SecViews.sql
PjcrtSP1.sql.
Important You must run this script with Osql or SQL Server Query Analyzer will not open
this script file because of the line length of the binary data in the last UPDATE command.
The Osql command must be in the following format and must be run from the command
line on the server. You can run this command-line tool from either database server.
osql –S <ProjectTablesDatabaseServerName> -d
<ProjectTablesDatabaseName> -U <Login> -P <Password> -i <Input
File>
For example:
PJCRTSP1.SQL

Migrate.sql, from within the Project Server database context.
This creates several stored procedures that are needed to facilitate the data migration.
Server'
For example:
following command:
EXEC MigrateProjTablesSP <MainDatabaseServerName>,
<ProjectTablesDatabaseServerName>, <ProjectTablesDatabaseName>,
<ProjectTablesDatabaseServer Account Login Name>,
<ProjectTablesDatabaseServer Account Password>, <Local File Path
to Temporarily Hold the BCP Files>
For example:
EXEC MigrateProjTablesSP PSMain, ProjectServerMAIN, MyAccount,
hello, PSProj, ProjectServerPROJ, MyAccount, hello, c:\temp
LnkProj.sql from within the Project Server database context.
5. Verify that the Project tables were successfully created and populated on the new
server running the Project Tables database.
6. On the server running the Main database, using SQL Server Query Analyzer and
connecting with your login account, execute the ExecLinkedViewsSP stored
procedure as follows:
For example:
This deletes the local Project tables and creates database views that point to the Project
tables on the new server that is running the Project Tables database.
DropSecV.sql from within the Project Server database context.
This deletes the local security views, which now exist in the Project Tables database.
8. Modify the PjcrtSP2.sql script and change the WinProjServerName and
name of the server running the Project Tables database and the name of the Project
Tables database, respectively.
9. Run the modified PjcrtSP2.sql from within the Project Server database context.

Installation Guide.
Deployment option.
that server.

Using Three-Way Partitioning

If your deployment is configured with all Project Server 2003 database tables in one
database, you can install the Web tables, Project tables, and View tables onto three different
database servers. The databases are configured as follows:
• Server running Main database Contains the Web tables and Cube tables.
• Server running Project Tables database Contains the Project tables and Security
views.
• Server running View Tables database Contains the View tables.


example, ProjectServerPROJ).
same on both the server running the Main database and the server running the Project
Tables database.

following scripts in the listed order from within the Project Server database context:
a. ProjTbls.sql
b. ProjSPS.sql
c. SecViews.sql
PjcrtSP1.sql.
File>
For example:

PJCRTSP1.SQL
X To configure the server running the View Tables database

1. Create a new Project Server database (for example, ProjectServerVIEW).
PSROLES.SQL from within the Project Server database context.
use SQL Server authentication and to select the View Tables database on the
same on both the server running the Main database and the server running the View Tables
database.

ViewTbls.sql from within the View Tables database context.
X To configure the server running the Main database
Migrate.sql from within the Project Server database context.
Server'
For example:

Server'
For example:
following command:
<Project Server Account Login Name>, <ProjectTablesDatabaseServer
Account Password>, <Local File Path to Temporarily Hold BCP
Files>
For example:
following command:
For example:
EXEC MigrateViewTablesSP PSMain, ProjectServerMAIN, MyAccount,
hello, PSView, ProjectServerVIEW, MyAccount, hello, c:\temp
6. Using SQL Server Query Analyzer and connected with your login account, run

For example:
LNKVIEWS.SQL, from within the Project Server database context.
10. Verify that the View tables were successfully created and populated on the new View
Server.
For example:
This will drop the local security views; these views now exist in the Project Tables
database.
13. Modify the PjcrtSP2.sql script and change the <WinProjServerName> and
<WinProjDatabaseName> parameters on the line where the
Installation Guide.
Deployment option.
4. In the SQL Server box, type the name of server running the View Tables database.
that server.


that server.
Migrating from View Tables Partition to Three-Way Partition

If you have configured your Project Server deployment with the main database and the
View Tables on different instances of SQL Server, you can further enhance performance
by migrating the Project tables to a third instance of SQL Server.
This configures the databases as follows:
• Server running the Main database Contains the Web tables and Cube tables.
• Server running the Project Tables database Contains the Project tables and
Security views.
• Server running the View Tables database Contains the View tables.
X To configure the server running the Project Tables database

1. In SQL Server Enterprise Manager, create a new Project Server database for the
Project tables (for example, ProjectServerPROJ).
same on both the server running the Main database and the server running the Project
Tables database.

following scripts from the Project Server database context:
a. ProjTbls.sql
b. ProjSPS.sql
c. SecViews.sql
PjcrtSP1.sql.
File>
For example:
PJCRTSP1.SQL
X To configure the server running the Main database

Server'
For example:
following command:
<ProjectTablesDatabaseServer Account Login Name>,
<ProjectTablesDatabaseServer Account Password>, <Local File Path
to Temporarily Hold BCP Files>
For example:

ExecLinkedViewsSP stored procedure as follows.
For example:
This will drop the local Project tables and create database views pointing to the Project
tables on the new Project Tables server.
This will drop the local security views; these views now exist in the Project Tables
database.
8. Modify thePjcrtSP2.sql script and change the WinProjServerName and
Installation Guide.
Deployment option.
that server.

Migrating from Project Tables Partition to Three-Way Partition

If you have configured your Project Server deployment with the main database and the
Project Tables on different instances of SQL Server, you can further enhance performance
by migrating the View Tables to a third instance of SQL Server.
This configures the databases as follows:
• Instance running the Main database Contains the Web tables and Cube tables.
• Instance running the Project Tables database Contains the Project tables and
Security views.
• Instance running the View Tables database Contains the View tables.

1. In SQL Server Enterprise Manager, create a new Project Server database for the View
tables (for example, ProjectServerVIEW).
same on both your Main database server and your Views Tables database server.

following scripts from the Project Server database context:
a. ViewTbls.sql
b. ViewSPS.sql

Server'
For example:
following command:
For example:
EXEC MigrateViewTablesSP PSMain, ProjectServerMAIN, MyAccount,

hello, PSView, ProjectServerVIEW, MyAccount, hello, c:\temp
LinkViews.sql from within the Project Server database context.
5. Verify that the View tables were successfully created and populated on the new Project
Tables server.
ExecLinkedViewsSP stored procedure as follows.
For example:

Installation Guide.
Deployment option.
5. In the Database box, type the name of the View Server database that you created on
that server.

Load Balancing the Project Server Views Notification Service

If users in your organization submit a high volume of requests to publish projects and
enterprise resources to the Microsoft® Office Project Server 2003 database, and you have
offloaded the Project Server Views Notification Service to a dedicated server, load
balancing the Project Server Views Notification Service can significantly improve the
performance of your publishing process. Project Server 2003 Service Pack 1 (SP1) supports
the load balancing of the Project Server Views Notification Service.
Note You must be running Project Server 2003 SP1 on all computers in your deployment before
you can take advantage of these performance improvements.
Load balancing the Project Server Views Notification Service improves the performance of
the publishing process for projects and resources. To test the performance results, 1146
projects were published to the computer running Project Server 2003 and 550 resources
were created and shared among the 1146 projects. The average project included 40
assignments.
The following table lists the publishing times for a single offloaded Project Server Views
Notification Service.
Number of Projects Publishing Time

10 30 seconds
100 601 seconds
500 3539 seconds
The following table lists the publishing times for two offloaded Project Server Views
Notification Services.

10 • Server 1, 25 seconds
• Server 2, 25 seconds


The following table lists the publishing times for three offloaded Project Server Views
Notification Services.


• Server 2, 1425 seconds,
With a single Project Server Views Notification Service running in the tested environment,
publishing 500 projects took 3539 seconds. With two services running, publishing 500
projects took 3517 seconds total, but when the load is split across two servers, the average
time to publish was 1758 seconds and the average savings was 1830 seconds. With three
services running, publishing 500 projects took 4194 seconds, but when the load is split
across three servers, the average time to publish was 1398 seconds and the average savings
was 2141 seconds.
Note While up to 1000 servers can be configured to support a load-balanced Project Server Views
Notification Service, performance testing indicates a rate of diminishing return on real performance
improvement.
Configuring the Computers Running the Project Server Views

Notification Service
Load-balancing the Project Server Views Notification Service involves the following steps:
• Using Project Server Setup to install the components required for load balancing the
Project Server Views Notification Service on the additional servers.
• Completing a few manual steps on the new servers (including disabling the Project
Server Scheduled Process Service).
• Updating the registry on the front-end application server or servers so that it is aware
of the new load-balanced configuration for the Project Server Views Notification
Service. Only the front-end application server needs to be aware of the load-balanced
configuration.
If you are running Analysis Services, you must also do the following on any server running
the offloaded Project Server Views Notification Service:
• Create the same OLAP administrator account that is used on other servers in your
deployment.
• Install Decision Support Objects (DSOs).
• Apply SQL Server 2000 Service Pack 3 (SP3).
• Disable the Project Server Scheduled Process Service on all but one of the servers
running the offloaded Project Server Views Notification Service. If you do not do this,
OLAP cube generation might fail and resource tables will not be updated.
X To deploy additional servers running the Project Server Views Notification Service
1. Install Project Server 2003 SP1 on all computers in your Project Server deployment.
2. On a new computer, using the same user accounts that are associated with any other
server running the Project Server Views Notification Service or Analysis Services in
your deployment, run Project Server Setup and install the Project Server Views
Notification Service (select the View Processing option from the Choose the
services you want to install on this server page).
Note Do not select the Project Server front-end and Session Manager options on this page.
Follow the steps listed in the topic Choosing the Services to Install in Chapter 7,
Install Project Server 2003, of the Microsoft Office Project Server 2003 Installation Guide
(http://go.microsoft.com/fwlink/?LinkID=20233) to complete these steps.
3. Install Project Server 2003 SP1 on the new computer.
4. Follow the steps listed in the topic Install Decision Support Objects in Chapter 4,
Prepare the Servers, of the Microsoft Office Project Server 2003 Installation Guide
(http://go.microsoft.com/fwlink/?LinkID=20233) to install the components required by the
OLAP cube building process that is shared by the Project Server Views Notification
Service.
5. Follow the steps listed in the topic Create an OLAP Administrator in Chapter 4,
Prepare the Servers, of the Microsoft Office Project Server 2003 Installation Guide
(http://go.microsoft.com/fwlink/?LinkID=20233) to create the OLAP administrator account
on the server that will be running a load-balanced configuration of the Project Server
Views Notification Service.
6. Stop and then disable the Project Server Scheduled Process Service on any additional
server after the first. You only need to run the Project Server Scheduled Process
Service on a single server in your deployment.
Configuring the Front-End Application Server to Support Load-

Balancing of the Project Server Views Notification Service
To complete the process of offloading the Project Server Views Notification Service, you
must edit the registry on the front-end application server or servers in your Project Server
deployment.
Note You must complete this procedure for all front-end application servers in your Project Server
deployment.
X To configure the front-end application server

1. On the front-end application server in your Project Server deployment, navigate to the
following registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\MS
Project\WebClient Server\ProjectServer\Datasets\ViewsFileDrop
2. Rename the ForwardUNC registry key to ForwardUNC000.

3. For each server running the Project Server Views Notification Service, add a sequential
registry entry, for example ForwardUNC001, ForwardUNC002, ForwardUNC003, and
so on, with the value being the directory path for the ViewDrop location on the server
running the Project Server Views Notification Service. If you skip a number in the
sequential order, it will be ignored and the Project Server front-end application server
will return to the ForwaredUNC000 entry. Additionally, each registry entry can only
represent a unique server running the Project Server Views Notification Service.
For example, in a configuration that supports four servers running the Project Server
Views Notification Service, the registry format is the following:
ForwardUNC000 = “\\serverName000\viewdrop”
4. Restart the front-end application server.

11
International Deployment
Considerations
Microsoft® Office Project Server 2003 supports the use of multiple languages by providing
a language plug-in called Multilingual User Interface (MUI) Pack. To add language support
after you install Project Server 2003, you can install the MUI Pack for the language that you
want to add. Although Project Server must be installed with a primary language (for
example, English or Japanese), the MUI Pack enables users of Microsoft Office Project
Web Access to interact with Project Server 2003 in any of eighteen different languages. The
same number of languages is also available to users of Microsoft Office Project
Professional 2003.
Project Server 2003 provides support for the deployment of an international Microsoft
Enterprise Project Management Solution in the following ways:
• The Project Server MUI Pack enables you to install, deploy, and use Project
Server 2003 in a mixed-language environment that can be tailored to the language
requirements of individual users or entire organizations. The MUI Pack enables users
to use Project Server 2003 in their native language.
• Project Server 2003 and Project Web Access support Unicode, as well as code page–
based information. This makes it easier to display information in a user's native
language when the user is using Project Web Access to work with project data. Project
Professional does not use Unicode, which can create some configuration limitations
for organizations that include users that do not speak the same language.
• Microsoft Windows® SharePoint® Services is available in the same set of languages
that Project Server 2003 supports. Windows SharePoint Services sites can be created in
any language that Project Server 2003 supports.
• Numbers, dates, and times are based on a user's regional settings, as determined by the
user's computer and Project Professional.
• Input Method Editor (IME) is a software tool that converts keystrokes to characters in
a language where characters represent words or syllables. Project Server 2003 supports
IMEs for Japanese, Korean, Simplified Chinese, and Traditional Chinese for use in
Project Web Access.
• Project Web Access supports surrogate pairs if Microsoft Windows XP Professional is
the operating system used by the client machine. If Microsoft Windows 2000 is the
operating system that the client machine uses, users might experience issues with the
display of surrogate extension-B characters.
Planning an International Deployment

With some planning, your organization can install, customize, and maintain a single
deployment of Project Server 2003 in a multi-language environment. Plug-in language
features enable users in foreign locales to continue working in their own languages.
Alternatively, you can deploy a localized version of Project Server 2003 for each language-
speaking area. You might install a Project Server MUI Pack instead of a unique, localized
version of Project Server 2003 in the following scenarios:
• When simulating a localized version of Project Server 2003 for a small group of users
who do not actually need a localized version of Project Server 2003.
• To make different language options available on the same computer for users who
need to change languages while using Project Server 2003.
Before installing Project Server 2003, determine which languages users in your organization
need to use, and then determine which primary language makes the most sense for your
deployment. For example, the Latin code page is a subset of the Japanese code page. If
your organization has users in Japan, England, and France, using Japanese as the primary
language will enable all users to interact with Project Server 2003 in their own languages,
with the exception of some French characters that are not supported by the Japanese code
page. Some combinations of languages are not possible; for example, Korean and Japanese
cannot be on the same server because one of the code pages is not a subset of the other.
Data stored in the Project Server database and the interaction between Project Server 2003,
Microsoft SQL Server™ 2000, Project Web Access, and Project Professional are based on
your choice of a primary language and the code pages that are associated with them. The
code pages for Project Server 2003, SQL Server 2000, and Project Professional must match
in order for users of Project Professional to connect to the Project Server database.
Installing Project Server Multilingual User Interface Packs

After you install Project Server 2003 (which sets your primary language), determine the
additional languages that your organization needs to make available to its users. Apply these
languages to Project Server 2003 by installing the appropriate MUI Pack. The MUI Packs
for Project Server 2003 are available from the Microsoft Download Center
(http://go.microsoft.com/fwlink/?LinkID=20897). Twenty-two languages are available. The MUI
Pack for Microsoft Office Project Professional 2003 is available through Microsoft
licensing programs. Some users will need to install the language upgrades for Microsoft
Internet Explorer in order to take advantage of the full multilingual capabilities of Project
Web Access.
If Project Server 2003 has more than one MUI Pack installed, users can choose the
language for their notification and reminder e-mails. This option is available in the
Subscribe to Notifications and Reminders page on the Project Web Access home page.
Note The data in an e-mail message remains in the language in which the message was originally
created.
The Project Server MUI Pack Setup program installs features that allow you to change the
language of the following:
• The user interface
• Help
• User interface fonts (Asian languages and Hebrew)
Project Web Access detects a user's Internet Explorer language setting. If the language
pack for that language is installed on Project Server 2003, Project Web Access displays the
user interface in that language. If you install a localized version of Project Server 2003, the
default language setting for Project Web Access is the same language. All localized versions
of Project Server 2003 contain an English version as well, so that you can change the
language settings to English. For example, if you want to view Project Web Access in
Korean, and the Korean MUI Pack is installed on Project Server 2003, you can view the
Project Web Access user interface in Korean. If Korean is unavailable, Project Web Access
displays the user interface in the Project Server installation language or in English.
Note If you want to input Asian language or Hebrew text into most areas of Project Web Access,
including status reports, the timesheet, notifications and reminders, and so on, you can use the
Input Method Editor.
MUI Packs for Project Server 2003 can only be installed on a computer on which Project
Server 2003 is already installed. MUI Packs are available for the following languages:
• Brazilian Portuguese (PSMUIPTB.exe)
• Chinese (Simplified) (PSMUICHS.exe)
• Chinese (Traditional) (PSMUITCH.exe)
• Czech (PSMUICSY.exe)
• Danish (PSMUIDAN.exe)
• Dutch (PSMUINLD.exe)
• Finnish (PSMUIFIN.exe)
• French (PSMUIFRA.exe)
• German (PSMUIGER.exe)
• Greek (PSMUIELL.exe)
• Hebrew (PSMUIHEB.exe)
• Hungarian (PSMUIHUN.exe)
• Italian (PSMUIITA.exe)
• Japanese (PSMUIJPN.exe)
• Korean (PSMUIKOR.exe)
• Norwegian (PSMUINOR.exe)
• Polish (PSMUIPLK.exe)
• Portuguese (PSMUIPTG.exe)
• Russian (PSMUIRUS.exe)
• Spanish (PSMUISPA.exe)
• Swedish (PSMUISWE.exe)
• Turkish (PSMUITRK.exe)
Project Server Installation Language

The installation language setting in the registry determines which language will be the
primary language when Project Server 2003 is installed. This language setting is the locale
ID (LCID) assigned to the value entry InstallLanguage, which Project Server Setup creates
in the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\MS
Project\WebClient Server\Languages
The DefLCID name/value pair indicates the default language for Project Web Access. The
default language is used whenever Internet Explorer is not set to a specific language. Any
installed languages will have an LCIDnnnn entry in the registry, where nnnn is the four-
digit language code (for example, 1033 for English or 1031 for German).
Note Users can only collaborate on documents and issues that are stored on a Windows
SharePoint Services site in the primary installation language for Project Server 2003, unless the
appropriate language packs for Windows SharePoint Services are applied.
Project Server Code Page Limitations

A code page (or character set) defines the numeric representation of characters for a given
set of languages. For example, the Western European languages use a common code page
(1252) and Central European languages (such as Czech and Polish) use a different common
code page (1250), while Japanese has its own code page (932). To use different language
versions of Project Professional with Project Server 2003, you must ensure that the code
page within the SQL Server 2000 collation, the code page of the computer running Project
Server 2003, and the code pages of all computers running Project Professional are identical.
If the Project Server database is partitioned, the collation of all partitions must be identical.
Note Project Professional reads and writes data to the Project Server database by using open
database connectivity (ODBC), and uses American National Standards Institute (ANSI) characters
when sending and receiving data. If the code page of Project Professional does not match the code
page of Project Server 2003, the connection will fail when users attempt to connect Project
Professional to Project Server 2003. Project Professional is not allowed to connect to Project
Server 2003 when the code pages do not match because characters will be translated incorrectly
or, if unrecognized, will be converted to the "?" character.
Using Windows SharePoint Services in an International

Deployment
Windows SharePoint Services must be installed in the same installation language in which
Project Server 2003 is installed in order for users to experience Documents, Issues, Risks,
and Windows SharePoint Services administrative tasks in the same language that Project
Server 2003 uses. You can make additional languages available for Windows SharePoint
Services by applying language packs. Both Project Server MUI Packs and Windows
SharePoint Services language packs must be applied for the same language to add support
for that language.
Because Windows SharePoint Services is installed as a separate application and connected
to Project Web Access, the user interface is restricted to a single language for each
Windows SharePoint Services site. Even if a user changes languages in Project Web Access,
each site remains in the language in which the site was originally created.
You can only create Windows SharePoint Services sites in the languages that are installed
with Project Server 2003. You can manage the language settings for new sites from the Site
template language drop-down list that is available on the Windows SharePoint Services
team Web site provisioning settings page in Project Web Access.
Note Windows SharePoint Services supports Unicode, so the actual data in the files stored within
the Documents and Issues areas can be in multiple languages.
Ensuring that Windows SharePoint Services URLs Are in Unicode

If your Web server uses the same code page that a client computer uses, you can use
double-byte characters in names, as long as you set up the Web server running Windows
SharePoint Services to send uniform resource locators (URLs) in Unicode. Ensuring that
Windows SharePoint Services sends and receives URLs in Unicode involves the following
two steps:
• Ensuring that URLs are always sent as UTF-8.
• Configuring the server running Windows SharePoint Services to receive requests for
URLs in Unicode.
X To ensure that URLs are always sent as UTF-8
1. Start Internet Explorer.
2. On the Tools menu, click Internet Options.
3. On the Advanced tab, click Browsing.
4. Ensure the Always send URLs as UTF-8 check box is selected.
5. Click OK.
X To configure the server running Windows SharePoint Services to be able to receive requests
for URLs in Unicode
1. Browse to the following registry folder:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\InetInfo\
Parameters
2. Set the following entries:
Type = REG_DWORD
Name = FavorDBCS
FavorDBCS = 0
Data = 0
Using Input Method Editor

Input Method Editor (IME) is a software tool that converts keystrokes to characters in a
language where characters represent words or syllables. Project Server 2003 supports IMEs
for Japanese, Korean, Simplified Chinese, and Traditional Chinese for use in Project Web
Access.
Choosing an Operating System for Project Web Access Users

Users run Project Web Access on client computers that are using Microsoft Internet
Explorer 5.5 or later. Project Web Access provides the best multilingual support if the
operating system of the computer on which it is installed supports the international
features of Project Server 2003. Microsoft Windows 98, Microsoft Windows Me, and
Microsoft Windows NT® 4.0 provide adequate support for most international languages
that are available for Project Web Access. If your organization requires support for Asian
or right-to-left languages, Microsoft Windows 2000, Microsoft Windows XP Professional,
or Microsoft Windows Server™ 2003 provide the best level of support for displaying
project data in Project Web Access.
Note Windows XP Home edition is not supported for use as a client operating system.
Viewing Project Web Access in Other Languages

Project Server 2003 supports the use of multiple languages as long as the appropriate MUI
Pack is installed on the computer running Project Server 2003 and the language is made
available in Internet Explorer on the client computer. Users of Project Web Access can
then change the language that is displayed in the user interface from the primary language
for Project Server 2003 and any language that is added by means of an MUI Pack.
Language support for Project Server 2003 is automatic upon installation of the MUI Pack.
Language support in Internet Explorer must be configured manually.
X To configure support for a language in Internet Explorer
1. Start Internet Explorer.
2. On the Tools menu, click Internet Options.
3. On the General tab, click Languages.
4. In the Language Preference dialog box, click Add to open the Add Languages
dialog box.
5. In the Add Languages dialog box, choose the language for which you want to add
support.
6. Click OK to close the Add Languages dialog box, click OK to close the Language
Preferences dialog box, and then click OK to close the Internet Options dialog box.
7. Restart Internet Explorer.
Appendices
A
Additional Resources
If you want to learn more about Microsoft® Office Project Server 2003, Microsoft Office
Project Web Access 2003, and Microsoft Office Project Professional 2003, or how to use
these three applications as part of your organization’s Microsoft Office Enterprise Project
Management (EPM) Solution, please refer to the following online books and Web sites.
Microsoft Office Project Server 2003 Online Books Series

• Microsoft Office Project Server 2003 Solution Planning Guide
• Microsoft Office Project Server 2003 Configuration Planning Guide
• Microsoft Office Project Server 2003 Disaster Recovery Guide
• Microsoft Office Project Server 2003 Installation Guide
• Microsoft Office Project Server 2003Small-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
• 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
Project Server–Related Web Sites

The following Web sites are also available:
• Microsoft Office Project Server 2003 Software Development Kit:
• Microsoft Office Online: http://www.office.microsoft.com
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.
mailto:projdocs@microsoft.com?subject=Feedback: Microsoft Office Project Server 2003 Installation
Guide
B
Project Server Service Accounts
A number of service accounts are required in order for Microsoft® Office Project
Server 2003 components to access one another. This appendix includes summary
information about the required accounts, their purpose, their characteristics, and how and
when they are used.
Analysis Services Account

The Analysis Services account is a Microsoft Windows® account that enables the
computer running Project Server 2003 to access Microsoft SQL Server™ 2000 Analysis
Services. The Analysis Services account has the following characteristics:
• It is either a domain or local user account.
• It must be added to the online analytical processing (OLAP) Administrators group on
the computers on which the account is located.
• It is located on the computer or computers on which SQL Server 2000 Analysis
Services or the Decision Support Objects (DSO) are located.
Note You do not need this account if you are not using Analysis Services with Project
Server 2003.
The account information for this account is used on the Enter Analysis Services
Information page during Project Server Setup. It is also used when you are creating an
OLAP Administrator.
If you are using a local user account for the Analysis Services account, you must create
identical accounts and passwords on the computer running Analysis Services, the computer
running the Project Server Front-End service, and the computer running the Project Server
View Processing service. If Analysis Services is not installed on the same computer on
which Project Server 2003 is installed, you must also add the Analysis Services account to
the OLAP Administrators user group on the computers on which the Project Server Front-
End service and the View Processing service are located.
Note The Decision Support Objects (DSO) must be installed on the computers on which the Project
Server Front-End service and the View Processing service are running. If they are not installed on
these computers, the OLAP Administrators group will not appear in Computer Management.
If during Project Server Setup you selected to add the Analysis Services information later,
you must update the account by using the Project Server COM+ Settings tool
(PSCOMPlus.exe).
Windows SharePoint Services Administrator Account

The Windows SharePoint Services Administrator account enables the computer running
Project Server 2003 to access Microsoft Windows SharePoint® Services. This account has
the following characteristics:
• It is either a Windows domain or local user account.
• It must be assigned to a user who is part of the Administrators group on the computer
that is running Windows SharePoint Services.
• It is located on the computer or computers on which Windows SharePoint Services
and the Project Server Front-End service are installed.
Note You do not need this account if you are not using Windows SharePoint Services with Project
Server 2003.
The account information for this account is used on the Enter Account Information for
Windows SharePoint Services page during Project Server Setup.
If you are using a local user account for the Windows SharePoint Services account, you
must create identical accounts with identical passwords on each computer running
Windows SharePoint Services as well as each computer running the Project Server Front-
End service. On computers running the Project Server Front-End service, run
PSCOMPlus.exe to enter the user name and password of the Windows SharePoint Services
Administrator.
If during Project Server Setup you selected to add the Windows SharePoint Services
information later, you will have to update the account by using PSCOMPlus.exe.
Project Server Database Account

The Project Server Database account is a SQL Server account that is used to create the
Project Server database. This account has the following characteristics:
• It can use either Windows or SQL Server authentication.

• It must belong to the Security Administrators and Database Creators roles.
• It is located on the computer or computers running SQL Server 2000 on which the
Project Server database is located.
The account information for this account is used on the Enter Database Server
Information page during Project Server Setup. If you select SQL Server authentication on
this page, you can use the SQL Server system administrator (sa) account.
Windows SharePoint Services Database Account

The Windows SharePoint Services Database account is used to create the Windows
SharePoint Services database in SQL Server. This account is required only for the
installation of Windows SharePoint Services. The Windows SharePoint Services Database
account has the following characteristics:
• It can use either Windows or SQL Server authentication. (Windows authentication is
recommended.)
• It must belong to the Security Administrators and Database Creators role.
• It is located on the computer running SQL Server on which the Windows SharePoint
Services database is located.
The account information for this account is used on the Set Configuration Database
Server page during Windows SharePoint Services Setup.
Project Server User Database Account

The Project Server User Database account is used by the computer running Project
Server 2003 to access the Project Server database. This account is created automatically
when a new Project Server database is created during Project Server 2003 Setup, but it can
also be created manually. When it is created automatically, the default logon name is
MSProjectServerUser. If this account already exists, the default logon name is
MSProjectServerUserXXXX (where XXXX is a random four-digit number).
You must enter a password for this account on the Create Database Account
Information page during Project Server Setup. If you are connecting to an existing
database, you also have the option to enter the logon name on this page.
If you create the account manually, you must configure the account in the SQL Server 2000
Enterprises Manager when you create the Project Server database.
The Project Server User Database account is located on the computer running SQL Server
on which the Project Server database is located.
Project User Database Account

The Project User Database account is used by Microsoft Office Project Professional 2003
to access the Project Server database. This account is created automatically when a new
Project Server database is created during Project Server Setup, but it can also be created
manually. When it is created automatically, the default logon name is MSProjectUser. If
this account already exists, the default logon name is MSProjectUserXXXX (where
XXXX is a random four-digit number).
You must enter a password for this account on the Create Database Account
Information page during Project Server Setup. If you are connecting to an existing
database, you also have the option to enter the logon name on this page.
If you create the account manually, you must configure the account in the SQL Server 2000
Enterprises Manager when you create the Project Server database.
This account is located on the computer running SQL Server on which the Project Server
database is located.
View Administrator Account

The View Administrator Account is used by the Project Server Front-End service to access
the View Staging shared folder if the View Processing service is located on another
computer. This account has the following characteristics:
• It is either a Windows domain or local user account.
• It must have read and change permissions to the View Staging shared folder.
• It is located on the computer running the View Processing service and the computer
running the Project Server Front-End service.
The account information for this account is used on the Enter the Views Processing
Server Information page (for both the Project Server Front-End service and the View
Processing service installations) during Project Server Setup. Project Server Setup assigns
the account the required permissions for the folder.
C
Project Server Installation Tools
This appendix describes tools that are available to the Microsoft® Office Project
Server 2003 administrator. These tools can be used during initial deployment and for day-
to-day operations following deployment.
Connection Information Tool

Microsoft Office Project Server 2003 stores information in the registry about the location
of the Project Server database and which accounts are associated with Project Server roles.
If you change your configuration by moving all or part of the database to a new computer,
you must update the information in the registry. Also, if you change which users are
members of the MSProjectRole or MSProjectServerRole roles, you must update this
information in the registry. Use the Connection Information tool (ConnInfo.exe) to update
this information.
X To use ConnInfo.exe for a single database
1. Start ConnInfo.exe. You can find this tool in the BIN\1033 folder of your Project
Server installation, or you can download it from the Microsoft Download Center
2. Select the Single database configuration option.
3. In the SQL Server box, type the name of the instance of Microsoft SQL Server™
2000 on which the Project Server database is located.
4. In the Database box, type the name of the Project Server database.
5. Under MSProjectServerRole Member:, type the user name and password for the
account that is a member of the MSProjectServer role in the Project Server database.
6. Under MSProjectRole Member:, type the user name and password for the account
that is a member of the MSProjectServer role in the Project Server database.
X To use ConnInfo.exe for a partitioned database
1. Start ConnInfo.exe. You can find this tool in the BIN\1033 folder of your Project
Server installation.
2. Select the Partitioned database configuration option.
3. If you have partitioned only the View tables, select the Standard 2-Way Deployment
option; otherwise, select the Custom Deployment option.
4. Select one of the following options for the database that you want to configure:
• Project Tables To configure the database that contains the Project tables and
Security views.
• View Tables To configure the database that contains the View tables.
• Web Tables To configure the database that contains the Microsoft Office
Project Web Access tables and Cube tables.
Note If you select the Standard 2-Way Deployment option, the Web Tables option is not
available.
5. In the SQL Server box, type the name or IP address of the instance of SQL Server on
which the Project Server database is located.
6. In the Database box, type the name of the Project Server database.
7. Under MSProjectServerRole Member, type the user name and password for the
account that is a member of the MSProjectServer role in the Project Server database.
8. Under MSProjectRole Member, type the user name and password for the account
that is a member of the MSProjectServer role in the Project Server database.
9. Repeat steps 4 through 8 for each database that you want to configure.
EditSite Tool
You can use the EditSite tool (EditSite.exe) to create a Project Server hosted deployment
and to edit the properties for existing hosted sites. A hosted deployment is a large
installation of Project Server 2003 that hosts Project Server site collections for departments
or divisions within the organization. The host can also be an application service provider
that hosts Project Server site collections for other companies, similar to the way that an
Internet service provider hosts Web sites.
In a Project Server hosted deployment, a single installation of Project Server 2003 hosts
multiple instances of Project Web Access, each with its own SQL Server database.
Typically, in a hosted deployment, multiple Project Server sites share a single Microsoft
Windows® SharePoint® Services content database.
When you install Project Server 2003, only one site is available (called ProjectServer),
accessible by means of the URL http://computername/projectserver. When you use
EditSite.exe to add a Project Server site, a new URL (http://computername/sitename) is
available from which you can access a new instance of Project Web Access.
X To install the Edit Site tool
1. Download and run the file EditSite.exe from the Microsoft Download Center:
http://go.microsoft.com/fwlink/?LinkId=20891.
2. Double-click the Setup file to complete the installation.
EditSite.exe is located in a folder called EditSite that is created in the directory in which
you installed the tool.
Note You must have .NET Framework version 1.1 installed on the computer on which you run
EditSite.exe.
To complete the following procedures, you must run EditSite.exe on the computer on
which Project Server 2003 is installed, and you must be an administrator on the computer
running Project Server 2003 and the computers running the Project Server Views
Notification Service and Windows SharePoint Services, if applicable.
The EditSite tool.

You can edit the site and database information for an existing Project Server site by clicking
that site in the Virtual Directory list box.
X To edit site information for a single database configuration
1. In the Virtual Directory list box, click the site.
2. In the Site Information area, update the DSN Name, Query Timeout, and Session
Manager settings.
3. In the Database Information area, select the Single database configuration option.
4. In the SQL Server box, type the name of the instance of SQL Server on which the
Project Server database is located for this site.
5. In the Database box, type the name of the Project Server database for this site.
6. Under MSProjectServer Role Member:, type the user name and password for the
account that is a member of the MSProjectServer role in the Project Server database
for this site.
7. Under MSProject Role Member:, type the user name and password for the account
that is a member of the MSProjectServer role in the Project Server database for this
site.
8. Click Save.
X To edit site information for a partitioned database configuration

1. In the Virtual Directory list, click the site.
2. In the Site Information area, update the DSN Name, Query Timeout, and Session
Manager settings.
3. In the Database Information area, select the Partitioned database configuration
option.
4. If you have partitioned only the View tables, select the 2 Way Deployment option;
otherwise, select the Custom option.
Security views.
Note If you select the 2 Way Deployment option, the Web Tables option is not available.
Project Server database for this site is located.
8. Under MSProjectServer Role Member, type the user name and password for the
for this site.
9. Under MSProject Role Member, type the user name and password for the account
site.
11. Click Save.
X To delete a site
1. In the Virtual Directory list, select the site that you want to delete.
2. Click Delete.
EditSite.exe deletes the virtual directory and the registry information associated with the
site. EditSite.exe does not delete the ODBC connection registry keys because that ODBC
connection might be used for other purposes.
X To add a new site
1. Create a database for the new site. For more information about creating a Project
Server database, see Chapter 6, Deploy the Database in the Microsoft Office Project
2. Run EditSite.exe.
3. Click Add. The Microsoft Office Project Server 2003 Site Editor – Add Site page is
displayed.
4. Enter the site, database, and Windows SharePoint Services information as described in
the following procedures.
Site Information Tab

Use the Site Information tab to configure site information.
The Site Information tab.

X To configure site information
1. On the Site Information tab, in the Site Name box, type the name that you want to
use for the new site.
2. Verify that the information in the Project Server directory box is correct.
3. When you specify a site name, the DSN Name box is populated with a name for the
new DSN based on the site name that you chose. If you want to use a different name
for the DSN, type it in the DSN Name box.
4. In the Session Manager box, type the name of the computer running the Session
Manager service.
5. In the Web Site to use list, choose the Web site that you want to use for the new
Project Server site.
6. If you are running Microsoft Windows Server™ 2003, in the IIS 6 Application Pool
to use box, select the application pool that you want to use with the new site.
7. Click the Database Information tab to configure the database information for the
new site.
Database Information Tab

Use the Database Information tab to specify the database configuration for a single
database or a partitioned database configuration.
The Database Information tab.

X To specify the database configuration for a single database configuration
1. On the Database Information tab, select the Single database configuration option.
Project Server database is located for this site.
4. Under MSProjectServer Role Member:, type the user name and password for the
for this site.
5. Under MSProject Role Member:, type the user name and password for the account
site.
6. Click the Windows SharePoint Information tab to specify Windows SharePoint
Services information for the new site.
X To specify the database configuration for a partitioned database configuration
1. On the Database Information tab, select the Partitioned database configuration
option.
2. If you have partitioned only the View tables, select the 2 Way Deployment option;
otherwise, select the Custom option.
Security views.
Note If you select the 2 Way Deployment option, the Web Tables option is not available.
Project Server database for this site is located.
6. Under MSProjectServer Role Member, type the user name and password for the
for this site.
7. Under MSProject Role Member, type the user name and password for the account
site.
9. Click the Windows SharePoint Information tab to specify Windows SharePoint
Services information for the new site.
Windows SharePoint Services Information Tab

Use the Windows SharePoint Services Information tab to configure Windows
SharePoint Services information for your site.
The Windows SharePoint Services Information tab.

If you are not using Windows SharePoint Services with the new site, clear the Setup
Windows SharePoint Services Project Server Integration check box, and then click
Create to create the new site. If you are using Windows SharePoint Services, complete the
following procedure.
X To configure Windows SharePoint Services information

1. On the Windows SharePoint Services Information tab, select the Set up Windows
SharePoint Services and Project Server Integration check box.
2. In the Admin URL box, type the URL for the Windows SharePoint Services Central
Administration page.
3. In the Site URL box, type the URL where you want to create Windows SharePoint
Services sites for projects.
4. In the Site Admin NT Account box, type the name of the Windows SharePoint
Services site administrator.
5. In the Admin Name box, type the name of the Windows SharePoint Services site
administrator.
6. In the Admin e-mail box, type the e-mail address for the Windows SharePoint
Services site administrator.
7. If you are deploying Windows SharePoint Services in an extranet scenario, select the
Extranet check box.
8. To prevent users of the new site from connecting to Windows SharePoint Services
sites that belong to other Project Server sites, select the Hosted Organization check
box.
9. Optionally, complete the fields for the second Windows SharePoint Services user
account, name, and e-mail address.
10. Click Create.
Completing Site Setup

After you use EditSite.exe to create a new site, you must perform the following tasks:
• Restart the Views Notification service.
Note In deployments in which the Views Notification service is installed on a different
computer than the Front-End service, you must restart the Views Notification on the
computer running the Views Notification service and the computer running the Front-End
service.
• Synchronize Windows SharePoint Services Web administrator accounts.

X To restart the Views Notification service
1. On the computer running the Views Notification service, open Administrative Tools.
2. Double-click Services.
3. In the Name column, right-click Project Server Views Notification Service, and
then click Restart.
X To synchronize Windows SharePoint Services Web administrator accounts

1. Log on to Project Web Access for the new site.
Note When EditSite.exe creates a new site, the administrator password is blank.

3. In the left pane, click Manage Windows SharePoint Services.
4. In the left pane, click Synchronize administrator accounts.
5. Click Synchronize Web Administrators.
Running the EditSite Tool from the Command Line

You can run EditSite.exe from a command line to add or delete a site. To display usage
information, run EditSite.exe from the command line and use the -? parameter.
The following table lists the command-line parameters for EditSite.exe.
Parameter Description
-? Display syntax information.
-S SQL Server. Specify the instance of SQL Server on which the main Project
Server database is located.
-D Database. Specify the main Project Server database to be used with the new
site.
-U MSProjectServer Role Member. Specify the user in the database that is a

member of the MSProjectServer role.
-P MSProjectServer Role Member password. Specify the password for the user
that is a member of the MSProjectServer role.
-E MSProject Role Member. Specify the user in the database that is a member
of the MSProject role.
-A MSProject Role Member password. Specify the password for the user that is
a member of the MSProject role.
-V Name of the Project Server site. Used when adding and deleting a site.
-W The Web root number of the Web site on which you want to install Project
Server 2003. The Web root number is found in the Internet Information
Services (IIS) metabase. You can use a tool such as the Meta-Data Edit Tool
from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=21727) to
determine the Web root number of the site that you want to use.
-L Project Server path. The path in which Project Server 2003 is installed.
-G Session Manager. Specify the name of the server running the Project Server
Session Manager service.
-H Application Pool. Microsoft Windows Server 2003 only. Specify the

application pool to use with the new site.
-I View Tables server. Specify the instance of SQL Server on which the View
Tables are located. Only required when the View Tables are located on a
different server from the main database.
-T View Tables database. Specify the name of the database that contains the
View Tables. Only required when the View Tables are located on a different
server from the main database.
-O Windows SharePoint Services AdminPort. Specify the URL for the Windows
SharePoint Services Central Administration page.
-Y Windows SharePoint Services site URL. Specify the URL where you want to
create Windows SharePoint Services sites for projects.
-C Windows SharePoint Services Admin NT Account. Specify the domain

account for the Windows SharePoint Services site administrator.
-N Windows SharePoint Services Admin Name. The name of the Windows

SharePoint Services site administrator.
-M Windows SharePoint Services Admin Mail. The e-mail address for the
Windows SharePoint Services site administrator.
-Q Quiet mode. Use –Q to suppress alerts.
-K Delete site. Deletes the site specified by the -V option.
To add a site, run EditSite.exe by using the following syntax:

EditSite [-S database server] [-D database] [-U Project Server user]
[-P Project Server password] [-E Project user] [-A Project password
[-V site name] [-W Web site number] [-L Project Server path]
-G Session Manager -H Application Pool
-I View Tables server -T View Tables database -B Web Tables server -
F Web Tables database -O Windows SharePoint Services Admin URL -Y
Windows SharePoint Services Site URL
-C Windows SharePoint Services Admin NT Account -N Windows
SharePoint Services Admin Name -M Windows SharePoint Services Admin

Mail
To delete a site, run EditSite.exe by using the following syntax:

EditSite [-K] [-V site name]
Project Server COM+ Settings Tool

The Project Server COM+ Settings tool (PSCOMPlus.exe) is used to specify the accounts
that you want Project Server 2003 to use when it accesses Analysis Services and Windows
SharePoint Services. PSCOMPlus.exe can be found in the \BIN\1033 folder of your
Project Server installation, or you can download it from the Microsoft Download Center
The Project Server COM+ Settings tool.

X To update the Analysis Services access identity
1. Run PSCOMPlus.exe.
2. In the Analysis Services (OLAP) Access Identity section, do the following:
b. In the Username box, type the domain and user name for the account that you
want Project Server 2003 to use to access Analysis Services.
c. In the Password box, type the password for that account.
3. If you are not updating the Windows SharePoint Services Administration Identity,
clear the Process this identity update check box in the Windows SharePoint
Services Administration Identity section.
4. Click Create/Update Com+ Apps.
X To update the Windows SharePoint Services Administration identity
1. Run PSCOMPlus.exe.
2. In the Windows SharePoint Services Administration Identity section, do the
following:
b. In the Username box, type the domain and user name for the account that you
want Project Server 2003 to use to access Windows SharePoint Services. This
account must have administrative rights for Windows SharePoint Services.
c. In the Password box, type the password for that account.
3. If you are not updating the Analysis Services Access Identity, clear the Process this
identity update check box in the Analysis Services (OLAP) Access Identity
section.
4. Click Create/Update Com+ Apps.
Windows SharePoint Services Backup and Restore Tool

The Windows SharePoint Services Backup and Restore tool (SMigrate.exe) is a Microsoft
Windows SharePoint Services tool that can be used to back up and restore a SharePoint
site. This tool is used in conjunction with PSMigrat.exe when migrating a SharePoint Team
Services deployment to Windows SharePoint Services. For more information, see 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. You can download Smigrate.exe from the Microsoft
Download Center (http://go.microsoft.com/fwlink/?LinkId=20881).
Note SMigrate.exe requires that CABARC.exe and EXTRACT.exe be in the same folder in order to
run.
To back up a SharePoint Web site by using SMigrate.exe, use the following syntax:
smigrate -w Web site URL -f backup file [-e] [-y]
To restore a SharePoint Web site by using SMigrate.exe, use the following syntax:
smigrate -r -w Web site URL -f backup file [-x]
The following table lists the command-line parameters for SMigrate.exe.

-f Backup file name (required). Specify a file name with the extension .fwp.
-e Exclude subsites during backup (optional). No parameters.
-r Restore (optional). No parameters.
-w Web site URL (required). Valid URL to a SharePoint Web site.
-x Exclude security during restore (optional). No parameters.
-y Confirm that you want to overwrite an existing backup file.
-u Administrator username.
-pw Administrator password. Specify * as the password to be prompted for a

password.
Project Server Data Migration Tool

The Project Server Data Migration tool (PSMigrat.exe) is a command-line tool that is used
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 .fwp 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. PSMigrat.exe then runs the Smigrate.exe tool to add this information to the
server running Windows SharePoint Services. You can download PSMigrat.exe from the
Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=20877).
The following table lists the command-line parameters that can be used with PSMigrat.exe.
*-w The managed path (URL) for Microsoft Windows SharePoint Services
project sites. Optional only if –bo (backup only) is specified.
*-ownerlogin A Windows account with permission to create a top-level Web site.
*-owneremail The e-mail address of the user specified in –ownerlogin.
-i Indicates the Project ID numbers (in Project Server 2003) whose

SharePoint Team Services subwebs will be migrated to Windows
SharePoint Services. It can be a single project ID, a range of project IDs, or
a series of project IDs that is out of order. If this parameter is not used, all
subwebs will be migrated. Use -1 to migrate the Public Document library.
*-f The path of the backup file and the working subfolder. Required for
PSMigrat.exe to run.
*-dbserver The Project Server database server.
*-dbname The name of the Project Server database.
-dblogin Required if SQL Server authentication is used.
-dbpassword Required if SQL Server authentication is used.
-c Connection string. Can be used in place of the –db* parameters.
-l The path to the log file. Optional; defaults to %temp% if not specified.
-s Specifies that PSMigrat.exe is to run in silent mode. Optional.
-ro Restore only from the expanded format (with Manifest.xml and other files
listed in a directory) from the work directory (-f). Optional.
-bo Back up the SharePoint Team Services subwebs into an .fwp file. This also
keeps the expanded file list out of the .fwp file.
*-p Accepts a prefix for the site name. For example, for a site with a target
name of ProjectServer_101, the prefix is "ProjectServer".
-u User name for computers running Microsoft Windows Server™ 2003 with
Internet Explorer Enhanced Security installed.
-pw Password for computers running Windows Server 2003 with Microsoft
Internet Explorer Enhanced Security installed.
-psintraneturl If specified, this URL will be set as a site property on each Project Web site
upon restoration.
-psextraneturl If specified, this URL will be set as a site property on each Project Web site
upon restoration.
Note Items with an asterisk (*) are required.

Windows SharePoint Services Site Migration Tool

When Project Server 2003 is used with Windows SharePoint Services, a site collection is
created on Windows SharePoint Services, and a subsite is created for every project that is
published to the server.
The Windows SharePoint Services Site Migration tool (WSSMigr.exe) is a command-line
tool that enables you to easily back up a selection of subsites or restore these subsites from
a previous backup. It can back up and restore a single subsite or a range of subsites that
you specify.
Based on Project IDs that you specify, WSSMigr.exe reads the subsite names from the
Project Server database for the Windows SharePoint Services subsites to be backed up, and
then calls the Windows SharePoint Services Site backup and restore tool (STSAdm.exe) to
perform the backup operation.
You can use WSSMigr.exe for the following two scenarios:
• A hosted deployment migration
• A single project restore
Hosted Deployment Migration

A hosted deployment is a large installation of Project Server 2003 that hosts Project Server
site collections for departments or divisions within the organization. The host can also be
an application service provider that hosts Project Server site collections for other
companies, similar to the way that an Internet service provider hosts Web sites.
In a typical hosted Project Server deployment, a single Windows SharePoint Services
content database is shared between multiple instances of Project Server 2003. You can use
WSSMigr.exe to migrate the Windows SharePoint Services site collection that is associated
with a single Project Server instance into or out of a hosted deployment.
When migrating in or out of a hosted deployment, run WSSMigr.exe without the -i
parameter to back up all the Windows SharePoint Services subsites in the site collection
that are associated with an instance of Project Server 2003.
Single Project Restore

You can use WSSMigr.exe in conjunction with the Restore Single Project tool
(RestoreP.exe) to restore a single project to an earlier point in time. To do this, run
WSSMigr.exe with the -i parameter and specify the ID of the project that you want to
restore. You must be following the database backup techniques described in the Microsoft
Office Project Server 2003 Disaster Recovery Guide (http://go.microsoft.com/fwlink/?LinkID=20234) in
order to successfully synchronize your Project Server data with your Windows SharePoint
Services data for the project that you want to restore.
Note For more information about restoring a single project, see the topic Restore a Single Project
in Appendix C, Project Server Recovery Tools of the Microsoft Office Project Server 2003 Disaster
Recovery Guide (http://go.microsoft.com/fwlink/?LinkID=20234).
Running the Tool

WSSMigr.exe is a command-line tool that calls the Windows SharePoint Services
STSAdm.exe tool to perform the actual backup operation.
Important WSSMigr.exe overwrites existing backup files when backing up and overwrites existing
subsites when restoring.
X To install WSSMigr.exe
• Download and run the file WSSMigr.exe from the Microsoft Download Center:
http://go.microsoft.com/fwlink/?LinkId=20895.
When you use WSSMigr.exe to back up subsites, the tool:
1. Queries the Project Server database for the URL for each subsite that you specified.
2. Creates a filename based on the subsite name (for example, projectserver_101.bak) for
each subsite.
3. Runs STSAdm.exe by using the following syntax:
Stsadm.exe -o backup -url [subsiteURL] -file [-f parameter +

filename] -overwrite
When you use WSSMigr.exe to restore subsites, the tool runs STSAdm.exe for each subsite
in the backup by using the following syntax:
Stsadm.exe -o restore -url [subsiteURL] -file [-f parameter +
filename] –overwrite
Note You must be a Windows SharePoint Services administrator to run WSSMigr.exe.
X To back up Windows SharePoint Services subsites

• Run WSSMigr.exe -bo on the computer running Windows SharePoint Services for the
subsites that you want to back up.
For example:
WSSMigr.exe –bo -f c:\wssmigr\temp
-dbserver SQLServer
-dbname ProjectServer
-l c:\temp\psmlog.txt
X To restore Windows SharePoint Services subsites

1. Copy the backup files to the computer running Windows SharePoint Services where
you want to restore them.
2. Run WSSMigr.exe -ro on that computer.
For example:
WSSMigr.exe –ro -w http://wss_restore_server/sites -f
c:\pswssbr\temp
-dbserver SQLServer
-dbname ProjectServer
-l c:\temp\psmlog.txt
WSSMigr.exe uses the following command-line parameters:
-? Display command-line help.
-w The managed path (the URL) of Windows SharePoint Services where the
subsites will be restored. Optional when backing up; required when
restoring. You must use the NetBIOS name for the server name. When used
with the -bo parameter, this value will override the Windows SharePoint
Services managed path associated with the project in the Project Server
database
-f Required. The directory path where the backup files are stored. For
example, c:\backup or \\myserver\folder\.
-dbserver Required. The name of the server running SQL Server that hosts the Project
Server database. You must use the NetBIOS name.
-dbname Required. The name of the Project Server database. Usually, this value is
'ProjectServer'.
-dblogin Required if using SQL Server authentication to access the Project Server
database. This account must have read permissions on the Project Server
database.
-dbpassword Required if using SQL Server authentication to access the Project Server
database.
-c Required if -dbname and -dbserver are not specified. Project Server

database connection parameters.
-i Optional. The range of Project IDs whose Windows SharePoint Services

subsites will be backed up. If this parameter is not specified, all Windows
SharePoint Services subsites created by Project Server 2003 in that site
collection will be backed up.
Specify either a single project ID, a series of project IDs, or a range of
Project IDs.
Examples:
-i 101-111 (Backs up the subsites for project 101-111)
-i 103,109,111 (Backs up the subsites for project 103, 109, 111)
-i 103,109-111 (Backs up the subsites for project 103, 109, 110, and 111)
-i 103 (Backs up the subsite for project 103)
-i -1 (Only backs up the public documents subsite)
(Note: You cannot include spaces in the list.)
-p Optional. This switch denotes a prefix to append to each Project Web site.
For example, if '-p Org1' is specified, site ProjectServer_101 will become
Org1_ProjectServer_101 and MS_ProjectServer_PublicDocuments will
become Org1_MS_ProjectServer_PublicDocuments.
-l Optional. The path and filename for the log file. If you do not specify a file
name, a file called WSSMigr.log will be created. If you do not specify a path,
the log file will be created in the %temp% directory for your user account.
-s Optional. Runs in silent mode with no output of the progress.
-ro Required when restoring. Restores all Windows SharePoint Services

subsites from the working directory (-f).
-bo Required when backing up. Back up all Windows SharePoint Services
subsites into the working directory (-f) as .bak files.
-u Optional. Administrator user name for Windows SharePoint Services.

Required if authentication credentials need to be passed. (Windows
Server 2003 Enhanced Security configurations.)
-pw Optional. Administrator password. Required if authentication credentials

need to be passed. (Windows Server 2003 Enhanced Security
configurations.)
WinHTTP Proxy Configuration Tool

When you run Project Server Setup, proxy settings are automatically configured for your
Project Server installation. If you need to change or update the proxy server configuration,
you can use the WinHTTP proxy configuration tool (Proxycfg.exe), which is installed on
the server when you run Project Server Setup.
X To run Proxycfg.exe
1. On the computer on which Project Server 2003 is installed, click Start, click Run, type
cmd, and then click OK.
2. Browse to the \Program Files\Microsoft Office Project Server 2003\Bin folder, and
then run Proxycfg.exe by using the parameters listed in the following tables.
3. Restart Internet Information Services (IIS).
Note New or updated information for Proxycfg.exe will not take effect until Internet
Information Services is restarted.
WinHTTP Proxy Configuration Tool Options

The following table lists and describes the options for Proxycfg.exe.
Option Description
Proxycfg This command displays the current WinHTTP
proxy settings.
proxycfg –d This command specifies that all HTTP and

HTTPS servers should be accessed directly.
Use this command if there is no proxy
server.
proxycfg -p proxy-server-list optional-bypass- This command specifies one or more proxy

list servers, and an optional list of hosts that
should be accessed directly. If a proxy server
is not specified for a given protocol and that
server is not in the bypass list, the -p option
specifies that the server cannot be accessed
at all.
Option Description
proxycfg -d -p proxy-server-list optional- This command specifies one or more proxy
bypass-list servers, and an optional list of hosts that
should be accessed directly. If a proxy server
is not specified for the given protocol, the -d
option specifies that the server should be
accessed directly instead.
proxycfg –u This command imports the Internet Explorer

proxy settings of the current user. WinHTTP
does not support auto-discovery and
configuration script–based proxy settings.
The following table describes how to use both the proxy-server-list and optional-bypass-list
parameters.
proxy-server-list Proxies are specified in a space-delimited
string. The proxy listings can contain the port
number used to access the proxy.
Proxy servers can be listed to use a specific
protocol. The valid protocols are HTTP or
HTTPS. The syntax for a proxy listing that
specifies a protocol is:
protocol=protocol://proxyNname
where protocol is either http or https and
proxyName is the name of the proxy server.
For example, the string
http=http://proxy_name:80
specifies that the protocol is HTTP, the name
of the proxy server is proxy_name, and the
port number for this server is 80. An
example of a proxy listing that specifies the
HTTPS protocol is:
https=https://proxyName
If the proxy server uses the default port
number for the protocol, the port number
can be omitted.
If a proxyName is listed by itself, the
Proxycfg.exe tool uses that proxy as the
default proxy for any protocols that do not
have a proxy specified. For example, the
listing
http=http://proxyName
other_proxy
specifies using the proxyName server for
any HTTP operations and the other_proxy
server for any HTTPS operations.
optional-bypass-list This list contains host names or IP

addresses that are locally known.
This list can contain wildcards, "*", that
cause the application to bypass the proxy
server for addresses that fit the specified
pattern. For example, both *.example.com
and *.org are acceptable wildcard patterns.
Wildcard characters must be the left-most
characters in the list, so myserver.* is not
supported.
To list multiple addresses and host names,
enclose them in quotes and separate them
with semicolons. If the <local> macro is
specified, the function bypasses any host
name that does not contain a period.
Examples
The following is the most common command used with the Proxycfg.exe tool. This
command specifies the use of the proxy server named myproxy to access both HTTP and
HTTPS servers, and also to bypass any host names that do not contain a period. In this
case, the -d option has no effect.
proxycfg -d -p myproxy "<local>"
Compare the previous command to the following command, which specifies use of the
proxy server named myproxy to access both HTTP and HTTPS servers, and to not bypass
any servers.
proxycfg -p myproxy
The following is an example of a more complex command used by the Proxycfg.exe tool.
This command specifies the use of the proxy server named http_proxy to access HTTP
servers and the server named https_proxy to access HTTPS servers. This command also
specifies that local intranet sites (for example, host names that do not contain a period) and
any site in the *.example.com domain bypass the proxy.
proxycfg -p "http=http_proxy https=https_proxy"
"<local>;*.example.com"
D
Configuring the Sample Database
This appendix describes the process for installing and configuring the Microsoft® Office
Project Server 2003 Sample database.
Installing Project Server 2003 with the Sample Database

Before configuring the Sample database, be sure that you have migrated the Analysis
Services repository to a Microsoft SQL Server™ database.
For more information about migrating the Analysis Services repository, see the topic Migrate the
Analysis Services Repository to a SQL Server Database in Chapter 8, Post-Installation Tasks of the
If you did not select the Project Server Sample Data component during Project Server
Setup, you can manually copy the files to the server. On the Project Server 2003 CD, copy
the files from the \Support\Sample\1033 folder to \Microsoft Office Project
Server 2003\Sample Data\1033 on your server. To restore and configure the data, type
sampcfg.exe /r at the command line. To back up your data, type sampcfg.exe /b at the
command line.
Note If you want to run the Sample database offline, you need to configure the HOSTS file at
\WINNT\System32\Drivers\Etc to map the IP address to your computer name in addition to the
localhost. When you are finished, save the file. For example:
127.0.0.1 localhost
127.0.0.1 servername
The Sample database has the following requirements:

• Microsoft Windows Server™ 2003 or Microsoft Windows 2000 Server, Service Pack 3
or later. Microsoft Windows® SharePoint® Services requires Windows Server 2003.
• Microsoft Internet Information Services (IIS) 5.0 or later, including the latest updates
for SSI Privilege Elevation Vulnerability. Refer to Knowledge Base article 301625 on
the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=24702).
• Microsoft SQL Server 2000, Service Pack 3, including server and client tools.
• Microsoft SQL Server Analysis Services, Service Pack 3.
• Windows SharePoint Services (requires Windows Server 2003); must be installed to a
port other than Port 80.
• Microsoft Office Project Server 2003.
• Microsoft Office Project Professional 2003.
• Microsoft Outlook® 2000 or later, or Microsoft Office Outlook 2003; optional, but
required to use the Outlook Integration features of Project Server 2003.
• Microsoft Excel 2000 or later; optional, but required to complete a full evaluation of
• Microsoft Word 2003.
When you are finished configuring the Sample database, see the files Samprm.htm and
Sampepm.htms in the \Sample Data\1033 folder of your Project Server installation for
more information about using the Sample database.
User Accounts
The Sample Data Configuration Wizard creates local computer user accounts on your
server for each of the roles listed in the following table. If you prefer, you can specify user
accounts for these roles.
Name Type Demo Role

Jo Brown User Executive, Portfolio Management Scenario
Scott Bishop User Resource Manager, Portfolio Management Scenario
Steve Masters User Project Manager, Portfolio Management Scenario
Brad Sutton Power User Team Member, Portfolio Management Scenario
Eva Corets User Project and Resource Manager, Resource Management

Scenario
Wendy Wheeler User Resource Manager, Resource Management Scenario
Rob Young Power User Team Member, Resource Management Scenario

Each user listed in the table has a Windows password of pass@word1 and uses Windows
authentication to access the computer running Project Server. All other users in the sample
data have a blank password.
Note The administrator account is not created by the Sample Data Configuration Wizard.
Sample Data Installation and Configuration

To install and configure the sample data, run the Sample Data Configuration Wizard.
X To run the Sample Data Configuration Wizard
1. On the Start menu, point to Programs, click Microsoft Office Project Server 2003,
and then click Restore and Configure Sample Data.
The Sample Data Configuration Wizard starts.
2. Click Next to view the End-User License Agreement.
3. If you agree to the terms of the End-User License Agreement, select the I accept the
terms of the License Agreement option, and then click Next.
4. Select the database types that you want to restore, and then click Next.
Note The documents, issues, and risks features require Windows SharePoint Services.
5. On the Microsoft Office Project 2003 Database page, the path and file name for the
Project Server Sample database file, and the new database name, are included as default
values. Edit these values if you want to restore a different backup or use a different
database name, and then click Next.
6. On the Windows SharePoint Services Database page, the path and file name for the
Windows SharePoint Services Sample database file, and the new database name, are
included as default values. Edit these values if you want to restore a different backup
or use a different database name, and then click Next.
7. Specify the URL that you will use to access the sample data, and then click Next.
8. Either choose to allow the wizard to create user accounts on your computer, or specify
existing user accounts to use for each role (remember the option that you select here;
you will need it later). It is recommended that you allow the wizard to create user
accounts—this will help you to follow demo scripts provided.
Note If you choose not to have the wizard create user accounts for you, you will need to
manually add the users Brad Sutton and Rob Young to the Power Users group when you
create the user accounts.
9. Click Install.
10. Click Finish.
Note You might want to set up multiple copies of the sample data on the server so that different
people can use their own copy of the sample data. To do this, run this wizard multiple times. Each
time that you run the wizard, specify a different database name and URL. If you need to install
multiple copies of the Windows SharePoint Services sample data, see the topic Installing Multiple
Copies of the Windows SharePoint Services Data in Appendix D, Configuring the Sample Database
of the Microsoft Office Project Server 2003 Installation Guide.
Configuring Windows SharePoint Services for Project

Server 2003
Because you are restoring a database from a different computer, you must reconfigure
Windows SharePoint Services and Project Web Access. This involves completing the
following steps:
• Creating a new virtual server.
• Assigning application pool ID permissions on the new database.
• Extending the Windows SharePoint Services site and adding the restored database.
• Adding Project Server 2003 to the Windows SharePoint Services exclusion list.
• Complete the integration between Windows SharePoint Services and Project
Server 2003.
X To create a new virtual server
1. On the Start menu, click Run.
2. In the Open box, type Inetmgr and then click OK.
The Internet Information Services Manager starts.
3. In the left pane, expand the tree until you view the Web Sites folder.
4. Click the Web Sites folder and on the Action menu, click New, and then click Web
Site.
5. In the Web Site Creation Wizard, click Next.
6. On the Web Site Description page, type a description (for example, SharePoint
Sample Database) and then click Next.
7. On the IP Address and Port Settings page, change the TCP port to a value such as
5555 and then click Next. This number must be unique. Do not use 80 or any other
port you have previously defined for a Web site.
8. On the Web Site Home Directory page, click the Browse button. On the drive on
which Windows is installed, find and select the Inetpub folder.
9. Click Make New Folder. Type Sample and then click OK.
10. Click Next.
11. On the Web Site Access Permissions page, click Next.
12. Click Finish.
13. Close IIS Manager.
X To assign application pool ID permissions on the new database
1. On the Start menu, point to All Programs, Microsoft SQL Server, and then choose
Enterprise Manager to open SQL Server Enterprise Manager.
2. In the tree view, browse to the Security folder, expand it, and then select Logins. Then
do one of the following:
• If the NT Authority\Network Service login does not exist, you need to add it as
a login account. To do this, right-click Logins, select New Login, and then create
the NT Authority\Network Service account in the SQL Server Login Properties
dialog box. In the Name box, enter NT Authority\Network Service, and then
select the Database Access tab. Select the Permit box next to the Windows
SharePoint Services database; in this case it should be the same database restored
previously (default name MPSWSSSampleDatabase). Do not change the settings
for any other database. Under Database roles, enable db_owner and then click
OK.
Note This step assumes that Windows SharePoint Services sample Content database
application pool is running under the identity of NT Authority\Network Service.
• If the NT Authority\Network Service login does exist, you need to verify that
this account exists as a db_owner on the MPSWSSSampleDatabase database.
Double-click NT Authority\Network Service, and then select the Database
Access tab. Select the Permit box next to the Windows SharePoint Services
database; it should be the same database restored previously (default name
MPSWSSSampleDatabase). Do not change the settings for any other database.
Under Database roles, enable db_owner and then click OK.
Note This step assumes that Windows SharePoint Services sample content database
application pool is running under the identity of NT Authority\Network Service.
3. Close SQL Server Enterprise Manager.

X To extend the Windows SharePoint Services site and add the restored database
1. On the Start menu, point to Administrative Tools, and then click SharePoint
Central Administration.
2. Click Configure Virtual Server Settings.
3. On the Virtual Server List page, click the virtual server that you created (for example,
SharePoint Sample Database).
4. On the Extend Virtual Server page, go to the Provisioning Options section and
click Extend and create a content database.
5. In the Application Pool section, in the Application pool name box, type a name for
the application pool (for example, WSSSampAppPool).
6. Select the Predefined option, and choose Network Service from the list.
7. In the Site Owner section, type a domain and user name in the User Name box. This
account should have access to this computer.
8. In the E-Mail box, type an e-mail address for the site owner, and click OK.
9. On the Virtual Server Successfully Extended page, click OK.
10. Under Virtual Server Management, click Manage content databases.
11. Under Content Databases, click Add a content database.
12. Under Database Information, select the Specify database server settings option, and
then type the name of the restored Windows SharePoint Services database (for
example, MPSWSSSampleDatabase) in the Database name box.
13. Type a user name and password to use to access the database. You can use your SQL
Server sa account for this.
14. Enter values in the Number of sites before a warning event is generated and
Maximum number of sites that can be created in this database boxes, such as
9000 and 15000, and then click OK.
15. If you are installing an additional copy of the SharePoint sample data, follow the
procedures in the topic Installing Multiple Copies of the Windows SharePoint
Services Data in Appendix D, Configuring the Sample Database of the Microsoft
X To add Project Serve 2003 to the Windows SharePoint Services exclusion list
1. In Administrative Tools in Control Panel, open the Windows SharePoint Services
Central Administration page.
2. Under Virtual Server Configuration, click Configure virtual server settings.
3. On the Virtual Server List page, click the Default Web Site link that points to the
server running Project Server 2003.
4. On the Virtual Server Settings page, under Virtual Server Management, click
Define Managed Paths.
5. On the Define Managed Paths page, under Add a new path, type the name of the
Project Server Sample database path (for example, “sample”) in the Path text box.
6. Under Type, select Excluded Path.
Note If you click Check URL, the page will not load. This is expected behavior.
7. Click OK. The name of the Project Server Sample database virtual directory appears in
the list of excluded servers under Excluded Paths.
X To complete the integration between Windows SharePoint Services and Project Server 2003
1. Open Project Web Access for the sample data (for example,
http://computername/sample).
2. Log on as an administrator by using the password pass@word1.
4. On the side pane, click Manage Windows SharePoint Services.
5. In the SharePoint Central Administration URL box, type the URL for SharePoint
Central Administration. Be sure to use the server name and not localhost.
6. In the Create a site under this SharePoint URL box, type

http://servername:port/sites, where port is the port number that you specified for
the new virtual server (for example, 5555). Be sure to use the server name and not
localhost.

8. In the left pane, click Manage SharePoint sites.
9. Click the first project name in the list (not including the Public Documents project).
10. Click Synchronize.
11. Click Yes for the alert that pops up.
12. Repeat steps 9, 10, and 11 for all other projects listed.
Installing Multiple Copies of the Windows SharePoint Services

Data
The Project Server Sample database was designed to allow a single installation of Project
Server 2003 and Windows SharePoint Services data on a computer. If you want to use
more than one copy of the Project Server data, you can install additional copies by running
the Sample Data Configuration Wizard. If you want to install more than one copy of the
Windows SharePoint Services data, you will need to configure the new datasets manually.
This topic describes the process for installing more than one copy of the Windows
SharePoint Services sample data on a computer.
If you want to install more than one copy of the Windows SharePoint Services sample data,
you must do so before making any changes to the data in your initial Project Server Sample
database deployment.
Caution Do not attempt to restore multiple copies of the Windows SharePoint Services sample
data by using the Sample Data Configuration Wizard without following the procedure in this topic.
Previous installations will be corrupted and become unusable.
X To install additional copies of the SharePoint sample data

1. Follow the procedures in the topics Sample Data Installation and Configuration
and Configuring Windows SharePoint Services for Project Server 2003 in
Appendix D, Configuring the Sample Data of the Microsoft Office Project Server 2003
Installation Guide until you reach step 15 in the procedure To extend the Windows
SharePoint Services site and add the restored database.
2. Run the Site backup/restore tool (STSAdm.exe) to back up and restore the Sample
database sites onto a different virtual server by using the batch program that follows.
Restore the sites under the same name.
@ECHO OFF
REM Declare variables
REM Source vserver

SET SVRNAME1=<servername>
SET SVRWEBPORT1=<port>
SET SVRMPATH1=sites
SET SVRSITEPREFIX1=ProjectServer
REM Target vserver

SET SVRNAME2=<servername>
SET SVRWEBPORT2=<port>
SET SVRMPATH2=sites
SET SVRSITEPREFIX2=ProjectServer
IF [%1]==[b] (
REM Backup the sites from the (Sample) first Windows SharePoint
Services VServer
STSAdm.exe -o backup -url

http://%SVRNAME1%:%SVRWEBPORT1%/%SVRMPATH1%/MS_ProjectServer_Publ
icDocuments -filename backup_MS_ProjectServer_PublicDocuments
FOR %%a IN (101 103 105 107 109 110 112 114 116 118 119 120 122
124 125) DO (
STSAdm.exe -o backup -url
http://%SVRNAME1%:%SVRWEBPORT1%/%SVRMPATH1%/%SVRSITEPREFIX1%_%%a
-filename backup_%%a
)
)
IF [%1]==[r] (
REM Restore the sites to the (clean) second Windows SharePoint
Services VServer
STSAdm.exe -o restore -url

http://%SVRNAME2%:%SVRWEBPORT2%/%SVRMPATH2%/MS_ProjectServer_Publ
icDocuments -filename backup_MS_ProjectServer_PublicDocuments
FOR %%a IN (MS_ProjectServer_PublicDocuments 101 103 105 107 109

110 112 114 116 118 119 120 122 124 125) DO (
STSAdm.exe -o restore -url
http://%SVRNAME2%:%SVRWEBPORT2%/%SVRMPATH2%/%SVRSITEPREFIX2%_%%a
-filename backup_%%a
)
)
3. Follow the procedure To add Project Server 2003 to the Windows SharePoint
Services exclusion list in the topic Configuring Windows SharePoint Services for
Project Server 2003 in Appendix D, Configuring the Sample Data of the Microsoft
Building the OLAP Cube

Project Web Access uses an online analytical processing (OLAP) cube for modeling and
analyzing data. If you make major changes to the database, such as renaming a project or
significantly modifying assignments or views, you will need to rebuild the OLAP cube to
ensure that Portfolio Analyzer views are updated accordingly.
Note If you install multiple instances of the Project Server Sample database and do not specify
unique names for the OLAP cube, each instance of the Project Server Sample database will point to
the same OLAP cube. If you specify a new name for the OLAP cube, you will also need to change the
Portfolio Analyzer view configuration to point to the new cube.
X To build the OLAP cube

1. Open Internet Explorer and launch Project Web Access (http://servername/Sample).
2. Log on to Project Web Access as the administrator and type the password:
pass@word1.
3. In the top-level navigation, click Admin.
4. In the side pane, under Actions, click Manage enterprise features.
5. Under Enterprise options, click Update resource tables and OLAP cube, or do
one of the following:
• Under Build the OLAP cube, select Yes, I want to update resource
availability information and build an OLAP cube.
• Under OLAP cube name and description, specify the name of the Analysis
Services server, the OLAP cube name, and description.
• Under Date range for resource availability, specify the range that you want to
use for resource updates.
6. Under Update frequency, select Update only when specified, and then click
Update Now. The OLAP cube will be created. This might take several minutes. You
can check the status of the OLAP cube by refreshing the page and then referring to the
Current Cube Status section. Remember the name of the OLAP cube that you are
generating as you will need to refer to it later.
Note If you receive an error message stating that the connection to the repository cannot be
established, you might need to set additional permissions for the OLAP repository.
X To set additional permissions for the OLAP cube

1. On the Start menu, select My Computer.
2. Browse to and open the \Program Files\Microsoft Analysis Services folder.
3. Right-click the Bin directory and select Properties to open the Bin Properties dialog
box.
4. Select the Security tab, and then click the Add button to open the Select Users,
Computers, or Groups dialog box.
5. In the Enter the object names to select text box, type servername\OLAP
Administrators, and then click OK.
6. In the Bin Properties dialog box, under Groups or user names, select the OLAP
Administrators group.
7. Under Permissions for, set Full Control to Allow.
8. Click OK.
Verifying the Resource Availability Tables

When the OLAP cube is built, it sometimes fails to update the Resource Availability tables
automatically. Therefore, after building the OLAP cube, be sure to verify that the Resource
Availability tables were updated after you build the OLAP cube. Occasionally, you might
need to rebuild the Resource Availability tables.
X To verify that the Resource Availability tables were updated
1. On the Start menu, point to All Programs, Microsoft SQL Server, and then choose
Enterprise Manager to open SQL Server Enterprise Manager.
2. Expand the Console Root until you reach Databases. Expand Databases and select
the Project Server database; for example, MPSSampleDatabase.
3. Click Tables.
4. Find the table MSP_VIEW_RES_TP_BY_DAY, right-click, point to Open Table,
and then choose Return all rows.
5. If the fields ResourceTimeStart, ResourceTimeFinish, and
ResourceWorkAvailability are empty, you need to rebuild the Resource Availability
tables.
X To rebuild the Resource Availability tables
1. Open Internet Explorer and launch Project Web Access (http://servername/Sample).
2. Log on to Project Web Access as the administrator and type the password:
pass@word1.
3. In the top-level navigation, click Admin.
4. In the side pane, under Actions, select Manage enterprise features.
5. Under Enterprise options, click Update resource tables and OLAP cube.
6. Under Build the OLAP cube, select No, I only want to update resource
availability information.
7. Under OLAP cube name and description, verify the name of the Analysis Services
server, the OLAP cube name, and the description.
8. Under Date range for resource availability, specify the range that you want to use
for resource updates.
9. Under Update frequency, select Update only when specified, and then click
Update Now. The Resource Availability tables will be updated. This should take less
time than creating the entire OLAP cube.
Granting Users Permission to Access the OLAP Cube

The users who need to view the OLAP cube by using Portfolio Analyzer must be granted
permission to access the OLAP cube.
X To grant users permission to access the OLAP cube
1. On the Start menu, point to All Programs, Microsoft SQL Server, Analysis
Services, and then click Analysis Manager.
2. Locate the Sample database OLAP cube, right-click Database Roles, and then select
Manage Roles.
3. In the Database Role Manager dialog box, click New to open the Create a
Database Role dialog box.
4. Enter the name of the role in the Role Name box, and then click Add on the
Membership tab to open the Add Users and Groups dialog box.
5. In the List Names From list, select the servername/ computername if you selected Create
Windows user accounts for each user on this computer or the domain name if you
selected Use existing Windows user accounts for the roles.
6. Click Show Users and select Jo Brown. Click Add. Repeat this step for the users
Steve Masters, Scott Bishop, Eva Corets, and Wendy Wheeler. Click OK.
7. Click the Cubes tab, select the option MSP_Portfolio_Analyzer, and then click OK.
8. When you are finished, close Analysis Manager.
Creating Project Server Accounts for Project Professional Users

Use the following procedure to create Project Server accounts for Project Professional
users.
X To create Project Server accounts for Project Professional users
1. Log on to the computer running Project Server 2003 as an administrator.
2. Start Project Professional in offline mode (not connected to Project Server 2003).
3. On the Tools menu, point to Enterprise Options, and then click Microsoft Office
Project Server Accounts.
4. Click Add.
5. Enter Sample Data in the Account Name box.
6. Enter the URL for the Project Server Web site in the Project Server box (for example,
http://servername/sample).
7. Select the Use a Microsoft Project Server account option.
8. Select the Set as default account check box.
9. In the User name box, type Administrator.
10. Click OK.
11. Click OK to close the dialog box.
12. Close Project Professional.
13. Log off of the computer.
14. Log on to the computer as the user Eva Corets.
16. On the Tools menu, point to Enterprise Options, and then click Microsoft Project
Server Accounts.
17. Click Add.
18. In the Account Name box, type Sample Data.
19. Type the URL for your Project Server site in the Project Server text box (for example,
20. Select the Use Windows user account option.
21. Select the Set as default check box.
22. Click OK.
26. Log on to the computer as the user Steve Masters.
28. On the Tools menu, point to Enterprise Options, and then click Microsoft Project
Server Accounts.
29. Click Add.
30. In the Account Name text box, type Sample Data.
31. Type the URL for your Project Server site in the Project Server text box (for example,
32. Select the Use Windows user account option.
33. Check the Set as default account check box.
34. Click OK.
Configuring Internet Explorer

Use the following procedure to configure Internet Explorer.
X To configure Internet Explorer
1. Log on to a computer as the user Jo Brown.
2. Open Internet Explorer and on the Tools menu, click Internet Options.
3. Click the Security tab.
4. Select the Trusted Site icon and then click Sites to open the Trusted Sites dialog
box.
5. Clear the Require server verification (https://) for all sites in this zone check box.
6. Add your Web site as a trusted site by typing http://servername in the Add this
Web site to the zone text box, and then click Add.
7. Click OK.
8. Log off of the computer, and repeat this procedure for the users Scott Bishop, Steve
Masters, Eva Corets, Wendy Wheeler, Brad Sutton, and Rob Young.
Setting Up Outlook Integration

Use the following procedure to set up Outlook integration.
X To set up Outlook integration
1. Log on to the computer as an Administrator, open Internet Explorer, and then log on
to Project Web Access as an administrator by using the URL that you created earlier.
2. Click Tasks, click View and report on your tasks from your Outlook calendar, and
then click Download Now to download the Outlook Add-in.
3. On the File Download dialog box, click Open. Follow the instructions to complete
the installation.
4. Log on to the computer as Brad Sutton, right-click the Outlook icon, and then select
Properties.
5. Click Add and specify a new profile name. Click OK.
6. Select View or change existing e-mail accounts, and then click Next.
7. Click Finish.
8. Click OK in the alert regarding creating a profile with no e-mail accounts.
9. Click OK to close the Profile dialog box.
10. Open Outlook.
11. Click Next.
12. Select No on the E-mail accounts page of the wizard and click Finish. You might
get a User Name dialog box that states your full name and initials. Click OK if you are
presented with this dialog box.
13. In the Outlook menu, select Tools, point to Options, and then select the Other tab.
14. Click Advanced Options, click COM Add-ins, and then click Add.
15. Browse to drive:\Program Files\Microsoft Office\Office 11.
16. Double-click the MPSAddIn.dll file. Click OK three times.
17. On the Tools menu, click Options.
18. On the Project Web Access tab, click Enter login information.
19. In the Enter Login Information dialog box, type the URL for the Project Server
Sample database, and then click OK.
20. Click OK to close the Options dialog box.
21. Close Outlook and log off of the computer.
22. Repeat this procedure for the user Rob Young.
Backing Up Custom Databases

It is strongly recommended that you back up both your Project Server and Windows
SharePoint Services databases at this phase of working with the Project Server Sample
database. This is a fully functional sample database. You can use this backup the next time
you want to use the sample as a clean starting point. This is essential if you want to
repeatedly evaluate or demo Project by using the Evaluation Guide scripts. For detailed
information about backing up Project Server and Windows SharePoint Services databases,
see the Microsoft Office Project Server 2003 Disaster Recovery Guide.
(http://go.microsoft.com/fwlink/?LinkID=20234)
Note If you plan to restore the Project Server database on another server, you must remove the
SQL users for the Project Server and Windows SharePoint Services databases before creating the
backup file.
X To remove user roles for Project Server and Windows SharePoint Services
2. On the Start menu, point to All Programs, Microsoft SQL Server, and then click
Enterprise Manager.
3. Under Console Root, expand the tree until the Databases folder appears.
4. Expand the Databases folder, and then expand the folder for the database that you
intend to back up (for example, MPSSampleDatabase).
5. Select the Users folder.
6. Right-click MSProjectSampleDBUser and select Delete.
7. Right-click MSProjectServerSampleDBUser and select Delete.
X To back up the Sample database
2. On the Start menu, point to All Programs, Microsoft Office Project Server 2003,
and then select Back Up Sample Data to open the Sample Data Backup Wizard.
Click Next.
4. On the Data Type page, choose Back up Microsoft Office Project Server database
if you are not using Windows SharePoint Services, or choose Back up Microsoft
Office Project Server 2003 and Windows SharePoint Services databases,
including integrated documents, issues, and risks if you are using Windows
SharePoint Services. Click Next.
5. On the Microsoft Office Project Server 2003 Database page, under Microsoft
Office Project Server database to back up, type the name of the database. Under
Back up as, specify the path for the backup. Click Back Up.
6. After the Project Sample Data Backup Wizard creates the backup file, click Finish.
Note You can also type sampcfg.exe /b at the command line to back up your data.
X To restore the Sample database

2. On the Start menu, point to All Programs, Microsoft Office Project Server 2003,
and then select Configure Sample Data to open the Sample Data Wizard. Click
Next.
4. On the Data Type page, choose Install Microsoft Office Project Server data if you
are not restoring Windows SharePoint Services data, or choose Install Microsoft
Office Project Server 2003 and Windows SharePoint Services data if you are
restoring Windows SharePoint Services. Click Next.
5. On the Microsoft Office Project Server 2003 Database page, under Microsoft
Office Project Server database backup file to restore, specify the path name for the
database. Under Restore as, specify the name of the backup file. Click Next.
6. If you are restoring the Windows SharePoint Services database, on the Windows
SharePoint Services Database page, edit the path and file name if necessary, and
then click Next.
7. On the URL page, specify the URL for the server running Windows SharePoint
Services, for example, http:// servername/sample).
8. On the User Accounts page, specify the user accounts that you want to use for the
restored database. Select Create Windows user accounts for each role on this
computer for me if you want the user accounts to be created automatically, or select
Use existing Windows user accounts for the roles if you want to preserve existing
user accounts. You will need to provide the credentials for these user accounts during
the restore process if you choose this option.
9. Click Install.
10. After the Sample Data Wizard restores the backup file, click Finish.
Note You can also type sampcfg.exe /r at the command line to restore and configure the data.
E
Uninstalling Project Server 2003
You can uninstall Microsoft® Office Project Server 2003 by using Add or Remove
Programs in Control Panel. When you uninstall Project Server 2003, the following
components are unaffected:
• Database files in Microsoft SQL Server™ 2000 or the Microsoft Desktop Engine
(MSDE).
• System files installed by Project Server Setup (such as the files for Microsoft XML).
• Additional products or components, such as Microsoft Windows® SharePoint®
Services.
• Project Server templates and sites that Project Server 2003 created by using those
templates.
On the other hand, the registry keys that were created for Project Server 2003 are removed
when you uninstall the software.
You can use the Windows SharePoint Services Configuration Wizard to uninstall the
Project Server templates and restore the Windows SharePoint Services templates to their
original state (existing subsites are not affected). To uninstall Windows SharePoint Services
completely, use the Windows SharePoint Services Configuration Wizard to uninstall the
Project Server templates, unextend the virtual server, and delete the content database.
Then, uninstall Windows SharePoint Services by using Add or Remove Programs in
Control Panel.
Uninstalling Project Server 2003 does not remove the database. You can delete the
database after uninstalling Project Server 2003, but this is not recommended, as this is the
record stored on the server of all projects that were planned.
F
Installing Project Server 2003 From
the Command Line
When you run Project Server Setup for Microsoft® Office Project Server 2003, you can
use command-line options to enter the parameters that Project Server Setup uses during
installation, instead of entering them on the Project Server Setup pages or entering them
later by using Microsoft Office Project Web Access 2003.
Note The command-line functionality described in this appendix only works on versions of Project
Server 2003 that are sold by means of a volume licensing agreement.
This appendix provides the command-line options that are available to you for each of the
steps within Project Server Setup.
To see a visual representation of the relationships between the various Project Server Setup
steps, see the Project Server Setup Flow Diagram, available on the Microsoft Web site
Important It is strongly recommended that you install Project Server 2003 by using Project Server
Setup, as described in Chapter 7, Install Project Server 2003, in the Microsoft Office Project
Server 2003 Installation Guide, rather than by using the command line. It is easier to install Project
Server 2003 by using Project Server Setup.
Command-Line Parameters for Installing Project Server 2003

To install Project Server 2003 from the command line, run the setupsvr.exe program
(which is located in the prjsvr folder on the Project Server 2003 CD) from the command
line, followed by the required parameters and values. Use the following syntax to install
Project Server 2003 from the command line:
setupsvr.exe AddLocal=value1, value2, value3 parameter=value

parameter=value parameter=value parameter=value
Important When you install Project Server 2003 from the command line, no validation of
parameters or values is performed. If parameters or values are used incorrectly, the installation will
roll back and Project Server Setup will be unable to provide error information.
The AddLocal parameter is used to specify which features of Project Server 2003 you are
installing. The following sections describe the values that you need to include with the
AddLocal parameter.
Important Specify the AddLocal parameter only once on the command line. Include all the
AddLocal parameters for the features that you want to install in one comma delimited string after
the AddLocal parameter.
Select a Location for Installation

In Project Server Setup, on the Select a location for installation page, you specify the
location where Project Server 2003 will be installed on your computer. To do this, use the
following parameter at the command prompt:
PRJSERVERDIR=path Specify the Project Server installation
directory. For example, “C:\Program
Files\Microsoft Office Project Server 2003”
Choose the Services You Want to Install on This Server

In Project Server Setup, on the Choose the services you want to install on this server
page, you can specify the components of Project Server 2003 that you want to install. To
do this at the command prompt, select one of the following values for the AddLocal
parameter:
AddLocal=PrjSvrFrontEnd Add the value PrjSvrFrontEnd to your
AddLocal parameter string if you want to
install the Project Server Front-End service.
AddLocal=PrjSvrViews Add the value PrjSvrViews to your AddLocal

parameter string if you want to install the
Project Server View Processing Service.
AddLocal=PrjSvrSessionMgr Add the value PrjSvrSessionMgr to your
install the Project Server Session Manager
service.
AddLocal=PrjSvrSampleDB Add the value PrjSvrSampleDB to your

install the Project Server Sample database.
You must install all services on the same
computer if you are installing the Sample
database.
Installing the Session Manager Service Without the Front-End

Service
If you are installing the Session Manager service but not the Front-End service, you must
specify the name of the computer on which you are installing the Session Manager Service
when you install that service. To do this, use the following parameter at the command
prompt:
SMSERVER=servername Specify the NetBIOS name of the computer
on which you are installing the Session
Manager Service.
Create the View Processing Share

In Project Server Setup, on the Enter the Views Processing server information page,
you can specify connection information for the server running the View Processing
Service, if you are installing the View Processing Service but not the Front-End service. To
do this, use the following parameters at the command prompt:
VWSHARE=folder name Specify the name that you want to use for
the view share.
VWPATH=path Specify the path of the view share in the

form: \\computername\share
VWLOGONNAME=domain\user Specify a domain user account that has
sufficient permissions to create the share.
Use the format: domain\user
VWPASSWORD=password Specify the password for the domain user.
Enter the Session Manager Server Name

In Project Server Setup, on the Enter the Session Manager server name page, you can
specify the server on which the Session Manager Service is located if you have installed it
on another computer. To do this, use the following parameter at the command prompt:
SMSERVER=server name Specify the NetBIOS name of the computer
where the Session Manager is installed.
Enter the View Processing Server Information

In Project Server Setup, on the Enter the Views Processing server information page,
you can specify the location and connection information for the server running the View
Processing Service, if you installed it on a different computer. To do this, use the following
parameters at the command prompt:
VWPATH=path Specify the path to the qualified path to the
View Staging share in the format:
\\server\share
VWSVCLOGONNAME=domain\user Specify a domain user account with read

and change permissions to the View Staging
share. Use the format: domain\user.
VWSVCPASSWORD=password Specify the password for the domain user

account.
Enter Database Server Information

In Project Server Setup, on the Enter database server information page, you can specify
database server and connection information. To do this, use the following parameters at
the command prompt:
AddLocal=PrjSvrCreateDBFeature If you are creating a new database, add the
value PrjSvrCreateDBFeature to your
AddLocal string. If you are connecting to an
existing database, do not include this value.
SERVERNAME=server\instance Specify the instance of SQL Server where

you will set up the Project Server database.
SQLDBNAME=database name Specify the name of the Project Server

database.
SAAUTHTYPE=[WIN | SQL] Specify the type of authentication to use

when connecting to the computer running
SQL Server. Use a value of WIN for Windows
authentication or SQL for SQL Server
authentication.
DBADMIN=ServerSA If you are using SQL Server authentication

(SAAUTHTYPE=SQL), you must include the
DBADMIN=ServerSA parameter.
SANAME=login If you are using SQL Server authentication,

use the SANAME parameter to specify the
SQL Server login that you want to use.
SAPASSWORD=password If you are using SQL Server authentication,

use the SAPASSWORD parameter to specify
the SQL Server password that you want to
use.
Enter Connection Information for Views Tables

In Project Server Setup, on the Enter connection information for Views tables page,
you can specify server and connection information for the Project Server Views tables. To
do this, use the following parameters at the command prompt:
AddLocal=PrjSvrCreateDBFeature2 If you are creating a new database and
offloading the View tables to a different
server, add the value
PrjSvrCreateDBFeature2 to your AddLocal
string.
AddLocal=PrjSvrSplitDBFeature If you are offloading the View tables to a

different server, add the value
PrjSvrSplitDBFeature to your AddLocal
string.
SERVERNAME2=SQL Server instance Specify the instance of SQL Server where

you will set up the Project Server View
Tables database. Use the same value that
you specified for SERVERNAME if you are
not offloading the View tables.
SQLDBNAME2=database Specify the name of the Project Server

database. Use the same value that you
specified for SQLDBNAME if you are not
offloading the View tables.
DB2ADMIN=[ServerSA | Server2SA] Required. Use ServerSA if you are not

offloading the View tables; otherwise, use
Server2SA.
SANAME2=username If you are using SQL Server authentication,

use the SANAME2 parameter to specify the
SQL Server login that you want to use. If you
are not offloading the View tables, use the
same value that you specified for SANAME.
SAPASSWORD2=password If you are using SQL Server authentication,

use the SAPASSWORD parameter to specify
the SQL Server password that you want to
use. If you are not offloading the View
tables, use the same value that you
specified for SAPASSWORD.
Enter Database Account Information

In Project Server Setup, on the Enter database account information page, you can
specify the account information to be used by Project Server 2003 and Project Professional
to access the database. To do this, use the following parameters at the command prompt:
PSNAME=username Specify the name of the SQL Server login
that is a member of the
MSProjectServerRole role (normally
MSProjectServerUser).
PSPASSWORD=password Specify the password for the SQL Server

login that is a member of the
MSProjectServerRole role.
PRJNAME=use name Specify the name of the SQL Server login

that is a member of the MSProjectRole role
(normally MSProjectUser).
PRJPASSWORD=password Specify the password for the SQL Server

login that is a member of the MSProjectRole
role.
Enter Analysis Services Connection Information

In Project Server Setup, on the Enter Analysis Services connection information page,
you can specify the server running Analysis Services and the account information to use
when connecting to it. To do this, use the following parameters at the command prompt:
Note Only use these parameters if you are installing the Project Server Front-End service.
AddLocal=PrjSvrDBInfoAS If you want to specify Analysis Services
connection information, add the value
PrjSvrDBInfoAS to your AddLocal string.
ASSERVERNAME=server Specify the NetBIOS name of the server

running Analysis Services.
ASLOGINNAME=username Specify the user account that is a member

of the OLAP Administrators group on the
server running Analysis Services. Use the
format: domain\user
ASPASSWORD=password Specify the password for the user account.
Select a Web Site

In Project Server Setup, on the Select a Web site page, you can specify the Web site where
you want the virtual directory for Project Server 2003 to be installed. To do this, use the
following parameter at the command prompt:
Note Only use this parameter if you are installing the Project Server Front-End service.
WEBVROOT=web root number The Web root number of the Web site where
you want to install Project Server. The Web
root number is found in the IIS metabase.
You can use a tool such as the Meta-Data
Edit Tool from the Microsoft Web site
(http://go.microsoft.com/fwlink/?LinkId=21727)
to determine the Web root number of the
site that you want to use.
Enter Web Server Address Information

In Project Server Setup, on the Enter Web server address information page, you can
specify the intranet and, optionally, extranet address for Project Server 2003. To do this,
use the following parameters at the command prompt:
AddLocal=PrjSvrDBInfoAS If you want to specify the intranet and
extranet addresses for Project Server 2003,
add the value PrjSvrDBInfoAS to your
AddLocal string.
INTRANETURL=url Specify the intranet URL for Project

Server 2003. For example:
http://redbird/ProjectServer
EXTRANETURL=url Optionally, specify the extranet address for

Project Server 2003. For example:
http://www.example.com/ProjectServer
Enter SMTP Mail Server Information

In Project Server Setup, on the Enter SMTP mail server information page, you can
specify the e-mail server to use for e-mail notifications and reminders. To do this, use the
following parameters at the command prompt:
AddLocal=PrjSvrDBInfoSMTP If you want to specify SMTP mail server
settings, add the value PrjSvrDBInfoSMTP to
your AddLocal string.
SMTPSERVERNAME=server Specify the name of the SMTP mail server.
SMTPSERVERPORT=port number Specify the port number for the SMTP mail
server.
SMTPFROMADDRESS=e-mail address Specify the e-mail address that you want to

appear in the From field on all notification e-
mail messages. Use the format:
someone@example.com
Connect to a Web Server Running Windows SharePoint Services

In Project Server Setup, on the Connect to a Web server running Windows SharePoint
Services pages, you can specify connection information for Windows SharePoint Services.
To do this, use the following parameters at the command prompt:
AddLocal=PrjSvrDBInfoSTS If you want to connect Project Server 2003
to a server running Windows SharePoint
Services, add the value PrjSvrDBInfoSTS to
your AddLocal string.
STSADMINURLTYPE=[http:// | https://] Specify the protocol (http:// or https://) that

is used to access the Windows SharePoint
Services Central Administration site.
STSADMINURLSERVER=server:port Specify the server name and port of the

Windows SharePoint Services Central
Administration site. For example:
tribeca:3456
STSCREATEURLTYPE=[http:// | https://] Specify the protocol (http:// or https://) to

use when connecting to Windows
STSCREATEURLSERVER=path Specify the URL at which to create Windows

SharePoint Services sites. For example:
rockaway:443/sites
STSADMINNAME=username Specify the Windows account for the user

who will administer Windows SharePoint
Services. Use the format domain\user.
STSADMINPWD=password Specify the password for the user account.
Connect to a Web Site Running SharePoint Portal Server 2003

In Project Server Setup, on the Connect to a Web site running Microsoft SharePoint
Portal Server 2003 page, you can specify connection information for Microsoft Office
SharePoint Portal Server 2003. To do this, use the following parameters at the command
prompt:
AddLocal=PrjSvrDBInfoSPS If you want to connect Project Server 2003
to SharePoint Portal Server, add the value
PrjSvrDBInfoSPS to your AddLocal string.
Note: If you use this parameter, you must
also add the value PrjSvrDBInfoSTS to your
AddLocal string and specify connection
parameters for connecting to Windows
SPSURLTYPE=[http:// | https://] Specify the protocol (http:// or https://) to

use when connecting to SharePoint Portal
Server.
SPSURLSERVER=server/portal Specify the Web address for accessing

SharePoint Portal Server. Use the format:
servername/portalname.
SPSPORTALNAME=portal Specify the portal display name. Use the

format: "My Portal".
Choose an Installation Environment

In Project Server Setup, on the Choose an installation environment page, you can
specify whether you want to deploy Project Server 2003 in Enterprise or Non-enterprise
mode. To do this, use the following parameters at the command prompt:
AddLocal=PrjSvrDBInfoSecurityHigh If you want to install Project Server 2003 in
Enterprise mode, add the value
PrjSvrDBInfoSecurityHigh to your AddLocal
string.
AddLocal=PrjSvrDBInfoSecurityLow If you want to install Project Server 2003 in

Non-enterprise mode, add the value
PrjSvrDBInfoSecurityLow to your AddLocal
string.
Enter the Administrator Password

In Project Server Setup, on the Enter the Administrator password page, you can specify
the Administrator password to access Project Web Access. To do this, use the following
parameter at the command prompt:
Note Only use this parameter if you are installing the Project Server Front-End service.
PRJSVRADMINPWD=password Specify the Administrator password for
Project Web Access.
G
Working with the Outlook Add-in
You can use the Microsoft® Office Project Add-in for Outlook® to update tasks from
within Microsoft Outlook 2000 and later versions of Outlook.
Installing the Outlook Add-in

You can install the Outlook Add-in from the Microsoft Office Project Web Access 2003
home page.
X To install the Outlook Add-in
1. Log on to Project Web Access.
2. Click Tasks, and then in the left navigation pane, click View and report on your
tasks from your Outlook calendar.
3. Click Download Now.
Security Settings Required for Installation

To install the Outlook Add-in, you might need to change your security settings in
Microsoft Internet Explorer from the default Disable to Prompt for the option to
download Microsoft ActiveX® controls to your computer. You can change these settings
in Internet Explorer by clicking the Custom Level button on the Security tab in the
Internet Options dialog box located on the Tools menu.
If Microsoft is a trusted source, macros will run in Outlook by using the default macro
security level High.
Connecting to the Computer Running Project Server 2003

When you install the Outlook Add-in from Project Web Access, the server name from
which you are installing the add-in is automatically entered in the Project Server URL field
in the Enter Login Information dialog box in Outlook. A Microsoft Windows® user
account is required if you want to import and update tasks automatically. If, however, you
only want to make manual updates to Project Web Access, you can choose the Project
Server account option. To import tasks from more than one project, you can log on to only
one computer running Project Server 2003 at a time.
Removing the Outlook Add-in from Outlook

Removing the Outlook Add-in from Outlook requires several steps. If you remove the
Outlook Add-in by using the Add or Remove Programs option in Control Panel, some of
the add-in elements are still visible in Outlook, such as the Project Web Access toolbar.
Use the following procedures to remove all elements of the Outlook Add-in:
X To remove the Outlook Add-in from Outlook
1. From Control Panel, select Add or Remove Programs, select Microsoft Office
Project Add-in for Outlook, and click Remove.
2. In Outlook, on the Tools menu, click Customize. On the Toolbars tab, select
Project Web Access, and then click Delete.
X To delete the Project Web Access Appointment form in Outlook
1. From Outlook, on the Tools menu, click Options.
2. On the Other tab, under General, click Advanced Options, click Custom Forms,
and then click Manage Forms.
3. In the Forms Manager dialog box, select Project Web Access Appointment, and
then click Delete.
Note This procedure is optional because the Other tab only appears when you open a Project
Professional task assignment.
You can delete all of your Project Professional tasks from your calendar by using the
following procedure. This procedure is optional. For example, you might want to keep a
record of work done in the past six months.
X To delete all Project Professional tasks from the calendar
• In a current view of all active Project Professional–related appointments, select all
appointments, and then press the DELETE key.
H
Installing Project Web Access ActiveX
Controls
You can install Project Web Access ActiveX® controls on client workstations manually if
your organization operates in a locked-down environment in which users cannot install
OCX controls.
To install ActiveX controls on client computers, you must copy the controls to and register
the controls on the client computers. The following table lists and describes the controls
that you must copy and register.
ActiveX Control Description

pj11xxxc.dll (where xxx is the abbreviation Contains strings and bitmaps used by the
for your language) grid and the text converter.
pjres11c.dll Loads strings and bitmaps from the

resource dynamic-link libraries (DLLs).
pjtextconv11.dll Converts raw numeric data into strings, and

vice-versa.
pjcalendar11.ocx Provides a drop-down calendar for picking

dates.
pjgrid11.ocx Displays task details, the timesheet, and the

Gantt Chart.
pjoutlook11.ocx Pulls task and calendar entries from

Microsoft Outlook® and converts them into
ActiveX Control Description

ActiveX Data Objects (ADO) record sets that
the grid can interpret. This control warns the
user before it reads data from Outlook. It
cannot be used to access Outlook
information without the user being aware.
Note PjOutlook.ocx is marked as unsafe for
scripting.
pjprint11.dll Provides print control.
pjquery11.ocx Acts as a general-purpose control for all

miscellaneous client utility functions.
pjupdate11.ocx Updates tasks and calendar entries from

Project Web Access to the Project
Server database.
pjoffline11.ocx Caches pages for offline use when users

switch to offline mode.
Note You need to have administrative access on the computers on which you will be registering
these controls.
Because there are no specific installation directory requirements, you can copy these
controls to any directory on the client computer; however, you must register them by using
the Regsvr32 tool (Regsvr32.exe).
Important You must register these controls in the order listed above. They are available for
download from the Microsoft Web site Project Server 2003: ActiveX Controls
If you are installing the Project Web Access ActiveX controls for multiple languages, you
must also include the file pj11xxxc.dll (where xxx is the abbreviation for your language) for
each language in the same directory in which you install the other controls. You must
register each of these files by using Regsvr32.exe.
You can deploy the files manually or by using an automated deployment tool such as
Systems Management Server (SMS). For more information about SMS, see the Microsoft
Web site (http://go.microsoft.com/fwlink/?LinkId=20341). You only need to install the controls
once on each computer in order for all users of the computer to have access to them. If
you need to uninstall these controls at any time, you can use Regsvr32.exe to uninstall
them.
I
Service Packs for Project Server
Components
You must install all required service packs for Microsoft® Office Project Server 2003
components in order for your installation to function properly. In addition, some service
packs are required in order for you to enable specific functionality in your environment.
This appendix lists and describes the service packs that are available for Project Server 2003
and related Project Server components.
Note This appendix lists the service packs that are available at the time that this document was
published. Be sure to visit the product pages on the Microsoft Web site for more information about
available service packs.
The following table lists the service packs that are currently available for Project Server
components and provides the download location for each.
Service Pack Description Location
Microsoft Office Project Contains the latest updates to You can download this
Server 2003 Service Microsoft Office Project service pack from the
Pack 1 (SP1) Server 2003. Also contains Microsoft Download Center
significant security (http://go.microsoft.com/fwli
enhancements and stability and nk/?LinkId=33336).
performance improvements.
Some of the updates that are
included in Project Server 2003
SP1 were previously released as
separate updates. Project
Server 2003 SP1 combines the
previously-released updates into

one update.
Microsoft SQL Update to SQL Server 2000. This You can download this
Server™ 2000 Service service pack is required for a service pack from the
Pack 3 Project Server installation. Microsoft SQL Server page
(http://go.microsoft.com/fwli
nk/?linkid=19683). Select
the file sql2k3.exe.
SQL Server 2000 Update to SQL Server 2000 You can download this
Analysis Services Service Analysis Services. This service service pack from the
Pack 3 pack is required for a Project Microsoft SQL Server page
Server installation if your (http://go.microsoft.com/fwli
organization requires the use of nk/?linkid=19683). Select
online analytical processing the file sql2kasp3.exe.
(OLAP) services, which are
required for the Portfolio
Analyzer feature.
Microsoft Office XP Contains the OWS1002.exe You can download this

Service Pack 3 update file. Install this service service pack from the
pack if you are migrating Microsoft Download Center
SharePoint® Team Services from (http://go.microsoft.com/fwli
Microsoft to Microsoft Windows® nk/?LinkId=30880).

Project Server 2003 Installation Guide

Загружено:

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

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

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

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

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

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

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

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

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

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

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

Project Server 2003 Installation Guide

Загружено:

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

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

Microsoft Office Project

Server 2003 Installation Guide

Configuring Windows SharePoint Services Settings.....................................127

Configuring the Front-End Application Server to Support

Windows SharePoint Services Site Migration Tool ..............................................204

Connect to a Web Server Running Windows SharePoint Services ..............238

Microsoft Office Project Server 2003 Online Books Series

• Microsoft Office Project Server 2003 Disaster Recovery Guide

What Can You Learn from This Book?

Who Should Read This Book?

January 2004 • Added Chapter 9, Extranet and Non-

August 2004 • Added Appendix B, Project Server Service

September 2004 • Updated the section Database

Project Server 2003 Components

EPM Solution Architecture

Windows SharePoint Services is an optional component that integrates with Project

Single Computer Installation Roadmap

Example of a single computer deployment.

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

5. Verify network and domain connectivity.

4. To ensure proper connectivity to Analysis Services, migrate the Analysis Services

Small-Scale Installation Roadmap

Example of a small-scale deployment.

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

6. Verify network and domain connectivity.

X To install Windows SharePoint Services

X To perform post-installation tasks

Medium-Scale Installation Roadmap

Example of a medium-scale deployment.

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

6. Verify network and domain connectivity.

X To prepare the servers

Log On By Using a Different Windows User Account in Chapter 8, Post-

Large-Scale Installation Roadmap

Example of a large-scale deployment.

3. Install SQL Server 2000 on the appropriate computer.

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

6. Verify network and domain connectivity.

in the topic Configure SQL Server Authentication in Chapter 4, Prepare the

Upgrading from Microsoft Project Central or Microsoft Project

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

UPG09DB.CMD PROJSQL2000 ProjectCentral sa hello

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

Upgrading from Microsoft Project Server 2002 and MSDE

2. Uninstall Microsoft Project Server 2002 and MSDE 2000.

X To upgrade from Microsoft Project Server 2002 and MSDE 2000

Note There might be a long delay after running this command.

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

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

where strong_pwd is your System Administrator (sa) password.

Note There might be a long delay after running this command.

Migrating from SharePoint Team Services

Requirements for Migrating from SharePoint Team Services

Limitations to Migrating to Windows SharePoint Services

Migrating a SharePoint Team Services Site to Windows

X To migrate a SharePoint Team Services site to Windows SharePoint Services

prompt, change to your CD-ROM drive and change to the \SUPPORT\PSMIGRAT

For example, you can run the following:

For each subweb, PSMigrat.exe does the following:

Create User Accounts

X To create a Windows domain user account

X To create a local user account

5. In Description, type a description for the user account.