Citrix Printing Series - Managing Printer Drivers

Drivers are required for all print devices. In large organisations managing print drivers can be a time consuming task. Citrix provides a few technologies to improve the printer management experience.

Automatic installation of printer drivers can be enabled to automatically install the native printer driver when a new printer is detected. Generally the automatic installation of printer drivers can cause inconsistencies in the environment so automatic installation should be disabled. RDS includes similar functionality and that should also be disabled.

It's generally a good idea to avoid Kernel-mode drivers (version 2) and use User-mode drivers instead. If a User-mode driver is not available, experiment with the Citrix Universal Driver to see if it will make a viable alternative.

Generally the client and printer driver names must match. In some cases, the driver names do not match but the driver does. Printer Driver Mapping can be used to correct name matching issues. Try using the Citrix Universal Printer Driver and if it does not work as intended, use printer driver mapping instead. Be sure to test the results.

Popular posts from this blog

Get local computer UUID/GUID using Windows Powershell

Use the following syntax to get the local computer's UUID/GUID using Windows Powershell: get-wmiobject Win32_ComputerSystemProduct  | Select-Object -ExpandProperty UUID Add -computername after the WMI class to find a remote computer's UUID, example: get-wmiobject Win32_ComputerSystemProduct -computername RANTPC | Select-Object -ExpandProperty UUID
Read more

gPLink and gPOptions

gPLink is a property for sites, domains and organisational units that contains a prioritised list of GPOs linked to the node. gPOptions is a property that contains all Block Policy Inheritance settings for the node. To manage GPO links on a node, you must have read and write access to the gPLink and gPOptions properties.
Read more

PSLoggedOn Getting Started on Windows Server 2008 R2

Image
PSLoggedOn is a tool I downloaded to allow me to find out which computers a user is currently logged on to. Getting it up and running wasn’t exactly easy. I’m running a Windows Server 2008 R2 test environment. The first error I encountered was: Error browing network: The list of servers for this workgroup is not currently available. Note: I kept the spelling mistake from the error message to make it easier to find via search engines. To get past this error, you have to enable and start the “Computer Browser” service. Then I started getting the error telling me that the Administrator is not logged on. That’s simply not true because I am logged onto another server (Name: ELARA): I turned the firewall OFF OFF OFF (It is a test network after all). I enabled Network Discovery and to do that I went on a service starting frenzy: DNS Client, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host, Computer Browser After all that, I ran the script against the se
Read more