Best posts made by Junkhacker

@Tom-Elliott that’s what i meant to convey. the default is 10, and that works fine for most in initial setups and test environments. it’s up to the person running the server to monitor and adjust settings to fit their environments optimal configuration.

@Mentaloid said in FOG + Powershell (WinUpdate) Question:

I used a snapin for tasks like this - because I found fog service was renaming and rebooting before any tasks that took more than a few seconds in my setupcomplete.bat. Any snapins are installed after domain join, at least by my testing.

Snapin Run With : %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe
Snapin run with argument : -ExecutionPolicy Bypass -File
Snapin File : WindowsUpdate.ps1
Snapin Args: Y Y

Snapin Command should look like this:
%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -File WindowsUpdate.ps1 Y Y

That should work fine - and it seems snapins are pushed in order now, so I have this snapin named as 005.wsus for example.

just wanted to post my results from getting a powershell script to run with the legacy client. i had to use the following settings:

Snapin Run With : powershell.exe
Snapin run with argument : -ExecutionPolicy Bypass -command "& ’
Snapin File : script.ps1
Snapin Args: ’ "

the -command "& ’ and ’ " will wrap the script with it’s full path in quotes, allowing for spaces in the path.

@TCS_Taylor files are no longer used the way they were in FOG 0.3x
ipxe can request the files over http instead of just tftp like pxelinux could, so we generate the boot information on demand using php.

@jguest what kind of hardware is in that computer? does it actually have a private mac address of 01:01:01:01:01:01 assigned to it?

@Scott-Adams i’m under the impression that cost is one of the main reasons people choose FOG to begin with (of course, they stick around because they realize how awesome it is, but anyway…) so i don’t know how many people would be willing to pay for classes. as it is, there’s a lot of written tutorials, and a few video tutorials.

of course, that’s just my opinion, do you think there is much interest in classes?

@SaxxAppeal if you want to use the new client, yes. fwiw, there have been so many improvements since 1.2.0 that it’s well worth the update

@alouis here’s what i use

:MENU
menu
item --gap -- ---------------- iPXE boot menu ----------------
item clonezilla_backup Clonezilla backup
item clonezilla_restore Clonezilla restore
item return return to previous menu
choose --default return target && goto ${target}

:clonezilla_backup
login
kernel http://${fog-ip}/ipxe/clonezilla/live/vmlinuz initrd=http://${fog-ip}/ipxe/clonezilla/live/initrd.img ocs_live_run="ocs-live-general" boot=live live-config noswap nolocales keyboard-layouts=NONE edd=on nomodeset ocs_daemonon="ssh" ocs_lang="en_US.UTF-8" vga=788 nosplash fetch=http://${fog-ip}/ipxe/clonezilla/live/filesystem.squashfs ocs_prerun="mount.cifs -o user=${username},dom=<domain>,pass=${password},vers=2.1,rsize=32768,wsize=32768,rw, //server/share/clonezilla/${username} /home/partimag "
initrd http://${fog-ip}/ipxe/clonezilla/live/initrd.img
boot ||
goto MENU
:clonezilla_restore
login
kernel http://${fog-ip}/ipxe/clonezilla/live/vmlinuz initrd=http://${fog-ip}/ipxe/clonezilla/live/initrd.img ocs_live_run="ocs-live-general" boot=live live-config noswap nolocales keyboard-layouts=NONE edd=on nomodeset ocs_daemonon="ssh" ocs_lang="en_US.UTF-8" vga=788 nosplash fetch=http://${fog-ip}/ipxe/clonezilla/live/filesystem.squashfs ocs_prerun="mount.cifs -o user=${username},dom=<domain>,pass=${password},vers=2.1,rsize=32768,ro, //server/share/clonezilla/restore /home/partimag "
initrd http://${fog-ip}/ipxe/clonezilla/live/initrd.img
boot ||
goto MENU

i this uses a mapped smb location using user supplied credentials to save into a folder that shares the user’s name.
to restore images, move the image to the “restore” directory.
i did it this way to reduce clutter by multiple people saving images, and adding a small amount of security, since most of this is done by student workers.

the “update/install failed” was because it couldn’t connect to the database, because fog didn’t have the database password set
now that you’re on 1.2.0, you need to edit the password in <web-root>/fog/lib/fog/Config.class.php

other important information to know

we used PIGZ because it was a parallel implementation of gzip. it took better advantage of multicore/multithread processors than standard gzip while maintaining complete compatibility with the widely used gzip compression.
gzip has been around for a long time and is a widely used standard. it, however, even using pigz, does not multi-thread well.
gzip/pigz compression can go from 1-9, or you can crank it to 11 for a very intensive compression at high cpu cost (there is no compression level 10)

zstd (zstandard) is a new type of compression. zstandard hasn’t been around long enough to become widely adopted, so if you ever want to use the files created by fog with another program, like clonezilla, that needs to be kept in mind. zstandard multi-threads well, and has better performance overall than gzip.
zstd compression can go from 1-22. 20-22 are “ultra” settings that will fail to work if the system you’re using to capture does not have a high amount of ram.

my personal experience in converting an image from pigz -6 compression to zstd -11 are as follows:
capture ~20% faster
size ~26% smaller
deploy ~36% faster

@KevFlwrs the “size on disk” is the partition size that partclone is trying to capture. fog tries to resize the partition down before capturing it, but it can only shrink down to the last used block on the partition. you might be able to get it to shrink down if you defrag the drive before you attempt to capture the image.

@klkwarrior why not do full registration?

i recommend opening the file and making sure the changes were saved

@adame lol, we’re all morons sometimes.

unless you’re specifically testing the ipxe boot file, you can just set up a line in the default.ipxe file like this

:bootme
# redirected to dev server for test environments
##test-computer 
iseq ${serial} F8HLK02 && chain http://test-server/fog/service/ipxe/boot.php##params ||

# normal fog server
chain http://normal-fogserver/fog/service/ipxe/boot.php##params

@ayoward yes

you’ve transferred the files, but fog also stores for each image a “profile” of information. this information is stored in the database. if you’re comfortable with interacting with the database directly from the mysql command line or a tool like phpmyadmin, the easiest way to transfer this data from an old server to a new one is to copy the “images” table from the “fog” database to the new server’s “fog” database. on a new server where you have not created any new images, this should be safe to do. if you have created new images on the new server prior to copying over your old info, you’ll need to be careful to not duplicate any “imageID” values.

if it fails, run the task again as a debug task. that will make it easier to see where exactly it fails

@george1421 i don’t think my setup is really that special. it’s a gigabit network with dell clients and a used Poweredge R510 we picked up cheap for the server (perc H700 raid controller with a 24 drive array, which is probably why i have the nice speed, tbh)

or, you can recreate the image profiles manually through the web interface

i would take a backup of the drive with clonezilla and play around with removing/resizing the wasted space partitions with gparted