• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

FOG client : printer from master appears on all client

Scheduled Pinned Locked Moved Solved
Bug Reports
3
15
5.0k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • W
    Wayne Workman @Matthieu Jacquart
    last edited by Wayne Workman Sep 1, 2016, 11:58 AM Sep 1, 2016, 5:57 PM

    @Matthieu-Jacquart For now, download the image to a computer, un-associate all fog printers and let the fog client delete them (do not do it manually). Then re-upload to a new image with a new name (so you don’t overwrite you’re old one).

    Then try to deploy this new image, see if you still have the issue.

    Also, re-pinging @Joe-Schmitt about what to do with all the other existing deployments.

    Also, this line from your log:

    24/08/2016 16:34 Middleware::Response Module is disabled on the host
    

    That would tell me that printer management is disabled on that computer. I would check that out. Set it to ā€œFOG Managed Printersā€ and see if it’s fixed.

    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
    Daily Clean Installation Results:
    https://fogtesting.fogproject.us/
    FOG Reporting:
    https://fog-external-reporting-results.fogproject.us/

    M 1 Reply Last reply Sep 2, 2016, 8:15 AM Reply Quote 0
    • M
      Matthieu Jacquart @Wayne Workman
      last edited by Sep 2, 2016, 8:15 AM

      @Wayne-Workman Some tests :

      • I enable printer manager service on these hosts and set it to Fog management printer, with no printer, but even after client reboot S101Laser1 always appears twice…
      • I deployed image on another host with no printer, but these 2 printers always appears, so if I upload image theses printers will stay in image…

      Maybe registry entry to modify/delete for these printers ?

      Fog 1.5.9.138
      Debian 11
      Vmware ESXi

      T 1 Reply Last reply Sep 2, 2016, 10:21 AM Reply Quote 0
      • T
        Tom Elliott @Matthieu Jacquart
        last edited by Sep 2, 2016, 10:21 AM

        @Matthieu-Jacquart is this really due to the fog client? If you disable the client and remove these printers and the host does the printers still appear?

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        M 1 Reply Last reply Sep 2, 2016, 11:58 AM Reply Quote 0
        • M
          Matthieu Jacquart @Tom Elliott
          last edited by Sep 2, 2016, 11:58 AM

          @Tom-Elliott Ok I found problem, printer s101laser1 was stored in registry HKCU/printers and HKU/printers, so it appeared twice…
          If i removed these registry key it’s all good, now the problem is : if an image is built on host with network printer associate, this printer stay in registry, and I have to delete it manually on each computer…

          Fog 1.5.9.138
          Debian 11
          Vmware ESXi

          W 1 Reply Last reply Sep 2, 2016, 12:41 PM Reply Quote 0
          • W
            Wayne Workman @Matthieu Jacquart
            last edited by Sep 2, 2016, 12:41 PM

            @Matthieu-Jacquart You could write a batch file that deletes that 2nd key, and deploy it with snapins.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
            Daily Clean Installation Results:
            https://fogtesting.fogproject.us/
            FOG Reporting:
            https://fog-external-reporting-results.fogproject.us/

            1 Reply Last reply Reply Quote 0
            • T
              Tom Elliott
              last edited by Sep 29, 2016, 10:24 AM

              bump, I’m still guessing this issue is still happening?

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

              M 1 Reply Last reply Sep 30, 2016, 1:07 PM Reply Quote 0
              • W
                Wayne Workman
                last edited by Sep 29, 2016, 4:23 PM

                In here, there’s a powershell script that you can use as a snapin that deletes all IP printers and IP ports. I’d only advise this if all your IP printers are managed by FOG already, as the FOG client would just re-add them back after this runs.
                https://forums.fogproject.org/topic/8406/fog-client-printer-not-displaying

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                Daily Clean Installation Results:
                https://fogtesting.fogproject.us/
                FOG Reporting:
                https://fog-external-reporting-results.fogproject.us/

                1 Reply Last reply Reply Quote 0
                • M
                  Matthieu Jacquart @Tom Elliott
                  last edited by Sep 30, 2016, 1:07 PM

                  @Tom-Elliott Yes problem persist, so I clean registry manually to delete those printers, and after it seems ok…
                  But it’s not convenient at all !

                  @Wayne-Workman Problem is I only use network shared printer (no ip printers)

                  Fog 1.5.9.138
                  Debian 11
                  Vmware ESXi

                  T 1 Reply Last reply Nov 8, 2016, 11:57 AM Reply Quote 0
                  • T
                    Tom Elliott @Matthieu Jacquart
                    last edited by Nov 8, 2016, 11:57 AM

                    @Matthieu-Jacquart Just guessing this still happens? (Trying to keep unsolved bugs to the first page so we don’t ā€œloseā€ them).

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                    M 1 Reply Last reply Nov 8, 2016, 1:23 PM Reply Quote 0
                    • M
                      Matthieu Jacquart @Tom Elliott
                      last edited by Nov 8, 2016, 1:23 PM

                      @Tom-Elliott I think you can close, I had to clean registry on these computers but when my image is clean deployment is ok.

                      Fog 1.5.9.138
                      Debian 11
                      Vmware ESXi

                      1 Reply Last reply Reply Quote 0
                      • 1 / 1
                      • First post
                        Last post

                      174

                      Online

                      12.1k

                      Users

                      17.3k

                      Topics

                      155.4k

                      Posts
                      Copyright Ā© 2012-2024 FOG Project