@Fernando-Gietz Okay I got it working. You guys are awesome keep it up!

@Lenain I think that your only option is develop a new plugin to do this.

@Junkhacker further testing suggests that everything works fine without the --ignore_crc flag we have set in all restore operations. i’ve also learned that due to a bug in partclone 2.89, the checksums it was making were practically useless. if/when we upgrade to the newer version of partclone, we might want to consider disabled checksums to be the default, since we’ve been, in essence, operating without checksums all along.

@Sebastian-Roth said in Option to delete files when deleting multiple images / snapins.:

I really like the idea although it would mean that users need to confirm twice.

I think it’s fine. It’s like Tom said, very serious to mass delete images.

@george1421
Thanks for the answer, do you know you can install DSM over VM or into no synology hardware?
check xpenology

@Sebastian-Roth Thanks that all makes sense.

Thanks Sebastian — from my point of view I could still get rid of TFTP by recognizing either UEFI HTTP Boot (physical hardware) or existing iPXE ROM (in my Nutanix VM) vi DHCP headers (vendor class / user class) and in either case chainload the FOG iPXE binary (with “params” enabled) via HTTP and eventually perhaps HTTPS.

This should be pretty straightforward, I’ll see if I can work it out and I’ll post back - may be worth a wiki article.

Now … the next item to tackle would be replacing FTP (vsftpd) with SFTP 🙂

Feel free to close this thread if it’s no longer appropriate as a “feature request”.

@Fernando-Gietz So lets think about it a bit. in a way you want to tell the pxe booting client (in iPXE) don’t boot of the normal boot loader, but boot from a different partition (lets use /dev/sda6 for discussion). By default sanboot will boot from the first hard drive, and uefi will boot via refind.

Grub can boot uefi. I don’t know if grub distributed with FOG can boot uefi.

If you set the exit mode for a host to Grub first hard drive the iPXE menu is created this way:
chain -ar ${boot-url}/service/ipxe/grub.exe --config-file="rootnoverify (hd0);chainloader +1" || goto MENU

I’m wondering if someone could repurpose the setting rootnoverify (hd0);chainloader +1 to actually load /dev/sda6?

The other challenge is that grub.exe is probably a bios mode application where we would want to use grub.efi for uefi.

Again this is just me thinking out loud about the issue.

@Tom-Elliott Maybe add another user confirmation to make clear this will overwrite an existing image…?

@Tom-Elliott Store them in the database and have a daily cron job that cleans out logs older than N days (user defined). If FOG were to switch to MariaDB 10.3, the TokuDB engine would be available for use. TokuDB has in-engine compression. The compression savings is pretty staggering compared to InnoDB. TokuDB does not support foreign constraints - and because the FOG db doesn’t use them, we are A-OK there.

The compatibility menu is accessible to a host machine when there are no tasks for the host. When you have a queued task the host would automatically boot into it.

@dsloan-ethra Thanks. Also another option would be to just stop the FOG Client service via a snapin.

@psyfer9983 There isn’t a tutorial on what you ask, because poking about in the windows registry using a non-windows OS is not typically a good choice. But with that said, I can give you the match and can of gas. What you do with them is up to you.

In this post there is an example of how to use the reged linux utility. https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection/4

From that post here is the interesting snippet of code.

regfile="/ntfs/Windows/System32/config/SOFTWARE" key="\Microsoft\Windows\CurrentVersion\DevicePath" devpath="%SystemRoot%\DRV;%SystemRoot%\inf;"; reged -e "$regfile" &>/dev/null <<EOFREG ed $key $devpath q y EOFREG

You can probably stack the ed commands so you only need to call reged once. Here is a help page for reged: http://manpages.ubuntu.com/manpages/bionic/man8/reged.8.html

So once you have the bash script you need, you can call it during the post install actions after the image is placed on the target hard drive and before FOS exits and reboots. The first link shows you how to update/attach scripts to the postinstall script (which can be used for driver deployments).

We have made a special setting in deploy.image menu for the computers of the room. Then login and password are not requested to access to deploy menu.

#login params param mac0 ${net0/mac} param arch ${arch} param hostname ${hostname} goto host_${hostname} || goto autres :host_bug :host_win10-3 :host_i207m01 :host_i207m02 :host_i207m03 :host_i207m04 :host_i207m05 :host_i207m06 :host_i207m07 :host_i207m08 :host_i207m09 :host_i207m10 set username userlogin set password userpassword params param username userlogin param password userpassword param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme goto fin :autres login params param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fin

@p4cm4n You could probably use a snapin-pack to deliver the Chrome MSI as well as a powershell script. The powershell script could do a small loop with a maximum of say three iterations. Each time, it can try to install Chrome and then check if it’s installed. If the correct version is installed, exit the loop.

If the imagesize is empty, FOG only shows me the option to capture or deploy all image. If the imagesize is not empty, FOG shows me the options: all image or only one partition

@trialanderror I get where you’re coming from, but I agree with Tom that this for free software would be too much of a nightmare to do LTS support on. I mean, there isn’t even a support team. I’m glad they don’t spend a ton of time going back to old codebases and backporting it. The installer does a good job of not blowing stuff up and the db schema typically upgrades fine too.

I say “good” because it isn’t totally transparent about what’s going on, so you do actually have to be a bit familiar with the upgrade process to make sure that you don’t do anything that could lead to loss of data.

@wayne-workman and @george1421 this has been added for 1.6. I’m not going to try adding it to 1.5 as it is a bit of work to add the tests and the return information is at best rudimentary in 1.5.

I can work on adding a feature like this but it’s a lot of code and checks that have to go in on groups, and hosts. Perhaps, images would be better suited for ou/domain joining though i would prefer to see ou/domain management in its own format potentially as its own plugin. This, in my eyes, makes the most sense as OUs typically go with the domain being associated. The method used for the current ou system works by a single domain though you can keep in mind that hosts can be manually assigned domain/ou information. The “global” setting is just a quick way to set default information. It is by no means the only domain that can be used.