
Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 24
The amount of work it will take to bring an application in line with the Terminal
Server guidelines varies from one application to another. If an application was
designed to operate in a multi-user network environment, chances are it will take
very little tweaking to turn it into an application that is optimized for Windows NT
Server 4.0, Terminal Server Edition.. This is what Application Compatibility scripts
are designed for.
This document has presented a variety of guidelines and suggestions for using and
developing applications compatibility scripts for the Terminal Server environment.
All of these guidelines and suggestions should be taken into consideration when
you develop 32-bit applications; however, the three main points you should
remember about the Terminal Server environment are:
• Registry Settings - Applications keep configuration information in a system
database called the registry. The two most important sections of the registry
are called HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER. Being
aware of the differences between these two locations and the impact they have
on the application is critical to optimal performance
• Files - The files and directories an application uses can also cause problems.
Primarily, the issue is with applications that use public locations for per-user
files. It is important to be able to find the files that are inaccessible for whatever
reason and make them available to the application/user.
• Object - Windows applications can create objects (such as Events, Devices,
Semaphores, and Sections) which are used to communicate with other
applications. Each object has a name which is globally visible on the system.
This can create a problem similar to shared files. Take this into account
By taking these points into consideration, System Administrators, developers, etc.
can make the most of their a pplications in the Terminal Server enviro nment.
Comentarios a estos manuales