Terminal server windows 2000 console

Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. One of my client have a Windows Server and I can connect to this server using remote desktop.

I did a lot of google search The console option was added to Remote Desktop in Windows Server It is not available on Windows Server Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Connection to Terminal Server administrator console Ask Question.

Each connection is given a unique session identifier or "SessionID" to represent an individual session to the Terminal Server. Each process created within a session is "tagged" with the associated SessionID to differentiate its namespace from any other connection's namespace. The console Terminal Server keyboard, mouse, and video session is always the first to load, and is treated as a special-case client connection and assigned SessionID.

The console session starts as a normal Windows NT system session with the configured Windows NT display, mouse, and keyboard drivers loaded. The modified Windows NT image loader will recognize this Win32k. It will then relocate the code portion of the image into physical memory, with pointers from the virtual kernel address space for that session, if Win32k. By design, it will always attach to a previously loaded image's code Win32k.

For example, from any active application or session. The data or non-shared section of this image will then be allocated to the new session from a newly created SessionSpace pageable kernel memory section. Unlike the console session, Terminal Server Client sessions are configured to load separate drivers for the display, keyboard, and mouse. The mouse and keyboard drivers communicate into the stack through the multiple instance stack manager, termdd.

These drivers allow the RDP client session to be remotely available and interactive. Finally, Terminal Server will also invoke a connection listener thread for the RDP protocol, again managed by the multiple instance stack manager Termdd.

This prevents processes with different SessionIDs from accessing another session's data. Non-Windows-based clients are supported by the Citrix Metaframe add-on. The listener thread will hand over the incoming session to the new RDP stack instance and continue listening on TCP port for further connection attempts. Each RDP stack is created as the client sessions are connected to handle negotiation of session configuration details. The first details will be to establish an encryption level for the session.

The Terminal Server will initially support three encryption levels: low, medium, and high. Low encryption will encrypt only packets being sent from the client to the Terminal Server. This "input only" encryption is to protect the input of sensitive data, such as a user's password. Medium encryption will encrypt outgoing packets from the client the same as low-level encryption, but will also encrypt all display packets being returned to the client from the Terminal Server.

This method of encryption secures sensitive data, as it travels over the network to be displayed on a remote screen. Both low and medium encryption use the Microsoft-RC4 algorithm modified RC4 algorithm with improved performance with a bit key. Installing Terminal Services in remote administration mode is the most common and the simplest configuration.

This mode gives systems administrators the ability to remotely control a Win2K server. Remote administration mode doesn't require a Terminal Services License Server, and applications installed on the server aren't tuned for multiple interactive users.

But doing so can have unexpected results as applications running on the server aren't tuned for simultaneous users. Select the Terminal Services check box, and click Next, as Figure 2. To add or remove a component, click the checkbox.

A shaded box means that only part of the component will be installed. To see what's included in a component, click Details.