Deploy Office SharePoint Server 2007 to an existing deployment of Project Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.

 

Topic Last Modified: 2008-04-04

This article describes how to deploy Microsoft Office SharePoint Server 2007 on an existing deployment of Microsoft Office Project Server 2007. This is one of three deployment scenarios used in deploying Office SharePoint Server 2007 with Office Project Server 2007. The other two scenarios are:

• Deploy Project Server 2007 to an existing deployment of Office SharePoint Server 2007

• Deploy Office SharePoint Server 2007 and Office Project Server 2007 to a new environment

For additional information about deploying Office SharePoint Server 2007 with Office Project Server 2007, see Deploy Office Project Server 2007 with Office SharePoint Server 2007.

Important

Before installing Office Project Server 2007 or Office SharePoint Server 2007, it is very important to thoroughly plan for the deployment. For information on planning for Office Project Server 2007, see Planning and architecture for Office Project Server 2007. For information on planning for Office SharePoint Server 2007, see Planning and architecture for Office SharePoint Server 2007.

Deployment overview

This scenario is typically used in an environment in which a Office Project Server 2007 farm is deployed, its services are in use, and your organization wants to integrate Office SharePoint Server 2007 functionality. Another common scenario is that the organization wants to enable the Office Project Server 2007 proposal feature, which requires Office SharePoint Server 2007 workflows.

For information about the advantages of integrating Office SharePoint Server 2007 with Office Project Server 2007, see Deploy Office Project Server 2007 with Office SharePoint Server 2007.

Installing Office SharePoint Server 2007 on an existing Office Project Server 2007 farm involves the following general steps that need to occur on each server in the farm:

1. Install Office SharePoint Server 2007 on all computers in the Office Project Server 2007 farm.

2. Start the Office SharePoint Server Search service.

3. Start the Windows SharePoint Services Search service (optional).

4. Configure additional Office SharePoint Server 2007 services.

When installing Office SharePoint Server 2007 to an existing Office Project Server 2007 farm, prior to configuring the Shared Services Provider to use any additional Office SharePoint Server 2007 services, you need to determine which Office SharePoint Server 2007 services you plan on using. For example, if you plan on using the Excel Calculation Services functionality, you need to determine what the requirements are for using this service.

Note

For more information on Office SharePoint Server 2007 services, see Planning and architecture for Office SharePoint Server 2007.

Additional configuration is required to enable the Office Project Server 2007 proposal feature. This information is in the Deployment requirements for the Project Server 2007 Proposals feature section of this article.

Quiescing the farm

Prior to deploying Office SharePoint Server 2007 with Office Project Server 2007, it is important to plan when to quiesce the farm (gradually take the farm offline). The farm needs to be offline when installing binary files to a server on the farm so that it receives no incoming requests. This enables the farm to be in a consistent state after the binary files are installed to servers in the farm and the farm is brought back online.

The process of quiescing the farm can be performed through the SharePoint Central Administration Web site.

Note

You can run the SharePoint Products and Technologies Configuration Wizard on each server after resetting the farm.

Install Office SharePoint Server 2007 on all Project Server 2007 Front-end Web and Application Servers

On all of the Office Project Server 2007 front-end Web and application servers, you need to install the Office SharePoint Server 2007 binary files and then run the SharePoint Products and Technologies Configuration Wizard.

Note

For detailed information about installing Office SharePoint Server 2007, see Deploy Office SharePoint Server 2007 in a server farm environment.

Install Office SharePoint Server 2007

Important

Installing the Office SharePoint Server 2007 binary files and running the SharePoint Products and Technologies Configuration Wizard is required on all servers in the Office Project Server 2007 farm. Afterwards you can turn on the services you want to run on each server through Central Administration.

When installing the Office SharePoint Server 2007 binary files to servers in an existing Office Project Server 2007 farm, the installation will auto-sense the Office Project Server 2007 server type installed to the computer and will then install the appropriate Office SharePoint Server 2007 server type. For example, if a server is installed as a Office Project Server 2007 application server, the Office SharePoint Server 2007 installation will detect the server type and will automatically install the Office SharePoint Server 2007 application server binary files. This makes the process of installing the Office SharePoint Server 2007 binary files identical on different server types.

