I using Microsoft Server 2008, and am exploring Remote Applications for the first time. I successfully published the application I wanted to use, but I am running into a problem when the application tries to run a report.
The problem is, the program (in all its antiquated goodness) will not use UNCs, and is looking for the drive letter Q:
I have the drive letter mapped on the client machine and verified under TS Remote App Manager, that Devices and Resources - Disk Drives was checked (I have tried unchecked as well thinking maybe I wasn't reading it correctly).
I have tried writing a new NET USE command in a USRLOGN1.CMD, and put it in the Terminal Server's Windows\System32 directory, and sure enough it will work when my user logs into the actual Terminal Server, but not when I am running the Remote Application published application...
I suppose my question really is, is there a way to make sure a drive letter is being mapped every time a Remote Application is executed?
I've read that there are CMDs that run out of the Application Compatibility Scripts directory, but I am not sure if / which one I should tackle trying to add it to.
Thanks for the help