The majority of older applications do not have built-in provisions to operate in a multi-user environment, so most of the time they need to be appropriately tweaked if installed on a Terminal Server. This is typically accomplished through the use of application compatibility scripts. The scripts are batch files, commonly available from an application vendor, Microsoft (some are included with the operating system), or Internet-based support groups. Their role is to emulate a standalone application environment on a multi-user system. They may need to be run during installation, user logon, and uninstall. Depending on their role, they are located in the Install, Logon, and Uninstall subfolders of the %SystemRoot%\Application Compatibility Scripts folder. Those required on every logon are invoked through a sequence of batch files initiated by the Terminal Server logon script USRLOGON.CMD (residing in the %SystemRoot%\System32 folder), which runs whenever any user logs on to Terminal Server (regardless of the user's logon script). The logon scripts are automatically added to this sequence by the application compatibility installation script.
Fortunately, application compatibility scripts are becoming a thing of the past. A growing number of newer applications do not require them.
Was this article helpful?