SIMS Remote Access

To allow remote access to SIMS .net, a separate Windows 2003 server was set up for this sole use and had Terminal Services configured. Initially we use a single user account to log on to the server with just for ease of setting it up quickly and so we didn't have to modify each individual user's account. This user account was given appropriate permissions on the SIMS server to access the share, and on the TS server to be able to log in remotely, run SIMS etc.

Another reason is that our main servers are still running Windows 2000, and its VBScript interpreter doesn't include the required objects or properties to get and set the appropriate Terminal Services items in AD.

The server was placed in its own OU within our CC3 Active Directory (BBARRINGTON.internal\Domain Controllers\Establishments\BBS\Servers - No Inheritance\TS) and did not inherit any other domain GPOs.

To ensure quick logons and a minimal and easy to use interface, we replaced the Windows shell (explorer.exe - Desktop, Start Menu etc) with a batch file that:

• Maps S drive
• Runs SIMS
• Logs off when SIMS process terminates

This is set in the user properties - Environment - Starting Program:

cmd /c start /min c:\sims.bat

@echo off
 
echo.
echo.
echo * * * DO NOT CLOSE THIS WINDOW * * *
echo.
echo.
 
net use * /delete /yes
 
net use S: \\SERVER\SIMSPATH /user:DOMAIN\SIMSUSER PASSWORD /PERSISTENT:NO
 
cd "c:\Program Files (x86)\SIMS\SIMS .net"
 
start /wait Pulsar.exe
 
net use s: /delete /yes
 
logoff

The web part of the remote access is simply to allow staff to download a saved Terminal Services Client .rdp profile to save staff entering details. Any web security can be used to protect access to the .rdp file but in this case, a simple PHP script that checks a posted password is all that was used.