Remote Desktop Services Support

[John Bevan]

Adding Windows Server 2008 (and previous server versions of windows) to the supported operating systems, and including terminal services / remote desktop services support would allow users to install one copy of the application centrally, with users accessing this instance remotely.  For teams distributed in various countries / remote locations, this would improve the performance of the application as the program could be located centrally, along with the data files.
Additionally, this would avoid the need for clients to install the application, reducing the support overhead.

[John Bevan]

== I've just tested on Window Server 2003 & it seems to work, despite that OS not being listed as supported - it's only 2008 with the issue ==

[Wowbagger]

One thing I've tried that works is to run EA under Wine, and then tunnel it via SSH - that will allow EA to run on machine while displaying on another.

Just FYI.

[John Bevan]

Nice trick.  Sadly we're an MS only shop, so have to stick to Windows Server.  However, I've got it working on Win 2003, and with a bit of registry manipulation (registerring DLLs and pointing addins to these), have also got ScreenArchitect working on TS for those users we've licensed.  Should anyone want to use this trick, I've outlined the process below.

After installing enterprisearchitect & screenarchitect, run regedit & export the following three keys.

[HKEY_CURRENT_USER\Software\Sparx Systems\EAAddins\ScreenArchitect]
[HKEY_CLASSES_ROOT\SA.ScreenArchitect.Addin.ScreenArchitectPrototypeHost]
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{3D864CB6-8738-3247-B08A-897D9D474145}]

Next, for each user with a named-license for SA, get them to log in to the terminal server (desktop session, rather than pointing to an application) and run each of the exported .reg files.
When they now log into EA through TS, the SA addin should appear.