Best posts made by Junkhacker

i have to recommend that you give FOG a shot as it is supposed to be configured. with as fast as FOG images systems, you’ll have them all imaged in the time it would take you to remove all their hard drives for your original intended method. does anyone have a demo video from after we added zstd compression?

this is what i had to do to upgrade my Ubuntu 12.04 dev server
manually run:

	sudo add-apt-repository -y ppa:ondrej/php5-5.6
	sudo apt-get update
	sudo apt-get install php5

allow all config files to be replaced with defaults
re-run fog installer

@Polii123 after you reset the encryption data, it takes a while for the clients to all check in and get up to date.

@Wayne-Workman i’ve created a demo video in the past for a conference i spoke at
https://youtu.be/gHNPTmlrccM
i just don’t have the time to edit the video for a new one

/tmp/pigz1 is a temporary location where data is streamed for compression/decompression. that part of your system seems to be running fine. what it sounds like, however, is that your drive is not being re-sized to fill the disk after imaging completes.
what version of fog are you using?
i’m assuming this is a resizable image, is that correct?

that’s part of the reason i asked what happens if you boot into windows and restart. for some nics the windows drivers properly initialize and shut off the card, allowing the card to properly initialize on the next boot. but a non-windows reboot may not.

@Benjamin_D look into the location plugin. i think you should be able to do what you want to do, but i don’t think anyone has done it before.

or perhaps a “quick register and shutdown” ?
if you are running the trunk version of fog you can add a new item to the ipxe menu by clicking “iPXE New Menu Entry” in “fog configuration”
in that area you can create a new entry with the following values
Menu Item: fog.autoreg.off
Description: Quick register and Shutdown
Parameters: <leave this blank>
Boot Options: mode=autoreg shutdown=1
Default Item: <unchecked>
Menu Show with: Not Registered Hosts
that should shut the computer down after quick registration. let me know if it doesn’t work for you

@daniell you could register the hosts and issue the imaging task from the web gui instead of from the pxe menu

@dantehaversham just read some of the documentation on network booting the pi. it should be possible to get this working with fog, actually. with exceptions. it would be able to push images down, but without the finesse that we do on PCs. the ipxe menu systems and dynamic configuration parts wouldn’t work.

if it’s taking 5 hours to upload, it makes me wonder: did bitlocker somehow get enabled on the machine you’re trying to upload?

@Spark for the
Windows VM, (someone feel free to correct me if i’m wrong on these specs)
80GB HD, 1 CPU, 4GB ram

for the Fog server, you’ll probably want at least enough room to store 3 images (remember that when you replace an existing image, both old and new exist at the same time on the server for a short time) so
200GB HD, 1 CPU, and at least 512MB ram

@flipwalker fog should have no problem with this.
though, with that much data, it will probably take close to an hour to image each machine. (of course, you can do more than one at a time)

@Wayne-Workman beta implies that it has reached a point where it is being tested to be considered a release candidate, trunk is simply the development trunk. the central repo of all changes that have been brought into the mainline. while we try to keep the development trunk stable, it is not a finalized form and hasn’t necessarily been tested much at all, depending on how much has been committed to it on a given day.
I prefer to recommend upgrades to specific versions of the trunk if I can. an upgrade from 1.2.0 to svn revision 3652 should be pretty painless and has most of the new features that most users would notice.

is there a reason you chose to use a mysql query instead of using the built in mechanism of an http request to

<fog-ip>/fog/service/hostname.php?mac=f8:bc:12:6e:67:78&newService=0 

using the http request, you wouldn’t need to utilize database credentials

@flipwalker consistently isn’t generally an issue when you’re using fog. once you know it works with your specific model of computer (which is most of them), it just works.

I don’t believe you’ve mentioned what network boot file you’re using, but I’m going to assume it’s the default undionly.kpxe
sometimes the undionly.kkpxe works better, especially on buggy bios/pxe implementations. I’d give that a try before giving up on it.

@george1421 yuck, you’re right about the line wrap. it would look better and work just as well to make that:

set net0/next-server <otherPXEbootServerIP> 
set filename <whateverFile> 
chain tftp://<otherPXEbootServerIP>/<whateverFile> ||

@foglalt said in Disappearing hosts from host list:

as far as I know about fog database updates are done upon things finish and starting point. I mean if i change mac during deployment, database is updated on change and upon task finish

actually, it’s updated every couple of seconds during the task with the progress of the task.

have you considered just customizing the inventory report built in to fog?