WVD - Unable to access after restore

%3CLINGO-SUB%20id%3D%22lingo-sub-991743%22%20slang%3D%22en-US%22%3EWVD%20-%20Unable%20to%20access%20after%20restore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-991743%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20testing%20out%20Windows%20Virtual%20Desktop%20when%20I%20tried%20to%20restore%20a%20single%20Windows%2010%20Multi%20session%20host%20using%20Azure%20Backup.%20The%20restore%20operation%20completed%20successfully%20and%20I%20can%20see%20that%20the%20VM%20is%20back%20online.%20However%20whenever%20I%20try%20to%20connect%20with%20the%20Remote%20Desktop%20app%20on%20my%20endpoint%20I%20get%20an%20error%20message%20stating%20internal%20error%20with%20no%20further%20information.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20connected%20to%20our%20domain%20controller%20which%20is%20on%20the%20same%20subnet%20and%20attempted%20to%20connect%20from%20there%20but%20I%20also%20received%20the%20following%20error%20message...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EThe%20remote%20computer%20that%20you%20are%20trying%20to%20connect%20to%20requires%20Network%20Level%20Authentication%20(NLA)%2C%20but%20your%20Windows%20domain%20controller%20cannot%20be%20contacted%20to%20perform%20NLA.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConnectivity%20does%20appear%20to%20be%20working%20as%20I%20was%20prompted%20for%20credentials%20when%20connecting%20from%20the%20Domain%20Controller.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tried%20to%20run%26nbsp%3B%3CSPAN%3EDisableNLA%20from%20the%20Azure%20portal%20however%20this%20seems%20to%20fail%20as%20I%20never%20get%20any%20output.%20I%20have%20also%20attempted%20to%20restore%20a%20different%20image%20but%20the%20result%20was%20the%20same.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWould%20really%20appreciate%20some%20assistance%20with%20this!%20Thanks.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1083832%22%20slang%3D%22en-US%22%3ERe%3A%20WVD%20-%20Unable%20to%20access%20after%20restore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1083832%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F449923%22%20target%3D%22_blank%22%3E%40blcyb%3C%2FA%3E%26nbsp%3B%3A%20I%20realize%20the%20response%20is%20a%20bit%20delayed%2C%20but%20were%20you%20successfully%20able%20to%20restore%3F%20Or%20was%20it%20still%20stuck%20in%20a%20broken%20state%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1108326%22%20slang%3D%22en-US%22%3ERe%3A%20WVD%20-%20Unable%20to%20access%20after%20restore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1108326%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F449923%22%20target%3D%22_blank%22%3E%40blcyb%3C%2FA%3E%20Hi%2C%3C%2FP%3E%0A%3CP%3EThe%20particular%20error%20that%20is%20being%20displayed%20indicates%20that%20the%20restored%20VM%20has%20lost%20trust%20with%20the%20Domain%20controller.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20are%20able%20to%20connect%20to%20the%20directly%20from%20RDP%2FBastion%20(not%20through%20WVD)%20you%20can%20(re)domain%20join%20the%20vm%20and%20that%20should%20fix%20it.%3C%2FP%3E%0A%3CP%3EIf%20you%20are%20NOT%20able%20to%20connect%20to%20the%20VM%20try%20running%20the%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fresources%2Ftemplates%2F201-vm-domain-join-existing%2F%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EDSC%3C%2FA%3E%20to%20do%20domain%20join.%20Last%20time%20that%20is%20what%20I%20used%20to%20fix%20the%20error%20you%20are%20getting.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFYI%20-%20this%20is%20not%20specific%20to%20WVD.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERegards%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ES%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi All,

 

I was testing out Windows Virtual Desktop when I tried to restore a single Windows 10 Multi session host using Azure Backup. The restore operation completed successfully and I can see that the VM is back online. However whenever I try to connect with the Remote Desktop app on my endpoint I get an error message stating internal error with no further information.

 

I connected to our domain controller which is on the same subnet and attempted to connect from there but I also received the following error message...

 

The remote computer that you are trying to connect to requires Network Level Authentication (NLA), but your Windows domain controller cannot be contacted to perform NLA.

 

Connectivity does appear to be working as I was prompted for credentials when connecting from the Domain Controller.

 

I have tried to run DisableNLA from the Azure portal however this seems to fail as I never get any output. I have also attempted to restore a different image but the result was the same.

 

Would really appreciate some assistance with this! Thanks.

2 Replies

@blcyb : I realize the response is a bit delayed, but were you successfully able to restore? Or was it still stuck in a broken state?

@blcyb Hi,

The particular error that is being displayed indicates that the restored VM has lost trust with the Domain controller. 

If you are able to connect to the directly from RDP/Bastion (not through WVD) you can (re)domain join the vm and that should fix it.

If you are NOT able to connect to the VM try running the DSC to do domain join. Last time that is what I used to fix the error you are getting.

 

FYI - this is not specific to WVD.

 

Regards

 

S