For Royal TSX (for macOS) : the following connection types require Royal Server:

  • Windows Events 
  • Windows Processes
  • Windows Services
  • Terminal Services
  • Hyper-V
  • PowerShell



For Royal TS (for Windows) : the following connection types are supported using Royal Server:

  • Windows Events 
  • Windows Processes
  • Windows Services
  • Terminal Services
  • Hyper-V
  • PowerShell
  • VMware


All these connection types can also be used via "Direct Connect (No Royal Server)". While it's possible to use the new connection types in Royal TS (for Windows) without Royal Server, it's highly recommended to use Royal Server and install it in the same environment where the machines you want to manage are located.

What are the benefits of using Royal Server?

  1. Efficiency - Royal Server bundles the connections from the clients to Royal Server
    Direct Connect of the new connections require different network ports to be open depending on the underlying protocol used. Your networking guys probably wont like this. When using Royal Server only one machine is connecting to the managed servers. We suggest installing Royal Server "close" to the managed servers (in terms of network/firewall)
  2. Standards based - Royal Server uses HTTP/S or SSH
    Royal Server is exposing its functionality via the standard HTTP/S and SSH protocol on a configurable port. 
  3. Cross-Platform - Royal Server can be accessed by non-Windows clients
    Since the protocol is HTTP/S, our non-Windows clients can use this functionality easily - right now we have Royal TSX integrated, and we work hard on adapting our Android and IOS clients. A WinRT client is on the roadmap.
  4. Security - Royal Server adds additional security
    If configured with Authentication enabled, only a specified set of users can access the functionality offered by Royal Server. Also, IP blocking can be configured.
  5. Security - Royal Server adds centralised logging
    If logging is configured on the Royal Server, every action from a client is being logged and can be reviewed later.
  6. Extensibility - Royal Server is the base for many additions
    Having a infrastructure like Royal Server in place, enables us to develop many more features which will benefit from a central server. So far, we have the Management connections, Secure Gateway and Document store plugins available.
  7. Security - Royal Server includes a Secure Gateway
    A Secure Gateway is a component included in Royal Server which can be used to access computers through an encrypted SSH tunnel (aka port forwarding)


OK, but what is this "Direct Connect (No Royal Server)" i can configure in Royal TS V3/V4 (for Windows)?
Since the codebase of Royal Server works directly on Windows, we added an option to execute the code from Royal TS without the Royal Server. But Direct Connect requires you to open many firewall ports (all high ports) in order to communicate with your servers. While it's possible to use all management connections in Royal TS (on Windows) without Royal Server, it's still highly recommended to use Royal Server and install it in the same environment where the machines you want to manage are located. Think of Royal Server as a special kind of "proxy" server which streamlines and channels traffic between Royal TS/X and your managed servers. Your network security guys will be delighted!


This overview should give a clearer picture which features require Royal Server and where it is needed.

Connection Type
Royal TS (for Windows)
Royal TSX (for macOS)
Remote Desktop


VNC


Terminal


Web Page


External Application

 
Performance

 
Terminal Services new
1
2
Hyper-V Management new
1
2
Windows Events new
1
2
Windows Services new
1
2
Windows Processes new
1
2
PowerShell new
1
2
VMware
1
2, ✔ 3


Remarks:
1) Royal TS V3/V4 (for Windows) can handle the new connection types by using Royal Server or via Direct Connect (No Royal Server is required in this case)
2) Royal TSX V2/V3 (for macOS) can handle the new connection types by using Royal Server

3) Royal TSX V3 (for macOS) can handle VMware connections as "Direct Connect"