Issues with Side by Side Stack

New Contributor

I have been trying to deploy WVD host pool with a custom image, and having trouble with SxS stack. As a result (I believe) although I can see the VM/desktop/pool available in the WVD portal, connection to it fails.


Now the run down of what I've done:


Custom image creation:
An Azure Windows 10 1803 Pro VM is created.

Various programs and configuration installed.

Sysprep and shutdown, then capture into an image.

I even ran through the steps here second time around


Once image is created, a new Windows Virtual Desktop host pool is deployed using that and as far as host pool deployment, everything is fine. No errors, domain join is good, Windows Virtual Desktop Agent and Bootloader are installed and reg keys are present, however running Get-RdsSessionHost shows SxSStackListenerNotReady for SxSStackStatus.


I have even followed these instructions and manually joined to domain and installed agent and bootloader and Get-RdsSessionHost does not even show the new VM!


Running qwinsta does NOT show rdp-sxs process.


I've also run through this troubleshooting page and the only section that applies to my situation is SxS not installed or enabled, and it talks about a enablesxstackrs.ps1 script, however that's no where to be found on the page!


If I deploy a host pool with MS gallery images( i.e. Win 10 Ent Multisession and O365), I can connect to the VM/desktop from and obviously rdp-sxs shows when you run qwinsta and Get-RdsSessionHost returns the heartbeat data for SxSStackStatus.


So I am pretty sure either I am missing a step, or something does not get enabled when installing agent and bootloader. Otherwise maybe no other version of Win 10 is supported for this, hence the issues with SxS stack.


Would really appreciate some help.




6 Replies
Can you post the output of Get-RDSSessionHost for us here from the machine where you have manually installed the bootloader and agent ?
Thanks for the reply.

Unfortunately since we needed a solution ASAP, I removed the original pools and VMs and created my image from Win 10 1809 for WVD (from Azure Gallery) and that seems to work fine. Agent and bootloader were installed during host pool creation and I didn't have to do any other customization on the image itself.

I may revisit 1803 image again and will post the output, but I have a feeling running those non-multisession versions is probably not supported. Even though hearing otherwise from couple of Azure Solutions Architects.


@fara1I've had the same issue with no reply so far. Thing is, it was working before with older builds.
MS removed the SxS script and setup from the technet articles, according to the comment on github becasue SxS is not needed anymore... well I'd say that's not entirely true.

Thanks for the reply. Yeah, not sure why they removed the script but are referencing it in the guide still! Also would have been nice to have some direct support as first impression, technical and end user, is everything with a new tech.

We have not been happy with the (laggy) user experience either so will probably move away and look for a different solution. I am assuming the lag is because of the management plane being in US only!

@fara1In the end I've just deployed a VM with the image from the marketplace and on top of that installed and configured everything we need, then created a managed Image and deployed this one, works like a charm but for another issue that the RD agent Updater doesn't work anymore.


Yes the preformance is related to the management plane in the US.

@A_priori_superiorYeah I basically did the same thing to capture from a VM and use for hostpool.


Also Today I asked our developers to use the standard RDP into those VMs and obviously massive improvements in user experience. They can actually do their work. I was really excited about WVD and it was my suggestion to implement and use it but unfortunately it is not enterprise yet or at least for outside US.


Back to the whole SXS issue, I created another VM from Win 10 1809 for WVD (from Azure Gallery) today and followed this to domain join and install RD agent and bootloader. It still did not register with the hostpool and rdp-sxs does not appear! So whatever they have removed from the guides, whether it's the PoSH script or something else, has definitely broken this process.