Forum Discussion
MicrosoftMigration from Fall 2019 to Spring update 2020
MicrosoftWas 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?
No. There is one session host.
I tried to add more session hosts from the Azure portal after manually adding a session host to the host pool.
> Were you asked to fill out the VM Prefix before seeing this error?
Yes.
I couldn't type the Basic Tab, but I had to type everything else as usual.
> Do you have VMs in the resource group with or without the prefix?
I've seen some patterns, but it doesn't seem that the resource group is empty or the name of the VM has anything to do with it.
My scenario
1. Create a host pool. (Desktop Application Group is automatically created)
2. Create a windows 10 VM from Marketplace.
3. Join the domain in windows 10, and install a wvd agent and fill the registration key.
4. Add session hosts from Azure Portal. The error occurred at this time.
