The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly customize your community to find the content you seek.
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 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 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
A few days ago a Windows update rolled out that broke pipelines all over the place and the suggested workaround is to use hyper-v isolation instead of process isolation so that the container is not affected by whatever happened on the host.In addition to Freddy’s blog about what happened and how to fix it, there are a few things you need to know about hyper-v isolation on Windows Server and that switching to hyper-v isolation could introduce new errors.
If you want to use hyper-v isolation on a Windows Server VM, the Hyper-V feature needs to be installed and this can be done by calling the Install-WindowsFeature HyperV PowerShell command.However, if your VM doesn’t support nested virtualization, the installation seems to succeed, but in fact, creating a container with hyper-v isolation will still fail with an error saying that the feature is not installed.Not every VM size on Azure supports nested virtualization, you can check if the VM size you are using supports it here: https://docs.microsoft.com/nl-nl/azure/virtual-machines/windows/acu(The entries with three stars (***) support it)In my case, this forced me to switch to a more expensive, less powerful VM size just to use hyper-v isolation.
After I had switched to hyper-v isolation I ran into completely different issues like:– Text files could not be imported– Objects could not be compiledEverything had to do with the wrong locale being used, even though I had specified the right locale when creating the container.I even tried to set the right locale again, after creating the container but without luck.In the end, I decided to simply uninstall the update from the control panel and disable automatic updates on the server for now.You can disable automatic updates through sconfig.exe (only works for Windows Server) -> option 5 -> manual.Happy building!
Business Applications communities