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

Advanced Printer Management Plugin and Fog Service Module

Scheduled Pinned Locked Moved
Feature Request
modules plugins printer managem printmanagement fog service
2
6
2.3k
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.
  • J
    JJ Fullmer Testers
    last edited by Jan 29, 2016, 5:23 PM

    So this isn’t so much as a request for someone else to do this as it is a request for more ideas.
    After adding the code for importing printer configurations to the service I had some ideas for improving the fog printer management in the service and the gui.
    However, I don’t think that everyone would quite care that much about these ideas enough to add them into the core, but making a module for the fog service and a plugin for the gui would probably do the trick. I intend to start working on this in a few weeks to a month from now after a couple other projects are done first. But I figured why not get some feedback on the idea while it is in the brainstorming phase.

    So here is some of the stuff I would be looking to add to an Advanced Printer Management plugin/client module

    • Adding printer ports with existing prnport.vbs windows command
      (Cscript %WINDIR%\System32\Printing_Admin_Scripts\en-US\Prnport.vbs)

      • Option to add SNMP private key for printers locked down with snmp keys
      • Option to enable SNMP on port with default public key
      • Option to use LPR or RAW port on standard local/TCP IP Printers
      • Option to add a usb printer shared on the network through a computer, NAS, or other network device.
    • Installing the inf file to the OS with PNPUTIL -i -a file.inf

    • Adding printers with Prnmngr.vbs if RUNDLL32 PRINTUI.DLL,PrintUIEntry /if fails for any reason
      (Cscript %WINDIR%\System32\Printing_Admin_Scripts\en-US\Prnmngr.vbs)

    • Allowing the use of network shares for inf driver files and config files

      • Either a checkbox in the add/edit printer menu or auto detect of unc path start \\ would bring up an option for domain\username and auto encrypting password (like the AD password box)
      • This user/pass would be used with a net use %share% /USER:username password command at the start of adding the printer and a subsequent net use %share% /delete at the end.
      • Also an option to ask (and perhaps detect) if a windows enterprise version is present with the nfs client installed, and if so saying to just put the printer files in a folder in the fog /images nfs share and mounting it in windows with nfs without the need for a password.
        • Maybe add the option to autoinstall a third party nfs tool to use the fog nfs share option on any version of windows
      • Maybe create a universal printer driver folder structure that can be downloaded to the fog nfs share or other network share
        • Maybe even add to that with the option to select from existing printer drivers in a drop down menu when adding a printer
        • This idea might require help, and would have the caveat of being difficult to update without some sort of automation of downloading new drivers for every model as they become available. Could just make it publicly accessible and let the community handle that as it happens or something.

    Thoughts?

    Have you tried the FogApi powershell module? It's pretty cool IMHO
    https://github.com/darksidemilk/FogApi
    https://fogapi.readthedocs.io/en/latest/
    https://www.powershellgallery.com/packages/FogApi
    https://forums.fogproject.org/topic/12026/powershell-api-module

    1 Reply Last reply Reply Quote 0
    • J
      JJ Fullmer Testers
      last edited by Jan 29, 2016, 10:46 PM

      • Ability to add local printers on nul: port with no ip address (.i.e. Send to OneNote, PDF Printers, etc)
      • Ability to add usb printers or at least set them as allowed so FOG doesn’t delete them if they aren’t in the printer list and FOG is set to remove all extra printers

      Have you tried the FogApi powershell module? It's pretty cool IMHO
      https://github.com/darksidemilk/FogApi
      https://fogapi.readthedocs.io/en/latest/
      https://www.powershellgallery.com/packages/FogApi
      https://forums.fogproject.org/topic/12026/powershell-api-module

      1 Reply Last reply Reply Quote 0
      • W
        Wayne Workman
        last edited by Jan 29, 2016, 10:54 PM

        I’d personally want to see this wait until fog-too.

        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/

        J 1 Reply Last reply Jan 29, 2016, 11:14 PM Reply Quote 1
        • J
          JJ Fullmer Testers @Wayne Workman
          last edited by Jan 29, 2016, 11:14 PM

          @Wayne-Workman But that involves waiting for functionality I could use now…

          Have you tried the FogApi powershell module? It's pretty cool IMHO
          https://github.com/darksidemilk/FogApi
          https://fogapi.readthedocs.io/en/latest/
          https://www.powershellgallery.com/packages/FogApi
          https://forums.fogproject.org/topic/12026/powershell-api-module

          W 1 Reply Last reply Jan 29, 2016, 11:16 PM Reply Quote 0
          • W
            Wayne Workman @JJ Fullmer
            last edited by Jan 29, 2016, 11:16 PM

            @Arrowhead-IT Code it yourself lol. Nobody is stopping you, go crazy. I only want to see it wait because I really want to see 1.3.0 released soon.

            I feel like fog trunk is REALLY close to release. There are just a handful of odds and ins that are in the way, but I feel those will be taken care of fairly soon.

            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/

            J 1 Reply Last reply Jan 29, 2016, 11:19 PM Reply Quote 0
            • J
              JJ Fullmer Testers @Wayne Workman
              last edited by Jan 29, 2016, 11:19 PM

              @Wayne-Workman Well yeah, I don’t want to hold up 1.3, hence the plugin/module idea.

              Have you tried the FogApi powershell module? It's pretty cool IMHO
              https://github.com/darksidemilk/FogApi
              https://fogapi.readthedocs.io/en/latest/
              https://www.powershellgallery.com/packages/FogApi
              https://forums.fogproject.org/topic/12026/powershell-api-module

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

              156

              Online

              12.1k

              Users

              17.3k

              Topics

              155.3k

              Posts
              Copyright © 2012-2024 FOG Project