Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
What is needed: Access to LCS, one-box dev VM, On-premises database backup that needs to be upgraded. In this scenario I will walk through the process of upgrading 10.0.4 VHD to 10.0.5 PU29 and running code and data upgrade from 7.3PU 12 to 10.0.5PU29. Before you begin always check for the updated instructions on docs.microsoft.com. The process of upgrading to the latest version is described here: https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/migration-upgrade/upgrade-data-to-latest-update
This is high level overview of the activities involved in the process:
Prior to proceeding, the dev VM VHD must already be downloaded from LCS and set up locally. In order to configure the new VM properly, use the following document before the machine is renamed https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/migration-upgrade/vso-machine-renaming
First step is to apply application/platform update. https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/migration-upgrade/vso-machine-renaming#additional-steps-to-install-one-version-service-updates
Note: Application/Platform update might fail if you don’t update MR settings: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/migration-upgrade/vso-machine-renaming#update-financial-reporting
PS C:\D365Upgrade\PlatformUpdate\MROneBox\Scripts\Update> .\ConfigureMRDatabase.ps1 -NewAosDatabaseName AxDB -NewAosDatabaseServerName <YOURSERVERNAME> -NewMRDatabaseName ManagementReporter -NewAxAdminUserPassword AOSWebSite@123 -NewMRAdminUserName MRUser -NewMRAdminUserPassword MRWebSite@123 -NewMRRuntimeUserName MRUSer -NewMRRuntimeUserPassword MRWebSite@123 -NewAxMRRuntimeUserName MRUser -NewAxMRRuntimeUserPassword MRWebSite@123
Update 10.0.4 VM to 10.0.5
First things first: Download the target application/platform update to the local vm and follow the process described in https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/install-deployable-package.
Note: Make sure you close Visual Studio instances before proceeding with application or platform updates.
AXUpdateInstaller.exe generate -runbookid=ЭapplicationUpdate" -topologyfile="DefaultTopologyData.xml" -servicemodelfile="DefaultServiceModelData.xml" -runbookfile="applicationUpdate.xml"
AXUpdateInstaller.exe import -runbookfile="applicationUpdate.xml"
AXUpdateInstaller.exe execute -runbookid="applicationUpdate"
Run LCS Code Upgrade
Double check that the upgrade services are configured by following the process documented here https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/configure-execute-code-upgrade
Restore Source database on VM
The next step is to restore Source AXDB on VM:
net stop W3SVC
net stop MR2012ProcessService
net stop DynamicsAxBatch
After you run the SQL against imported database your AXDB users will look like the following:
At this point AXDB is ready for data upgrade package execution
Run data upgrade package
Download and unzip data upgrade package from LCS
Extract the files. In the folder where you extracted the deployable package, open DefaultTopologyData.xml and repeat the steps for deploy application update using runbook:
AXUpdateInstaller.exe generate -runbookid="DataUpgrade" -topologyfile="DefaultTopologyData.xml" -servicemodelfile="DefaultServiceModelData.xml" -runbookfile="DataUpgrade.xml"
AXUpdateInstaller.exe import -runbookfile="DataUpgrade.xml"
AXUpdateInstaller.exe execute -runbookid="DataUpgrade"
Once the data upgrade package is executed, start the services:
net start W3SVC
net start MR2012ProcessService
net start DynamicsAxBatch
Run the Admin Provisioning Tool to provision yourself as a new admin (as users may be different) and begin testing. In the next post we’ll continue the in-place upgrade process to restore the upgraded AXDB on the source environment and deploy new AX application.
Business Applications communities