|
 |
 |
 |
Printing in a Terminal Server environment has always been, and
continues to be a challenge. That being said, we've come leaps
and bounds from where we were in NT4 TSE, and it is now possible to
print to virtually any client printer. Depending on your setup
and needs this may require some registry editing, scripting, or a 3rd party
printing solution.
|
 |
|
| |
Terminal Server
& Citrix Printing Whitepapers & Downloads
Printing Scripting:
Terminal Server Printing Best Practices and FAQ
Question:
Is it possible to print to my local printer from my
Terminal Services session?
Answer:
Yes.
Brian Madden's Printing chapter
from his book "Terminal
Services for Windows Server 2003 Advanced Technical Design Guide"
gives very detailed information on the printing process, and is a
MUST READ for anyone who is responsible for supporting Windows
Terminal Servers. This chapter is
FREE to download.
Question:
What programs are available that would allow
users to print to any local printer, regardless of the model?
Answer:
1.
Provision Networks Print-IT
2.
ThinPrint
.Print Server Engine
3.
UniPrint Terminal
Server Edition
4.
triCerat Simplify Printing
Question:
What are the
Best Practices for
Installing and Using Printer Drivers
With Windows 2000 Terminal Services
Answer:
Microsoft recommends that you use the
printer drivers that are included with
Windows 2000. These printer drivers have
been extensively tested in the Terminal
Services environment. If the drivers
that are included with Windows 2000 do
not provide the functionality that you
need and you must install a third-party
printer driver, contact the vendor to
determine if their version of the
printer driver support the Terminal
Services environment before you install
the driver. Do not install a printer
driver that is not designed for the
Terminal Services environment in a
Windows 2000 Terminal Services
environment.
If a Windows 2000 version of the driver
for your printer is not included with
Windows 2000, you can
create a
"user defined inf
file"
to map the unsupported printer to a
built-in driver. For
additional information about how to
configure the computer to use different
printer drivers, click the following
article number to view the article in
the Microsoft Knowledge Base: 239088
Windows 2000 Terminal Services Server
Logs Events 1111, 1105, and 1106
Question:
I'm logged onto Terminal Services with
Remote Desktop Client 5.x, but I don't
see my local printer listed in the
"Printers & Faxes" Control Panel. How do
I fix this?
Answer:
1. Make sure in the settings of your
Remote Desktop Client -> Local Devices
-> Local Resources -> "Printers" is
checked.
2. If your Remote Desktop Client is
setup correctly, make sure "Windows
Printer Mapping" is NOT disabled in the
Terminal Services Configuration of the
server you're connecting to.
3. Check the Terminal Server's System
Event Log for Event ID 1111. If you see
one of these errors for each time you
logon, then the Terminal Server does NOT
have the appropriate driver for your
local printer, so the Windows Printer is
NOT auto-created.
Question:
The Terminal Server logs
Event ID 1111
every time I logon and my local printer
is not auto-created. How do I load the
appropriate driver to support my
printer?
Answer:
It is recommended that instead of adding
printer drivers to your Terminal Server
to support new printers, that you
map
your unsupported printer to a built-in
printer driver with similar
capabilities.
Here is
a sample of the registry entry and inf
file you'll need. These are derived
from the Print Driver mapping lists on
PrintingSupport.com The
syntax of the inf file is:
"Unsupported printer listed in Event ID
1111" = "Built-in supported print
driver"
Stefan from printingsupport.com has also
created a
Installation
Program so people
not-so-comfortable with registry editing
and customizing inf files can map RDP
Printers. It creates the required
registry entries and a sample inf file,
which can be accessed via the Start
Menu.
Question:
On Windows 2000 Server Terminal
Services, why are Printers That Use
Ports That Do Not Begin With COM, LPT,
or USB Not Redirected in a Remote
Desktop or Terminal Services Session
Answer:
To resolve this problem on a computer
that is not running Windows Server 2003,
force all ports (including DOT4) on the
client computer to be filtered for
redirection. To do this, add a DWORD
value named FilterQueueType to
HKEY_CURRENT_USER\Software\Microsoft\Terminal
Server Client\Default\AddIns\RDPDR and
set its value data to FFFFFFFF.
Reference
Microsoft Knowledge Base Article - 302361
Question:
W hat
causes high CPU usage in the
Winlogon.exe and Spoolsv.exe Processes
on a Windows 2000 Terminal Server
Answer:
This problem occurs when the print
spooler stops responding on the Terminal
server. A spooler failure can be
identified by information in the
application event log or in the
Drwtsn32.log on the Terminal server. The
log indicates that the Spoolsv.exe
process has terminated unexpectedly.
This is explained in
Microsoft Knowledge Base Article -
822834
Question:
How can I remove 3rd party print drivers
from my terminal server, if I think
they're causing problems?
Answer:
Follow the directions in this
article from Citrix or this
Knowledge Base
Article from Microsoft
Question:
Why do you receive an error message when
you try to print to a shared network
printer in a terminal server session
Answer:
If you receive on of these error
messages, either lock down the print
drivers used, or install the hotfix
listed in
this KB Article
-
No printers are installed. To
install a printer, point to settings
on the Windows Start Menu, click
Printer, and then double-click Add
Printer. Follow the instructions in
the wizard.
Current printer is unavailable.
Select another printer. Before you
can print, you need to select a
printer.
If you need to install a printer,
either double-click the Add Printer
icon or click the Find Printer
button located on the general tab of
this dialog.
Question:
How can I print to my
network printers from a terminal
services session?
Answer: Install the most recent
version of the
Remote Desktop
Client. (If this isn't
possible, see:
Windows 2000
Terminal Services Does Not Redirect
Network Printers (Q264039)
and
302361 -
Multifunction Printers That Use DOT4
Ports Are Not Redirected By Using Remote
Desktop.)
Question:
Why does printing to
Terminal Services-redirected printers
seem slow over WAN connections?
Answer:
Print jobs created in a
session are rendered entirely on the
terminal server, using the
server-installed printer driver, and raw
print data is sent over the Remote
Desktop connection to the client.
Depending on what you are trying to
print, the volume of raw data generated
might be very large. How fast the data
gets to the client is limited by the
speed of the network between client and
server. Over dial-up/WAN links, due to
the limited amount of bandwidth
available, printing might appear slow.
Question:
How do I know which
printer drivers work with Terminal
Services?
Answer: All of the
Microsoft-supplied printer drivers are
tested with Terminal Services and
guaranteed to work. Before using a
third-party printer driver, make sure it
has been certified for Terminal
Services. There is a Windows Hardware
Quality Labs (WHQL) program for getting
third-party printer drivers certified on
Terminal Services. Please ask your
printer driver vendor to secure such
certification. The list I refer to is
here.
Question:
Why is my client
machine's printer not available in my
session?
Answer:
Automatic printer
installation works very well when there
is an exact match on the server for the
client-side printer driver name. There
are, however, several scenarios in which
there may not be an exact match on the
server for the client-side driver
name-for example, when the client is
Windows NT or Windows 9x or the client
is using an OEM-supplied driver. In
these scenarios,
a custom INF file
can be written to create the mapping
between client- and server-side driver
names.
Question: How do I keep my
printer settings (such as A4 paper) from
being lost every time I log off?
Answer:
After making the printer
setting change, be sure to wait at least
60 seconds before logging off or
disconnecting. See
Terminal Services
Printer Redirection Not Signaled on
Change to Server-Side Device Settings
Tab (243942). Also, be sure
to wait for 60 seconds after the
redirected printer is created (after
logon) before making your setting
changes.
Question: After I installed
Windows 2000 SP3, I have trouble with
printing. How do I fix this?
Answer:
Windows 2000 SP3
initially broke some printing
functionality, and
hot fix Q328020
was released. We later discovered that
the hot fix caused a separate printing
problem. After that problem was fixed,
we re-released the hot fix. If you don't
have the hot fix, download and apply it.
If you do have it, but from shortly
after SP3, uninstall it, download the
updated version, and apply the
new version of the
hotfix. See the hot fix
details for more information.
Question: Why are Users'
Automatically Created Printers Visible
to Other Users?
Answer:
Microsoft
Knowledge Base Article - 253922
Question:
How do I configure
a local Citrix ICA Printer
connected to a Linux or Unix
Workstation?
Answer:
CTX103329 - ICA
Client for UNIX Printing Explained
|
|
|
|
 
|
