Forum Discussion
PavithraT
May 14, 2020Microsoft
Migration from Fall 2019 to Spring update 2020
*Important:
The PowerShell cmdlets named in the article aren’t available yet. We’ll update this article when we publish the cmdlets.
The Fall 2019 release of Windows Virtual Desktop provided ...
PavithraT
Microsoft
Could you give me the following info:
Was the hsotpool completely empty when you started the Add VM workflow?
Were you asked to fill out the VM Prefix before seeing this error?
Do you have VMs in the resource group with or without the prefix?
I validated the fix prior to deploying it (had 3 different scenarios) and I was able to successfully create VMs. The scenarios were all around adding VM to an empty hostpool or a hostpool with a previously failed VM creation (due to domain error, etc.). This info will give me more info to repro the issue.
Was the hsotpool completely empty when you started the Add VM workflow?
Were you asked to fill out the VM Prefix before seeing this error?
Do you have VMs in the resource group with or without the prefix?
I validated the fix prior to deploying it (had 3 different scenarios) and I was able to successfully create VMs. The scenarios were all around adding VM to an empty hostpool or a hostpool with a previously failed VM creation (due to domain error, etc.). This info will give me more info to repro the issue.