To install Office SharePoint Server 2007 to a server in a Office Project Server 2007 farm, do the following on each server:

1. Navigate to the installation location for Office SharePoint Server 2007, and then double-click the Setup.exe file to begin the setup process.

2. On the Enter your Product Key page, type the 25-character product key, and then click Continue.

3. On the Read the Microsoft Software License Terms page, view the terms of the agreement. Select I accept the terms of the agreement, and then click Continue. This will start the installation of the binary files.

4. When installation of the binary files is completed, a page that prompts you to run the SharePoint Products and Technologies Configuration Wizard is displayed. Verify that Run the SharePoint Products and Technologies Configuration Wizard now is selected if you want to run it now, and then click Close.

   If you choose to run the SharePoint Products and Technologies Configuration Wizard at a later time, click to clear the check box, and then click Close. To start the SharePoint Products and Technologies Configuration Wizard later, click Start, click All Programs, click Microsoft Office Server, and then click SharePoint Products and Technologies Configuration Wizard.

Run the SharePoint Products and Technologies Configuration Wizard

After installing the Office SharePoint Server 2007 binary files on each front-end Web and application server in the farm, you need to run the SharePoint Products and Technologies Configuration Wizard on each server. To do this, after installing the binary files on a server in the farm, perform the following steps:

1. After starting the SharePoint Products and Technologies Configuration Wizard, the Welcome to SharePoint Products and Technologies page appears, stating that the wizard will upgrade SharePoint Products and Technologies. Click Next.

2. Click Yes to the message alerting you that specified services might need to be restarted or reset during the installation. These services will include:

   • Internet Information Services

   • Windows SharePoint Services Administration Service

   • Windows SharePoint Services Timer Service

3. In the Completing the SharePoint Products and Technologies Configuration Wizard page, the configuration will point to the existing configuration settings for the Office Project Server 2007 farm. Click Next to start the configuration process.

4. When configuration is finished, the Configuration Successful page displays the configuration settings. Click Finish. This will automatically start Central Administration.

Start the Office SharePoint Server Search service

The Office SharePoint Server Search service is based on the search service that is provided with earlier versions of SharePoint Products & Technologies, but with many improvements. You should use the Office SharePoint Server Search service to crawl and index all content that you want to be searchable (other than the Help system).

Important

It is important to understand how you plan to crawl and index content in your environment. For more information on the Office SharePoint Server Search Service, see Plan search (Office SharePoint Server).

Starting the Office SharePoint Server Search service requires you to designate Index and query servers. Once you have determined which server in your farm will serve as an Index server and query server, use the following steps on that server to start the Office SharePoint Server Search service.

Note

An Index server can only be designated on an application server in the farm. We also recommend that a dedicated application server be used for indexing. Do not use a Project Server application server for indexing. Doing so would have an adverse affect on throughput.

Start the Office SharePoint Server Search service on the index server

1. On the Central Administration home page, click the Operations tab on the top link bar.

2. On the Operations page, in the Topology and Services section, click Services on server.

3. In the Server list, select the server that you want to configure as an index server and optionally a query server.

4. On the Services on Server page, next to Office SharePoint Server Search, click Start.

5. Select the Use this server for indexing content check box. This expands the page and adds the Index Server Default File Location, Indexer Performance, and Web Front End and Crawling sections.

   Note

   Properly plan your Indexer Performance settings. Indexing is very resource intensive and could affect performance when run with other application services. If you plan on running the Project Application service on an index server, you may want to run indexing at reduced or partially reduced settings.

6. If you want to use this server to service search queries, select the Use this server for servicing search queries check box. This expands the page and adds the Query Server Index File Location section. If not, skip to the next step.

7. In the Contact E-mail Address section, type the e-mail address you want external site administrators to use to contact your organization if problems arise when their sites are being crawled by your index server.

8. In the Farm Search Service Account section, specify the User name and Password of the account under which the search service will run. This account must be a member of the Administrators group on the server and be a member of the Farm Administrators group in the Central Administration Web site (the WSS_ADMIN_WPG Windows security group).

