Remote Desktop Protocol (RDP) Client Setup
This paper describes how to configure your Remote Desktop Client so local printers become available resources in a Terminal Server Session. The topic talks specifically to printing from the
Paterson's EagleSoft Practice Management Software via a Terminal Server session, however any Microsoft Windows application will work as detailed here.
Once your Client is configured, read the following Topics on Terminal Server Session Printing:
EagleSoft requires a minimum desktop screen resolution of 1024X768 with a 24 Bit Color Palette. Anything less and the EagleSoft desktop will not open. So your Remote Desktop Client needs to be properly configured before connecting to the terminal server.
The following screen shots and dialog will show RDP Client setup screens, and how to configure your client to display the EagleSoft desktop and too direct print jobs back to your local printer.
Important Note: Unfortunately, EagleSoft does not always select the right remote printer; so every time you log-on to the Terminal Server, you must access the EagleSoft printer setup and ensure the correct printer was selected. Why every time? Because when you log out of a Terminal Server session, remote printers are removed from Terminal Server's printer list. This is by design.
(Note also that your local printer must be supported by EagleSoft and the Windows Server 2003 operating system. This will exclude some printers from being used. I describe a work-around for unsupported printers at the end of this document.)
Begin the client setup:
Start the Remote Desktop Client by clicking START, ACCESSORIES, COMMUNICATIONS, Remote Desktop Connection.
Here is the initial interface:
Initially, the RDP Client does not display all available settings. To expose all configurable settings, click the Options>> button to expand the interface.
Here is the expanded Interface showing TABS you select to expose configurable options:
The Save and Save As buttons for saving your settings. Saving your Client setup to the Windows Desktop will create a Short-Cut Icon pointing to the Remote Desktop Client with the saved configuration. Something you don't want to do if your using a public computer.
Click the Display TAB to configure the Desktop Video Settings and set the Remote Desktop size an Colors as shown below.
EagleSoft requires 1024 by 768 pixels with 24 bit Colors.
Next Click the Local Resources TAB to configure your printer attachment.
Disk Drives and Serial ports should not be checked. Select how sounds should be handled.
Click the box next to Printers to make your local printer available to the terminal server.
Once connected to a terminal server your local printer should be available in the remote session.
Important Note Here: Just because a printer is made available, does NOT mean your remote applications will automatically use it; you still need to tell remote applications which printer to use.
By default, applications will still print to their default printer. So in EagleSoft (or any other application) you must go into the printer setup screen and select your local printer.
This setting is only temporary and will revert back to previous settings after you Log Off.
Sadly, EagleSoft does not have an easy to use, nor intuitive printer setup screen.
Finally, click on the Experience TAB to configure system performance options.
This is where you select the 'Bells and Whistles' you desire. I feel it is best to clear all but the Bitmap caching options. All the other options will only slow down your remote session; especially if your connecting over a slow link, such as DSL or Dial-Up Modem.
Additional Topics on Printing from a Terminal Server Session:
Unsupported remote printer work-around
The workaround is to install a generic HP Deskjet on LPT1: printer on your local PC? Yes, you can install drivers for printers that you do not have. That generic printer driver can used in place of your unsupported printer in a Terminal Server session.
To make this trick work, you install a new (non existant, but supported printer) on your local computer and tell Windows setup the printer is connected to your local LPT1: port. Tell Windows Setup NOT to search for the printer and select the HP Deskjet from the list of available printers. After the installation is completed, go back and change the non existant printers port from LPT1: to the port your real printer actually uses. Now Terminal Server will pickup the new (supported) printer and let you send print Jobs to it. Since all printers recognize basic HP printer commands, your local (un-supported) printer should accept the print job. Some special features my not work, but basic printing should come out OK.
Computer Networking and Repair Service
609-641-6392