Skip to content


  1. JBensimon
    September 23, 2015 6:29 pm @ 18:29

    It’s incredible that after all these years, the issue still exists and the only (not sure if temporary) solution is to delete the users’ HKCUSoftwareCitrixPrinterProperties (or relevant subkeys thereof) on the client machines. The problem with the policy to disable the creation of “auto retained and auto restored printers” is that the first kind (“auto retained”) is *useful* and only the second kind (“auto restored”) is the problem, and as far as I know nobody purposefully creates this second kind. It would be great if there were *separate* policies for disabling each of these two kinds of printers. [“auto retained” are the additional ICA client printers that a user “requests” using “ICA Client Printer Configuration”, a great tool to provide users in combination with the policy to only auto-create the client default printer].
    I wish I knew what piece of Citrix code (ICA client? print manager service? …?) does (or did at some point) contain all these references to foreign usernames and printers and clients and gateways, etc. — somebody got hacked somewhere along the line and is being quiet about it!


  2. geoced
    March 22, 2017 2:14 pm @ 14:14

    Hello Travis,

    I have the exact same issue as you, down to the name of the bogus printers !

    This is an old topic, but did you manage to fix the issue or hear from Citrix ?

    This is driving me mad !


    • Travis Runyard
      March 22, 2017 4:06 pm @ 16:06

      Unfortunately, no. If you have a support contract with Citrix could you try opening a case with them and let me know? I would appreciate it even though this is an old/mystery issue. If you don’t figure it out I wouldn’t sweat it as it seems to be some sort of software conflict between the clients computer and the XenApp server.


      • geoced
        March 23, 2017 8:54 am @ 08:54

        Thanks for your quick reply !
        I’m gonna try what you suggested in your article and see if it helps. We have so many (fake) printers (I counted more than 400 the other day) that sometimes users cannot access their (real) client-side printers anymore !
        I’ll let you know in case we decide to open an official case with Citrix.


        • Travis Runyard
          July 10, 2018 9:50 am @ 09:50

          Hey did you end up opening that case with Citrix?


          • geoced
            July 10, 2018 10:06 am @ 10:06

            Nope, we pretty much gave up on that and are in the process of upgrading to Windows 2016 and XenApp 7.9.

  3. Stretchie
    April 4, 2017 7:30 am @ 07:30

    I’ve only just started seeing this on my client’s XenApp farm. They have XA6.0 with the R02 Hotfix pack and only just started seeing this issue in the last couple of days. I’m only seeing only of the LYNX printers: LYNXCKempbell
    But a mass of Microsoft XPS Document Writers using the Citrix Universal Printer driver.
    Each time I delete the auto created printers they come back. Checked Citrix User policy and we do have autocreate and restore configured for all client printer objects. I’ve changed this to only the default and going to see if this changes anything. I’ve also set the HKLMSOFTWARECitrixPrint DefaultPrnFlags to (hexidecimal) 90004000 as per other posts on this issue.
    You’re still the only google result for LYNXCKempbell + Citrix which I find bizarre!


    • Travis Runyard
      July 10, 2018 9:52 am @ 09:52

      Sweet, I just tried out searching “LYNXCKempbell + Citrix” and you’re right, I am still the only hit. Long live!!!


Leave a Reply

Your email address will not be published. Required fields are marked *