Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

(833422) - Describes how to move your Project Server 2002 and SharePoint Team Services Web site to a new server.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
Article ID: 833422 - Last Review: September 18, 2011 - Revision: 3.0

How to move your Microsoft Project Server 2002 and SharePoint Team Services Web site to a new server

View products that this article applies to.

INTRODUCTION

This article describes the steps that you must take to move your Microsoft Project Server 2002 and SharePoint Team Services from Microsoft Web site to a new server.

MORE INFORMATION

To move your Project Server 2002 and SharePoint Team Services Web site to a new server, follow these steps:
  1. Install Microsoft Office XP Service Pack 1 (SP-1) or later to your old server.

    Note You must do this before you back up your database files.
  2. Back up your Project Server 2002 database and your SharePoint Team Services database in Microsoft SQL Enterprise Manager. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
    323330  (http://kbalertz.com/Feedback.aspx?kbNumber=323330/ ) How to back up, schedule, and restore a Microsoft Project Server database
  3. Back up the inetpub\Wwwroot folder by using the Backup System tool.

    Note All your subweb folders are created in the Wwwroot folder. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
    301420  (http://kbalertz.com/Feedback.aspx?kbNumber=301420/ ) How to use Windows backup and recovery tools to make a data backup of Internet Information Services
  4. Copy these newly created database and Wwwroot backup files from the old server to your new server.
  5. Install Microsoft SQL Server 2000, Microsoft SQL Server 2000 Analysis Services, and all appropriate current service packs on your new computer.
  6. Restore your Project Server 2002 database to your new SQL Server. To do this, follow these steps:
    1. Click Start, point to Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
    2. Expand Microsoft SQL Servers, expand SQL Server Group, and then expand your SQL server.
    3. Right-click the Database folder, point to All Tasks, and then click Restore Database.
    4. In the Restore as database text box, type a name for your Project Server 2002 database, and then click From Device.
    5. Click Select Devices.
    6. In the Choose Restore Devices dialog box, click Add.
    7. In the Choose Restore Destination dialog box, click File name, and then click the ellipsis button (…).
    8. Locate, and then select the backup database file for the Project Server 2002 database. Click OK four times.
    9. After the restoration is complete, click OK.
  7. Delete the MSProjectServerUser and the MSProjectUser SQL accounts from your restored Project Server 2002 database.

    Note These accounts are located in the right pane when you expand your Project Server 2002database in SQL Enterprise Manager, and then click Users.
  8. In SQL Enterprise Manager, follow these steps:
    1. Create the MSProjectServerUser account. To do this, expand the Security folder, and then click Logins.
    2. Click SQL Server Authentication, and then type a password in the Password text box.
    3. Select the default database as your newly restored Project Server 2002 database.
    4. On the Database Access tab, select your ProjectServer 2002 database, and then select both Public and MSProjectServerRole permissions in Permit in Database Role. Confirm the new password.
  9. In SQL Enterprise Manager, follow these steps:
    1. Create the MSProjectUser account. To do so, expand the Security folder, and then click Logins.
    2. Click SQL Server Authentication, and then type a password in the Password text box.
    3. Select the default database as your newly restored Project Server 2002 database.
    4. On the Database Access tab, select your Project Server 2002 database, and then select both the Public and MSProjectRole permissions in Permit in Database Role. Confirm the new password.
  10. Install Project Server 2002, and then choose to use the existing database for Project Server 2002.

    When you are prompted to do so, type the MSProjectServerUser and MSProjectUser accounts and their corresponding passwords that you created in steps 8 and 9.
  11. Choose to configure information for Analysis Server and Simple Mail Transfer Protocol(SMTP), but choose to configure SharePoint Team Services later.
  12. Run the PSComplus.exe utility. To do this, follow these steps:
    1. Right-click Start, and then click Explore to start Microsoft Windows Explorer.
    2. Locate the following folder:
      drive:\Program Files\Microsoft Project Server\Bin\1033
    3. Double-click the Pscomplus.exe utility.
    4. Type the appropriate Windows user account and password in the Username and Password boxes under Analysis Services (OLAP) Access Identity, SharePoint Team Services Administration Identity, and SharePoint Team Services Database Access Identity.
    5. Click Create\Update COM+ Apps.
    Note This account must be a member of the Administrators group on the new SharePoint Team Services server.
  13. Run the SharePoint Configuration Wizard to install SharePoint Team Services from Microsoft. Note the SharePoint Administration Port number.
  14. Restore your SharePoint Team Services database with the same name as your original database name on your new SQL Server. To do this, follow these steps:
    1. Click Start, point to Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
    2. Expand Microsoft SQL Servers, expand SQL Server Group, and then expand your SQL server.
    3. Right-click the newly installed SharePoint Team Services Database , point to All Tasks, and then click Restore Database.
    4. In the Restore as database text box, type the exact name of the SharePoint Team Services database that you moved from the old server, and then click From Device.
    5. Click Select Devices.
    6. In the Choose Restore Devices dialog box, click Add.
    7. In the Choose Restore Destination dialog box, click File name, and then click the ellipsis button (…).
    8. Locate, and then select the backup database file for the SharePoint Team Services database. Click OK four times.
    9. After the restoration has completed, click OK.
    10. You will see two SharePoint Team Services databases. Delete the one that was not just restored.
  15. Delete all user accounts except for the system administrator (SA) account under the newly restored database.
  16. Re-create the Windows user account that you used in step 13. To do this, expand the Security folder, click Logins, and then select your restored SharePoint database as the default database.

    On the Database Access tab, select your SharePoint database, and then set the permission to Public and db_datareader in Permit in Database Role.
  17. Click Start, point to All Programs, point to Administrative Tools, and then click Microsoft SharePoint Administrator.
  18. Click the Administration hyperlink for the SharePoint Team Services Web site that you installed, and then click Change database connection.
  19. Change the database name to the restored SharePoint database name, type your database administrator name and password, type your database server name, and then click Submit.
  20. Run ProxyCfg from the Command Prompt (found in drive:\Program Files\Microsoft Project Server\Bin) with the syntax that is appropriate for your configuration environment.
    • If you are in a proxy server environment, type the following, where the YourProxyServer parameter is your proxy server name:
      proxycfg -d -p "YourProxyServer" "local"
    • If you are not in a proxy server environment, type the following:
      proxycfg -d -p "proxyserver" "local"
    • If you are using a Fully Qualified Domain Name (FQDN) as the server name for SharePoint Team Services, such as servername.mycompany.com, type your FQDN information, for example type:
      proxycfg -d -p "YourProxyServer" "local;servername.mycompany"
  21. Stop, and then restart Microsoft Internet Information Services (IIS). To do this, follow these steps:
    1. Click Start, and then click Run.
    2. In the Open box, type cmd, and then click OK.
    3. At the command prompt, type iisreset, and then press ENTER.
    4. After the reset is complete, type exit at the command prompt, and then press ENTER.
  22. Click Create Subweb for each project to re-create the subweb again.
  23. Log on to Microsoft Project Web Access as the administrator.

    Click Manage SharePoint Team Services, and then click Modify Server. Change the SQL server name, the SharePoint administration port, and the SharePoint server name to reflect the settings on the new server, and then save the changes. The "Connect to servers" page should appear.
  24. On the "Connect to servers" page, click Manage Subwebs, and then delete all the subwebs except for the MS_ProjectServer_PublicDocuments subweb.
  25. Click Create Subweb for each project to re-create the subweb again.
  26. Rebuild the OLAP Cube, and then re-create the Views for Portfolio Analyzer.
APPLIES TO
  • Microsoft Project Server 2002
  • Microsoft SharePoint Team Services
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Analysis Services
Back to the top
Keywords: 
kbhowto KB833422
        

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting