How is Royal Server Working?

Royal Server consists of three components: the Management Endpoint, the Secure Gateway and the Document Store. For the Management Endpoint and the Document Store component: Royal Server is based on HTTP/S and is using Windows security features like local users and groups to ensure proper authentication.

The Secure Gateway component is based on SSH standards.

Client devices like desktop computers running Royal TS/X or mobile devices running Royal TS for Android or iOS are accessing Royal Server over HTTP/S (possibly using a VPN tunnel). Royal Server itself is using different technologies to talk to the managed servers, depending on the used component and module. The Secure Gateway component is using a standards-based SSH connection.

In order to configure managed servers, please check the topic Configuration of Managed Servers.

Under the hood

Royal Server needs to query managed servers in order to get the required information (e.g. the list of Windows Services).

For this, there are two basic ways this can be done:

• using WMI
• using CIM

Note

The Terminal-Services Module is using the WTS API of Microsoft to get its data from the remote machine.

Using WMI

From Wikipedia, the free encyclopedia:

WMI (Windows Management Instrumentation) is a set of driver extensions to the Windows Driver Model that provides an operating system interface through which instrumented components provide information and notification.

WMI is Microsoft's implementation of Web-Based Enterprise Management (WBEM) and Common Information Model (CIM). It relies on a binary communication protocol that is using dynamic ports (TCP/135 for standard RPC and a randomly assigned port between 1024-65535 (for Windows 2003 and older) or 49152-65535 (for Windows 2008 and newer).