So my laptop packed up over the weekend, and that gave me the opportunity to actually walk the walk rather than just talking about Windows Virtual Desktop and Azure, actually drinking our own champagne. Hence for the last couple of days I have been using my own Windows 10 VDI that is in Azure delivered via Windows Virtual Desktop, and in fact I am writing this post form that very Virtual Machine. I created a little video of this whole user experience.
Showing posts from 2019
Windows Virtual Desktop pre-requisites - everything in the right place to enable you to deploy without errors
- Other Apps
Windows Virtual Desktop is a newly announced capability for managing VDI and RDSH as a service from Azure. It went into public preview in March of 2019, with many successful deployments for testing purposes having been completed. However we have seen a large number of failures of the Azure Resource Manager deployment from a set of customers, all for very similar quite simple errors entered into the Azure portal deployment process, things like incorrect accounts, or lack of name resolution. Hence this simple guide is designed to save you some time by avoiding common errors in the deployment process. There are a few pieces of information you need and it is possible to get this wrong. Hence this will clearly explain what prerequisites are required to be in place and where to get the relevant information and then where to exactly put these details into the Windows Virtual Desktop HostPool creation process in the Azure portal. This is to ensure the deployment process will complete success