9. Optionally, you can also configure other settings or accept the default settings.

10. When you have configured all the settings, click Start.

You can optionally use the following steps to start the Office SharePoint Server Search service to deploy query servers. Query servers can only be deployed to application servers in the farm.

Important

If you selected the Use this server for serving search queries option in step 6 of the previous procedure, you cannot deploy additional query servers unless you first remove the query server role from the index server.

Start the Office SharePoint Server Search service on query servers

1. On the Central Administration home page, click the Operations tab on the top link bar.

2. On the Operations page, in the Topology and Services section, click Services on server.

3. In the Server list, select the server that you want to configure as a query server.

4. On the Services on Server page, next to Office SharePoint Server Search, click Start.

5. Select the Use this server for servicing search queries check box. This expands the page and adds the Query Server Index File Location section.

6. In the Farm Search Service Account section, specify the User name and Password of the account under which the search service will run. This account must be a member of the Administrators group on the server and be a member of the Farm Administrators group in the Central Administration Web site (the WSS_ADMIN_WPG Windows security group).

7. In the Query Server Index File Location section, in the Query server index file location box, either type the location on the local drive of the query server on which you want to store the propagated index or accept the default path.

8. In the Query Server Index File Location section, select one the following:

   • Configure share automatically   Select this option to automatically configure the share on which you want to store the propagated index. Type the user name and password of the account that you want to use to propagate the index. (Recommended)

     Important

     This account must a member of the Administrators group and a member of the WSS_ADM_WPG group on the query server before you proceed to the next step or propagation of the index will fail.

   • I will configure the share with STSAdm   Select this option if you want to use the Stsadm.exe command-line tool to create this share at a later time.

   • Do nothing. The share is already configured   Select this option if the share already exists and the permissions to the share are configured as described above.

9. When you have configured all the settings, click Start.

Start the Windows SharePoint Services Search service (optional)

You must start the Windows SharePoint Services Search service on every computer that you want to search over Help content. If you do not want users to be able to search over Help content, you do not need to start this service.

Start the Windows SharePoint Services Search service (optional)

1. On the Central Administration home page, click the Operations tab on the top link bar.

2. On the Operations page, in the Topology and Services section, click Services on server.

3. In the Server list, select the server on which you want to start the service.

4. On the Services on Server page, next to Window SharePoint Services Search, click Start.

5. On the Configure Windows SharePoint Services Search Service Settings page, in the Service Account section, type the user name and password for the user account under which the Windows SharePoint Services Search service account will run.

6. In the Content Access Account section, type the user name and password for the user account that the search service will use to search over content. This account must have read access to all the content you want it to search over. If you do not specify credentials, the same account used for the search service will be used.

7. In the Indexing Schedule section, either accept the default settings, or specify the schedule that you want the search service to use when searching over content.

8. After you have configured all the settings, click Start.

Configure additional Office SharePoint Server 2007 services

You may want to configure additional Office SharePoint Server 2007 services that are available to you. For information on configuring additional Office SharePoint Server 2007 services, see the following articles:

• Chapter overview: Configure personalization

• Chapter overview: Configure business intelligence features

• Chapter overview: Configure Excel Services

• Configure InfoPath Forms Services for Office SharePoint Server

• Configure usage reporting

  Note

  Prior to configuring these services, we recommend that you see Planning and architecture for Office SharePoint Server 2007 for planning information on the services you intend to use.

Deployment requirements for the Project Server 2007 Proposals feature

In order to enable the automated project proposals feature in Office Project Server 2007, additional configuration is required. This additional work includes the following procedures:

1. Restrict access to non-approved proposals.

2. Add the Approval workflow as the project proposal workflow.

3. Add the UID for the proposal workflow to the ProjectServer_Published database.

4. Configure the State field to be governed by an external workflow.

5. Add proposals creators and reviewers to the Proposal Reviewers security group.

