Managing pools of drivers between TS servers in a farm
In a farm of Terminal Servers, you might have a large pool of clients with heterogeneous OS versions and a wide variety of client-side printers. If your client base is Windows 2000, your job is simple, because any in-box printer driver on the client side already exists on the server, in DRIVER.CAB. This file redirects any incoming client that uses a Microsoft-supplied driver when needed.
When you have mixed OSs and printer hardware, as in the HP DeskJet 722c scenario, you must investigate driver issues more thoroughly. In a farm with multiple nodes, this problem can affect many different server machines.
To manage the OEM printer drivers on the servers in your Terminal Server deployments, you can use Print Migrator. This tool allows you to create a .CAB file containing an image of all installed printer drivers on one server. The .CAB file can then be loaded on all Terminal Servers in the enterprise or the farm. Using Print Migrator ensures that consistent versions of OEM drivers are installed.
The latest Print Migrator version, 3.0, is available at the following link:
http://www.microsoft.com/windows2000/technologies/fileandprint/print/download.asp
For more information, consult the accompanying README available on this download page.
|
