The remote session was disconnected because there are no Remote Desktop License Servers available

%3CLINGO-SUB%20id%3D%22lingo-sub-775519%22%20slang%3D%22en-US%22%3EThe%20remote%20session%20was%20disconnected%20because%20there%20are%20no%20Remote%20Desktop%20License%20Servers%20available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-775519%22%20slang%3D%22en-US%22%3E%3CP%3EAnyone%20able%20to%20fix%20this%20error%3F%26nbsp%3B%20We%20got%20a%20similar%20error%20via%20client%20and%20browser.%26nbsp%3B%20After%20changing%20the%20licensing%20mode%20per%20the%20guidance%20at%26nbsp%3B%3CFONT%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Ftroubleshoot-vm-configuration%23remote-licensing-model-is-not-configured%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Ftroubleshoot-vm-configuration%23remote-licensing-model-is-not-configured%3C%2FA%3E%3C%2FFONT%3E%2C%20the%20web%20client%20now%20says%20there%20is%20a%20protocol%20error%2C%20but%20the%20full%20client%20error%20remains%20the%20same.%26nbsp%3B%20Thoughts%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-788053%22%20slang%3D%22en-US%22%3ERe%3A%20The%20remote%20session%20was%20disconnected%20because%20there%20are%20no%20Remote%20Desktop%20License%20Servers%20availabl%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-788053%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20also%20experiencing%20this%20error.%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F135720%22%20target%3D%22_blank%22%3E%40Sekou%20Page%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-789225%22%20slang%3D%22en-US%22%3ERe%3A%20The%20remote%20session%20was%20disconnected%20because%20there%20are%20no%20Remote%20Desktop%20License%20Servers%20availabl%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-789225%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F135720%22%20target%3D%22_blank%22%3E%40Sekou%20Page%3C%2FA%3EIs%20this%20a%20Windows%2010%20Multi-User%20image%3F%26nbsp%3B%20If%20so%2C%20I%20actually%20had%20to%20configure%20a%20RDS%20License%20Server%20and%20use%20GPO%20to%20point%20my%20desktops%20to%20it%20to%20overcome%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Anyone able to fix this error?  We got a similar error via client and browser.  After changing the licensing mode per the guidance at https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-vm-configuration#remote-licensin..., the web client now says there is a protocol error, but the full client error remains the same.  Thoughts?

2 Replies
Highlighted
Highlighted

@Sekou PageIs this a Windows 10 Multi-User image?  If so, I actually had to configure a RDS License Server and use GPO to point my desktops to it to overcome the issue.