Dynamics Community Forum Thread Details

[On-premise] Install new Frontend server role to existing CRM environment V9.1

Hi All,

We have a running environment of Dynamics 365 V9.1.17 on premise.

Our current need is to install a new frontend server to this existing environment but the available setup file is v9.0

Is it a correct action to start the setup on the new server with v9.0 setup and connect it during the setup to existing Dynamics v9.1 DB

Is the V9.0 setup will be compatible with DB v9.1 or we will face issues, please advice

Thanks in advance.

Hello Islam,

Yes, the correct action is to install v9.0 (v9.0.2) connected to the existing deployment, and then update it right away to v9.1.17.

Installing a frontend server does not touch DBs because DB version is higher than server version.

Still, when you install v9.1.17, i think that new frontend will try to verify DB on v9.1.17. Or maybe not.

Still its a best practice to disable autoupdate DBs via powershell, whenever you update a server.

PLease check: https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/update-to-v91?view=op-9-1&amp%3Btabs=v90&tabs=v90

----

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

Quick Links