Posts made by MRCUR

@Wayne-Workman Thanks Wayne. I guess my real question is about the upgrade path between clients, but it sounds like there isn’t info on that yet. Obviously out of the box, there is no “auto update” to the new client since the legacy client is still being supported - I’m just looking for guidance on what, if any, upgrade path there will be once 1.3.0 launches.

Upgrade path?

Currently, in FOG Trunk, you’d go to FOG Configuration -> FOG Settings -> Client Service -> and tick the new client checkbox.

There might not be a path of “upgrading” for the old clients… There is talk of discontinuing support of the legacy client, and just disabling it completely in 1.3.0.

As far as the old clients out in the field… they will just be out there… lonely… with nobody to talk to… and some day… they will go to a better place when a new image is applied.

Currently, though, FOG Trunk does support both the old client AND the new one, although you can’t set settings for the old client when the “new client” check box is ticked. Whatever AD credentials/ encrypted strings are set on clients will stay, but new changes will use the new client methods.

Did that answer your question?

@RLane We are rebuilding images (thankfully that’s not one of my responsibilities), but we won’t reimage every machine (tough to do with this many of them).

My actual plan is to upgrade the existing FOG servers (I have one storage node besides the main server) once I’m confident in the SVN rather than do a fresh install on new servers.

@Wayne-Workman Sorry to hop on this thread, but the discussion is very relevant to what I’m working on. Currently we run FOG 1.1.2 on Ubuntu 12.04 LTS. I’ve been messing around with the latest SVN builds on Ubuntu 14.04 LTS.

What’s the upgrade path for the “old” client to the new one? The speed improvements I’m seeing in the latest SVN builds, along with the hopefully improved management UI performance with our 8k+ hosts, makes me want to migrate before summer imaging gets underway on a large scale. With that said, I’m having a hard time finding info on what the upgrade is like to go from the current “old” client to the new one.

Anyone have some input on this?

[quote=“Chris Sodey, post: 40515, member: 1418”]I just tested again and Tom you are right about the typo, it is looking for default.ipxe[/quote]

Did you have any success Chris?

[quote=“Chris Sodey, post: 40510, member: 1418”]I get the same result when using ipxe.efi where the tftp boot server is asking for an IP address. I tried the ip address and the full path, e.g. [url]http://192.168.0.1/ipxe.efi[/url] and it just times out When I tried snp.efi and got to the menu, but it just resets back to the menu when I try to inventory.[/quote]

Good to know you’re having the same issues I am. Sounds like something with ipxe, perhaps someone from the Fog dev team can chime in.

I know this is an older thread, but I just got a few Surface Pro 3’s that I’d like to image through Fog. I installed the latest SVN build of Fog onto Ubuntu 13.10 this morning. I have the DHCP server set to ipxe.efi.

After disabling secure boot on a Surface, I was able to get it to the iPXE menu. Entered the server’s IP when prompted and after about 20 seconds received a timeout message.

Any ideas Tom?

Thanks for the explanation Lee. Sounds like the Location plugin along with the TFTP from Node option is what we want. I hope to put this into production later today.

Thanks again!

-MRCUR

That did the trick!

For the option “TFTP from node”, will this do anything if we’re not using DHCP through the Fog servers? We’d like to have TFTP enabled on both servers, the second one being a storage node though.

I’ve tried that multiple times on both of our Fog servers. Is it required to already have a second storage node added for the plugin to function?

Under “Activate Plugins”, Location is no longer listed. It’s listed under “Installed Plugins”. When I click it, I only get the plugin description. When I click the Location icon along the top Fog menu, I get blank pages.

[ATTACH=full]1176[/ATTACH]

[url=“/_imported_xf_attachments/1/1176_location.PNG?:”]location.PNG[/url]

Anyone?

Hi everyone,

I’ve been working on implementing Fog into our network this summer and have a few questions/issues about the Location plugin.

Our network consists of two rings with ~12 buildings on each. Each building is its own subnet and has L3 access to all of the other buildings across both rings. Currently we have one Fog server in place and are sending all clients to this server for imaging (including TFTP/PXE, DHCP is coming from Windows servers). Ideally we would like to have one Fog server on each ring and have clients go to a specific Fog server depending on their location. It sounds like the Location plugin will allow us to do this. Simply putting in more storage nodes doesn’t sound like it will accomplish what we want since clients can image from any of the nodes then (we do not want traffic to cross between the rings except for the Fog client traffic for AD joins, etc.).

I set up a new Fog server (Ubuntu 12.04 LTS, Fog 1.1.2) on the second ring. It’s working just fine - I can register hosts to it (provided they are sitting in a subnet with the PXE IP pointing to this second server), upload images, download images, etc. This server is running as a master - it’s not a storage node connected to the first Fog server.

I installed the Location plugin on this second Fog server but it doesn’t seem to be working. When I go to any of the three pages under the plugin (search, list all, create), I just get a blank page. The standard Fog UI shows, but nothing where the plugin should be.

Any ideas? It’d be great to know if there are any other solutions to setting up our Fog network as I described above, or getting some help with the Location plugin (if that is in fact what we should be using).

Thanks!

-MRCUR