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

    Protecting printers

    Scheduled Pinned Locked Moved
    Feature Request
    2
    3
    882
    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.
    • Wayne WorkmanW
      Wayne Workman
      last edited by

      This idea is a little late to the races but,

      Can printers be protected like images are?

      Take our situation in mind. almost 100 network printers all deployed to exactly the computers that need them - total computers is almost 2K. If all printers would be deleted, it’d more than a day to recreate them all and re-assign them all - all due to a dumb mistake.

      I just want them protected from deletion. Settings changes I don’t care about so much.

      If not, it’s fine. I figured maybe it would be easy since the code already exists for images.

      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
      • Tom ElliottT
        Tom Elliott
        last edited by

        The only hesitation I have is the difference in reasoning.

        With all items needing to be deleted, it can’t simply be a “dumb mistake” removing them, at least from the GUI level. If you individually delete an item, it prompts for user/pass to confirm the deletion. Same goes for en-mass deletions. So it’s not as “simple” to make the mistake of deleting these things.

        That all said, the reasoning images and snapins are “protected” is because they deal with physical files that might be detrimental, where (while not fun) the definitions are the only primary concern in regards to Hosts, Groups, Users, and Printers.

        Hopefully this makes sense. And as we’re already rolling in the RC’s, I’d rather maintain the “feature” freeze so as to focus on minor and semi major bugs as they come up.

        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

        Wayne WorkmanW 1 Reply Last reply Reply Quote 0
        • Wayne WorkmanW
          Wayne Workman @Tom Elliott
          last edited by

          @Tom-Elliott Ok then.

          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
          • 1 / 1
          • First post
            Last post

          148

          Online

          12.1k

          Users

          17.3k

          Topics

          155.4k

          Posts
          Copyright © 2012-2024 FOG Project