Windows-based terminal server

This app can Access all your files, peripheral devices, apps, programs and registry Access your Internet connection Microsoft. Permissions info. Installation Get this app while signed in to your Microsoft account and install on up to ten Windows 10 devices. Additional terms Windows Terminal privacy policy Terms of transaction.

Seizure warnings Photosensitive seizure warning. Report this product Report this app to Microsoft Thanks for reporting your concern. Our team will review it and, if necessary, take action. Sign in to report this app to Microsoft. Report this app to Microsoft. Report this app to Microsoft Potential violation Offensive content Child exploitation Malware or virus Privacy concerns Misleading app Poor performance.

How you found the violation and any other useful info. Submit Cancel. System Requirements Minimum Your device must meet all minimum requirements to open this product OS Windows 10 version Recommended Your device should meet these requirements for the best experience OS Windows 10 version 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. High encryption will encrypt packets in both directions, to and from the client, but will use the industry standard RC4 encryption algorithm, again with a bit key.

A font exchange will occur between the client and server to determine which common system fonts are installed. The client will notify the Terminal Server of all installed system fonts, to enable faster rendering of text during an RDP session.

When the Terminal Server knows what fonts the client has available, you can save network bandwidth by passing compressed font and Unicode character strings, rather than larger bitmaps, to the client. By default, all clients reserve 1. The Terminal Server also contains buffers to enable flow-controlled passing of screen refreshes to clients, rather than a constant bitstream.

When user interaction at the client is high, the buffer is flushed at approximately 20 times per second. During idle time, or when there is no user interaction, the buffer is slowed to only flush 10 times per second. You can tune all these numbers through the registry.

After session details have been negotiated, the server RDP stack instance for this connection will be mapped to an existing idle Win32k user session, and the user will be prompted with the Windows NT logon screen. If autologon is configured, the encrypted username and password will be passed to the Terminal Server, and logon will proceed. Much of the Win32k user session is utilizing shared code and will load noticeably faster after one instance has previously loaded.

After the user types a username and password, packets are sent encrypted to the Terminal Server. If a SessionID is already associated with this user for example, a disconnected session exists , the currently active session stack is attached to the old session. The temporary Win32 session used for the initial logon is then deleted. If for some reason more than one session is active for this user, the list of sessions is displayed and the user decides which one to select for reconnection.

After user logon, the desktop or application if in single-application mode is displayed for the user. When the user selects a bit application to run, the mouse commands are passed to the Terminal Server, which launches the selected application into a new virtual memory space 2-GB application, 2-GB kernel.

However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article.

If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request.

The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:.

If you do not see your language, it is because a hotfix is not available for that language. Important Windows Vista and Windows Server hotfixes are included in the same packages.

To request the hotfix package that applies to both Windows Vista and Windows Server , just select the product that is listed on the page. The English version of this hotfix has the file attributes or later file attributes that are listed in the following table. When you view the file information, it is converted to local time.

The security catalog files attributes not listed are signed with a Microsoft digital signature. Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly.