|
Optimizing Applications for Windows 2000 Terminal Services and Windows nt server 0
|
| bet | 20/49 | | Sana | 29.03.2021 | | Hajmi | 197,5 Kb. | | #13691 |
Do Not Modify the GINA
Modifications to the Graphical Identification and Authentication (GINA) component are supported in Windows 2000 Terminal Services with the availability of Terminal Services APIs that allow for session management and client credential access. Windows NT Server 4.0, Terminal Server Edition does not support modifications to GINA. For more information on the Terminal Services APIs, see the white paper "Using and Understanding APIs for Terminal Server" on the Windows NT Server Web site.
Do Not Replace System Files
Because Terminal Server Edition is a modified version of Windows NT Server 4.0, it uses operating system files with the same file names as a Windows NT Server 4.0 without the Terminal Server enabled, but in fact the files may be very different. Replacing system files, such as the TCP/IP network stack, could result in serious system problems. The same situation can occur if an application replaces Windows 2000 Server operating system files while Terminal Services are enabled.
Negotiate Client/Server Connections Inside the System
and Network
If your application is composed of a server component (such as a service) and client components (such as foreground applications) that communicate with the server component make sure that the server component can differentiate between multiple clients residing on the same system. To accomplish this, clients should establish communication with the server component through a well-defined global interface (for example, Remote Procedure Call or named pipes) and the server and client should negotiate a different communication channel for each user session.
This same client/server consideration applies to client applications running in the Terminal Services environment that need to establish connections to server components over the network. In this case, the client/server connection should use protocols that easily support this type of operation—such as TCP/IP where a different socket connection can be used for each client application. Applications should not assume that a single system connection equates to a single user session.
|
| |
