Registration & Menu issue
-
r6651
I’m working with an Optiplex 7010. It has a wireless card in it.
It’s got these two MACs:68-1c-a2-06-32-5f
90-b1-1c-9b-c1-4fI noticed the problem when I deleted the host via the web GUI and then tried to network boot to try to re-register. The FOG boot menu would not show.
I have always had “No Menu” turned on, and “Hide Menu” turned off.
The menu didn’t show so I’m thinking the wireless card must be registered to the last computer that used it. Sure enough, it was. I deleted the MAC from that host. But the menu still will not show!
So I un-checed the “No Menu” feature and the menu did show, and I tried to register and I see an “INVALID MAC” error pass by on the screen when it’s trying to send the info.
I’ve re-enabled the “No Menu” feature, and I’ve deleted another Optiplex 7010 that does not have a wireless card using the fog web GUI. When network booting this computer, the menu still does not show.
-
On the compatibility checks from the boot menu when I turn off “No Menu”, and I pick number “6” to show the MAC address, no MAC address is shown for the Optiplex 7010 that has a wireless card.
-
Registration should be fixed in current as well as speedier load up of network interfaces.
-
Confirmed fixed - and the speedier load up is also confirmed too - that’s super nice.
-
I feel the need to add.
No Menu is designed to ONLY check if a host has a tasking. This means registered hosts with no tasks and non-registered hosts will simply boot to the first hdd depending on what’s selected.
Hidden Menu is designed to prevent access to the menu. It will boot to a limited screen informing the user to press a key combo to see the menu. When they press the key combo within the timeout period, it will ask the user to login using the FOG GUI’s username and password. From there you will be presented with the normal menu items and this is also how you can access the debug menu item. We’ve protected the “Debug” menu item as it can be potentially dangerous as it gives the user full access to the hard drive and system.
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
-
@Tom-Elliott said:
I feel the need to add.
No Menu is designed to ONLY check if a host has a tasking. This means registered hosts with no tasks and non-registered hosts will simply boot to the first hdd depending on what’s selected.
Hidden Menu is designed to prevent access to the menu. It will boot to a limited screen informing the user to press a key combo to see the menu. When they press the key combo within the timeout period, it will ask the user to login using the FOG GUI’s username and password. From there you will be presented with the normal menu items and this is also how you can access the debug menu item. We’ve protected the “Debug” menu item as it can be potentially dangerous as it gives the user full access to the hard drive and system.
#wiki
