FOG boot alternatives
-
Slight recap:
Needed bits to ensure all works properly:
- If the host is registered and you created a tasking on the fog server
– mac=<macofhost>
– osid=<osidOfImage>
– 1. 1 = 2000/XP
– 2. 2 = Vista
– 3. 3 = Win 98
– 4. 4 = Other Windows
– 5. 5 = Windows 7
– 6. 6 = Windows 8
– 7. 7 = Windows 8.1
– 8. 8 = Apple Mac OS
– 9. 9 = Windows 10
–10. 50 = Linux
–11. 99 = Other
– imgPartitionType=<all, or partition number>
– img=<imageName>
– imgid=<imageID>
– imgFormat=<format 0 or blank = partclone, 1 = partimage>
– imgType=< n = resizable, mpa = Multi partition all disk non resizable, mps = Multi partition single disk non resizable, dd= raw>
– storageip=<IP of fog server>
– storage=<IP of fog server>:<path to images location>(Used for NFS connection)
– web=<IP Of fog server> (This is used to communicate progress info to the server, check in, check out, etc…). - For non registered hosts or you don’t want to make a tasking, you will need:
– osid=<osidOfImage>
– 1. 1 = 2000/XP
– 2. 2 = Vista
– 3. 3 = Win 98
– 4. 4 = Other Windows
– 5. 5 = Windows 7
– 6. 6 = Windows 8
– 7. 7 = Windows 8.1
– 8. 8 = Apple Mac OS
– 9. 9 = Windows 10
–10. 50 = Linux
–11. 99 = Other
– imgPartitionType=<all, or partition number>
– img=<imageName>
– imgid=<imageID>
– imgFormat=<format 0 or blank = partclone, 1 = partimage>
– imgType=< n = resizable, mpa = Multi partition all disk non resizable, mps = Multi partition single disk non resizable, dd= raw>
– storageip=<IP of fog server>
– storage=<IP of fog server>:<path to images location>(Used for NFS connection)
– web=<IP Of fog server> (This is used to communicate progress info to the server, check in, check out, etc…).
– capone=1
- If the host is registered and you created a tasking on the fog server
-
@Tom-Elliott Thank you for the excellent detailed information. From that info I’ve been able to come up with a workable solution. Its not complete, but is workable. if we were to update the hostinfo.php script to pull in the extra info the kernel call could be simpler by 3 variables. But that is a discussion for another time since this grub line will work, it will just take the OP a little leg work to collect all of the info.
Here is the menu entry that works on my server.
menuentry "1b. FOG Quick Image Deploy Win10Ent" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=$myfogip/fog/ storage=$myfogip:/images/ storageip=$myfogip boottype=usb consoleblank=0 rootfstype=ext4 imgPartitionType=all chkdsk=0 capone=1 type=down imgid=19 img=WIN10ENTX64 imgType=n osid=9 echo loading the virtual hard drive initrd $myinits echo booting kernel... }
The fields that will change per image are these
imgid=19 img=WIN10ENTX64 imgType=n osid=9
All of this information can be collected from the FOG Web GUI image page. If you go to the FOG web gui and select an image in question.- imgid = look at the browser address URL the
id
value from url is the imgid value - img = the value in the
Image Name
field - imgType = Image Type (calculated from Tom’s table. In the example above imgType of
n
== resizable) - osid = Operating System (the osid value is the number in the parentheses in my case the list box says
Windows 10 (9)
)
That should do it. Just update those 4 fields for each new menu entry matching the image type you want to push.
For reference this grub.conf file is located on the FOS USB boot drive in the following directory
../boot/grub
- imgid = look at the browser address URL the