Announcements
Hi all,
I'm planning on updating my on-premises version 9.0.11.9 (December 2019) to the latest version 9.1.17.29 (April 2023).
Questions:
1- Do i need to install the Dynamics 365 Server Service Pack 1, version 9.1 first? Or can i go for the latest version?
2- Is a in-place upgrade safe to do? (After all backups created)
Thanks for your help.
Hello Hugo,
1- It doesn't matter what is first. The most critical part is updating the DB, and making sure you don't use an organization without having all servers of the deployment updated. If you have auto updates ON, updating any of the servers (FE or BE) will trigger update of the enabled DB's.
2.1- Yes
2.2- It is to be installed on the server where you are running SSRS. Remember you can run SSRS on another SQL server than SQL server hosting CRM. If your Backend runs SQL + SSRS the answer is yes.
2-3 Tools is not an installation per say. Its a package with tools/samples to be used, but an installation has no dependencies on it.
Hi Pedro,
Appreciate your thoughts!!!
This is a multiserver installation (FrontEnd Server + BackEnd with SQL):
1- We should start the update on the backend server, correct?
2- The latest 9.1 have the following files:
CRM9.1-Server-KB5023894-ENU-amd64.exe
CRM9.1-Srs-KB5023894-ENU-amd64.exe
CRM9.1-Tools-KB5023894-ENU-amd64.exe
2.1 - The server package should be run on both servers, right?
2.2 - The Srs package is to be installed only on the backend;
2.3 - What are the tools to be installed? (FE or BE)
Appreciate your help.
Hello Hugo,
1- Do i need to install the Dynamics 365 Server Service Pack 1, version 9.1 first? Or can i go for the latest version?
As v9.1 cumulative updates are FULL, you don't need to install v9.1 RTM rtm first. You can install directly v9.1.17.
2- Is a in-place upgrade safe to do? (After all backups created)
In general we prefer separate environment installations because:
- Some customers have played around with CRM files on 9.0 that will cause problems on overwriting those files on installing v9.1. So the installation may be inconsistent and cause problems to upgrading DBs.
- In place upgrades will automatically try to upgrade the Database, so if something fails, that organization may not be available anymore until you fix the upgrade error.
Please check this article to disable automatic updates first, if you use an inplace upgrade.
On in place upgrades, imagine your deployment has 100 orgs, the process will only finish once all 100orgs that are enabled are attempted to be upgraded. As this causes sometimes a customer to NOT notice that a DB had a failure and will continue to use it, although becomes on a corrupted state.
learn.microsoft.com/.../update-to-v91
-------
By default, when you apply the Dynamics 365 Server, version 9.1 update, all organization databases that are enabled in the deployment will be updated to Dynamics 365 Customer Engagement (on-premises), version 9.1. Administrators can control which organization databases are upgraded in either of the following ways:
Disable the organizations you don't want upgraded. Notice that all organizations must remain disabled until all the servers in a multi-server deployment are updated. More information: Deployment Manager: Disable or enable an organization and PowerShell: Disable-CrmOrganization.
Configure the AutomaticallyInstallDatabaseUpdates deployment setting to false.
Add-PSSnapin Microsoft.Crm.PowerShell set-crmadvancedsetting -configurationentityname Deployment -setting AutomaticallyInstallDatabaseUpdates -value $false
-------
Separate environment with Handy DB restores if the update fails are easier to handle.
3-before installing the SP1, do i need to install the latest 9.0x version?
No.
We have seen rare scenarios where a DB may give an error if updated from 9.0.10 to v9.1.17, but not if 9.0.10 -> 9.0.46 -> 9.1.17.
But this is about DB update and you are focusing on Server install.
Thanks for you reply,
Another thing, before installing the SP1, do i need to install the latest 9.0x version?
André Arnaud de Cal... 291,359 Super User 2024 Season 2
Martin Dráb 230,370 Most Valuable Professional
nmaenpaa 101,156