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 Timeline
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
We have an OnPremise installation of Microsoft Dynamics 365. Our database is heading up towards 300Gb and due to investment over the past 8 years have 2 million lines of code in plugins, reports, and online portal functionality. We are looking to migrate from v8.2.7 to 9.0.12 (OnPremise), and have undertaken some test migrations on our Development and Test environments. Apart from the Plugins needing to be re-compiled in v4.6.2 (was in v4.7.2) everything has been relatively smooth (one of the best I must admit) - we are doing an upgrade in-place as all our servers are supported version.
For those contemplating we have the generic steps as follows
1. Backup etc2. Uninstall Reporting and Email Router3. Install v9.02 (Server, Email and Reporting)4. Install v9 upd 0.09 (? because v9 upd 10 doesn't allow Database upgrades from 8.2.7)5. Upgrade Databases6. Install v9 upd 0.12
One challenge however is our Claims Based and IFD deployment and looking for some guidance. We are running ADFS on Windows 2012 R2, and looking to migrate up to Windows 2019 (ADFS v5.0). Some of my questions are :-
a) Do I need to uninstall Claims and IFD on our Production Servers prior to running the upgrade, or can I upgrade in place?b) Will v9 upd 0.12 and ADFS running on Windows 2012 R2 run happily together? i.e we run our CRM upgrade, then later tackle ADFS.c) Will v9 upd 0.12 and ADFS run on Windows 2019? Can we goto the latest ADFS (is anyone running on this?)
Our ADFS integration is just to allow staff working from home access to our CRM, we aren't using any Apps including Outlook integration.
The answer of move to the Cloud isn't an option due to its limitations.
This article https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/software-requirements-for-microsoft-dynamics-365-server says that ADFS on Windows 2016 is supported.
And also this one, https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/configure-the-ad-fs-server-for-ifd implies ADFS on Windows 2016 is supported, because near the end there is a step to run "If you're AD FS server is running Windows Server 2016, run the following Windows PowerShell cmdlet"
But nothing to say that ADFS on Windows 2019 is supported.
I also know that Dynamics 365 itself is NOT supported on Windows 2019.
Have completed the upgrade and have answers to the questions I posed.
a) I left Claims and IFD in place on W2K12 R2, the upgrade was successful. To be safe I re-ran the Claims and then ADFS install within CRM, then refreshed the ADFS Relaying Party Trusts, by running Update from Federation Medadata. All worked perfectly. External and Internal logins successful.
b) v9.0.12 and W2K12 R2 ran fine with an in-place upgrade.
c) NO - 2 extremely long nights. We tried ADFS Level 3 on W2K19 Servers and complete disaster. We then tried ADFS Level 3 on W2K16 Servers and was able to get it working, however the WAP servers at W2K19 seem to cause the page just to hang when logging in externally (this was after playing with some MFA settings). We have reverted to W2K16 ADFS and W2K16 WAP servers and the system has returned to happy.
Business Applications communities