Forum Discussion

PavithraT's avatar
PavithraT
Icon for Microsoft rankMicrosoft
May 14, 2020

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 ...
Yuki398's avatar
Yuki398
Copper Contributor
May 20, 2020

PavithraT 

Thanks for fixing.But, unfortunately, it didn't fix properly.

The input form for adding a session host is now displayed and this has been fixed.

However, there seems to be an error in input validation.

Is this a problem for my environment?

Error message

The value of deployment parameter 'vmInitialNumber' is null. Please specify the value or use the parameter reference. See https://aka.ms/resource-manager-parameter-files for details.

 

  • PavithraT's avatar
    PavithraT
    Icon for Microsoft rankMicrosoft
    May 20, 2020
    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.
    • Yuki398's avatar
      Yuki398
      Copper Contributor
      May 20, 2020

      PavithraT 

      > 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.

    • yusuke55's avatar
      yusuke55
      Copper Contributor
      May 27, 2020

      PavithraT 

       

      I have the same issue.

       

      If host pool is completely empty, this error did not occur.

      Only when session hosts already exist in host pool, the error occurred.

      • yusuke55's avatar
        yusuke55
        Copper Contributor
        May 27, 2020
        I retried 5 minutes ago.
        It seems that this issue is resolved.

Resources