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

enable Debug mode

Scheduled Pinned Locked Moved
FOG Problems
4
6
4.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.
  • C
    cotec
    last edited by Jan 6, 2016, 10:20 AM

    Hi,

    i plan to image ca 40 pc’s in near future with multicast.

    i tried to test multicast with the wiki article (https://wiki.fogproject.org/wiki/index.php?title=Multicast)

    problem is point 4 of client
    Now boot up 1 client go to your FOG Menu and select debug mode.

    • If debug is not located on your FOG Menu then you will need to add it. See FOG Menu (v1.3.0)
    • You can also accomplish this by creating a Debug task in the Fog Web GUI and then network boot the client
    • Do this on the same subnet if possible.

    Problem is: Where do i setup or configure the debug-mode? I haven’t a menupoint that called debug and there is also no task that i can perform.

    regards,
    cotec

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Jan 6, 2016, 11:27 AM

      If I understand your question, this one got me confused for a bit too.

      (warning typing with one eye open) For debug mode go to the host and then for the host select tasks then advanced (its below the deploy and capture options). When you select advanced you will see a series of additional tasks you can assign to the target computer. Debug is one of 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!

      1 Reply Last reply Reply Quote 1
      • T
        Tom Elliott
        last edited by Jan 6, 2016, 12:15 PM

        You can also re-enable the access, on the menu, for debug mode by using the “Hide Menu” option.

        The reasoning behind the move is security. While we could certainly add a login element to the debug item, it’s simpler to just make it unusable as a default. To regain menu access to the debug item, you put the menu into “Hidden” mode.

        When you enter the key sequence you’ve selected, it will ask you to login. Once logged in, you should see the debug menu item.

        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

        C 1 Reply Last reply Jan 6, 2016, 12:59 PM Reply Quote 0
        • C
          cotec @Tom Elliott
          last edited by Jan 6, 2016, 12:59 PM

          @both: Thank you very much, have found both Options 👍

          A Question about the “hide menu”: there is a username and password needed.
          If a customers-workstation is broken and i need a fresh image, the customer needs this user/password, or iam wrong?
          The user which i can setup in FOG-WebGUI are admins or user? has this user access to webgui?

          C 1 Reply Last reply Jan 6, 2016, 1:03 PM Reply Quote 0
          • C
            cotec @cotec
            last edited by Jan 6, 2016, 1:03 PM

            @cotec said:

            The user which i can setup in FOG-WebGUI are admins or user? has this user access to webgui?

            forget my question…
            0_1452085363756_Unbenannt.png

            W 1 Reply Last reply Jan 6, 2016, 2:00 PM Reply Quote 0
            • W
              Wayne Workman @cotec
              last edited by Jan 6, 2016, 2:00 PM

              @cotec said:

              The user which i can setup in FOG-WebGUI are admins or user? has this user access to webgui?

              They are all sort of equal. the switch for “mobile only” really isn’t good because FOG mobile is in a state of disarray at the moment.

              There is an access control plugin that is intended to limit what users can do based on location - but it doesn’t totally work right.

              If you are concerned with other people goofing things up - just make everyone an account and tell them to use their own account. There is a history table in the database that will list most actions and the user that executed those actions.

              Also - training goes a long way.

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

              136

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project