US 1.877.212326.2662
Browse Search
HOWTO: Migrate PM Central 4.1/4.2 from SharePoint 2010 to SharePoint 2013
Created on: 22-May-13. Print Article
Last Modified on: 30-Apr-15. Email Article
Skill Level: Intermediate.
Article has been viewed: 17893 times.
Rated: 0 out of 10 based on 0 votes.
KB.12978

APPLIES TO:

Follow the steps below to perform an in-place upgrade of PM Central R4.1/4.2 from SharePoint 2010 to SharePoint 2013 using the database attach and upgrade method. For more information on this method, see the following Microsoft articles:

See the Known Issues and Limitations section for issues and limitations regarding the in-place upgrade.

Performing an In-Place Upgrade of PM Central:

  1. In your SharePoint 2010 environment, upgrade your existing PM Central sites to R4.1 or higher for SharePoint 2010.
    Warning: The version requires to be the same version in both environments (SP2010 & SP2013), i.e. migrate only from R4.1 SP2010 to R4.1 SP2013 only and not migrate from R4.1 SP2010 to R4.0 SP2013.
    Note: For customers who have PM Central older than 4.1 on SharePoint 2010, follow the upgrade from the online doc first prior to proceeding with the migration steps below. If you are using Alert Plus for alerts and reminders, please follow the steps in the article KB.12986 for the in-place upgrade steps for Alert Plus. 
     
  2. Back up your content database for the port that contains the PM Central sites, for example port 80.
     
  3. In your new SharePoint 2013 environment, create a new Web application using a new port, for example 81.
     
    Note:
    If you are creating new sites in your SharePoint 2013 environment, you can use port 80. If you have existing sites in port 80, you must use a different port and create new sites for PM Central. This is because when you dismount or delete the content database for the new port (such as 81) and then override the new database (for port 81) with the old content database (from port 80), the original data in the database for port 81 will be lost.
     
  4. In your SharePoint 2013 environment, deploy PM Central R4.1 (or higher) for SharePoint 2013 to this web application.
     
  5. Dismount or delete the content database for the new port, for example port 81.  Bamboo recommends dismounting the database. Do not do both. See these Microsoft articles for more information on dismounting or deleting content databases.
     
  6. In SQL Server, restore the content database from your SharePoint 2010 environment to your SharePoint 2013 environment by overriding the existing database for the new port, for example port 81. The account restoring the database must have permissions to the database. See this Microsoft article on restoring content databases for more information.
     
  7. Add the content database. See this Microsoft article for more information on adding databases. In SharePoint Central Administration > Manage Web Applications > Manage Content Databases, the Database Status for the content database should be Upgrading.
  8. Run command line to upgrade users in Share point 2013.
    Go to Start > Microsoft Share point 2013 > Share point 2013 Management Shell ( run as Administrator) and input command line as:

       Convert-SPWebApplication -Identity "http:// :port" -To Claims


    Then enter Y to continue. See picture follow:

    navigate to Central Administration

  9. Restart Internet Information Services (IIS): Go to Start > Run. Enter iisreset, and press Enter.
     
  10. When you are ready to perform the in-place upgrade, run the Bamboo PM Central Administration component in the PM Central Setup program:
     

    Prepare your SharePoint farm for the installation. On all servers in the SharePoint farm running the Microsoft SharePoint Foundation Web Application service, go to Start > Administrative Tools > Internet Information Services (IIS) Manager and stop the Application Pools:

    1. Stop the Application Pools on all servers. Do this step first. This prevents users from accessing sites during installation, and unlocks files that may need to be updated.
      • Restart the SharePoint Timer service on all servers. Do this step even if the service is currently running.
      • Restart the SharePoint Administration service on all servers. Do this step even if the service is currently running.
    2. On the SharePoint server where you extracted the PM Central installation files, run the Setup program by double-clicking the Setup.bat file. In the Optional Items section of the Setup program, click Bamboo PM Central Administration , and then click Install.

    3. Click Next and wait while the system checks are completed, and then click Next.

      system checks

    4. Click Upgrade/Repair Existing and Install New option and click Next.

      select 'Remove All'

    5. Wait while the component is repaired, and then click Next. Review the summary log to make sure that the repair was successful. Click Close.

      review the Summary log

    6. Restart the SharePoint 2013 Timer service: Go to Start > Administrative Tools > Services. Right-click on SharePoint Timer Service and select Restart.
    7. Run iisreset .
  11. Before performing the in-place upgrade for PM Central sites, it is required to upgrade all the site collections of the web application (example port 81) for Share point 2013. Go to the root site of the site collection > Site Settings > Site Collection Upgrade

    Site Collection Upgrade

    Upgrade

    Notes:
    1. If the step above is not performed, the application cannot perform the in-place upgrade for PM Central sites and in the Project Central Upgrade Monitoring Page in Central Administration the following warning message will be displayed:
      Warning: Site collection of this site has not yet upgraded to SharePoint 2013. It needs to upgrade first before upgrading this site.


    2. If the upgraded database has many language sites ( such as: German, French,...etc.), then you require to install the language packages for SharePoint 2013 before the upgrade.

  12. Complete the in-place upgrade by upgrading PM Central sites. Go to SharePoint Central Administration and click Project Central Upgrade Monitoring Page. Select the Web application and port you are upgrading and click the Upgrade button below the list of PM Central sites. Verify that you want to proceed, and then wait for the upgrade to finish. While a site is being upgraded, its status will be listed as Upgrade in Progress. Warning: Before upgrading sites, you must restart the SharePoint Timer Service as instructed in Step 10f above. If you do not do this, the upgrade will fail.

    navigate to Central Administration


    Click Upgrade button and waiting it in-place:


    When the upgrade is finished, the status for each PM Central site should be "[In-Place] Upgrade to v4.* completed on date and time. If the status for all sites remains in progress for an excessive amount of time, restart the SharePoint Timer Service. If the status remains in progress after restarting the SharePoint Timer Service and after a long wait, restart the server, return to the Project Central Upgrade Monitoring Page, and click the Upgrade button again.

  13. Activate the license key for PM Central for SharePoint 2013. See the following KB articles for more information about licensing:
  14. PM Central has successfully been migrated from SharePoint 2010 to SharePoint 2013.
  15. Note: If you are using Alert Plus for alerts and reminders with version older than 3.2 for SharePoint 2010, please follow the steps in the article KB.12986 for the in-place upgrade steps for Alert Plus.

