Win10 2004 not working with WVD? Unable to connect

%3CLINGO-SUB%20id%3D%22lingo-sub-1426181%22%20slang%3D%22en-US%22%3EWin10%202004%20not%20working%20with%20WVD%3F%20Unable%20to%20connect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1426181%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20just%20updated%20our%20WVD%20image%20with%20the%20new%202004%20update%20(ARM%20WVD).%3CBR%20%2F%3EIf%20I%20deploy%20new%20servers%20in%20the%20existing%20hostpool%2C%20they%20go%20into%20%22upgrading%22%20and%20then%20%22unavailable%22.%3CBR%20%2F%3ERestarting%20the%20VMs%20makes%20them%20come%20up%20as%20%22Available%22%20(and%20no%20issues%20either%20according%20to%20powershell).%3CBR%20%2F%3EHowever%2C%20I%20am%20unable%20to%20connect%20to%20any%20of%20the%20new%20VMs.%3CBR%20%2F%3E%3CBR%20%2F%3ESame%20issue%20occurs%20if%20i%20create%20a%20new%20hostpool%2Fapplication%20pool%20with%20the%20new%202004%20image.%3C%2FP%3E%3CP%3EI%20have%20also%20tried%20re-subscribing%20in%20the%20Remote%20Desktop%20app%20(newest%20version).%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EIf%20i%20disable%20drain%20mode%20on%20the%20old%20VMs%20(non-2004)%20I%20am%20able%20to%20join%20the%20servers%20without%20any%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1427265%22%20slang%3D%22en-US%22%3ERe%3A%20Win10%202004%20not%20working%20with%20WVD%3F%20Unable%20to%20connect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1427265%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F677026%22%20target%3D%22_blank%22%3E%40Raaert%3C%2FA%3E%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%20for%20raising%20your%20issue!%20Had%20the%20same%20today.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20able%20to%20solve%20it%20like%20this%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%26nbsp%3B%20Navigate%20to%20your%20future%20Session%20Host%20that%20has%20been%20deployed%20and%20navigate%20to%20the%20install%20folder%20of%20the%20%22Deploy%20Agent%22%3A%26nbsp%3B%3CSPAN%3EC%3A%5CDeployAgent%5CRDInfraSxSStackInstall%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E2.%20Reinstall%20the%26nbsp%3BSxSStackInstaller-181129002.msi%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E3.%20Restart%20the%20Session%20Host%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20should%20definitely%20solve%20your%20issue!%3C%2FP%3E%3CP%3EIf%20you%20need%20more%20help%2C%20please%20come%20back%20to%20me!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%2C%3C%2FP%3E%3CP%3EPatrick%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1427432%22%20slang%3D%22en-US%22%3ERe%3A%20Win10%202004%20not%20working%20with%20WVD%3F%20Unable%20to%20connect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1427432%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F448842%22%20target%3D%22_blank%22%3E%40patrickkoehler%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20could%20be%20the%20very%20fix%20I%20was%20looking%20for%20(i%20did%20notice%20a%20difference%20in%20sxs%20information%20in%20powershell).%3C%2FP%3E%3CP%3EHowever%2C%20I%20have%20just%20deployed%20my%20image%20(2004)%20and%20everything%20works%20as%20expected%2C%20I%20can%20only%20assume%20that%20Microsoft%20has%20fixed%20the%20bug%20in%20Azure.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1429080%22%20slang%3D%22en-US%22%3ERe%3A%20Win10%202004%20not%20working%20with%20WVD%3F%20Unable%20to%20connect%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1429080%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F448842%22%20target%3D%22_blank%22%3E%40patrickkoehler%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20this%20exact%20same%20issue%20with%20my%202004%20image%20and%20reinstalling%20the%20SXS%20Installer%20worked.%20Now%20though%20any%20update%20to%20it%20fails%3CBR%20%2F%3E%3CBR%20%2F%3ESxSStackVersion%20%3A%20rdp-sxs%3CBR%20%2F%3EType%20%3A%20Microsoft.DesktopVirtualization%2Fhostpools%2Fsessionhosts%3CBR%20%2F%3EUpdateErrorMessage%20%3A%20There%20was%20an%20issue%20installing%20the%20SxsStack%20This%20action%20is%20only%20valid%20for%20products%20that%20are%20currently%20installed.%3CBR%20%2F%3E%3CBR%20%2F%3EAnd%20manually%20reinstalling%20isn't%20exactly%20tenable%20when%20deploying%2020%20SessionHosts%20in%20bulk.%20I%20went%20ahead%20and%20opened%20a%20ticket%20with%20Microsoft%20on%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi,

I just updated our WVD image with the new 2004 update (ARM WVD).
If I deploy new servers in the existing hostpool, they go into "upgrading" and then "unavailable".
Restarting the VMs makes them come up as "Available" (and no issues either according to powershell).
However, I am unable to connect to any of the new VMs.

Same issue occurs if i create a new hostpool/application pool with the new 2004 image.

I have also tried re-subscribing in the Remote Desktop app (newest version).

 

I can RDP to the new (2004) server without any issue - just cant connect through WVD.


If i disable drain mode on the old VMs (non-2004) I am able to join the servers without any issue.

 

Any ideas?

3 Replies
Highlighted

Hi @Raaert

 

thanks for raising your issue! Had the same today. 

I was able to solve it like this:

 

1.  Navigate to your future Session Host that has been deployed and navigate to the install folder of the "Deploy Agent": C:\DeployAgent\RDInfraSxSStackInstall

2. Reinstall the SxSStackInstaller-181129002.msi

3. Restart the Session Host

 

That should definitely solve your issue!

If you need more help, please come back to me!

 

Cheers,

Patrick

Highlighted

@patrickkoehler 

 

That could be the very fix I was looking for (i did notice a difference in sxs information in powershell).

However, I have just deployed my image (2004) and everything works as expected, I can only assume that Microsoft has fixed the bug in Azure.

Highlighted

@patrickkoehler 

 

I had this exact same issue with my 2004 image and reinstalling the SXS Installer worked. Now though any update to it fails

SxSStackVersion : rdp-sxs
Type : Microsoft.DesktopVirtualization/hostpools/sessionhosts
UpdateErrorMessage : There was an issue installing the SxsStack This action is only valid for products that are currently installed.

And manually reinstalling isn't exactly tenable when deploying 20 SessionHosts in bulk. I went ahead and opened a ticket with Microsoft on it.