6. Add the Web part for Proposal Workflow Tasks to Project Web Access.

   Note

   These additional configuration steps are only required in the scenario in which you are adding Office SharePoint Server 2007 to and existing Office Project Server 2007 deployment and want to use the automated project proposals feature. If, on the other hand, you are adding Office Project Server 2007 to an existing Office SharePoint Server 2007 deployment, you are not required to do these additional configuration steps to use the automated project proposal feature.

   Note

   For more information about project proposals, see Create projects.

Restrict access to non-approved proposals

Enabling the Require content approval for submitted items option is a security measure that prevents non-approved proposals from being shown to unauthorized users. When this setting is enabled, only the proposal creator and proposal reviewers are able to view non-approved proposals.

Enable the "Require content approval for submitted items" option

1. In Project Web Access, in the Quick Launch, in the Documents section, click Shared Documents.

2. On the "Shared Documents" page, in the Quick Launch, click View All Site Content.

3. On the "All Site Content" page, in the List section, click Proposal Proxy list.

4. On the "Proposal proxy list" page, click Settings, and then click List Settings.

5. On the "Customize Proposal proxy list" page, in the General Settings section, click Versioning settings.

6. On the "List Versioning Settings: Proposal proxy list" page, in the Content Approval section, for the Require content approval for submitted items option, select Yes, and then click OK.

Add the approval workflow as the project proposal workflow

To use project proposals in an automated manner, a Office SharePoint Server 2007 workflow must be added through the Customize Proposal proxy list page. The Approval workflow is a default Office SharePoint Server 2007 workflow needed by the automated project proposals feature.

Note

For more information about the Approval workflow, see What are workflows?.

Add the Approval workflow as the project proposal workflow

1. On the "Customize Proposal proxy list" page, in the Permissions and Management section, click Workflow settings.

2. On the "Change Workflow Settings: Proposal proxy list" page, click Add a workflow.

3. On the "Add a Workflow: Proposal proxy list" page, in the Workflow section, from the Select a workflow template list, select Approval.

4. In the Name section, in the Type a unique name for this workflow box, type Project Proposal Workflow.

5. In the Start Options section, click Allow this workflow to be manually started by an authenticated user with Edit Items Permissions. Click Next.

6. On the "Customize Workflow: Project Proposal Workflow" page, in the Post-completion Workflow Activities section, select Update the approval status (use this workflow to control content approval).

   Note

   Do not configure anything else on this page or click OK yet.

7. From the end of the URL for this page, copy the unique identifier (UID). The UID is contained in the query string value and consists of 32 hexadecimal characters surrounded by curly braces at the end of the URL (for example, {9E541880-3580-4484-B1E4-196B47D07AF8}). You will need this UID for the next procedure.

8. Click OK.

Add the unique identifier for the project proposal workflow page to the ProjectServer_Published database

After copying the UID from the Customize Workflow: Project Proposal Workflow page, you must add the UID value to the ProjectServer_Published database.

Add the UID value from the Customize Workflow: Project Proposal Workflow page to the ProjectServer_Published database

1. Start SQL Server 2005 Management Studio and log on to the Database Engine.

2. In SQL Server 2005 Management Studio, in the Object Explorer pane, expand the Databases folder, and then expand the ProjectServer_Published folder. Expand the Tables folder and locate the dbo.MSP_WEB_ADMIN table. Right-click the entry and click Open Table.

   The table opens in the document window.

3. Scroll to the WADMIN_PROPOSAL_LIST_UID column. For the column value, enter the UID you copied from the Customize Workflow: Project Proposal Workflow page in the previous procedure (for example, {9E541880-3580-4484-B1E4-196B47D07AF8}). Be sure to include the curly braces.

4. Scroll to the WADMIN_IS_PROPOSAL_DLC_INSTALLED column. Change the value for this column to True.

5. On the File menu, choose Save All.

Configure the State field to governed by an external workflow

Each project proposal has a State field that provides its current status (either proposed, approved, or rejected). The State field is workflow-aware, meaning that it can be configured to work with workflows that are available through Office SharePoint Server 2007. To use project proposals in an automated manner, the State field must be configured to work with the Office SharePoint Server 2007 workflow selected for project proposals. When the State field is configured to be governed by an external workflow, the field is read-only in Project Web Access and cannot be changed manually.

