Using HQ Manager on Terminal Server

Bill,

Here a post from last year about someone running RMS on TS, maybe he can help a bit.

I have been running RMS v1.2 in a Win2k Terminal Server enviornment for three years. The problen that you encountered with duplicate terminal numbers can be resolved by launching the POS or Manager application from a .vbs script. In profiling the communication from the application I found that there is only one read of the registry when the application first loads. Therefore you can write a script that changes the registry before launching the application. I create a term1pos.vbs and term1manager.vbs script and then replace the RMS shortcuts in the profiles with shortcuts to each of these .vbs scripts. Ex. script:

' Begin code for term1pos.vbs ' Written by Ted Archer ' Version: 1.0 (February 25, 2003)

Option Explicit Dim WSHShell, RegKey, RegKey2 Set WSHShell = CreateObject("Wscript.Shell") RegKey = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Retail Management System\Store Operations\Server\Database\" RegKey2 = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Retail Management System\Store Operations\POSUser\Register\" WSHShell.RegWrite regkey & "Provider", "SQLOLEDB.1" WSHShell.RegWrite regkey & "Persist Security Info", "True" WSHShell.RegWrite regkey & "UserID", "sa" WSHShell.RegWrite regkey & "Password", "%TUOY" WSHShell.RegWrite regkey & "Data Source", "192.168.1.2" WSHShell.RegWrite regkey & "Connect Timeout", "45" WSHShell.RegWrite regkey & "Initial Catalog", "RMS" WSHShell.RegWrite regkey2 & "Number", "1" WSHShell.Run("soposuser.exe") ' End Code

You will want to modify the UserID, Password, and Initial Catalog to match what you have configured for your system. Also set the properties of the shortcut to start in "C:\Program Files\Microsoft Retail Management System\Store Operations". Then it is just a matter of setting the Number of the register to match what you have defined in Store Operations.

M$ has made such a push over the last few years towards supporting thin client computing, it is a shame that they cannot or will not write this support into RMS. I have fountd that thin clients are perfect for my receiving and processing operations as this is done in a warehouse environment that is very tough on PCs.

If you need any further help on using thin clients with RMS, please feel free to contact me.

Ted Archer CIO Fairvilla Megastores

Jeff,

This is a good fix if you are trying to run Store Ops on WTS, but unfortunately is not relevant to my concerns. Unlike Store Ops POS, where I can only have X number of simultaneous registers, I can have as many HQ users as I want, and as many copies of HQ Manager running as I wish.

I'm planning on running Headquarters, simply as a quick and easy way to allow multiple users (one at a time) to access the data and reports in HQ. I'm just trying to avoid a maintenance headache by centralizing access to the HQ data forms and reports on one machine.

Bill Yater The Worth Collection snipped-for-privacy@worthltd.com

"Jeff" wrote:

Bill,

I sent it to you as a potential contact for someone else using TS that was offering his help. The copied message was not necessarily pertaining to your issue, just didn't want to snip the rest.

Hi Bill,

I'm running HQ manager on a Terminal server now, no hoops to jump through, just install the application and allow TS users to access it. I normally put it so that it will launch the HQ manager application when they log in, so that they can't use other apps or even see the desktop when they log in. When they exit the app, it will log them out. I'm no expert, but let me know if you are into any problem, I will try to help.

Regards, Raym> Has anyone ever tried to deploy RMS Headquarters on a Terminal Server? If so,