when a particular client connected to our published application, xenapp auto restored a number of client printers with a name starting with “lynx” and “lynx”. the policy was set to auto-create the client’s default printer only so why was it auto restoring multiple printers? the lynx* printers do not even exist on the client’s pc and we do not have any users with names matching the printers. this has to be one of the strangest things i’ve seen so far in xenapp 6.5 with hotfix rollup pack 3 (xa650w2k8r2x64r03). i searched google and found this post on the citrix discussions which describes the exact same thing i was seeing. just too bad some of the posts are unresolved! after doing more digging, here’s what i found:
here is a list of the exact names (google returned 0 results for the names):
autocreated printers: client local or network printers that appear for the user within an ica session and use the ica protocol to send a print job. autocreated printers use the ica printer naming convention.
autorestored printers: a manually created client printer attached to a standard client printer port. this kind of printer can be created by an administrator or power user running the add printer wizard and manually creating a local printer that is attached to a standard client printer port. these printers are deleted when logging off and re-created when logging on.
autoretained printers: these are client printers that are added by the user within an ica session through the add printer wizard by browsing and connecting to printers enumerated through the client network print provider. when re-creating a retained printer, all citrix policies except the autocreation policy are respected. this means that retained client printers are created exactly as the autocreation policy would have selected them. such printers continue to be re-created with every logon from the same client until the client printer within the session is deleted manually or the remembered printer connection is removed from the client’s properties store. on a windows client, the properties store can be found in the user profile under
client printers: any printer available to a user before an ica session is launched.
- client local printer: printers that are physically connected to client devices through lpt, com, or tcp ports.
- client network printer: a network printer that appears in the printers and faxes folder of a client device and is managed by a print server. this differs from a print device attached to a standard tcp/ip port.
citrix print manager service (cpsvc.exe): provides printer management for all ica sessions including printer policy enforcement, driver installation, client printer port management, auto-creation of network and client printers, and printer/port cleanup when logging off.
because i read this citrix post, i knew someone out there in this world was also seeing these auto restored lynx printers with the same names. i thought maybe a bug in xenapp 6.5? a bug in the citrix print manager service (cpsvc.exe)? a bug in the citrix receiver on the client? since it was only happening to one client out of many it’s hard to tell where the fault lies, although i am suspecting it is the citrix print manager service. one of the problems troubleshooting citrix issues is that most of the time, as a sysadmin, we only touch the server. there really isn’t a way to do any client-side configuration outside of xenapp configurable properties such as deleting/adding local printers on the client’s pc without utilizing remote session software such as citrix gotomeeting. and we can’t just tell the user to re-image their pc.
after re-creating the users profile on the server, and using gotomeeting to delete and re-create the client’s local printers the problem was still there!
my next step was to look at the users profile on the server. i loaded the users registry hive from the old user profile i had renamed earlier in order to create a fresh profile for the user during my initial troubleshooting. let’s have a looksie:
what the heck is going on?
find the users sid with powershell and look at live hive:
$name = “pdiscordia” (new-object system.security.principal.ntaccount($name)).translate([system.security.principal.securityidentifier]).value
i’m convinced that the issue is a bug in the citrix print manager service, but until i get my hands back on the client pc i won’t be able to do further digging. because the lynx printers seem to be somehow associated with the microsoft xps document writer driver, i have decided to prohibit retained and restored client printers.
in addition, put the microsoft xps document writer in the shithouse by utilizing the xenapp policy called printer driver mapping and compatibility, and manually delete all of the lynx* printers.
if you have additional information regarding the lynx printer phenomenon, please post a comment below! your feedback is greatly appreciated.
when you're a little too careless about virtualizing your domain controllers, cloning, migrating, backing up and restoring, returning from vacation… Read More
systemd is new service manager for linux. it's a replacement for all previous init systems (sysv/sysvinit & ubuntu's upstart) and… Read More