Accessing EDX software via Remote Desktop

There are a large number of users that need to be able to access EDX software remotely. Working from home and wanting to access the software on a much more powerful machine is an example.

A common remote connection product is Windows Remote Desktop (RDP), which is built into every windows OS. There is also a MAC OSX version of Windows Remote Desktop.

If you are not familiar with RDP, for Windows OS computers, it can be accessed by typing Remote Desktop in the Search Bar. Opening the Remote Desktop client looks something like this:

and like this on Macintosh computers (available through the Mac App store):

You'll need the IP address or computer name of the machine that you want to access, and Username and Password for a user account on that machine. Once you click connect, it will initiate the connection, then ask you for a password, and once supplied with open the remote machine in a new window.

Other settings:

  • Display tab - for each session, make sure color/color bit depth is set to maximum (32bit).

  • Local Devices and Resources - Normally left unmodified. In some instances can give Remote session access to local drives.

Hardware Key/licensing considerations:

  • Green/purple/black keys - are considered single license "standalone" keys. They keys are not enabled to take advantage of Remote Desktop solutions. If you try to launch SignalPro over RDP that has one of these keys attached, the key will not allow itself to be attached to the RDP session, and SignalPro will report an error that no cirrus license is found, or that any hardware key was found, and won't launch.

  • Red keys - are multi-license keys designed to be used with a license manager that listens on an active TCP/IP connection for requests to launch SignalPro and authenticates against the hardware key. These keys ARE enabled for Remote Desktop use.

  • EDX Cirrus - soft licensing is also enabled for remote desktop.