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

FOG Client - Printer not displaying

Scheduled Pinned Locked Moved Solved
Bug Reports
2
8
2.7k
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
    last edited by Aug 19, 2016, 9:17 PM

    I’ve been having a fun issue with a particular printer. I’ve just realized what’s wrong, it’s there but isn’t displaying. The FOG Client is reporting on a false-positive somehow.

    I’m running Win10 LTSB x64. FOG 1.3.0 RC-8 with FOG Client 0.11.5

    So, this printer is assigned to my desktop computer, which is set with “FOG Managed Printers”.

    Below are pictures of the configuration in FOG, a pic of my installed printers in “Devices and Printers”, and… most importantly of all - the FOG PrinterManager Helper program showing the device as already installed…

    Now, I’ve not made any changes to printers for about 15 minutes - fog client is set to check with the server every 30 seconds. I have rebooted my computer, and then ran the FOG PrinterManager Helper to see what it says. It says the printer is installed, yet it’s not displaying in Devices and Printers.

    FOG Client Log:
    0_1471641440647_fog.log

    Printer Alias* SSD 1075
    Printer INF File* C:\Windows\inf\ntprint.inf
    Printer IP* 10.2.3.26
    Printer Port 10.2.3.26
    Printer Model HP LaserJet P4014/P4015 PCL6 Class Driver

    0_1471641304595_upload-c0f32025-800a-43b6-b328-4d96474588b3

    0_1471641403821_upload-421f424c-e790-451b-b373-af77dd291e26

    0_1471641415177_upload-65e21629-a07c-4f9c-8119-de4a781f1017

    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 1
    • W
      Wayne Workman
      last edited by Wayne Workman Sep 2, 2016, 10:40 PM Sep 2, 2016, 7:37 PM

      @Joe-Schmitt
      This powershell script deletes all local IP printers beginning with 10., and then deletes all printer ports that begin with 10.. After this ran, I witnessed the FOG client re-install all the printers afterwards. I’m going to deploy this as a snapin to clean up my printers.

      Get-WmiObject -ComputerName localhost -Class Win32_printer | where { $_.portname -like '10.**' -or $_.portname -like '10.***' -and $_.local -eq 'TRUE'} | Select -ExpandProperty Name | ForEach-Object { rundll32 printui.dll,PrintUIEntry /dl /n "$_" } 
      Remove-PrinterPort -Name "10.*"
      

      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
      • W
        Wayne Workman
        last edited by Aug 19, 2016, 10:20 PM

        Thinking more on this, I feel I should say -

        I did a lot of stuff to try to get this to work. I’ve tried the default printer drivers, HP Universal printer drivers, different printer names, different model numbers… All that shows in the log.

        I’m sorta thinking all my changes to attempt to fix it just broke it worse. But if that is the case, it just means the FOG Client needs to make sure the printer is configured according to what the FOG Server is saying.

        Just now, I noticed in the Printer Manager Helper that it’s showing the wrong model , that’s not what I had set in the FOG Server at that time.

        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 1
        • W
          Wayne Workman
          last edited by Aug 23, 2016, 6:33 PM

          @Joe-Schmitt How to replicate:

          Just manually delete a printer that the FOG Client added. I do this by going to Devices and Printers, right clicking, and choosing ‘remove’.

          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 1
          • J
            Joe Schmitt Senior Developer
            last edited by Aug 23, 2016, 7:02 PM

            @Wayne-Workman thanks for all the info. @JJ-Fullmer also has this issue and brought it to my attention earlier. I know what is causing the issue, but will be extremely tricky to safely patch. I’ll post in this thread with any progress I make.

            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.

            W 1 Reply Last reply Sep 29, 2016, 4:24 PM Reply Quote 1
            • W
              Wayne Workman
              last edited by Wayne Workman Sep 2, 2016, 10:40 PM Sep 2, 2016, 7:37 PM

              @Joe-Schmitt
              This powershell script deletes all local IP printers beginning with 10., and then deletes all printer ports that begin with 10.. After this ran, I witnessed the FOG client re-install all the printers afterwards. I’m going to deploy this as a snapin to clean up my printers.

              Get-WmiObject -ComputerName localhost -Class Win32_printer | where { $_.portname -like '10.**' -or $_.portname -like '10.***' -and $_.local -eq 'TRUE'} | Select -ExpandProperty Name | ForEach-Object { rundll32 printui.dll,PrintUIEntry /dl /n "$_" } 
              Remove-PrinterPort -Name "10.*"
              

              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
              • W
                Wayne Workman
                last edited by Wayne Workman Sep 2, 2016, 3:31 PM Sep 2, 2016, 8:25 PM

                That powershell script is confirmed working to fix the issue with orphaned Printer Ports and orphaned IP printers via a FOG Snapin.

                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
                • W
                  Wayne Workman @Joe Schmitt
                  last edited by Sep 29, 2016, 4:24 PM

                  @Joe-Schmitt Have you made any progress with the initial problem ?

                  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
                  • J
                    Joe Schmitt Senior Developer
                    last edited by Joe Schmitt Oct 1, 2016, 5:31 PM Oct 1, 2016, 11:31 PM

                    @Wayne-Workman I’ve been kept busy by my studies and patching the auto updating bug that affected many users (more work is still required to prevent it from happening in the future. The hotfix simply bought us 2 years to fix it).

                    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.

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

                    208

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project