Forum Discussion
Host in host pool changed by itself - how can this happen
Hi. I do some testing around WVD at the moment and I had a strange observation. I have a host pool. Let's name it 'hostpool1' And yesterday I had ONE host in this host pool. Let's name it '...
My recommendation is to make certain that you never install Windows Virtual Desktop Agent nor Windows Virtual Desktop Agent Bootloader on your image machines.
What we do is this: Create a VM using the Windows 10 multisession marketplace image. Install our apps. Run sysprep, make an image of the vhd. Deploy that image.
When it's time to apply patches or otherwise update the image, we build a new VM based on the image we created previously. Make whatever changes, run sysprep, make a new image. Deploy that image.
So at no point do we ever install the WVD agents on the images. Those agents only get installed during the host pool deployment process. We never make an image of an existing session host that has the WVD agents already on it, because it causes the exact kind of problems you're experiencing.
Keep your images free of WVD agents and you'll do fine.
What we do is this: Create a VM using the Windows 10 multisession marketplace image. Install our apps. Run sysprep, make an image of the vhd. Deploy that image.
When it's time to apply patches or otherwise update the image, we build a new VM based on the image we created previously. Make whatever changes, run sysprep, make a new image. Deploy that image.
So at no point do we ever install the WVD agents on the images. Those agents only get installed during the host pool deployment process. We never make an image of an existing session host that has the WVD agents already on it, because it causes the exact kind of problems you're experiencing.
Keep your images free of WVD agents and you'll do fine.