When trying to connect to a managed server via the PowerShell module, you might get the following Error logged in the Royal TS/X log:

Error: System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server 10.25.10.101 failed with the following error message : The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.
at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
at System.Management.Automation.RemoteRunspace.Open()
...

The PowerShell module is using PowerShell remoting under the hood to communicate with the managed server.

To enable this, you need to:
1) issue " enable-psremoting " issued on the managed server as well as on the Royal Server
2) issue " winrm quickconfig " issued on the managed server as well as on the Royal Server

Make sure the last command succeeds and adds an exception to the Windows Firewall named "Windows Remote Management (HTTP-In)" and "Windows Remote Management - Compatibility Mode (HTTP-In)"

Additionally, as the exception states, if you dont have Kerberos as authentication scheme or work in a non-domain environment, you need to add the managed host to the TrustedHosts configuration.

Check, which hosts are in the TrustedHosts configuration issued on the Royal Server:

get-item wsman:\localhost\Client\TrustedHosts


Add a new host (issued on the Royal Server):

set-item wsman:\localhost\Client\TrustedHosts -value host01

Remark: you can add "*" for all hosts, but this is not recommended.