Freigeben über

Dynamics CRM 2016 Upgrade - Complete Guide

  • Artikel

This blog post talks about the possible upgrade paths and provide guidance, which could be followed in order to a successful upgrade to the Dynamics CRM 2016 Sp1. As the only supported upgrade path to Microsoft Dynamics CRM Server 2016 is from Microsoft Dynamics CRM Server 2015, hence this blog post talks about an upgrade from Dynamics CRM 2015. If you have any previous versions of the Dynamics CRM installed then I would suggest upgrading to the Dynamics CRM 2015 first. For more information on upgrade from previous versions of Dynamics CRM, you could refer this: https://technet.microsoft.com/en-us/library/hh699673.aspx . I have tried to covers some basic guidelines on Dynamics CRM Upgrade which could be useful to you.

The only supported upgrade path to Microsoft Dynamics CRM Server 2016 is from Microsoft Dynamics CRM Server 2015. Microsoft Dynamics CRM 2015 server roles are not compatible with a Microsoft Dynamics CRM Server 2016 deployment. Therefore, after you upgrade the first Microsoft Dynamics CRM Server, other Microsoft Dynamics CRM 2015 servers that are running in the deployment will become disabled. As each server is upgraded, the corresponding server will be enabled.

You can upgrade Microsoft Dynamics CRM 2015 server roles in any order. However, to have a fully functioning Microsoft Dynamics CRM 2016 deployment, all servers and server roles must be upgraded.

Recommended upgrade steps:

To ease the upgrade process and minimize downtime, it is recommend that you use the following order when you upgrade Microsoft Dynamics CRM Server.

  • Although you can upgrade any version of Dynamics CRM 2015 for Outlook to Microsoft Dynamics CRM 2016 for Outlook, we recommend that you apply the latest update rollup before you begin the upgrade. Microsoft Dynamics CRM 2015 updates and hotfixes
  • Upgrade all Microsoft Dynamics CRM 2015 servers and organizations to Microsoft Dynamics CRM Server 2016.
  • Upgrade Dynamics CRM for Outlook to Microsoft Dynamics CRM 2016 for Outlook to have the Go offline capability.

Microsoft Dynamics CRM Server upgrade options:

There are three different upgrade options:

    • Migrate by using a new instance of SQL Server. We recommend this option for upgrading Microsoft Dynamics CRM Server. Although this option requires a different computer for Microsoft Dynamics CRM 2016 and a different instance of SQL Server, it provides the least amount of potential downtime for users since the existing deployment can remain functioning until the upgrade is completed and verified.
    • Migrate by using the same instance of SQL Server. This option requires a different computer for Microsoft Dynamics CRM Server 2016, but will upgrade in-place the configuration and default organization databases using the same instance of SQL Server. If issues occur during the upgrade, you must roll back to the previous Microsoft Dynamics CRM version to avoid significant downtime.
    • In-place upgrade. Although this option doesn’t require a different computer for Microsoft Dynamics CRM Server 2016 or a different instance of SQL Server, it poses the greatest risk if upgrade issues occur because a roll back and reinstall of the previous version of Microsoft Dynamics CRM will be required to avoid potential downtime.

You could also refer: https://technet.microsoft.com/en-us/library/hh699669.aspx for detailed information on Upgrade Microsoft Dynamics CRM Server.

In this example I am talking about an In-Place upgrade. There were 4 CRM Servers on a virtual environment (2 Frontend and 2 Backend), hence decided to take the snapshot of the all the servers before making any changes and then proceed with an In-Place upgrade.

Important:

  • Always run a full backup of the Microsoft Dynamics CRM databases before you upgrade to a new version of the product. For information about database backups, see Back up the Microsoft Dynamics CRM System.
  • During an in-place upgrade, only the organization that you specify to upgrade is upgraded. If the deployment contains additional organizations, those organizations are disabled and are not upgraded. You must upgrade those organizations using the Import-CrmOrganization Windows PowerShell command or by using Deployment Manager. More information: CRM 2016 PowerShell Reference and Import an organization

