How to use Terminal Services resources to redirect Windows [Figure]

Remote maintenance of the server is possible through Terminal Services. As shown in the figure below, there is a database server engaged in data management in the enterprise computer room. Usually, administrators generally perform remote maintenance of the database server through terminal services. The current requirement is that the administrator needs to print a file on the database server. What should I do? Normally, for security reasons, there are usually no additional services installed on the server, such as installing a printer. So the administrator can't print the file directly on the server. How to deal with this situation? Through the resource redirection function of Windows Terminal Services, you can expand the functionality of Windows Terminal Services.

If you have a Terminal Services session and then connect to a new Plug and Play device on the client, do you need to close the current session and reconnect to achieve the device's weight? Orientation? The answer is no. Administrators can change the default settings for Plug and Play device redirection when needed, allowing the system to recognize Plug and Play devices that redirect connections after a session has been established. It is easy to make this adjustment. Until you need to establish a session, in the configuration of the local client, select the Devices That I Plug In Later checkbox. In this case, even after the session is established, the new plug-and-play device is used on the client, and the remote server can recognize and use it directly.

In short, the local resource redirection feature allows clients to redirect many local resources in Terminal Services operations. To put it bluntly, resources on the local client can be used on the server. For example, a printer is installed on the local client and not on the server. When the administrator performs remote maintenance through the terminal service, the server can directly use the printer connected to the computer to complete the print job. This is the essence of the Windows Terminal Services Redirection feature. In particular, the serial port and printer port can be used in a terminal server session, allowing the user to send a terminal server print job to a locally configured printer and to allow access to the serial device from the terminal server session. In general, printers such as locally configured printers, sound cards, etc. can be used by remote servers.

First, printer redirection.

Administrators can redirect printers connected to local clients to remote servers as needed. This printer includes printers that are directly connected to local clients and network printers. It should be noted here that when the client opens a Terminal Services session configured to redirect Windows printers and LPT ports, the terminal server attempts to install each printer for use in the Terminal Services session.

In the printer redirection job, the more troublesome thing is the management of the printer driver. Requiring the remote server to use a local printer also requires a corresponding driver. In the 2003 version, although there is also a printer redirection function, it is cumbersome to use. This is mainly because the printer driver is reinstalled. In the 2008 version, improvements were made to this aspect. Added a TS EASY PRINT feature to help administrators reduce the difficulties and obstacles in managing Terminal Services printer redirection. In the actual work, you need to pay attention to the following two aspects.

One is the nature of TS, which essentially uses a generic printer driver. Traditional and new printer drivers are supported because of the common printer driver. This does not require an administrator to install these drivers on the terminal server. While reducing the workload, it will not bring hidden dangers to the security of the server.

Second, with this feature, administrators can view local printer driver settings, such as printer preferences, directly on the remote server. In this case, the administrator can use this driver as a proxy server to redirect all calls to the GUI to the actual driver on the client. The result is that the client actually launches the GUI of the client printer on the remote session. The simple understanding is that you don't need to install any printer drivers on the remote server. It can directly call the GUI of the client's local printer to print the job.

Previous 12 Next Total 2 Pages