Terminal Services Setup for Remote Users

Users in remote offices using PCs can access Easy Royalties via Windows Terminal Services. 


Each user in a terminal server environment needs their own private copy of the That’s Rights! front-end and supporting files; however, these separate copies cannot be installed multiple times from the installation .msi, because they are sharing the same windows registry entries. The objective therefore is to install That’s Rights! once, and then make multiple copies of the installation folders – once for each user.  

The instructions below provide a procedure to do this, taking into account registration of the software with the license key, and setting up the default database prior to making the copies.  

Note: Where the text refers to That’s Rights change the text to EasyRoyalties.

General procedure 

1. Install a first copy of That’s Rights! normally on the terminal server.  

2. Register the software with the license key.  

If you’ve already set up the database, use File -> Change Database and point to the database now, and set it as the default; then go to step 4 below.  

3. If you haven’t yet set up a database: Determine the location where you will keep the “production” (shared) database file.  

Your registered copy of That’s Rights! (or EasyRoyalties) is currently pointing to a database file that was automatically created during the trial period. You may keep this database (e.g. if you have already begun populating it with your data), or you can create a new one.  

To keep the ‘trial’ database: 

  • Determine the current name/location: in That’s Rights!(or EasyRoyalties), go to Help -> About That’s Rights…, and look for “Current DB File”  
  • Copy/rename this file to the final name/location  
  • Launch That’s Rights!, and go to File -> Change Database, and connect to the “production” database you have just set up. Say “Yes” to set this as the default database  

To create a new database file: 

  • Launch That’s Rights!  (or EasyRoyalties)
  • Go to File -> New Database…  
  • Create a database file with the final name/location  

4. For each additional user on the server, make a copy of the entire contents of the following directory:  

C:\Program Files\JDC Software\Thats Rights\…  or
C:\Program Files\JDC Software\EasyRoyalties\…

5. Each new user must then create a shortcut for accessing That’s Rights!(or Easy Royalties), using the following command:  

“C:\Program Files\Common Files\Sagekey Software\StartAccess_2003.exe” -normal /profile “Thats Rights” /wrkgrp “C:\Program Files\JDC Software\Thats Rights\System.mdw” “C:\

or for users of Easy Royalties:

“C:\Program Files\Common Files\Sagekey Software\StartAccess_2003.exe” -normal /profile “Thats Rights” /wrkgrp “C:\Program Files\JDC Software\EasyRoyalties\System.mdw” “C:\

where [new_location] is the path to the copied software from step 4.  

Sample Procedure and Scripts

The procedure outlined below uses naming conventions and variable-driven scripts which may be useful as an example of how to manage That’s Rights! in a terminal server  environment.  

Procedure for creating a new instance of That’s Rights! (or EasyRoyslties) on a terminal server (this assumes you have already installed & registered That’s Rights! once on the terminal server):  

1. Ensure that you are not running That’s Rights (or Easy Royalties) in your remote desktop session (otherwise step 3 will throw an error).  

2. Using your remote desktop session, locate the following folder using Windows Explorer:  

C:\Program Files\JDC Software  

3. Select (click once) on the “Thats Right” folder and click Edit…Copy and then Edit…Paste. You will now have a new folder called “Copy of Thats Rights”  

4. Rename this new folder to “Thats Rights – <login.name>”, where <login.name> exactly matches the remote desktop login name for the intended user, e.g. “Thats Rights – david.meads”. If you do not exactly match the login name in the new folder name, when the  intended user attempts to start That’s Rights, they will get an error message.  

5. Create a shortcut for the new user, and locate in the user’s profile (so they see it on their personal desktop):  

“C:\Program Files\Common Files\Sagekey Software\StartAccess_2003.exe” -normal  

/profile “Thats Rights” /wrkgrp “C:\Program Files\JDC Software\Thats  

Rights\System.mdw” “C:\Program Files\JDC Software\Thats Rights –  

%username%\trmain.mde” /runtime /excl  

The creation of this shortcut would need to be done using the intended user’s remote desktop session as you cannot create shortcuts for other people’s remote desktop using your own remote desktop.  

Windows PowerShell script to copy the files from the installation folder to each user instance folder:  

$UserFolders = get-childitem “C:\Program Files\JDC Software” -exclude “Thats Rights” |  

Where {$_.psIsContainer -eq $true}  

ForEach ($Folder in $UserFolders) {copy-item “C:\Program Files\JDC Software\Thats  

Rights\*” -destination $Folder -exclude trlocal.dat -recurse -force }  

If Easy Royalties cannot print from Terminal Services

If the user running Easy Royalties via Terminal Services cannot print this is usually due to one of the issues listed below:

1. Server Configuration

The “exact” same printer driver that is installed on the client desktop (or laptop) needs to be installed on the server.  

2. Desktop Configuration

Printer pooling needs to be enabled on the desktop.

3. Old Version of Snap View

Easy Royalties expects to find the newest version of SnapView.ocx installed (v11.0.8228) and delivers this with the installation process. If you have an older version installed then;

  • Go to your older copy of snapview.ocx;
  • Rename it to something else (e.g. snapview_old.ocx)
  • Place a copy of the newer version in that location