3 Replies Latest reply on Feb 18, 2019 7:23 AM by szilagyic

    Disappearing printers

    szilagyic Enthusiast

      Hello:

      I am curious if others are having this issue.  I am not entirely sure but I suspect it's an issue with Writable Volumes, because deleting and re-creating the Writable for affected users is fixing the issue.

      Users connect in from clients running Windows 10 LTSB, running the Horizon Client 4.9 software.  Recently after we upgraded to AppVol 2.14.2, users are calling in regarding one or both of the locally installed printers on the clients are disappearing in the VM.  The printers in the VM are passed through by ThinPrint from the client.  I have not been able to pinpoint the issue but I think it might be AppVol doing something with the printers.

      Is there anything I can check or look at, to try and pinpoint this?  I've started to look through AppVol logs.  I have seen past activity with AppVol and printers and wondering if the 2.14 version does something different as we had not had this problem until now.

      Thanks in advance.

        • 1. Re: Disappearing printers
          Ray_handels Master
          vExpertCommunity Warriors

          To be honest I haven't seen that before. Did you also update the View environment? Because for connecting local printers View used the Thin Print option and in version ( i thought) 7.6 changed this to it's own tool for redirecting printers.

          What happens to manually installed printers within the VDI and writable? are these printers pertained throughout sessions??

          • 2. Re: Disappearing printers
            szilagyic Enthusiast

            To be honest I haven't seen that before. Did you also update the View environment? Because for connecting local printers View used the Thin Print option and in version ( i thought) 7.6 changed this to it's own tool for redirecting printers.

            What happens to manually installed printers within the VDI and writable? are these printers pertained throughout sessions??

             

            Yes, we have updated our environment to 7.6.0 as well.  I wasn't aware or didn't see that change in 7.6 on the printer redirection, so I will have to dig in to that some more.  We have also upgraded the Horizon Client to 4.9 and still seeing the issue.  Unfortunately it's not affecting everybody so it's difficult to pinpoint.

             

            We currently don't use any manually installed printers to the Writable Volumes or within the VDI session itself, we rely on the printers to be passed through in all cases as we use standard thin client desktops with our own hardware and custom image.

             

            I'm not sure if we'll be able to pinpoint this but I'll post a followup if we find anything useful.  Re-creating the writable volume (and Windows profile) has been fixing the issue but there might be one case where the issue started happening again, I'm verifying.

             

            Thanks for your help.

            • 3. Re: Disappearing printers
              szilagyic Enthusiast

              I have a case open with support and so far they have collected logs and are showing errors like this in the ThinPrint logs from the VM side:

               

              OpenPrinter succeeded for printer <Zebra Label Printer>
              01.02.2019 09:46:09:532 Id:7320 (3900) _INF_/NORM=01h: PrinterAccessEx%331 _SVC_ GetPrinterDataEx failed for <Zebra Label Printer>:<TPAC-Comment> with error (2).

              01.02.2019 09:46:19:735 Id:7320 (3900) _INF_/NORM=01h: TPAutoConnDll%1197 _SVC_ Final name for template <%N>: <Zebra Label Printer>
              01.02.2019 09:46:19:735 Id:7320 (3900) _INF_/NORM=01h: TPAutoConnDll%3754 _SVC_ Printer <Zebra Label Printer> was NOT created by TPAC, so it won't be touched: probably printer name duplication.

              name for template <%N>: <Zebra Label Printer>
              01.02.2019 09:47:57:346 Id:7320 (7488) _INF_/NORM=01h: TPAutoConnDll%3754 _SVC_ Printer <Zebra Label Printer> was NOT created by TPAC, so it won't be touched: probably printer name duplication.

               

              But so far they are not sure the cause exactly.  I'm doing my own research , too, haven't found anything useful yet.  Figured I'd post it here on the chance maybe somebody has seen these errors before.

               

              Thanks.