Figured it out.

goto ${username} || goto MENU

:fogUser
menu
item --gap -- ---------------- Welcome fogUser ----------------
item return        return to previous menu
item kav        Kaspersky Antivirus
choose --default return target && goto ${target}

:fogTech
item --gap -- ---------------- Welcome fogTech ----------------
item return        return to previous menu
item Clonezilla        Clonezilla ISO
item UBCD        Ultimate Boot CD
item Hirens        Hiren's Boot CD
item kav        Kaspersky Antivirus
choose --default return target && goto ${target}

:MENU
menu
item --gap -- ---------------- iPXE boot menu ----------------
item return        return to previous menu
choose --default return target && goto ${target}

Then just define the functions below the menu. fogTech and fogUser being different users that the menu accounts for and MENU being the default menu.

This was made apparent after looking at the advanced.php code presented here https://wiki.fogproject.org/wiki/index.php/Advanced_Boot_Menu_Configuration_options

Access to this menu can be granted without granting that user rights to the website by clicking the “Mobile/Quick Image Access Only?” toggle when creating the user.

Not sure if this has been resolved or not, but this site was a great help to me in setting up my Clonezilla PXE boot; http://clonezilla.org/livepxe.php .

you’ll need initrd.img, vmlinuz, and filesystem.squashfs from the .iso or .zip of clonezilla.

Here’s what I ended up with…

:Clonezilla
initrd http://<fogIP>/fog/clonezilla/initrd.img
chain http://<fogIP>/fog/clonezilla/vmlinuz boot=live config noswap nolocales edd=on nomodeset ocs_live_run="ocs-live-general" ocs_live_extra_param="" keyboard-layouts="" ocs_live_batch="no" locales="" vga=788 nosplash noprompt fetch=http://<fogIP>/fog/clonezilla/filesystem.squashfs
||
goto MENU

and that has me booting to Clonezilla just as if I picked the default menu booting from usb.

This might be a tie in with this feature request https://forums.fogproject.org/topic/4408/security-for-fog-users but I’m wondering if a guy can present different ipxe menus in the advanced menu section based on what user is logged in? This user has access to this tool, but should have access to this tool… i.e. an IT deployment tech may need access to an SCCM deployment tool, but a IT Security tech may need access to a recovery tool to which the average IT tech shouldn’t.

I’ve been noticing that docker is picking up in popularity. Are there any plans for an official FOG docker image?

[‎1/‎26/‎2016 2:20 PM]
Ok
getmac didn’t work
I did that already
[‎1/‎26/‎2016 2:21 PM]
and netsh interface show interface gave me null response

Is what i get from my colleague at the computer. Good to know that this can cause the issue though and that it’s not the server itself. Going to suggest a hardware upgrade and get that going. Thank you.

Re: MAC IS null! only 0 mac address was found

I’m having a similar problem, but it’s only happening on one computer. I have nearly 20 other computers set up on this server and they’re working fine.

My theory is (this is a Gateway E6610D super old) that the drivers are bad, there are a couple of system items in device manager that don’t have drivers on them. So I’m asking, can screwed up drivers cause this problem?

Is CIFS supported in 1.2.0 though?

Do you have an example of what the storage node in the web interface would look like for a SMB storage node?

Is there a variable in the code or a setting in a file that would allow the clients to mount /images/ directly from the storage array?

It hasn’t been explained to me why our current situation is such a pain for the storage array administrator, but he’s expressed a strong desire to get it mapped onto the FOG server as an NFS or Samba share. Unfortunately neither of those can be re-exported out to the Client boot images. We went the virtual OS and storage array solution for redundancy and growth. And it is our standard practice for the rest of our servers. ((they’re still pretty hurt that it’s not a windows server))

Tried a Samba/Cifs share as well and it still acted the same way as the re-export did. A thought that I just had was if the Client computer mounted the storage array’s nfs export directly. I don’t see a setting for that out-right in the fog settings though, and it’d require the nfs to be wide open on our network.

This is a past deployment and we have since attached the share to the esxi host so that the FOG OS would see it as a physical drive. But the server team doesn’t want to keep it this way and would like it to be like their other shares which are not filled with vmdk files. So we are in a working state, but I’d like to know what others have done about this problem.

My FOG version is 1.2.0. I have my main operating system virtualized with 40 gb of storage. I am being provided an NFS share of 4 TB for my images. When I try to mount it to my /images/ folder i get an error on my client computers saying they can’t mount /images/. Further research tells me that what I’m trying to do is an NFS re-export which is impossible. Do you have any work arounds to this?

i have a task that I want to run every quarter. This would be */4 which implies the following set {0,4,8} which means it only runs 3x a year, so it really should be */3 which implies {0,3,6,9} so we get 4x a year. Unfortunately this task will need to be cascaded among a lot of different computers and I’d like to space them out over the quarters. So if this is correct then I should be able to put something like (wild+1)/3 which should imply {1,4,7,10}; (wild+2)/3 => {2,5,8,12}. ((the wilds were put in cuz * caused auto formatting))

To test this theory I’ve been playing with the Hours section and watching when the task activates and this does not work for (*+1)/2 which should flag the task every odd hour.

I know I can do this kind of thing with a list and maybe I should, but I was wondering if there is a more elegant way to state this in the fields?