SOLVED

Remote Desktop not working in Admin Center

%3CLINGO-SUB%20id%3D%22lingo-sub-279203%22%20slang%3D%22en-US%22%3ERemote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279203%22%20slang%3D%22en-US%22%3E%3CP%3ESetup%20a%20test%20of%20the%20Windows%20Admin%20Center%2C%20the%20only%20thing%20I%20cant%20seem%20to%20get%20to%20work%20is%20the%20Remote%20Desktop%20tab.%20I%20just%20get%20the%20spinning%20dots%20and%20errors%20in%20the%20console%2C%20which%20I%20have%20attached.%20Any%20Ideas%20on%20how%20to%20resolve%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-279203%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%20Center%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ERemote%20Desktop%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Admin%20Center%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-303670%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-303670%22%20slang%3D%22en-US%22%3EI%20updated%20to%201809.5%20which%20resolved%20my%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-303542%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-303542%22%20slang%3D%22en-US%22%3EI'm%20still%20unable%20to%20remote%20desktop%20via%20Admin%20Center%20even%20after%20making%20the%20changes%20in%20the%20registry%3A%3CBR%20%2F%3E%3CBR%20%2F%3EREG%20ADD%20%22HKLM%5CSOFTWARE%5CPolicies%5CMicrosoft%5CWindows%20NT%5CTerminal%20Services%22%20%2Fv%20%22KeepAliveEnable%22%20%2Ft%20REG_DWORD%20%2Fd%201%20%2Ff%3CBR%20%2F%3EREG%20ADD%20%22HKLM%5CSOFTWARE%5CPolicies%5CMicrosoft%5CWindows%20NT%5CTerminal%20Services%22%20%2Fv%20%22KeepAliveInterval%22%20%2Ft%20REG_DWORD%20%2Fd%201%20%2Ff%3CBR%20%2F%3E%3CBR%20%2F%3EI'm%20receiving%20the%20following%20error%3A%3CBR%20%2F%3EHTTP400%3A%20BAD%20REQUEST%20-%20The%20request%20could%20not%20be%20processed%20by%20the%20server%20due%20to%20invalid%20syntax.%20(XHR)PUT%20-%20https%3A%2F%2F%5Bgatewayserver%3A8080%5D%2Fapi%2Fnodes%2F%5Bservername%5D%2Ffeatures%2FpowershellApi%2Fpssessions%2FinstantSession%3CBR%20%2F%3E%3CBR%20%2F%3EI%20installed%20version%201809%20on%20a%20new%202016%20vm%20that%20has%20nothing%20else%20installed%20on%20it.%20Any%20assistance%20would%20be%20greatly%20appreciated.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297162%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297162%22%20slang%3D%22en-US%22%3E%3CP%3EExactly.%20It%20is%20important%20that%20there%20is%20at%20least%20one%20value%20in%20this%20place.%20The%20name%2C%20type%2C%20and%20data%20of%20that%20value%20can%20be%20anything.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20bug%20was%20probably%20fixed%20in%20Windows%20Admin%20Center%201809.5%20Insider%20Preview.%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fwindowsexperience%2F2018%2F12%2F11%2Fannouncing-windows-admin-center-1809-5-insider-preview%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.windows.com%2Fwindowsexperience%2F2018%2F12%2F11%2Fannouncing-windows-admin-center-1809-5-insider-preview%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297134%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297134%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can%20confirm%20that%20setting%20either%20of%20these%20works.%20It%20is%20not%20necessary%20to%20add%20both%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EREG%20ADD%20%22HKLM%5CSOFTWARE%5CPolicies%5CMicrosoft%5CWindows%20NT%5CTerminal%20Services%22%20%2Fv%20%22KeepAliveEnable%22%20%2Ft%20REG_DWORD%20%2Fd%201%20%2Ff%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSPAN%3EREG%20ADD%20%22HKLM%5CSOFTWARE%5CPolicies%5CMicrosoft%5CWindows%20NT%5CTerminal%20Services%22%20%2Fv%20%22KeepAliveInterval%22%20%2Ft%20REG_DWORD%20%2Fd%201%20%2Ff%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-293447%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-293447%22%20slang%3D%22en-US%22%3E%3CP%3EConfirmed%20as%20well!%26nbsp%3B%20Thank%20you.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGPO%20%3D%20Windows%20Components%2FRemote%20Desktop%20Services%2FRemote%20Desktop%20Session%20Host%2FConnections%2FAllow%20users%20to%20connect%20remotely%20by%20using%20Remote%20Desktop%20Services%20%3D%20Enabled%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-293337%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-293337%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20confirm%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F177295%22%20target%3D%22_blank%22%3E%E3%81%8B%E3%81%9A%E3%81%8A%20%E5%B1%B1%E5%86%85%3C%2FA%3E%26nbsp%3BSolution%20worked%20for%20me!%20Thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-293255%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-293255%22%20slang%3D%22en-US%22%3E%3CP%3EI%20could%20fix%20this%20problem%20by%20enabling%20%22Allow%20users%20to%20connect%20remotely%20by%20using%20Remote%20Desktop%20Services%22%20policy%20settings%20(gpedit.msc%20or%20gpo).%20This%20policy%20add%20fDenyConnection%3D0%20value%20to%20%22HKLM%5CSOFTWARE%5CPolicies%5CMicrosoft%5CWindows%20NT%5CTerminal%20Services%22%2C%20so%20%24resgistryKey%20never%20set%20to%20null.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-293184%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-293184%22%20slang%3D%22en-US%22%3E%3CP%3EPerhaps%20it%20is%20only%20necessary%20for%20something%20to%20exist%20in%20the%20%22HKLM%5CSOFTWARE%5CPolicies%5CMicrosoft%5CWindows%20NT%5CTerminal%20Services%22%20key.%20If%20there%20is%20no%20value%20in%20this%20reg%20path%2C%20%24regisgtryKey%20vaiable%20(you%20can%20see%20it%20by%20using%20%5B%26gt%3B_%5D%20show%20power%20shell%20script%20button)%20set%20to%20null%2C%20and%20followed%20script%20will%20cause%20error.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%24registryKey%20%3D%20Get-ItemProperty%20-Path%20%24RdpGroupPolicyRegistryKey%20-ErrorAction%20SilentlyContinue%3C%2FP%3E%0A%3CP%3Eif%20((Get-Member%20-ImputObject%20%24registryKey%20...%20%26lt%3B-%20Error%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-293167%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-293167%22%20slang%3D%22en-US%22%3E%3CP%3EI%20also%20had%20problems%20with%20remote%20desktop%20connection%20not%20working%20on-premises.%20And%20Settings%20%26gt%3B%20Remote%20Desktop%20page%20show%20%22Get-Member%22%20errors.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBut%20when%20setting%20up%20in%20the%20Azure%20VM%20environment%2C%20Remote%20Desktop%20Connection%20worked%20without%20any%20problems.%20Therefore%2C%20when%20comparing%20Remote%20Desktop%20settings%20in%20the%20registry%2C%20I%20confirmed%20that%20the%20following%20two%20values%20exist%20on%20the%20Azure%20VM%20side%20and%20do%20not%20exist%20in%20the%20on-premise%20side%20clean%20installation%20environment.%20%3CBR%20%2F%3E%3CBR%20%2F%3EHKLM%5CSOFTWARE%5CPolicies%5CMicrosoft%5CWindows%20NT%5CTerminal%20Services%3CBR%20%2F%3EKeepAliveEnable%26nbsp%3B%26nbsp%3B%20%26nbsp%3BREG_DWORD%26nbsp%3B%26nbsp%3B%20%26nbsp%3B1%3CBR%20%2F%3EKeepAliveInterval%26nbsp%3B%26nbsp%3B%20%26nbsp%3BREG_DWORD%26nbsp%3B%26nbsp%3B%20%26nbsp%3B1%3CBR%20%2F%3E%3CBR%20%2F%3EI%20created%20the%20same%20registry%20by%20running%20these%20command%20line%20on%20a%20remote%20server%20on-premises%2C%20the%20problem%20was%20solved.%26nbsp%3B%20Settings%20%26gt%3B%20remote%20desktop%20page's%20error%20was%20also%20gone.%20%EF%BC%88You%20do%20not%20need%20to%20restart%20the%20server.)%3CBR%20%2F%3E%3CBR%20%2F%3EREG%20ADD%20%22HKLM%5CSOFTWARE%5CPolicies%5CMicrosoft%5CWindows%20NT%5CTerminal%20Services%22%20%2Fv%20%22KeepAliveEnable%22%20%2Ft%20REG_DWORD%20%2Fd%201%20%2Ff%3CBR%20%2F%3EREG%20ADD%20%22HKLM%5CSOFTWARE%5CPolicies%5CMicrosoft%5CWindows%20NT%5CTerminal%20Services%22%20%2Fv%20%22KeepAliveInterval%22%20%2Ft%20REG_DWORD%20%2Fd%201%20%2Ff%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-289749%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-289749%22%20slang%3D%22en-US%22%3E%3CP%3EUpgraded%20to%20Windows%2010%201809%2C%20still%20same%20issue.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-287196%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-287196%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20a%20bug%20.%20Jeff%20Woolslayer%20find%20root%20cause%20%3A%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-Admin-Center%2FWindows-Admin-Center-1809-Generally-Available%2Fm-p%2F267971%2Fhighlight%2Ftrue%23M166%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-Admin-Center%2FWindows-Admin-Center-1809-Generally-Available%2Fm-p%2F267971%2Fhighlight%2Ftrue%23M166%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-285993%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-285993%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20the%20consistent%20error%20on%20Win10%201709%20and%201803%20for%20remote%20desktop%20module%20only.%26nbsp%3B%20Event%20viewer%20and%20Powershell%20work%20fine.%3C%2FP%3E%3CP%3E%3CSPAN%3EHTTP400%3A%20BAD%20REQUEST%20-%20The%20request%20could%20not%20be%20processed%20by%20the%20server%20due%20to%20invalid%20syntax.%20(XHR)PUT%20-%20https%3A%2F%2Flocalhost%3A6516%2Fapi%2Fnodes%2F%5Bservername%5D%2Ffeatures%2FpowershellApi%2Fpssessions%2FinstantSession%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280560%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280560%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20same%20exact%20errors%20when%20attempting%20to%20RDP.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280558%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280558%22%20slang%3D%22en-US%22%3E%3CP%3EOh%20sorry%2C%20I%20thought%20you%20were%20referencing%20some%20'developer%20console'%20for%20admin%20center%20specifically.%26nbsp%3B%20Wasn't%20thinking%20at%20all%20about%20browser%20functionality.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280408%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280408%22%20slang%3D%22en-US%22%3E%3CP%3EIts%20built%20into%20most%20browsers%2C%20I%20have%20attached%20how%20to%20find%20it%20in%20chrome%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-279907%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279907%22%20slang%3D%22en-US%22%3E%3CP%3EDeveloper%20console%3F%26nbsp%3B%20Is%20that%20a%20separate%20install%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-279841%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279841%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20you%20getting%20the%20same%20errors%20in%20your%20developer%20console%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-279803%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279803%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20stood%20up%20admin%20center%20as%20well%20and%20am%20having%20the%20same%20exact%20issue%20with%20remote%20desktop.%26nbsp%3B%20I've%20tried%20to%20connect%20to%20multiple%20different%20server%20using%20edge%2C%20chrome%2C%20firefox...%20remote%20desktop%20just%20'spins'.%26nbsp%3B%20Never%20connects.%26nbsp%3B%20Everything%20else%20seems%20to%20be%20working.%3C%2FP%3E%3CP%3EAdmin%20center%20installed%20on%202019%20server....attempting%20to%20remote%20desktop%20to%202019%2C%202016%2C%202012%20servers.%26nbsp%3B%20None%20work.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-279750%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279750%22%20slang%3D%22en-US%22%3E%3CP%3EUpdated%20to%20the%20latest%20Chrome%20Version%26nbsp%3B%3CSPAN%3E70.0.3538.77%20and%20still%20having%20the%20same%20issue.%20The%20problem%20also%20happens%20in%20other%20browsers%20like%20Edge.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-279718%22%20slang%3D%22en-US%22%3ERE%3A%20Remote%20Desktop%20not%20working%20in%20Admin%20Center%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279718%22%20slang%3D%22en-US%22%3EI've%20noticed%20a%20few%20problems%20with%20this...%20particularly%20with%20Chrome.%20As%20of%20Chrome%2070%2C%20it's%20working%20perfectly%20for%20me%2C%20but%20if%20you're%20still%20on%20older%20release%2C%20there's%20a%20lot%20of%20known%20issues%20with%20it.%20Any%20extra%20details%20you%20can%20provide%20might%20be%20helpful%20here...%3C%2FLINGO-BODY%3E
Highlighted
Deleted
Not applicable

Setup a test of the Windows Admin Center, the only thing I cant seem to get to work is the Remote Desktop tab. I just get the spinning dots and errors in the console, which I have attached. Any Ideas on how to resolve? 

20 Replies
Highlighted
I've noticed a few problems with this... particularly with Chrome. As of Chrome 70, it's working perfectly for me, but if you're still on older release, there's a lot of known issues with it. Any extra details you can provide might be helpful here...
Highlighted

Updated to the latest Chrome Version 70.0.3538.77 and still having the same issue. The problem also happens in other browsers like Edge. 

Highlighted

I just stood up admin center as well and am having the same exact issue with remote desktop.  I've tried to connect to multiple different server using edge, chrome, firefox... remote desktop just 'spins'.  Never connects.  Everything else seems to be working.

Admin center installed on 2019 server....attempting to remote desktop to 2019, 2016, 2012 servers.  None work.

Highlighted

Are you getting the same errors in your developer console? 

Highlighted

Developer console?  Is that a separate install?

Highlighted

Its built into most browsers, I have attached how to find it in chrome

Highlighted

Oh sorry, I thought you were referencing some 'developer console' for admin center specifically.  Wasn't thinking at all about browser functionality.

Highlighted

Yes same exact errors when attempting to RDP.

Highlighted

This is the consistent error on Win10 1709 and 1803 for remote desktop module only.  Event viewer and Powershell work fine.

HTTP400: BAD REQUEST - The request could not be processed by the server due to invalid syntax. (XHR)PUT - https://localhost:6516/api/nodes/[servername]/features/powershellApi/pssessions/instantSession

Highlighted
Highlighted

Upgraded to Windows 10 1809, still same issue. 

Highlighted

I also had problems with remote desktop connection not working on-premises. And Settings > Remote Desktop page show "Get-Member" errors.

 

But when setting up in the Azure VM environment, Remote Desktop Connection worked without any problems. Therefore, when comparing Remote Desktop settings in the registry, I confirmed that the following two values exist on the Azure VM side and do not exist in the on-premise side clean installation environment.

HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services
KeepAliveEnable    REG_DWORD    1
KeepAliveInterval    REG_DWORD    1

I created the same registry by running these command line on a remote server on-premises, the problem was solved.  Settings > remote desktop page's error was also gone. (You do not need to restart the server.)

REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v "KeepAliveEnable" /t REG_DWORD /d 1 /f
REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v "KeepAliveInterval" /t REG_DWORD /d 1 /f

Highlighted

Perhaps it is only necessary for something to exist in the "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" key. If there is no value in this reg path, $regisgtryKey vaiable (you can see it by using [>_] show power shell script button) set to null, and followed script will cause error.

$registryKey = Get-ItemProperty -Path $RdpGroupPolicyRegistryKey -ErrorAction SilentlyContinue

if ((Get-Member -ImputObject $registryKey ... <- Error

Highlighted
Best Response
Solution

I could fix this problem by enabling "Allow users to connect remotely by using Remote Desktop Services" policy settings (gpedit.msc or gpo). This policy add fDenyConnection=0 value to "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services", so $resgistryKey never set to null.

Highlighted

Can confirm かずお 山内 Solution worked for me! Thanks

Highlighted

Confirmed as well!  Thank you. 

 

GPO = Windows Components/Remote Desktop Services/Remote Desktop Session Host/Connections/Allow users to connect remotely by using Remote Desktop Services = Enabled

Highlighted

I can confirm that setting either of these works. It is not necessary to add both:

 

REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v "KeepAliveEnable" /t REG_DWORD /d 1 /f


REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v "KeepAliveInterval" /t REG_DWORD /d 1 /f

Highlighted

Exactly. It is important that there is at least one value in this place. The name, type, and data of that value can be anything.

 

This bug was probably fixed in Windows Admin Center 1809.5 Insider Preview.
https://blogs.windows.com/windowsexperience/2018/12/11/announcing-windows-admin-center-1809-5-inside...

Highlighted
I'm still unable to remote desktop via Admin Center even after making the changes in the registry:

REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v "KeepAliveEnable" /t REG_DWORD /d 1 /f
REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v "KeepAliveInterval" /t REG_DWORD /d 1 /f

I'm receiving the following error:
HTTP400: BAD REQUEST - The request could not be processed by the server due to invalid syntax. (XHR)PUT - https://[gatewayserver:8080]/api/nodes/[servername]/features/powershellApi/pssessions/instantSession

I installed version 1809 on a new 2016 vm that has nothing else installed on it. Any assistance would be greatly appreciated.