Antivirus can also do this. Have you tried letting the original VM boot?

When sysprep is run with reference to an unattend.xml it parses that .xml then writes a generated unattend.xml in Panther.

I would have expected it to overwrite what might already exist in Panther.

It’s been awhile since I’ve worked with anything but my own .xmls, but that generated .xml in Panther can reveal information from the original, which is why it’s good to always delete it in post-sysprep cleanup.

If after the machine has shutdown you were to alter the original unattend.xml you referenced by sysprep, it would have no effect because it only looks at the one it generated and left in Panther when it powers up for the first time.

Re-sysprepping an image can be messy or a thing of beauty depending on your forensic skills and how deeply you want to dig out the detritus of the previous sysprep.

Server

• FOG Version: 1.4.0-RC10
• OS: CentOS 7.3.1611

Client

• Service Version: n/a
• OS: n/a

Description

More of an FYI, but the installer spits this out during ‘Configuring services’.

 * Copying new files to web folder.............................OK
find: ‘/home//fog_web_1.4.0-RC-10.BACKUP/management/other/’: No such file or directory
 * Creating config file........................................OK

… and continues merrily on its way.

@ty900000 I’m currently running 1.4.0-RC-4 and I just tested on both types of VMs for this reply and they work.
Gen1 (Legacy) picks up undionly.kpxe and Gen2 (UEFI) pulls down ipxe.efi on Hyper-V 2016 VMs .

Wow … that one almost got lost to the mists of time.

Yes. An update.

I don’t remember precisely when, but I think it was soon after I made this initial post that it started working again.

Regardless, I’m currently running 1.4.0-RC-4 and I just tested on both types of VMs for this reply and they work.

Gen1 (Legacy) picks up undionly.kpxe and Gen2 (UEFI) pulls down ipxe.efi on Hyper-V 2016 VMs .

@Tom-Elliott Fix Network issues in inits that only looped one interface it seemed.

Woohoo!

Depending on how large a cache of new drivers you are injecting by using pnputil you run the risk of bloating the registry. I’ve poisoned Windows 7 images doing this. I haven’t gone back to pnputil since; Windows 10 may be more robust.

I may be the exception with the number of different systems I deal with.

However, building drivers into the local store bloats your master image permanently. I prefer now to install on-demand coming out of sysprep with synchronous commands in the unattend.xml or a .vbs run by auto-logged on Administrator, then deleting the local store at deployment to reclaim that disk space.

Why don’t I use a network-based driver repository? Systems we deploy to may not have access to our network or even a fog server when they first power up.

I’ve created a folder of all the drivers needed by all our platforms (just over 4 GiB worth) that sits in the image. Coming out of sysprep unattend.xml calls dpinst and installs the drivers before oobe, then deletes the folder to reclaim the space.

Outstanding!

Hmm, so a ZSTD compressed image requires what version FOG to deploy?

… and Clonezilla 2.5.0-25 does not support a PartClone image compressed with ZSTD?

May I suggest adding something along the following to FOG Settings?

FOG Image Capture
Enable PartImage capture [ . ]
Default PartImage compression level [#—#]
Set as Default capture method (.)

Enable PartClone (PIGZ) capture [ . ]
Default PartClone (PIGZ) compression level [#—#]
Set as Default capture method (.)

Enable PartClone (ZSTD) capture [ . ]
Default PartClone (ZSTD) compression level [#—#]
Set as Default capture method (.)

With notations of version compatibility for each capture option.

The FOG Boot Setting of FOG_PIGZ_COMP offers a value slider of 0-21 in RC13 (and a little earlier). I realize the change from 0-9 is because of implementing a new library( zstdmt vs pzstd?), but how does it affect things?

Is the FOG RC now using this new method permanently?

Is it still called PIGZ?

How does it affect an image captured with RC13 when it comes time to be deployed by say, 1.3.4?

Is it possible to switch between the old method and the new?

Why is it a BOOT setting?

Just looking for some clarity.

I’d been doing that for awhile until we put our Server 2016 DHCP solution into play. What you network boot with has zero impact on what you lay down onto the SSD/HDD.

Still, bummed that a UEFI network boot solution hasn’t been found for the 790 though. 8(

If only I could find documentation on how to build the boot sequence string in their BIOS.

Exactly how did you get the 790 to UEFI network boot?

You got a Dell OptiPlex 790 to UEFI network boot successfully ?? Ooh, I gotta try this.

And there was much rejoicing.

Lenovo ThinkCentre M72e latest BIOS is f1kt71a.

Lenovo ThinkCentre M72z latest BIOS is f6kt44a.

What is the exact long name of your model?

eg: our M72z models are 3548C1U and 3548C8U .

@george1421 M72e is a desktop, M72z is an All-in-One.

Using sysprep and an answerfile you can add:

<ExtendOSPartition>
        <Extend>true</Extend>
</ExtendOSPartition>

To the specialize phase.

See ExtendOSPartition.

Server

• FOG Version: 1.3.5 RC10
• OS: CentOS 7.2

Client

• Service Version: n/a
• OS: n/a

Description

I am unable to download a different kernel on either RC8 or RC10.

I can select the kernel desired, but selecting NEXT at the page for File Name immediately returns me to the Dashboard.