Recently, I worked on an upgrade project, where we upgraded our Microsoft Dynamics 365 for Finance and Operations, Enterprise Edition (D365FOEE) from Platform 3 to Platform 12. Platform Update 3 concerning availability is no longer available and is only supported today. Platform Update 3 was a significant release of D365FOEE and was called as release 1611.
Refer to the link below for available dates of the various platform updates for Microsoft Dynamics 365 for Finance and Operations, Enterprise Edition.
Microsoft D365 for Finance and Operations: Upgrade to Platform Update 12 Operations
Microsoft Dynamics 365 for Finance and Operations, Enterprise Edition consists of the following components that determine the architecture of the application (On Cloud and On-Premise).
- Application Object Server (AOS)
- Business Intelligence Components
- Development Tools
- Analytical components
- Data Management framework
- Environment orchestrator
The following are the three components that define the platform upgrade process in Operations:
- Deployable packages (Unit of deployment that can be applied to any environment. It consists of binary updates, hotfixes, application updates also stored in a package)
- AxUpdateInstaller.exe (Executable files that are bundled into a deployable package. Comes with the deployable package. Used to generate, export the runbook)
- Runbook (Consists of a series of steps that are used to facilitate the deployment)
There are two approaches that we can follow concerning platform updates
- Apply LCS Updates (Upgrade environments using Lifecycle Services)
- Manual On-Premise update (Upgrade manually after downloading the deployment packages)
Note: In this case, we are upgrading from Platform Update 3, and it’s recommended to use the LCS Updates approach for upgrading environments from Platform Update 4.
Step No 1:
Login to Lifecycle Services (LCS) through https://lcs.dynamics.com/Logon/Index. Log in to the system that hosts the Microsoft Dynamics 365 for Finance and Operations applications to run the upgrade. To find these details, select the LCS project and then choose the environment section in the LCS project.
The environment section is where the details of the system, hosting the Operations application is stored. Select the environment and the login details of the virtual machine, hosting the Dynamics 365 for Finance and Operations, can be found there under the section Local Administrator accounts (as per January 2018 update).
In the environment section, there are various sub-sections like Deployment Status and Local Administrator Accounts. In the Local Administrator Accounts, the VM name and the local administrator account details are stored.
Step No 2:
After logging into the virtual machine, open a browser window and re-login to Lifecycle Services through https://lcs.dynamics.com/Logon/Index. Download the deployment packages from the Shared Asset library through Microsoft Dynamics Lifecycle Services (LCS). From the Shared Asset Library, download the Platform Update 12 package for Finance and Operations.
Unblock the AxPlatformUpdate.zip file after downloading the package (Right click and select Properties-> Unblock the file).
Step No 3:
After unblocking the .zip file, extract the files and it will show up the list of extract files. Open a command line or a PowerShell ISE instance and then navigate to the directory where the .zip file is extracted.
<%systemdirectory%><extracteddirectoryName>AxUpdateInstaller.exe list is the command that highlights the list of services installed on the system.
The axupdateinstaller.exe list will also give the Runbook Id along with the list of services installed on the Microsoft Dynamics 365 for Finance and Operations, Enterprise Edition host machine.
Unblock the .zip file, highlighted about in Step No 3, before extracting the .zip file. If we fail to unblock the .zip file as highlighted in Step no 3, then the above-mentioned command AxUpdateInstaller.exe list will throw an error, which means it fails to identify the list of Microsoft Dynamics 365 for Finance and Operations services installed on the host machine.
Step No 4:
The directory where the platform components are installed will have a DefaultTopologyData file. This file hosts the list of AOS machine names and the services and components hosted on those machines and the metadata of those services and components. In addition to this, the runbook id is also hosted on this file. From the AxUpdateInstaller.exe list ensure that the list of components and the topology id are added to the default topology Data file. Also, the runbook id needs to be added to the file. Its highlighted within the <Name> tags. By default, the runbook id is Ax topology. Replace it with the runbook id, which in this case is fb73f8c8-bdc7-4aa7-8363-3ef19b6ea11d.
This is one of the most critical steps to ensure that the deployment is smooth. This is a pre-requisite used to generate the runbook that contains the sequence of deployment steps.
Step No 5:
The next step is to generate the runbook file with the topology id and the components to be upgraded. This will also instruct the AxUpdateInstaller.exe to run the sequence of steps to be followed for the deployment to be done. In the command line or a PowerShell ISE instance, use the AxUpdateInstaller.exe command to generate the runbook with the topology details and the components to be upgraded.
PS <%systemdirectory%>:AxPlatformUpdate> .AXUpdateInstaller.exe generate -runbookid=fb73f8c8-bdc7-4aa7-8363-3ef19b6ea11d -topologyfile=”<%system directory%>:AxPlatformUpdateDefaultTopologyData.xml” -servicemodelfile=”<%systemdirectory%>:AxPlatformUpdateDefaultServiceModelData.xml” -runbookfile=”<runbookname>-runbook.xml”
This will extract a runbook with the name <runbookname>-runbook.xml. Recommendation is to keep the runbook name simple and suffix it with -runbook, for ease of identification. At this stage, the runbook will have the sequence of steps to upgrade the Finance and Operations environment.
In my case, I have extracted the .zip files to a directory called a platform update.
Step No 6:
The next step is to import the runbook and this can be done through the command line.
<%systemdirectory%>AxPlatformUpdate> AxUpdateInstaller.exe import -runbookfile=”<runbookfilename>-runbook.xml”
This will start executing the sequence of steps highlighted in the runbook. Some of the steps highlighted in the runbook include starting and stopping the AOS Service and restarting them post-deployment. This is the step that will perform the upgrade steps on Microsoft Dynamics 365 for Finance and Operations.
Step No 7:
Once the upgrade is complete, check the environment for Platform Update 12. Click the gear icon and select About on the extreme right in the Default Dashboard screen in the Operations applications and this should show the platform version.
Step No 8:
Once the upgrade is complete, ensure that you export the runbook. To export the runbook, use the command
<%systemdirectory%>AxPlatformUpdate> AxUpdateInstaller.exe export -runbookid=”<runbookid>” -runbookFile=”<runbookfilename>.xml”
This is a backup copy of the runbook, post-deployment/post upgrade from Platform Update 3 to Platform Update 12.
Note: Remember, that starting Platform Update 3 it is recommended to use the extensions approach instead of the “Overlayering” approach. In my previous post, I have mentioned about the differences between extensions and the “Overlayering” approach.Disclaimer: The Questions and Answers provided on https://www.gigxp.com are for general information purposes only. We make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose.