Deployment of VMs to WVD host pool fails with VMAgentStatusCommunicationError

%3CLINGO-SUB%20id%3D%22lingo-sub-1675460%22%20slang%3D%22en-US%22%3EDeployment%20of%20VMs%20to%20WVD%20host%20pool%20fails%20with%20VMAgentStatusCommunicationError%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1675460%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20following%20Robin%20Hobo's%20%3CA%20href%3D%22https%3A%2F%2Fwww.robinhobo.com%2Fhow-to-create-a-custom-windows-10-multi-user-image-with-lob-applications-for-windows-virtual-desktop-preview-wvd-hostpool-deployments%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EWVD%20guide%3C%2FA%3E.%20I%20am%20aiming%20to%20test%20creation%20of%20a%20custom%20Windows%2010%20multi-user%20image%20with%20LOB%20applications%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20created%20a%20custom%20image%2C%20generalized%20it%2C%20and%20then%20saved%20the%20image%20to%20a%20Shared%20Image%20Gallery.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20created%20a%20new%20WVD%20host%20pool%20using%20my%20custom%20image.%20When%20I%20do%20this%2C%20it%20creates%20the%20VMs%20but%20fails%20at%20the%20joindomain%20stage%20with%20the%20VMAgentStatusCommunicationError%20error%20below.%20This%20seems%20to%20be%20because%20the%20Azure%20VM%20agent%20is%20not%20running.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EI%20have%20verified%20connectivity%20on%20the%20VMs%2FvNet.%20They%20can%20see%20DNS%2FAD%20okay.%3C%2FLI%3E%3CLI%3EIf%20i%20examine%20the%20created%20VMs%20after%20the%20deployment%20failure%2C%20they%20do%20not%20have%20the%20VM%20agent%20running%20(obviously).%20I%20cannot%20RDP%20to%20the%20VMs.%3C%2FLI%3E%3CLI%3EI%20have%20tried%20recreating%20my%20image%20from%20scratch%20once%2C%20but%20got%20the%20same%20error%20second%20time%20around.%3C%2FLI%3E%3C%2FUL%3E%3CDIV%3E%3CPRE%3E%3CSPAN%3E%22code%22%3C%2FSPAN%3E%3CSPAN%3E%3A%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3E%22VMAgentStatusCommunicationError%22%3C%2FSPAN%3E%3CSPAN%3E%2C%3C%2FSPAN%3E%3C%2FPRE%3E%3C%2FDIV%3E%3CPRE%3E%22message%22%3A%20%22VM%20'SVR-AZ-WVD-1'%20has%20not%20reported%20status%20for%20VM%20agent%20or%20extensions.%20Verify%20that%20the%20OS%20is%20up%20and%20healthy%2C%20the%20VM%20has%20a%20running%20VM%20agent%2C%20and%20that%20it%20can%20establish%20outbound%20connections%20to%20Azure%20storage.%20Please%20refer%20to%20https%3A%2F%2Faka.ms%2Fvmextensionwindowstroubleshoot%20for%20additional%20VM%20agent%20troubleshooting%20information.%22%3C%2FPRE%3E%3CP%3E%26nbsp%3BCan%20anyone%20suggest%20any%20troubleshooting%20steps%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Established Member

I am following Robin Hobo's WVD guide. I am aiming to test creation of a custom Windows 10 multi-user image with LOB applications

 

I have created a custom image, generalized it, and then saved the image to a Shared Image Gallery.

 

I have created a new WVD host pool using my custom image. When I do this, it creates the VMs but fails at the joindomain stage with the VMAgentStatusCommunicationError error below. This seems to be because the Azure VM agent is not running.

 

  • I have verified connectivity on the VMs/vNet. They can see DNS/AD okay.
  • If i examine the created VMs after the deployment failure, they do not have the VM agent running (obviously). I cannot RDP to the VMs.
  • I have tried recreating my image from scratch once, but got the same error second time around.
"code""VMAgentStatusCommunicationError",
"message": "VM 'SVR-AZ-WVD-1' has not reported status for VM agent or extensions. Verify that the OS is up and healthy, the VM has a running VM agent, and that it can establish outbound connections to Azure storage. Please refer to https://aka.ms/vmextensionwindowstroubleshoot for additional VM agent troubleshooting information."

 Can anyone suggest any troubleshooting steps?

0 Replies