[THIN] Really weird printer issues
- From: "Edward VanDewars" <evandewars@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Fri, 31 Mar 2006 08:38:58 -0500
So I have Citrix policies defined to create and set as default a printer
based on either client name (on thin clients which users can't change) or IP
(via DHCP and subnetted so I know that a client in a given area will get an
IP in a given range). Users in lab A get printer A and only that printer
created and set as default when working in that lab and the same for lab B
(with printer B). In all I have 15 such policies and everything has always
worked fine until a few weeks ago.
Suddenly some users log in to a lab A computer, hit File - Print, see
printer A in the print dialog, hit ok, and their print job goes to printer B
(on jobs that are large enough, I actually see a status window that says
"printing to B" even though printer A was in the original print dialog
box). What's even stranger is that if I leave the app open and hit file -
new and create a new document and print that document it goes where it is
supposed to go. The printers A and B are different models and the print
dialog shows the appropriate options for printer A, even when the job then
goes to B.
I have verified this myself and was just blown away that file - print showed
printer A (and only printer A, nothing else was in the printer list) but the
job printed to printer B.
This doesn't happen for everyone and in fact it only happens for (some)
users in lab A and when it happens they only print to printer B (i.e. users
in lab B never end up printing to printer A and users in lab A never end up
printing to printer C, etc.). It happens in at least Word, Publisher, and
IE. In one case I verified that the user never even used a terminal in lab
B so I know that the printer was not stored in their profile.
This is in PS 4 with rollup 1 and Win 2k3 but no SP1. Clients are Wyse
1200LE thin clients. Not that is should matter, but the policy assigning
printer A to lab A has the highest priority of all the printer policies.
Again, this just started happening a few weeks ago but, of course, "nothing
changed" (except Windows updates) so I'm at a lost. I have not been able to
determine if it is always happening on a specific server or if it is
farm-wide. Any help would be greatly appreciated.
Other related posts: