Thanks for the tip. I gave the VirtualComputerName setting a try and at first pass it failed to work but I have to admit this is the first time I've don't anything with ThinApp or software packa...
See more...
Thanks for the tip. I gave the VirtualComputerName setting a try and at first pass it failed to work but I have to admit this is the first time I've don't anything with ThinApp or software packaging so I'll keep trying to figure this out. I'm sure the VirtualComputerName gets me at least half way there. This application has to be installed from UNC mapping a drive to a "deployment" server which I believe somehow registers its computer name in the deployment server database when the install.exe is launched. If I copy all the install files locally and then run the install, the process fails. After the installation is complete I see the name of the computer in a partially encrypted file and in a database table. I believe each time the application is launched, the name of the computer is queried and matched against this encrypted file - the database table is just a log of what compute names tried to run the application. Since the VirtualComputerName setting didn't work for me the first run, I'm guessing that the application doesn't use the getcomputername api - but if not that, I wonder what it queries? To further complicate this - I said the partially encrypted file does show the computer name. Well, I've noticed that when I try to run the application on a View desktop - at the point it fails it throws up a security screen that has a Serial Code - this code changes with each launch. I'm betting what's encrypted in the file is that serial code matched to the machine name the app was origianlly installed on. The application is JDE Enterprise One - what we call the Fat client. I'll keep trying to get this to work and report back - thanks for all your help. Casey