
Chapter 1
Printer Management
Let’s not mince words: printing is a royal pain in a terminal server environment if you’re trying
to support client-side printers. To briefly recap, printing in a terminal server environment works
like this: the print job is generated on the terminal server, which creates a spool file that gets
redirected to the client-side printer. For this redirection to work, the printer drivers must exist on
both the client to which the printer is attached and the terminal server. Citrix hasn’t resolved all
the problems associated with printing, but with MetaFrame XP, the company has tackled two of
the problems: printer driver management and bandwidth throttling. We’ll discuss printing in
Chapter 7, but here’s a quick look at the tools that you can use to manage it.
To help you keep a handle on printer drivers, MetaFrame XP supports driver replication across
the servers in a farm, allowing you to install all the drivers you’re going to need on one terminal
server, then replicating them so that they’re available no matter which server someone happens
to be connected to. You’ll do this from the Drivers section of Printer Management in the console,
which Figure 1.10 shows.
Figure 1.10: You can replicate drivers from one server to all servers in the farm.
Bandwidth management is helpful because a print job can bring terminal sessions to a standstill
if traffic is heavy enough. Terminal sessions don’t use up much bandwidth, but print jobs do, and
on slow links, a print job that takes forever also keeps people from using their terminal sessions
while the print job is making its tortuous way to the client’s printer. By default, MetaFrame XP
doesn’t limit the amount of bandwidth that a print job may consume, but if you go to the Printer
Management part of the console, select the Bandwidth tab, and double-click each server for
which you want to limit bandwidth, you can set a bandwidth limit in the dialog box that Figure
1.11 shows.
19
Commenti su questo manuale