Appendix
138
6
❖ MetaFrame's [Auto-creating client
printers]
Using [Auto-creating client printers]
can select a logical printer created
by copying the client's local printer
data to the MetaFrame server. We
strongly recommend testing this
function in your network environ-
ment before using it for your work.
• The settings for optional equip-
ment will not be stored in the
server after the equipment is
disconnected. The settings for
optional equipment will be re-
stored to its defaults each time
the client computer logs on to
the server.
• When printing a large number
of bitmap images or using the
server in a WAN environment
over dial-up lines such as ISDN,
printing may not be possible or
errors may occur, depending on
data transfer rates.
• When using MetaFrame XP 1.0
or higher versions, we recom-
mend making settings in [Client
Printer bandwidth] under [Citrix
Management Console] according
to the environment.
• If a print error occurs on the
server and the print job or a
printer created in [Auto-creating
client printers] cannot be deleted,
we recommend the following:
• MetaFrame 1.8 SP3, Meta-
Frame XP 1.0 SP1/FR1
Make settings in [Delete unfin-
ished print jobs] in the registry.
For details, see the Readme
file provided with Meta-
Frame.
• MetaFrame XP 1.0 FR2
Make settings in [Delete pend-
ing print jobs at logout] under
[Printer Properties Management]
of Citrix Management Con-
sole.
❖ MetaFrame's [Printer driver replica-
tion]
Using [Printer driver replication] can
distribute printer drivers across all
servers in a server farm. We
strongly recommend testing this
function in your network environ-
ment before using it for your work.
• If the printer drivers are not
properly copied, install them di-
rectly onto each server.
