Home Remote Support (Formerly Control Center)

Remote Actions: Computer unavailable

We have installed Remote Support and tried to use Remote Actions. Some clients can be managed, some not. In my test environment there are two clients, both Windows 10 latest Release, both configured with "winrm quickconfig", service account is administrator on both, SCCM- Client is running. One of them can be managed, the second always says "unavailable". 

Service control and process insights report "Client unavailable".

What can i try to solve the problem?


  • Brian_WiestBrian_Wiest Customer Super IT Monkey ✭✭✭✭✭

    I typically start with the basics of the connection between the MGT server and the endpoint.

    Can you ping the workstation from the MGT server? Does that IP address match what in on the endpoint?

    Can you evoke a remote winrm powershell command?

    On the workstation you can also verify that winrm auth is enabled matching the workstation that is working.


  • Sibille_NimtschSibille_Nimtsch Customer IT Monkey ✭

    ping is ok, IP's correct.

    powershell, started on the server server "get-process -Computername <clientname>" works on both Clients

    The winrm Command reports on both clients the same:

    C:\WINDOWS\system32>winrm get winrm/config/client/auth


      Basic = true

     Digest = true

      Kerberos = true

      Negotiate = true

      Certificate = true

      CredSSP = false

  • Brian_WiestBrian_Wiest Customer Super IT Monkey ✭✭✭✭✭

    Log into the MGT server as the service account.

    Attempt a remote WMI query to verify permission.

    Get-WmiObject Win32_ComputerSystem -ComputerName $ComputerName

  • Sibille_NimtschSibille_Nimtsch Customer IT Monkey ✭

    Thanks a lot for your help.

    The first one causes the problem.

  • Brian_WiestBrian_Wiest Customer Super IT Monkey ✭✭✭✭✭

    Might need Cireson support on this.

    I can only guess that the failing computer has a bad SCCM client. It is reporting into SCCM?

  • Sibille_NimtschSibille_Nimtsch Customer IT Monkey ✭

    Client and server are in different IP subnet, so Windows Defender Firewall blocks the communication between server and client. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. We have to change AD group policies and then we will try again.

Sign In or Register to comment.