web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / From on prem V9.1.2.2 ...
Customer experience | Sales, Customer Insights,...
Suggested Answer

From on prem V9.1.2.2 to latest stable version

(5) ShareShare
ReportReport
Posted on by Abanoub_D365 95
Dears,
 Greetings.
 
Currently, we are managing on-prem version 9.1.2.2, and we need to update to the latest stable version. Shall I set up the latest version directly, which I believe is not the best practice, or shall I install all versions in between one by one? Another concern is how to apply this installation while the CRM is installed on multiple servers (2 Back & 2 Front & 2 SSRS & 1 SQL)
Categories:
Microsoft Dynamics CRM
I have the same question (0)
  • Suggested answer
    Holly Huffman Profile Picture
    Holly Huffman 6,530 Super User 2025 Season 2 on at
    Good morning, afternoon, or evening depending on your location!
     
    Upgrading from Dynamics CRM on-premise version 9.1.2.2 to the latest stable version, here are some recommendations:
    Upgrade Path:
    1. Direct Upgrade vs Incremental Upgrade:
      • It is not recommended to directly upgrade to the latest version without applying intermediate updates. Incremental upgrades ensure compatibility and reduce the risk of errors during the process.
      • Follow the upgrade path by installing cumulative updates sequentially. For example, upgrade to the next available version (e.g., 9.1.x) and then proceed step-by-step to the latest stable version.
    2. Check Compatibility:
      • Verify the compatibility of your current version with the latest stable version. Review the release notes and documentation for any prerequisites or changes that might impact your environment.
    Multi-Server Installation:
    1. Plan the Upgrade:
      • Since the CRM is installed on multiple servers (2 Back-End, 2 Front-End, 2 SSRS, and 1 SQL), ensure that all servers are synchronized during the upgrade process.
      • Begin with the SQL Server and ensure the database schema is updated. Then proceed with the Back-End servers, followed by the Front-End servers, and finally the SSRS servers.
    2. Backup and Testing:
      • Take a full backup of the CRM database and all server configurations before starting the upgrade.
      • Test the upgrade process in a sandbox environment to identify potential issues and validate the upgrade steps.
    3. Deployment Manager:
      • Use the Deployment Manager to manage the upgrade process across all servers. Ensure that the organization database is imported correctly after each upgrade step.
    Additional Considerations:
    • Service Accounts:
      • Verify that the service accounts used for CRM, SQL, and SSRS have the necessary permissions for the upgrade process.
    • Customizations:
      • Review any customizations or third-party integrations to ensure they are compatible with the latest version.
    • Documentation:
      • Follow Microsoft's official documentation for detailed upgrade steps and troubleshooting.
     
    Hope this is helpful :)
  • Abanoub_D365 Profile Picture
    Abanoub_D365 95 on at
    @holly Appreciated your detailed steps and roadmaps 
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at
    Moved the question from the General to the CRM forum.
  • Suggested answer
    Daivat Vartak (v-9davar) Profile Picture
    Daivat Vartak (v-9d... 7,835 Super User 2025 Season 2 on at
    Hello Abanoub_Techtrack,
     

    You are absolutely correct! Setting up the latest version directly from your current version (9.1.2.2) is generally NOT the recommended or best practice for a complex, multi-server Dynamics 365 on-premises deployment.

    Here's a breakdown of why and the recommended approach:

    Why Skipping Versions is Risky:

    • Complexity of Upgrades: Dynamics 365 upgrades involve significant database schema changes, application code updates, and potential infrastructure adjustments. Skipping multiple versions increases the risk of encountering unforeseen compatibility issues, data migration errors, and functional regressions.

    • Cumulative Updates: While later versions often include cumulative updates, they are primarily tested for upgrades from the immediately preceding version or a few versions back. Skipping many versions means you might miss critical intermediary updates that address specific bugs, security vulnerabilities, and prepare your environment for the larger changes in the latest version.

    • Testing Burden: Skipping versions significantly increases the complexity and scope of testing required. You'll need to test functionality across a much wider range of changes, making it harder to identify and resolve issues.

    • Potential for Data Loss or Corruption: The risk of data migration or corruption issues is higher when making large leaps between versions.

    • Support Implications: Microsoft's support for older versions eventually ends. While you're on 9.1, it's important to upgrade, but doing it correctly minimizes potential problems. Skipping versions might also complicate support if you encounter issues.

      •  

    Recommended Approach: Step-by-Step Upgrades:

    The best practice for upgrading a multi-server Dynamics 365 on-premises deployment like yours is to follow a sequential, version-by-version upgrade path to a stable intermediate version first, and then proceed to the latest stable version.

    Here's a general guideline:


    1. Identify the Upgrade Path: Consult the official Microsoft Dynamics 365 documentation for the recommended upgrade paths from your current version (9.1.2.2). Microsoft usually provides guidance on the supported upgrade sequences. You will likely need to upgrade to an intermediate version (e.g., a specific 9.x version or a more recent major release like 10.x) before moving to the latest stable version.

    2. Plan and Prepare:

      • Review Release Notes: Thoroughly review the release notes for each version you plan to upgrade through. Understand the new features, deprecated functionalities, and any specific upgrade considerations or prerequisites.

      • Hardware and Software Requirements: Ensure your server hardware and supporting software (Windows Server, SQL Server, etc.) meet the requirements for each target version.

      • Backup Everything: Perform full backups of your entire Dynamics 365 environment, including all databases (Organization, Configuration, MSCRM_CONFIG), file shares, and server configurations before starting any upgrade process.

      • Test in a Non-Production Environment: Crucially, replicate your production environment (including data and customizations) in a non-production (staging/test) environment and perform the entire upgrade process there first. This allows you to identify and resolve any issues without impacting your live system.

      • Customization Review: Analyze your existing customizations (plugins, JavaScript, workflows, integrations) for compatibility with each target version. You might need to update or rewrite some customizations.

      • Communication Plan: Inform your users about the planned upgrade schedule and potential downtime. 

    3. Execute the Upgrades Step-by-Step in the Test Environment:

      • Upgrade the Microsoft Dynamics 365 Server role(s) on one of your Front End servers first. Follow the official Microsoft upgrade guide for each version.

      • Upgrade the Microsoft Dynamics 365 Reporting Extensions on your SSRS server(s).

      • Upgrade the Microsoft Dynamics 365 Asynchronous Processing Service role(s) on one of your Back End servers.

      • Upgrade the Microsoft Dynamics 365 Sandbox Processing Service role(s) on your Back End servers.

      • Upgrade the Microsoft Dynamics 365 Deployment Administration Server role.

      • Finally, upgrade your Organization databases using the Deployment Manager.
      • Important Considerations for Multi-Server Deployments:

        • Order of Operations: The order in which you upgrade the different server roles is critical. The Deployment Administration Server is usually upgraded last after the core server roles.

        • Staged Rollout: In your test environment, simulate a staged rollout if possible, upgrading one server of each type at a time to identify any load balancing or connectivity issues.

        • Monitoring: Monitor the upgrade process closely using the setup logs and event viewers on each server.

    4. Thorough Testing in the Test Environment: After each successful upgrade in your test environment, perform comprehensive testing of all core functionalities, customizations, and integrations. Address any issues identified before proceeding to the next upgrade step.

    5. Plan and Execute the Production Upgrade: Once you have successfully upgraded and tested all intermediate versions in your test environment, develop a detailed plan for upgrading your production environment. This plan should include:

      • A well-defined maintenance window with minimal downtime.

      • A rollback plan in case any critical issues arise during the production upgrade.

      • The same step-by-step upgrade process used in the test environment.

      • Thorough post-upgrade testing in production. 

        •  

      6.  

    In summary, DO NOT skip versions when upgrading your multi-server Dynamics 365 on-premises deployment. Follow a sequential, step-by-step upgrade path, starting with a thorough assessment and testing in a non-production environment. Carefully follow the official Microsoft upgrade documentation for each version and pay close attention to the order of operations for your multi-server setup.

    This methodical approach will significantly reduce the risks associated with the upgrade and ensure a smoother transition to the latest stable version. Good luck!

     
    If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.
     
    My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.
     
    Regards,
    Daivat Vartak

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 108 Super User 2025 Season 2

#2
Jimmy Passeti Profile Picture

Jimmy Passeti 50 Most Valuable Professional

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 49 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans