Home

The client cannot connect to the destination specified in the request

%3CLINGO-SUB%20id%3D%22lingo-sub-420139%22%20slang%3D%22en-US%22%3EThe%20client%20cannot%20connect%20to%20the%20destination%20specified%20in%20the%20request%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-420139%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20getting%20the%20following%20error%20when%20deploying.%26nbsp%3B%20The%20VM's%20join%20the%20domain%20just%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22error%22%3A%20%7B%20%22code%22%3A%20%22VMExtensionProvisioningError%22%2C%20%22message%22%3A%20%22VM%20has%20reported%20a%20failure%20when%20processing%20extension%20'dscextension'.%20Error%20message%3A%20%5C%22DSC%20Configuration%20'FirstSessionHost'%20completed%20with%20error(s).%20Following%20are%20the%20first%20few%3A%20The%20client%20cannot%20connect%20to%20the%20destination%20specified%20in%20the%20request.%20Verify%20that%20the%20service%20on%20the%20destination%20is%20running%20and%20is%20accepting%20requests.%20Consult%20the%20logs%20and%20documentation%20for%20the%20WS-Management%20service%20running%20on%20the%20destination%2C%20most%20commonly%20IIS%20or%20WinRM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20someone%20let%20me%20know%20what%20I'm%20supposed%20to%20be%20troubleshooting%3F%26nbsp%3B%20It's%20not%20clear%20what%20destination%20machine%20is.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-572323%22%20slang%3D%22en-US%22%3ERe%3A%20The%20client%20cannot%20connect%20to%20the%20destination%20specified%20in%20the%20request%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-572323%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F24138%22%20target%3D%22_blank%22%3E%40chad%20Snelson%3C%2FA%3E%26nbsp%3B%3A%20Did%20you%20end%20up%20troubleshooting%20or%20redeploying%20and%20getting%20a%20working%20host%20pool%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20the%20Azure%20portal%2C%20it%20should%20specify%20which%20virtual%20machine%20was%20attempting%20to%20run%20this%20configuration%2C%20so%20you%20could%20troubleshoot%20that%20VM%2C%20as%20long%20as%20you%20have%20a%20connection%20to%20that%20machine.%20Typically%2C%20these%20errors%20occur%20from%20permissions%20issues.%20Since%20the%20beginning%20of%20May%2C%20we%20listened%20to%20feedback%20and%20re-ordered%20the%20%22Tutorial%22%20docs%20to%20mitigate%20these%20issues.%20You%20can%20check%20out%20our%20tutorials%20again%20at%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fwvdpreview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fwvdpreview%3C%2FA%3E%20and%20should%20be%20able%20to%20complete%20this%20task%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-572325%22%20slang%3D%22en-US%22%3ERe%3A%20The%20client%20cannot%20connect%20to%20the%20destination%20specified%20in%20the%20request%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-572325%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305776%22%20target%3D%22_blank%22%3E%40christianmontoya%3C%2FA%3E%26nbsp%3BI%20tried%20redeploying%20several%20times%20and%20it%20always%20failed.%26nbsp%3B%20I%20haven't%20tried%20since%20my%20first%20post.%26nbsp%3B%20I'll%20go%20back%20through%20the%20tutorial%20and%20let%20you%20know%20if%20I%20have%20success.%26nbsp%3B%20Thanks%20for%20the%20reply!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-794090%22%20slang%3D%22en-US%22%3ERe%3A%20The%20client%20cannot%20connect%20to%20the%20destination%20specified%20in%20the%20request%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-794090%22%20slang%3D%22en-US%22%3EI%20just%20redeployed%20and%20got%20the%20same%20error.%20What%20would%20you%20recommend%20at%20this%20point%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-794249%22%20slang%3D%22en-US%22%3ERe%3A%20The%20client%20cannot%20connect%20to%20the%20destination%20specified%20in%20the%20request%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-794249%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F24138%22%20target%3D%22_blank%22%3E%40chad%20Snelson%3C%2FA%3E%26nbsp%3B%3A%20The%20first%20step%20I'd%20take%20is%20to%20do%20a%20manual%20deployment%20to%20get%20a%20single%20VM%20running%2C%20and%20see%20if%20that%20works.%20From%20there%2C%20you%20should%20be%20able%20to%20verify%20the%20(1)%20domain%20join%2C%20(2)%20logging%20into%20the%20Windows%20Virtual%20Desktop%20PowerShell%20to%20create%20a%20host%20pool%20and%20registration%20token%20and%20(3)%20installing%20the%20Agents%20with%20the%20registration%20token.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I'm getting the following error when deploying.  The VM's join the domain just fine.

 

"error": { "code": "VMExtensionProvisioningError", "message": "VM has reported a failure when processing extension 'dscextension'. Error message: \"DSC Configuration 'FirstSessionHost' completed with error(s). Following are the first few: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM.

 

 

Can someone let me know what I'm supposed to be troubleshooting?  It's not clear what destination machine is.

4 Replies
Highlighted

@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.

Highlighted

@christianmontoya I tried redeploying several times and it always failed.  I haven't tried since my first post.  I'll go back through the tutorial and let you know if I have success.  Thanks for the reply!

Highlighted
I just redeployed and got the same error. What would you recommend at this point?
Highlighted

@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.