For each organization that you upgrade, we recommend that the volume have free space that is at least three times the size of the organization database file (organizationName_MSCRM.mdf) and four times the size of the log file (organizationName_MSCRM.ldf). For example, if a single organization database and log file are located on the same volume where the mdf file is 326 MB and the ldf file is 56 MB, the recommended available space should be at least 1.2 GB to allow for growth ((326 x 3) + (56 x 4)). Notice that the database files that expand during upgrade do not reduce in size after the upgrade is complete.

Tasks to perform before the upgrade:

To determine the location of the Microsoft Dynamics CRM installation files, see the Microsoft Dynamics CRM 2016 and Microsoft Dynamics CRM Online Readme.

Tips for a successful upgrade:

The following issues, if applicable to your current Microsoft Dynamics CRM 2015 deployment, should be resolved before you start the upgrade.

Do not exceed the maximum number of fields

If you have more than 1023 fields defined for an entity, you must delete the additional fields before you run the upgrade, or the upgrade will fail with the following message:

CREATE VIEW failed because column 'column_name' in view 'view_name' exceeds the maximum of 1024 columns.

Remove custom database objects

The Microsoft Dynamics CRM databases often change from one major release to the next because of database redesign.

We suggest that, if you have added custom database objects such as triggers, statistics, stored procedures, and certain indexes, you remove those objects from the configuration and organization databases. In many cases, Microsoft Dynamics CRM Server Setup displays a warning when these objects are detected.

Remove the Ignorechecks registry subkey

If you have manually added the ignorechecks registry subkey on the Microsoft Dynamics CRM server, remove it before you start the upgrade. More information: You cannot deploy Microsoft Dynamics CRM by using an account that does not have local administrator permissions on Microsoft SQL Server

Run the upgrade

  1. In the folder where the Microsoft Dynamics CRM files are located, go to the Server\amd64 folder, and then double-click SetupServer.exe.
  2. On the Welcome to Microsoft Dynamics CRM Server Setup page, we recommend that you select Get updates for Microsoft Dynamics CRM to make sure that Setup has the most recent installation files. Click Next. After Setup is done checking for updates, click Next again.
  3. Note: For the Get updates for Microsoft Dynamics CRM functionality to work you must, have an Internet connection on the computer where Setup is running. Enable Microsoft Update for “other Microsoft products” on the Windows Server computer where Microsoft Dynamics CRM Server Setup is running.
  4. On the Product Key Information page, type your product key in the Product key boxes, and then click Next.
  5. On the License Agreement page, review the information and if you accept the license agreement, click I accept this license agreement, and then click I Accept.
  6. If Setup detects that components are missing, the Install Required Components page appears.
    • If you have already installed the required components, this page won’t appear.
    • If you haven’t installed the required components listed, you can install them now. Click Install. When the components are installed, the status column changes from Not Installed to Installed, and you can click Next to continue.
    • Note: If you’re prompted to restart the computer, do so, and then start Setup again.
  7. On the Upgrade to Microsoft Dynamics CRM 2016 page, you can select an organization to upgrade or leave the choice <None> so that no organizations will be upgraded during Setup. Before you select an organization, consider the following:
    • Notice that any organization not upgraded will become disabled after the upgrade is complete. To upgrade organizations after Setup is complete, use the Import-CrmOrganization Windows PowerShell command. Alternatively, you can use Deployment Manager.
  8. On the Specify Service Accounts page, Setup will add the service accounts used for the Microsoft Dynamics CRM Server services. You can use the existing service accounts or specify new ones. For information about the permissions required to run these services see Minimum permissions required for Microsoft Dynamics CRM Setup and services.
  9. If you want to use server-side synchronization and/or Dynamics CRM for Outlook for the deployment, leave this box blank. More information: Integrate your email system with Microsoft Dynamics CRM
  10. Otherwise, on the Specify E-mail Router Settings in the, Email router server name box, type the name of the computer where the Email Router will be installed. This computer will route Microsoft Dynamics CRM email messages. If you leave the box blank but decide later you want to use the Email Router, you must add the computer where the Email Router Service is running (part of the Asynchronous Service) when you use Network Service, or if you use a domain user account, the account to the PrivUserGroup security group.
  11. Click Next.
  12. On the Select Microsoft Update Preference page, select whether you want to use Microsoft Update for checking for updates for your Microsoft products, and click Next. We recommend that you use Microsoft Update to check for updates because this helps keep your computer up-to-date and secure. For more information about the legal terms and privacy with Microsoft Update licensing, see Windows Update FAQ.
  13. The System Checks page appears. This page is a summary of all requirements and recommendations for a successful installation. Errors must be resolved before installation can continue. If no errors, or only warnings appear, you can continue with the installation. To do this, click Next.
  14. The Service Disruption Warning page appears. This page lists all services that will be stopped or restarted during Setup. Verify the suitability of the services that will be stopped or restarted, and then click Next.
  15. Review the Ready to Upgrade the Application page, and click Back to correct any errors. When you are ready to continue, click Upgrade.
  16. When Setup completes successfully, the Microsoft Dynamics CRM Server Setup completed page appears. If the Reporting Server instance that you specified during this Setup points to the local computer where Microsoft Dynamics CRM is installed, Setup provides an option to invoke Microsoft Dynamics CRM Reporting Extensions Setup.
  17. For a full server deployment running on the Microsoft SQL Server Reporting Services computer, select the Launch Microsoft Dynamics CRM Reporting Extensions Setup check box to install Microsoft Dynamics CRM Reporting Extensions. Click Finish.

