@george1421 This is from 2009. I’ve tried this before and totally abandoned trying. https://wiki.fogproject.org/wiki/index.php/Bootable_Media

I started to mess around with using etherboot but never got anywhere with it.

just updated. all the clients in the building took it in under a minute lol. Good job as usual, @Jbob and @Tom-Elliott

https://forums.fogproject.org/topic/5587/bootable-usb-stick-v1-2-0/10

https://forums.fogproject.org/topic/4782/help-usb-boot-fog/10?page=2

ba-da-bing-ba-da-boom. RC 1.

@george1421 said:

The only issue I can see for dnsmasq is that the fog server is not on a subnet by itself. From what I think I understand the fog server is on the same network as the clients and the dhcp settings are coming from a remote location. Unless I’m off on this you can not run dnsmasq and dhcp-relay for the same subnet since both will respond to the dhcp request

You would run dnsmasq in proxy mode. It responds to DHCP Requests with only add-on information. It operates with a pre-existing DHCP server, it does not serve as a DHCP server.

https://wiki.fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server

I concur with Tom’s post. I did write a huge thing I was going to post, but then realized it was like three pages long… so I deleted it. I’ll summarize that you’ll have less problems if you use RHEL, CentOS, or Debian for server OSs. Ubuntu is my favorite workstation OS, but I won’t use it for a server if I can at-all avoid it. And I do speak from some experience. Tom of course speaks from way, way more experience.

@Canonical I wish you’d stop changing stuff so much so often, and stop assuming that you know better than the administrator. If we set a setting via SQL manually, post OS installation, and post-mysql installation, you have no right to change it with an update that you push out at whim. I’m sick and tired of the unity-webapps-common package, I think it’s source code should be deleted forever. And I think that automatic updates via unattended-upgrades is complete bogus. Often I’ve found that even though I select “Do not update automatically” during the OS installation, the unattended-upgrades package still applies updates. This is evidenced by the message “You need to restart your server” when I log in via SSH. Then you went off and fell in love with Microsoft, I don’t approve of this. I think you’re too young to be in a relationship with such an older company. Surely, the older company will take advantage of you and you’ll end up pregnant with a WinBuntu baby, or worse get some kind of virus that you’ll need to see Dr. Symantec for.

@Arrowhead-IT Tagging your post for the #wiki -and I need to finish that article https://wiki.fogproject.org/wiki/index.php/ProxyDHCP_/_dnsmasq_-_DRAFT and I’ll likely use some of the stuff from that post below.

@illustry said in Ubuntu is FOG's enemy:

In short … it updated itself along with its configuration.

Another example of Canonical thinking they know better than the administrator. It has never been ok to overwrite configuration set by the administrator, nor will it ever be. Updating the schema of a configuration file while preserving the configuration is one thing, but overwriting custom configuration is unacceptable.

What version of FOG are you trying to install?

Are you behind a proxy server?

Goodness that is a huge list. Well done.

I’ll share all the curl commands I have for the new API soon as I’m back home.

@kbramhall Isolated subnet? Does it have an internet connection?

I think it’s sharp.

@Arrowhead-IT said:

Just so you know. The reason I chose not to use DHCP with FOG is because I had the mistaken assumption that FOG would automatically manage it in some way, or that the gui would have some control over it. It does not, you’ll be doing a bunch of manual configuration.

I guess now is as good a time as ever to say I’m working on an add-on that does just this.

@tom-elliott Great work, we all appreciate what you do.

@george1421 @Arrowhead-IT Good point. Right now I think we’ve got it narrowed down to either a DNS issue or a proxy issue.

@george1421 no implied warranty - for fund raising only. Sell it as a “key chain”… that just so happens to have your USB UEFI booting stuff on it lol

@templink When you’re posting large chunks of code to the forums, please use the code box feature. It looks like in the pic below, it’s located just above the editing window. Highlight your code and then click the code box feature and it will wrap your code for you.

@fry_p Once DHCP is configured, you will never have to change it. It takes 10 minutes to setup, every step is laid out for you in here:

https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

Being aggravated with fog renaming computers, and then wanting to disable it… that’s like being used to a manual transmission, and then being aggravated when you get a car that shifts automatically… and then trying to go through 1st, 2nd, and D manually instead of just slapping it into D and not worrying about it.

Computer renaming is one of the top reasons to use fog.

People have all of these other ways they “take care of” renaming and domain joining. And that is fine void of FOG, but FOG offers a more simple and streamlined solution. A lot of people are confused at first, but I promise it’s worth your time to check it out.

How is it worth your time? Simple math.

It used to take me and a team mate half a day to image 30 computers in our building. If it was just me, it was most of the day. With fog, it only takes one person, and I just click a button. Then I go do something else for an hour, and I come back and it’s done. Computers renamed, joined to the domain, software and printers deployed. Computers READY TO BE USED by the user, right then and there.

It’s hard to keep the compatibility list updated. We only know what people tell us. Generally, if the model ever worked with fog, it will work with future versions - generally.

Upgrading from .32 to 1.3.0 RC2 should go smoothly. You’ll need to set your old images to use ‘partimage’ instead of partclone.

Before updating, take a DB backup. I don’t know if .32 can export the DB or not, in later versions it’s located in FOG Configuration -> Configuration Save -> Export. If you don’t have that, you’ll need to do it manually. Instructions on that can be found here: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL

Also, if you don’t have FOG doing dhcp, you’ll likely have it setup in Windows, and option 067 for this old installation is likely set to the old unsupported file, you’ll want to change that to undionly.kkpxe

Further - CentOS 6… @Developers @Moderators @Testers can anyone confirm that 1.3.0 RC2 works on CentOS 6 without a hitch?