Note

If you intend to use the project proposal feature manually (in which a workflow is not used), the Is the state field governed by an external workflow value can be set to No.

Configure the State field to be governed by an external workflow

1. In Project Web Access, in Quick Launch, click Server Settings.

2. On the Server Settings page, in the Operational Policies section, click Additional Server Settings.

3. On the Additional Server Settings page, in the Project State Field section, for the Is the state field governed by an external workflow option, select Yes.

4. Click Save.

Add proposal creators and reviewers to the Proposal Reviewers security group

Users within your organization who need to create and review proposals must have the required permissions. You can add these users to the Proposal Reviewers security group. The Proposal Reviewers security group is a default group that is installed with Office Project Server 2007 and provides users permissions that are needed to create and review proposals. You can edit the default permissions for this group.

Note

For details about the default permissions allowed for the Proposal Reviewers security group, see Microsoft Office Project Server 2007 default group and template permissions.

Add users to the Proposal Reviewers security group

1. In Project Web Access, in Quick Launch, click Server Settings.

2. On the "Server Settings" page, in the Security section, click Manage Users.

3. On the "Manage Users" page, in the User Name list, click the user to which you want to add the permission.

4. On the "Edit User" page for the selected user, in the Security Groups section, select Proposal Reviewers from the Available Groups list.

5. Click Add. Proposal Reviewers will now appear in the Groups that contain this user list.

6. Click Save.

Add the Web part for Proposal Workflow Tasks to Project Web Access

When a proposal is created, the proposal workflow generates task assignments for proposal reviewers and the creator as the proposal makes its way through the proposal process. These tasks are shown to their owners through the Web part for Proposal Workflow Tasks. We recommend adding this Web part to the Project Web Access home page of all users who create or review proposals.

Add the Proposal Workflow Tasks Web part to the Project Web Access home page

1. On the Project Web Access Home page, click Site Actions, and then click Edit Page.

2. On the Edit Mode version of your Project Web Access Home page, select a location in which you want to embed the Web part (Header, Left, Middle, Right, or Footer). In this location, click Add a Web Part.

3. On the "Add Web Parts Web Page Dialog" page, in the List and Libraries section, select Proposal Workflow Tasks, and then click Add.

4. On the Edit Mode version of your Project Web Access Home page, verify that the Web part named Proposal Workflow Tasks appears in the proper location. Click Exit Edit Mode.

Use project proposals manually

Project proposals can also be used without automation. If you are going to use project proposals manually, then you do not need to install Office SharePoint Server 2007, because the workflow component is not needed. Because the workflow component is not used, proposal creators and reviewers must manually set the State field. To allow proposal creators and reviewers to set the value of the State field in Project Web Access, you must:

• Configure the State field to not be governed by an external workflow

• Grant the Change Project State security permission to your proposal creators and reviewers. This global permission is automatically assigned to the Proposal Reviewers security group.

Configure the State field to not be governed by an external workflow

1. In Project Web Access, in Quick Launch, click Server Settings.

2. On the "Server Settings" page, in the Operational Policies section, click Additional Server Settings.

3. On the "Additional Server Settings" page, in the Project State Field section, for the Is the state field governed by an external workflow option, select No.

4. Click Save.

Uninstalling from an Office SharePoint Server/Project Server 2007 deployment

Removing either Office SharePoint Server 2007 or Office Project Server 2007 from a joint installation is not supported. Installing Office SharePoint Server 2007 with Office Project Server 2007 extends the farm schema, and it cannot be undone by uninstalling one of the applications.

See Also

Concepts

Deploy Office Project Server 2007 with Office SharePoint Server 2007
Deploy Project Server 2007 to an existing deployment of Office SharePoint Server 2007
Deploy Office SharePoint Server 2007 and Office Project Server 2007 to a new environment
Planning and architecture for Office Project Server 2007
Deploy Project Server 2007 to a server farm environment

Other Resources

Planning and architecture for Office SharePoint Server 2007
Deploy Office SharePoint Server 2007 in a server farm environment