How to make win2008 remote desktop more smooth

When using Windows 2008 remote login function, if you need to log in with multiple users, you can use the following configuration method:

Firstly, you need to enable remote desktop: right Click "My Computer" → Properties & Rarr; Remote Configuration & Rarr; Remote Desktop, you can configure the corresponding Remote Desktop function.

First, improve the priority of data display.

By default, in Remote Desktop Services, if you encounter a job such as printing or transferring files, the user's remote session may be frozen. Only after these jobs are completed can they be restored. This means that transmission jobs such as prints or files have a higher priority. This is not very convenient for system engineers to maintain remote servers. To this end, system administrators may wish to increase the priority of remote desktop data display to ensure the stability of remote maintenance.

In the Win2008 version, there is a setting option for displaying the data priority level for the remote desktop. Based on this feature, system engineers can provide higher priority for data such as keyboards, mice, displays, etc. than other virtual channels. With this setting, it is possible to ensure that the remote desktop service and the print file transfer service coexist peacefully. Virtual channel traffic, such as file printing, does not adversely affect the interaction of system administrators with remote sessions.

However, it should be noted that the priority level of remote sessions cannot be set very high. Otherwise, it will adversely affect the normal access of other users to the server. There is a process of mutual equilibrium here. In general, the ratio of the bandwidth used to display the data prioritization feature is preferably controlled at around 60:40. Depending on the situation, appropriate adjustments can be made. This ratio indicates that 60% of the bandwidth is dedicated to display and input data; and 30% of the bandwidth is dedicated to other communication traffic. However, it should be noted that this ratio is not static. You need to make the appropriate adjustments based on the type of remote server. If the remote server is a print server, it is obviously necessary to reduce the bandwidth ratio dedicated to displaying and inputting data. If you need to adjust this ratio, you need to change the keyword in the server registry: FlowControlChargePostCompression. As the name suggests, this key determines the bandwidth based primarily on pre-compressed bytes or post-compressed bytes.

Second, disable Session 0 to improve the security of remote desktop access.

In previous versions, remote session access required the control session Session0. In addition to the interactive login session, Session is also the session in which all services run. The importance of this conversation can be seen. However, this session later proved to be a major security risk. Allowing certain services to run in the same painting that hosts the interactive login gives the attacker an opportunity to attack. To this end, Session0 control sessions become the target of malicious agents who attempt to escalate their rights.

In 2008, some improvements were made to this. Adjust the Session0 session to a non-interactive session. That is to say, in 2008, when the system administrator opens the remote desktop connection to establish an interactive session, the system no longer provides Session0, but directly provides the Session1 session. Provide a Session2 session to the next parallel remote desktop access user. This change has indeed improved the security and performance of remote desktop access. However, what I need to remind here is that Microsoft has also had some side effects after disabling the interactive features of the Session0 session. For example, only connections for up to two remote desktop sessions are allowed at the same time. In previous releases, the server allowed two remote desktop sessions and one remote console session. Now that the Session0 session is changed to a non-interactive session, up to two concurrent Remote Desktop sessions are allowed in 2008, which does not allow remote console sessions. This improves the performance of Remote Desktop Services while reducing the number of sessions.

Third, let the remote connection screen reflect on multiple monitors.

When you encounter some complicated problems, you may need multiple experts to consult. At this point, you need to display the remote desktop on multiple monitors to help each expert solve the problem. To achieve this, you need to use the monitor extension feature of Win2008. The monitor extends, in a nutshell, the simultaneous display of remote desktop sessions on multiple monitors. Each user has a monitor in front of them to facilitate the user to observe the results displayed by the remote desktop.

However, in Win2008, there are some prerequisites for using this feature. If each monitor is required to have the same resolution, the total resolution of each monitor cannot exceed 4096*2048, and each monitor must be horizontally arranged. There is no limit to the number of monitors. However, due to the limitation of the total resolution, the more the number of monitors, the lower the resolution. This is undoubtedly a disguised restriction on the number of monitors.

By default, this feature is not enabled. If the system engineer needs to enable this feature, first of all need to ensure that each monitor meets the conditions specified above. If it is satisfied after the view, you can use the following command on the command line to enable the monitor extension feature: mstsc.exe /span.

Fourth, customize the appropriate resolution.

During the remote desktop connection, it is likely that the client and server resolution settings are different. In this case, the system administrator looks particularly tired and affects the display performance of the system. In previous versions, only two resolutions were provided by default. At this point the system engineer can only do it. In Win2008, system administrators can set the resolution required for remote desktops based on the resolution of the monitor they are using, without the limitations of the resolution used by the remote server.

However, when using this feature, you need to be careful not to set the resolution very high. Because the higher the resolution, the more bandwidth is needed during the transmission. And as I mentioned above, there are no strict restrictions on the number of monitors when using the monitor extension feature, but there is a limit to the total resolution of the resolutions they use. If the resolution is set higher here, the number of monitors that can be used simultaneously is relatively small. If you need to use the monitor extension feature, you need to pay attention to this limitation when adjusting the resolution.

If you need to change the resolution, you can do this by changing the configuration file or by using the command line directly. In general, if the client used for remote access is fixed, it may be appropriate to change the configuration file directly. This resolution setting is also available when you need it next time. If the system engineer temporarily borrows someone else's host for remote access, it is reasonable to use the command line setting. Because this is often one-off. If you want to use the command line, you can use the following command: mstsc.ext /w:1600 /h:1200. This command sets the resolution to 1600*1200.

V. Temporarily turn off unwanted services to improve performance.

On a remote server, there may be many services. However, some services may not be used temporarily. For example, there is a DNS service on the remote server. However, this DNS service is spare. At this point, if you need to make a remote desktop connection to this server, then you can consider suspending these unused services after the connection. This saves server bandwidth consumption and saves more bandwidth for remote desktop sessions. According to the above 60:40 principle, the saved bandwidth can not only improve the display efficiency of the remote desktop, but also improve the performance of other running jobs, such as print file jobs. This can compensate for the negative impact of using a remote desktop session on the server.

However, here is a special reminder that you need to re-enable this temporarily stopped service before disconnecting the remote desktop. In actual work, many system engineers only remember to suspend the service, but forgot to reopen the suspended service, resulting in a lot of unnecessary trouble.

Open Control Panel → Management Tools → Terminal Services → Terminal Services Configuration

1. (Modify the number of people who can log in at the same time, including themselves, The default is 2, if you only need another person to remotely log in to your computer, such as mm or gg, then this step is not necessary, jump directly to the second step) Connections: RDP-tcp right click → Attribute → Network Adapter → Maximum number of connections →

2, Edit settings: Terminal Services licensing mode → Right click → Attribute → General → Restrict each user can only use one session (Restrict each user to a single session), remove the previous hook → OK. You can log in as many users here. If the setting does not take effect, restart it (try it, take effect d).

3, to prevent spoofing, prevent remote users from terminating the console administrator. Start → run → gpedit.msc → computer configuration → management template → Windows component (Windows Components) → terminal services (Terminal Services) → terminal server (Terminal Server) → connection (Connections) → Deny logoff of an administrator logged in to the console session, right-click → attribute → (Restart takes effect)

The use of remote desktops is no stranger to many users, especially to network administrators, who do this almost every day. Therefore, it is necessary to optimize the remote desktop. I hope that the above introduction will help everyone.