Known Issues and Limitations

See below for information about known issues and limitations. For additional information, see the release notes.

Known Issues:

  • Before running the in-place upgrade, sites that are not PM Central sites will be displayed as sites that have been upgraded to R4.* in Central Administration in the Project Central Upgrade Monitoring Page.
  • For project sites with unique permissions where users do not have access to the portfolio site, users can still access the information from the Enterprise Resource Pool in the Contacts List.
  • When viewing the Contacts Lists at the project site after running the in-place upgrade, the Resource column is blank. The workaround is to edit each contact item and click OK.
  • After running the in-place upgrade and when project sites have unique permissions, the Project Portfolio Dashboard on the portfolio site's Schedules tab displays project sites to users who do not have access to some of the projects.
  • On the portfolio site's, the Gantt chart for Resource Assignments always shows No Group when users select the View By Enterprise Resource Pool view.
  • When the project site has been created from a saved lite template and the tasks belonging to this project are not edited again, then the Resource Work By Project and Resource Work by Project Department tabs under Report Center on the portfolio site will display an error. This issue only occurs when migrating from SP2010 to SP2013. The workaround is to edit and save the tasks of this project site - where the project site was created from a saved lite template.

Limitations:

  • Any customizations made to the sites (master pages, CSS, logos, etc.) will not be retained after running the in-place upgrade to SharePoint 2013.
  • Does not support SharePoint 2010 look and feel.
  • The upgrade must be run on a new SharePoint 2013 server with content that was upgraded from a SharePoint 2010 server using the database attach and upgrade method. Upgrading PM Central on a server that was upgraded from SharePoint 2010 to SharePoint 2013 (Foundation or Server) on the same hardware will not work.
    Related Articles
    No Related Articles Available.

    Article Attachments
    No Attachments Available.

    Related External Links
    No Related Links Available.
    Help Us Improve This Article
    What did you think of this article?

    poor 
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10

     excellent
    Tell us why you rated the content this way. (optional)
       
    Approved Comments
    No user comments available for this article.