Forum Discussion
The client cannot connect to the destination specified in the request
chad Snelson : Did you end up troubleshooting or redeploying and getting a working host pool?
In the Azure portal, it should specify which virtual machine was attempting to run this configuration, so you could troubleshoot that VM, as long as you have a connection to that machine. Typically, these errors occur from permissions issues. Since the beginning of May, we listened to feedback and re-ordered the "Tutorial" docs to mitigate these issues. You can check out our tutorials again at https://aka.ms/wvdpreview and should be able to complete this task now.
- Marco41May 04, 2020Copper Contributor
Hello chad Snelson
Were you ever able to resolve this? If so can you please help me! I am having the same issue!
Thank you
- emmanuelgaltierMay 26, 2020Copper Contributor
Marco41 I've got the same issue when my Session host where deploy in an OU with configuration GPO.
I deploy a new one in an OU without GPO Applies and it's OK.
Hope it's helping you.
- Andrew NeeJun 03, 2020Copper Contributor
Thanks for the tip. This suggestion worked for me too!
- Christian_MontoyaAug 08, 2019
Microsoft
chad Snelson : The first step I'd take is to do a manual deployment to get a single VM running, and see if that works. From there, you should be able to verify the (1) domain join, (2) logging into the Windows Virtual Desktop PowerShell to create a host pool and registration token and (3) installing the Agents with the registration token.