@george1421 Yes, I think that client A will always boot from the same iso, but I am thinking that I could change iso’s by simply changing the fog.local parameters and point to another iso. This idea looks like it will work, so it is just a matter of trying it out in my lab setup. If that works, I’ll roll it out into the production environment.
As far as using FOG for imaging, I don’t really know at this point. Probably yes, but since I just discovered FOG, it will be a work in progress. Almost all of our Windows machines boot from SAN over FC, and to take snaps of their O/S’s I use dd right on the SAN array. The only problem with that is that the machines need to be shut down for this procedure. Possibly FOG could make this simpler…
Thanks for all the input. I will report back hopefully within the week and let you all know how this is working.
Scott
Best posts made by guthriesound
-
RE: Custom client boot menus for each client
-
RE: Custom client boot menus for each client
@george1421 I think we can mark this as solved. This conditional test works very well. I ended up using the MAC address for this and then creating a separate menu for each iso.
Example: In fog.local parameters
iseq ${net0/mac} f4:4d:30:65:23:94 && goto fog.Ubuntu-16 ||
iseq ${net0/mac} 00:30:1b:82:d2:d2 && goto fog.Gparted ||Thanks,
Scott