Here is the KB for the registry key! I knew I remembered seeing it out there. How to Disable Autorestored and Autoretained Printers in a Presentation Server Environment http://support.citrix.com/article/CTX117805 Jim Kenzig Blog: http://www.techblink.com On Tue, Jan 6, 2009 at 4:23 PM, Jim Kenzig http://thin.ms <jkenzig@xxxxxxxxx > wrote: > Found this pretty good explanation of the Auto Retained functionality > *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 *HKEY_CURRENT_USER\Software\Citrix\PrinterProperties > > > http://www.gregmoseley.co.uk/index.php?option=com_content&task=view&id=115&Itemid=52 > > *Jim Kenzig > Blog: http://www.techblink.com > > > On Tue, Jan 6, 2009 at 4:19 PM, Jim Kenzig http://thin.ms < > jkenzig@xxxxxxxxx> wrote: > >> See Section 4.2.2 in this doc There is an HKCU key you can fiddle with >> >> http://support.citrix.com/servlet/KbServlet/download/8451-102-15600/PresentationServer4[1].0PrintingEnhancementsWhitepaper.pdf<http://support.citrix.com/servlet/KbServlet/download/8451-102-15600/PresentationServer4%5B1%5D.0PrintingEnhancementsWhitepaper.pdf> >> >> Jim Kenzig >> Blog: http://www.techblink.com >> >> >> >> On Tue, Jan 6, 2009 at 3:01 PM, Stratton, Doug ISMC:EX < >> Doug.M.Stratton@xxxxxxxxx> wrote: >> >>> Still stuck but have some more info. >>> >>> What I finally noticed was that it says "*Auto Retained Client >>> Printer...."* in the comment field for this printer. >>> >>> No jobs in the queue. >>> >>> The only way I have been able to get rid of it is to totally disable >>> client printer mapping in Citrix Policy. Then all the printers are gone. >>> >>> If I set the "Turn off client printer mapping" to "Not configured" and >>> set the Auto-creation policy to "Do not auto-create client printers" I get >>> the Office Document Image writer back but on others. >>> >>> Some how I ended up also getting one that says "Auto Restored" Think it >>> happened when I changed the comment then tried deleting. >>> >>> I have removed any user rights from the local Microsoft Office Document >>> Image Writer. (and deleted the local printer (not drivers)). Same problem. >>> >>> Regards, >>> *Doug Stratton*, Shared Service BC >>> Service Desk Email:* 77000@xxxxxxxxx* >>> Service Desk Tel:* (250)387-7000* >>> >>> ** >>> ------------------------------ >>> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On >>> Behalf Of *Stratton, Doug ISMC:EX >>> *Sent:* December 19, 2008 12:14 PM >>> *To:* thin@xxxxxxxxxxxxx >>> *Subject:* [THIN] Re: 2 printers showing up for clients >>> >>> Joe, unfortunatly the citrix policy did not correct the problem. >>> >>> Tried one of the other suggestions. >>> >>> I renamed the pc's Microsoft Office Document Image Writer to Microsoft >>> Office Document Image Writerii and it did not map. >>> >>> Renamed it back came back. >>> >>> I checked Driver mappings nothing in the console related to this printer. >>> >>> PS I am sure it is on the server but it is also showing up as a printer >>> mapped to the client. >>> >>> Regards, >>> *Doug Stratton*, Shared Service BC >>> Service Desk Email:* 77000@xxxxxxxxx* >>> Service Desk Tel:* (250)387-7000* >>> >>> >>> ------------------------------ >>> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On >>> Behalf Of *Joe Shonk >>> *Sent:* December 19, 2008 10:59 AM >>> *To:* thin@xxxxxxxxxxxxx >>> *Subject:* [THIN] Re: 2 printers showing up for clients >>> >>> Try setting your Citrix Policies. You should get the results you're >>> after. >>> >>> >>> >>> Joe >>> >>> >>> >>> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On >>> Behalf Of *Stratton, Doug ISMC:EX >>> *Sent:* Friday, December 19, 2008 11:35 AM >>> *To:* thin@xxxxxxxxxxxxx >>> *Subject:* [THIN] Re: 2 printers showing up for clients >>> >>> >>> >>> Nope no citrix policy. >>> >>> >>> >>> Possibly GP? Not sure where that would be set. >>> >>> >>> >>> I just don't get why 2 and not all local printers if that is what is >>> causing it. >>> >>> >>> >>> I for example have 5 or 6 local printers. Just the 2 get mapped. >>> >>> >>> >>> Regards, >>> *Doug Stratton*, Shared Service BC >>> Service Desk Email:* **77000@xxxxxxxxx* >>> Service Desk Tel:* **(250)387-7000* >>> >>> >>> >>> >>> ------------------------------ >>> >>> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On >>> Behalf Of *Joe Shonk >>> *Sent:* December 19, 2008 10:10 AM >>> *To:* thin@xxxxxxxxxxxxx >>> *Subject:* [THIN] Re: 2 printers showing up for clients >>> >>> Ok, you have the ICA listener setup for one printer… What about your >>> Citrix Policies in the PSMC? >>> >>> >>> >>> Joe >>> >>> >>> >>> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On >>> Behalf Of *Stratton, Doug ISMC:EX >>> *Sent:* Friday, December 19, 2008 10:31 AM >>> *To:* thin@xxxxxxxxxxxxx >>> *Subject:* [THIN] Re: 2 printers showing up for clients >>> >>> >>> >>> As i mentioned we are getting 2 printers per user in each session. >>> >>> >>> >>> One network printer which is the default on the pc they are logging in >>> from. >>> >>> >>> >>> Also a second printer which is not default and is the Microsoft ..... >>> printer. >>> >>> >>> >>> We have the ica listener set to only map the default printer which the >>> Microsoft printer is not. >>> >>> >>> >>> >>> >>> >>> >>> Regards, >>> *Doug Stratton*, Shared Service BC >>> Service Desk Email:* **77000@xxxxxxxxx* >>> Service Desk Tel:* **(250)387-7000* >>> >>> >>> >>> >>> ------------------------------ >>> >>> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On >>> Behalf Of *Jeremy Saunders >>> *Sent:* December 18, 2008 2:24 PM >>> *To:* thin@xxxxxxxxxxxxx >>> *Subject:* [THIN] Re: 2 printers showing up for clients >>> >>> But that's a client printer mapping because the Users have Office >>> installed locally on their client devices. >>> >>> >>> >>> Cheers, >>> >>> Jeremy. >>> >>> >>> >>> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On >>> Behalf Of *Stratton, Doug ISMC:EX >>> *Sent:* Friday, December 19, 2008 7:09 AM >>> *To:* thin@xxxxxxxxxxxxx >>> *Subject:* [THIN] Re: 2 printers showing up for clients >>> >>> >>> >>> It is but the ones I am want to get rid of are the ones that are showing >>> as users version of "local" printers on the server >>> >>> >>> >>> Looks like this: "Microsoft Office Document Image Writer (from >>> ws0000007) in session 4 Ready Auto Retained Client printer......" >>> >>> Regards, >>> *Doug Stratton*, Shared Service BC >>> Service Desk Email:* **77000@xxxxxxxxx* >>> Service Desk Tel:* **(250)387-7000* >>> >>> >>> >>> >>> ------------------------------ >>> >>> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On >>> Behalf Of *Robert K Coffman Jr. -Info From Data Corp. >>> *Sent:* December 18, 2008 11:09 AM >>> *To:* thin@xxxxxxxxxxxxx >>> *Subject:* [THIN] Re: 2 printers showing up for clients >>> >>> Check to see if the Office Document Image writer is installed as a local >>> printer on your Term Servers. >>> ------------------------------ >>> >>> *Confidentiality and Privilege Notice ** >>> *This document is intended solely for the named addressee. The >>> information contained in the pages is confidential and contains legally >>> privileged information. If you are not the addressee indicated in this >>> message (or responsible for delivery of the message to such person), you may >>> not copy or deliver this message to anyone, and you should destroy this >>> message and kindly notify the sender by reply email. Confidentiality and >>> legal privilege are not waived or lost by reason of mistaken delivery to >>> you. >>> ------------------------------ >>> >> >> >