Here’s my 2 cents:

Option 1.) Make a plugin. Please don’t even attempt to edit FOG gui without using a plugin. The plugin API is much simpler to use.
Option 2.) Make a bash script. It could copy the image directory and the appropriate SQL data.

@Wayne-Workman said:

the WiKi SVN article somewhat promotes upgrading to the developmental revisions…
I really think that the other upgrading methods should be ditched, IMHO. But others here feel otherwise.

I very much agree. There have been so many major fixes, changes and improvements, that anything less than SVN (3410 in my case) is hamstrung by comparison.

Sad truth is, although Tom is fuc**** awesome at what he does, he is largely a one-man-army and he has a full time job and wife and so on. He’s the driving force behind FOG.

Indeed 👏 👏 👏

The IP field may not be visible, directly, but it is not gone. When you search for a host, it automatically searches for the ip field, at least in SVN.

Or something more elaborate than a green dot…

Funny you should request this. I actually implemented this exact thing at my old work place. You could update the host location from the ipxe boot menu, and see their locations when editing the host.

[quote=“Joseph Hales, post: 47440, member: 18131”]Maybe adding a hash check to the troubleshooting script? Were we going to include the updated troubleshooting script in the utils folder for SVN.[/quote]

Now that’s a winner. Let ya know if your FOG files are busted or not.

How about…

Apply the snapin to everyone,

Then, in your script, just specify computer names… if the computers name matches such-n-such, install the font.

Added.

No idea if this is currently possible or not, I’ve not gotten the opportunity to mess with the location plugin yet…

But this is a good idea.

[quote=“Wayne Workman, post: 46571, member: 28155”]Then, can we get rid of all the settings that don’t do anything?[/quote]

Try it and see 😉

Regards,
Ch3i.

MBR & Partition Table of Disk causing error…

[url=“/_imported_xf_attachments/1/1950_sfdisk.txt?:”]sfdisk.txt[/url][url=“/_imported_xf_attachments/1/1951_mbr-part-table.txt?:”]mbr-part-table.txt[/url][url=“/_imported_xf_attachments/1/1952_mbr-backup.txt?:”]mbr-backup.txt[/url][url=“/_imported_xf_attachments/1/1953_mbr-boot-code.txt?:”]mbr-boot-code.txt[/url]

If you’re trying to just add version, it at that point has already loaded System.class.php. All you’d need to do is append the FOG_VERSION to the file name. But scufa doesn’t always change even though it does always ask to check. Maybe date is better option as even if you revert the newer items are likely not read anymore.

awesome.

This is already up and running. File didn’t work the same on all distros but I found a similar method that appears to work the same.

That is exactly what I was looking for, Tom. Thank you so much!!!

SVN 3320 Released has this in a real simple form.

The difference, for now, is ipxe is hosted directly in the SVN folders. This means an svn up -r <rev#> will roll you back. Of course I don’t constantly update ipxe files. I try to keep up with the speed of development on ipxe, but many times I’m much faster.

The USB restore would be cool there have been lots of times in our business where we have a couple of fog servers that having the ability to restore images via a USB would have been cool and saved time

Simple enough to add. SVN 3285 released with all of this.

No more need.

I’ve removed the flags that seem to error and even removed the cause of the error in the first place. This should no longer be an issue.