The kernel element of the 32-bit subsystem handles interrupting all graphical output to the system driver. They can be reused at any time on reconnection.įrom a technical perspective, only the RDP and TCP/IP drivers are removed from memory when a connection is terminated without logging off. The IDs of disconnected sessions and the corresponding user IDs are stored in memory. Therefore, the user can reconnect to the session on the terminal server and resume work. The session’s graphical image and user processes are stored on the server just before disconnecting. The connection can also be terminated when a predefined time limit is reached. The user can terminate the connection between client and terminal server without logging off. As soon as the user is identified, he or she can start the interactive session. Finally, the user is authenticated by means of an interactive dialog box or automatic forwarding of the identification information on the client. Then the session space is initialized (Csrss, WinLogon, and kernel driver) and a new idle session is generated. If the connection is successful, it is assigned to one of the idle sessions. This new thread handles the negotiation between server and client regarding cache size, compression, encryption, client version number, license details, and virtual channels. Terminal Services initializes a special thread to handle the request. The kernel driver transmits the request to Terminal Services. As soon as a user connects to the terminal server through his or her client, the connection request is immediately accepted and forwarded to the kernel driver of the appropriate protocol (for example, RDP). A monitoring thread is launched and waits for a connection request via a certain TCP/IP port. When Terminal Services is started, it first initializes two user sessions in idle mode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |