I am in the process of rolling out Thin Clients that will be connecting to a Citrix Server running on Windows Server 2003. The core application that the Thin Client users will be accessing on the Citrix Servers is a product called Symitar. Symitar is a banking application. The Thin Clients are XP Embedded and have Topaz USB Signature Pads attached to them. The Signature pads are used when transactions are completed. USB Sig Pads are not natively supported in Windows Server 2003 Terminal Services and Citrix Presentation Server 4.5 However, Topaz has created a program that runs on the server that will allow the information form the Sig pad to be transferred to the Terminal Server Session. This works great with the testing application that Topaz supplies for testing the Sig pad functionality. The testing application uses an ini file that is stored in the users profile\windows directory (sigplus.ini). This file is unique to each user, thus creating a separate sigsock session for the signature pad information to be transferred to user's terminal server session. This works very well!
Here is the issue: The core application that we need to use the Signature Pads with also uses the Sigplus.ini file. However, the application will only look in c:\windows\ for the Sigplus.ini. This is an issue because this sigplus.ini file needs to be unique and is not. Because of this, the core application used the same same file for everyone and the signature pads to not work.
The vendor will not change the location where program accesses the sigplus.ini.
I have tried using a variable (%username%) in the ini file, but the program does not treat %username% as a variable.
Any thoughts would be greatly appreciated!
