@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
@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
@george1421 Thanks for all the replies. I’ll try to be more concise on how I need it to work. It basically comes down to how the various flavors of VNC work. I run the sound department of a fairly large regional theater company. We use both Windows and Mac based PC’s to run our audio playback software. The thin-clients are used as view-only monitors that various personnel use to monitor which cues are running during the performances. On the Windows side we use UltraVNC utilizing the MS logon feature to control access. The Mac screen sharing, on the other-hand, just needs a password to authenticate. vncviewer will work fine with the Macs but not with the Windows machines. For these we run UltraVNC under WINE. Thus, these thin-clients need to have different ISO’s if I want them to start up, load the appropriate version of VNC with the necessary command line switches. The goal is to create a system where the user simply plugs in the thin-client to power and a net connection and turns it on. I would administer which ISO each machine would boot to via configuration of the FOG boot menus. Currently we are using USB sticks with the different ISO’s on them. This works but is more cumbersome to manage.
I hope that better explains what I am trying to accomplish.
Thanks,
Scott
Hi list,
I am working on a project that I need some help with. I have 6 small thin-clients that I want to boot via ipxe from my FOG server without user interaction. I.E. no keyboard or mouse. I have this working very nicely with one unit which I set the default boot device to the iso I want it to boot from, but I am at a loss as how to create individual boot menus each with a different default boot item for each specific client. Can this be done? These clients are used for VNC viewing of different servers on our network and each needs a slightly different O/S depending on which flavor of server it is connected to.
Thanks for all the great work on this project!
Scott