Export (0) Print
Expand All

Upgrade from Microsoft Dynamics CRM 2011 Server

Applies To: Microsoft Dynamics CRM 2013

This section shows you how to run the actual in-place upgrade on a Microsoft Dynamics CRM server. If you encounter problems during the upgrade, see Troubleshooting installation and upgrade in this guide.

Following these steps may cause significant application downtime if issues occur during the upgrade. Instead of using an upgrade option that may affect the production deployment, we recommend that you migrate your deployment to Microsoft Dynamics CRM 2013.

We strongly recommend that you back up your existing Microsoft Dynamics CRM data, including all reports and customizations, before you run Setup. In addition, we recommend that you implement the following backup strategy before you run Setup:

  1. Configure the Microsoft Dynamics CRM 2011 databases by using a simple recovery model.

  2. Complete a full backup of all production configuration and organization databases and transaction logs.

For more information, see Back up the Microsoft Dynamics CRM 2013 System in the Operating and Maintaining Guide.

  • Only Microsoft Dynamics CRM 2011 Update Rollup 6 (version 05.00.9690.1992) or Microsoft Dynamics CRM 2011 Update Rollup 14 or later update rollup versions can be upgraded to Microsoft Dynamics CRM 2013.

  • The user who is running Microsoft Dynamics CRM Server Setup to upgrade an existing Microsoft Dynamics CRM deployment must be a member of the Deployment Administrators group. Additionally, the user must have db_owner permission on the Microsoft Dynamics CRM 2011 databases and have sysadmin permission on the SQL Server. For more information about how to add a member to the Deployment Administrators group, see the Deployment Manager Help. For more information about how to grant permission in SQL Server, see the SQL Server Management Studio Help.

  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 2013 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 or tap Next. After Setup is done checking for updates, click or tap Next again.

    For Get updates for Microsoft Dynamics CRM functionality to work you must:

    • Have an Internet connection on the computer where Setup is running.

    • For Windows Server 2012, have Microsoft Update enabled for “other Microsoft products” on the Windows Server 2012 computer where Microsoft Dynamics CRM Server Setup is running.

  3. On the Product Key Information page, type your product key in the Product key boxes, and then click or tap Next.

    If you purchased Microsoft Dynamics CRM through a Microsoft Volume Licensing program, the license key is provided in the license.txt file, which is included in the Microsoft Dynamics CRM installation files.

  4. On the License Agreement page, review the information and if you accept the license agreement, click or tap I accept this license agreement, and then click or tap I Accept.

  5. 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 or tap Install. When the components are installed, the status column changes from Not Installed to Installed, and you can click or tap Next to continue.

    If you’re prompted to restart the computer, do so, and then start Setup again.

  6. On the Upgrade to Microsoft Dynamics CRM 2013 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:

    • By default, during an organization upgrade, every base and extension table will become merged. For large organization databases that are highly customized the merging may take several hours to complete. For more information, see Run the base and extension table merge as a separate operation.

    • New indexes will be added during organization upgrade, which can potentially overwrite existing custom indexes or indexes added by installing a solution. For more information, see Before you upgrade: issues and considerations.

    • Notice that any organization not upgraded will become disabled after the upgrade is complete. To upgrade organizations, use Deployment Manager.

    Click or tap Next to upgrade Microsoft Dynamics CRM.

  7. On the Specify Service Accounts page, Setup will add the service accounts used for the Microsoft Dynamics CRM Server 2011 services. You can use the existing service accounts or specify new ones. Additionally, there are two new service accounts for the VSS Writer Service and the Monitoring Service that you must specify. For information about the permissions required to run these services see Minimum permissions required for Microsoft Dynamics CRM Setup, services, and components.

  8. On the Specify E-mail Router Settings page, 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 will not use the Email Router you can leave this box blank. However, 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. Click or tap Next.

  9. If you aren’t using Microsoft Update, on the Select Microsoft Update Preference page, you must select either of the following options. For more information about the legal terms and privacy with Microsoft Update licensing, see Windows Update FAQ.

    • Use Microsoft Update when I check for updates (recommended). By selecting this option, Microsoft Dynamics CRM Server 2011 will use the Microsoft Update settings on the computer.

    • I don’t want to use Microsoft update. You should only select this option if the computer uses another method to install updates such as by using Windows Update Services.

  10. 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 or tap Next.

  11. The Service Disruption Warning page appears. This page lists all services that will be stopped or restarted during Setup.

  12. Review the Ready to Upgrade the Application page, and click or tap Back to correct any errors. When you are ready to continue, click or tap Upgrade.

    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.

  13. 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 or tap Finish.

  • After you upgrade to Microsoft Dynamics CRM Server 2013, 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 2013 Reporting Extensions in this guide.

  • You can’t install the Microsoft Dynamics CRM 2013 Reporting Extensions before you install or upgrade to Microsoft Dynamics CRM Server 2013.

  • If you had Microsoft Dynamics CRM 2011 Language Packs provisioned in your deployment, to continue to use multiple languages, upgrade each language pack to Microsoft Dynamics CRM 2013, and then provision them. More information: Upgrade and deploy a Language Pack

  • By default, Setup turns on HTTP compression on the server that is 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. To do this, start Internet Information Services (IIS) Manager, click or tap the website, double-click Compression, and then clear the compression check boxes.

See Also

Send comments about this article to Microsoft.

© 2014 Microsoft Corporation. All rights reserved.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2014 Microsoft