Important:

  • After you upgrade, you must install the Microsoft Dynamics CRM Reporting Extensions to create, run, and schedule reports in Microsoft Dynamics CRM. For instructions, see Install Microsoft Dynamics CRM Reporting Extensions in this guide.
  • You can’t install the Microsoft Dynamics CRM Reporting Extensions before you install or upgrade Microsoft Dynamics CRM Server.
  • If you had Language Packs provisioned in your deployment, to continue to use multiple languages, upgrade each language pack to Microsoft Dynamics CRM 2016, and then provision them. More information: Upgrade and enable a Language Pack
  • Notice that Setup turns on HTTP compression on the server that’s running IIS where the web application is installed. If you use another method to compress HTTP communications, you may want to turn this feature off after Setup completes. To do this, start Internet Information Services (IIS) Manager, choose the website, double-click Compression, and then clear the compression check boxes.

Post-upgrade steps for servers

  1. If you have additional network load balanced servers or Microsoft Dynamics CRM server roles installed on other computers, upgrade or uninstall and reinstall Microsoft Dynamics CRM on those servers as described in Install Microsoft Dynamics CRM Front End Server and Back End Server roles.
  2. Install the Microsoft Dynamics CRM Reporting Extensions. You must install Microsoft Dynamics CRM Reporting Extensions before you can import and upgrade organizations not upgraded during Microsoft Dynamics CRM Server Setup.
  3. If you had Language Packs provisioned in the deployment, download and install Microsoft Dynamics CRM 2016 Language Packs for the languages that you want. More information: Upgrade and enable a Language Pack
  4. Install the latest update rollup packages/service packs.
  5. If needed, import organizations. During import, each organization will be upgraded. To do this, use the Import-CrmOrganization Windows PowerShell command. Alternatively, you can use Microsoft Dynamics CRM Deployment Manager.
  6. In Microsoft SQL Server Reporting Services Report Manager, re-create any custom data sources under the OrganizationName_MSCRM folders.
  7. Some organization data is encrypted using encryption keys. These keys should be copied as part of your failure recovery procedures. More information: Data encryption
  8. Verify that the system jobs and workflows are running.

Although not required, we recommend that you register Microsoft Dynamics CRM.

Thank you!!

Please do share your feedback and let me know if you want me to write on any other topics you encounter often and need some more information.

Comments

  • Anonymous
    November 03, 2016
    Awesome tips! Thanks for this blog!!
    • Anonymous
      November 09, 2016
      Thank you Jon for your feedback, appreciate it!