So we've been testing WVD in our organization for a about a month, we've had some of the common issues others were having deploying host pools, getting connection errors, etc. We've worked all of that out and can now do personal and pooled deployments, create app groups and deploy applications all without issue. The problem I'm running into now happens when I do a deployment with a custom image. The deployment finishes successfully but does not attach itself to the WVD service. The machine gets built, I can RDP into it but it doesn't show up in the Remote Desktop Web Client, in powershell the host pool doesn't show in the tenant, nor the management UI. I've also created the image in several different ways. I've used sysprep on one of the machines already deployed in WVD, captured the image from the Azure portal and did a WVD deployment, I've followed the steps in this arcticle, I've also created a machine from the marketplace using the multi user Windows 10 + O365 image, sysprep, and deploying using the VHD URI of the disk. Each one results in the same, the deployment goes through without error, the machine joins the domain and shows up my computers OU, you can RDP to it and use it normally, but it does not show up in RDP and you cant find any trace of the host pools or sessionhosts in powershell using any of the Get-RDS commands. Appreciate any help on this.
Thanks!
