

#ROYAL TSX RDP SHADOW WINDOWS#
This setting works in Windows but does not in OS X ( find a detailed explanation here). In this case, choose a correctly configured Royal Server which points to a Royal Server installation. You get this message in Royal TSX (for OS X) when you try to use a connection that has “Direct Connect (No Royal Server)” selected and that was saved with that setting in Royal TS V3 for Windows. Please assign a Royal Server to the connection” “Direct Connect is not supported for this connection. They can use the same file even at the same time! Just make sure you have configured “Merge file on save” in the document settings. We made sure that you can use the exact same document in clients running on both platforms. Working with the same document in Royal TS (for Windows) V3 and Royal TSX (for OS X) V2 Of course, the same functionality is included in Royal TS (for Windows) V3: Make sure you have the correct credentials to access the remote system configured on the Hyper-V connection:īased on the result and the state of the Hyper-V instance, you can also act on the instances directly from Royal TSX: Since this Connection Type in Royal TSX is based on Royal Server, you will need to specify a Royal Server object:

Simply add a new Hyper-V connection to your document using the “Add” -> “Hyper-V” menu entry: Consider adding users to these groups and restart Royal Server (since group memberships are cached by Royal Server by default). Create a Hyper-V connection in Royal TSX and Royal Server Royal Server can only be accessed by accounts that are member of the 'Royal Server Users' group (for Secure Gateway connections it is the 'Royal Server Gateway Users' group).
#ROYAL TSX RDP SHADOW SERIES#
Remark: This blogpost belongs to a series of posts explaining Royal Server and the new connection types we have introduced with Royal TS V3 (for Windows) and Royal TSX V2 (for OS X).
