Baza znanja: Kyocera javno
Windows 2003 Terminal Server Driver Installation
Posted by Marko Lipovec (Import) on 24 June 2010 08:50 AM

Windows 2003 Terminal Server Driver Installation

Printer Driver Installation Windows 2003 Terminal Server

Which Printer Driver should be used: KX or Classic?

In a Windows Terminal Server environment, every task or program will run on the Windows 2003 Terminal Server, so it depends on CPU, RAM and Hard Disk Space of the Windows 2003 Terminal Server.

Because of this, we propose to use the Kyocera WHQ Classic Driver for PCL or KPDL (Postscript). The WHQ KX Driver can also be used, but this Printer Driver requires more CPU usage and RAM.

This short manual describes the Driver Installation, using a Kyocera WHQ PCL Mini Driver.

Which rights are necessary to install the Printer Driver?

Normally, a System Administrator will install the driver with Administrator Rights. If a user wants to install the Driver on the Windows 20003 Terminal Server, minimum right required are Printer Administrator / Operator.

If you only have user rights, you don't have access to the Registry Settings, so you can't write the correct Registry Keys. Installation will fail!

Install Printer Driver on Windows 2003 Terminal Server

To install the Kyocera WHQ Mini Driver, use the Windows 2003 Terminal Server Standard Process, the Add Printer Wizard. When you are asked for the connection, you can selected LPT1 for the installation and Print No Windows Test page.




Install Printer Driver on Windows 2003 Terminal Server


The Kyocera WHQ Mini PCL Driver is now installed ( in our example for FS-2000D ).



Checking Printer Driver Suite of Windows 2003 Terminal Server

Checking the Printer Driver Suite of the Windows 2003 Terminal Server is necessary for a successful pushed Session Printer from Client Side. So make sure, that the driver is a known in the Printer Driver Suite of the Windows 2003 Terminal Server.

Open the Printers and Faxes Dialog. Click on File and select Server Properties. Select the tab Drivers. The actually installed printer drivers are displayed.

   Important

   Only the drivers shown here can be used for a Client Session Printer. The printer driver must be known by the Printer Driver Suite of the Terminal Server.

If the printer driver is unknown, no Session Printer is available.

Delete Driver Icon from Server

If the printer driver is not used and set up as Shared Network Printer, you can deleted the printer icon in the Printers and Faxes dialog, if necessary.

Printer Driver Installation Windows XP / VISTA Client

Install Driver

To install the Kyocera WHQ Mini Driver on the Windows XP or Vista Client, use the Add Printer wizard. When you are ask for the connection, select the correct port, the printer is connected to ( Parallel / USB / TCP/IP ) for installation and print a Windows Test page.

The Kyocera WHQ Mini PCL Driver is now installed ( in our example: FS-2000D ).



Using Remote Desktop and Printer


To use the local printer in a Remote Desktop Session, you have to set up the Windows Remote Desktop Tool to share the printer driver of the client as Session Printer with the Windows 2003 Terminal Server.

Open the Remote Desktop Tool and click Options>>



Using Remote Desktop and Printer


Check Printers from the Local Resources tab, to share a Windows Clients Printer with a Terminal Server.



If you open a session to the Windows 2003 Terminal Server now, your printer will be shown in the Printers and Faxes dialog as your Session Printer.



Driver Settings in Terminal Session


Depending on your user rights on your local Windows Client, it is possible to use different features or settings of the printer driver like Duplex, Second Paper Tray or, depending on the devices features, booklet or punch.

   Important

   The settings will be lost, when you close your Terminal Session. The reason for that is, that the settings are stored with a Terminal Session Number. If you reconnect your
   session, you will get a different Terminal Session ID, so your further printer driver settings are lost and will be set to default.



The Way of the Print Data Stream

Short description, how Spool Files will be placed and handled by this type of Printer Driver Installation:

The client sends the print data to the Windows 2003 Terminal Server, where they are spooled for the first time.
After spooling the print data, the job will be returned to the spool system of the client with the physical Print Device.
The Spool System at client side will not spool the print job again, it will be used like a Print Output Queue.


Session Printer is not available

There are three reasons, if a Session Printer failed:

  1. Unknown Printer Driver in Printer Driver Suite Windows 2003 Terminal Server
  2. Installed Printer Model is different between Client and Terminal Server, ie. Client FS-4000D Kyocera WHQ Classic Driver, Windows Terminal Server FS-2000D Kyocera WHQ Classic Driver, same driver platform, but different models.
  3. Same Models FS-2000D, but different printer driver platforms on Client PC and Terminal Server, ie. Classic Printer Driver FS-2000D on Windows 2003 Terminal Server, Client PC FS-2000D WHQ Kyocera KX Driver.
(79 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below. This is required to prevent automated registrations and form submissions.

Help Desk Software by Kayako servis.xenon-forte.si/index.php?