Forum Discussion
Remote Desktop not working in Admin Center
- Nov 30, 2018
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.
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
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
- Terry_HoulahanDec 07, 2018Copper Contributor
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- kazuo_yamauchiDec 07, 2018Brass Contributor
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-insider-preview/- cfails77Dec 18, 2018Copper ContributorI'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.
- kazuo_yamauchiNov 30, 2018Brass Contributor
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.
- AnonymousNov 30, 2018
Can confirm かずお 山内 Solution worked for me! Thanks
- Mark Van HornNov 30, 2018Copper Contributor
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