Forum Discussion

Deleted's avatar
Deleted
Oct 29, 2018

Remote Desktop not working in Admin Center

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? 

Admin Center
Remote Desktop
Windows Admin Center
  • kazuo_yamauchi's avatar
    kazuo_yamauchi
    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.

  • Aaron Hall's avatar
    Aaron Hall
    Brass Contributor
    Oct 30, 2018
    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...
    • Deleted's avatar
      Deleted
      Oct 30, 2018

      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. 

      • Chad Kegerreis's avatar
        Chad Kegerreis
        Copper Contributor
        Oct 30, 2018

        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.

  • kazuo_yamauchi's avatar
    kazuo_yamauchi
    Brass Contributor
    Nov 30, 2018

    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

    • kazuo_yamauchi's avatar
      kazuo_yamauchi
      Brass Contributor
      Nov 30, 2018

      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

      • kazuo_yamauchi's avatar
        kazuo_yamauchi
        Brass Contributor
        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.

Resources