Most likely these are partially (or fully captured that were unable to move) capture images hanging out in /images/dev

@irishfoguser Hi, generally speaking you’re better off using Resizable image. If this for some reason doesn’t work (fails to deploy), then trying the other options is recommended.

For your situation, it sounds like Resizable Image will do the trick. So I recommend picking an image, setting it to resizable, recapture, deploy and see if it works for you.

1.3 is able to resize the correct partition for you before Windows even boots for the first time.

To be fair, it’s been a longstanding recommendation that the FOG server should be running nothing but the FOG server for a reason.

@TomBagley Considering you have to enter tftp server address, it is likely you have another DHCP server on your network (likely your modem), which might be interfering.

Apparentally, to prevent Windows search from breaking after copying the profile over, all you have to do is delete

AppData\Local\Microsoft\Windows\UsrClass.dat

Windows will create one on login.

It’s /var/www/fog/service/ipxe (singular service)

I’m guessing you launch a batch script which launches a msiexec and then closes rather than waiting

Adjust accordingly.

What error are you getting?

set username foglogin
set password foglogin
params
param mac0 ${net0/mac}
param arch ${arch}
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

Try using that, changing the set username and set password parts to your own webgui login info

@lebrun78 You could try a different disk boot command. You can choose these globally, per group or per host I believe. Default is Sanboot if I’m not mistaken.

There’s different options because different hardware handles it differrently, annoyingly enough.

Fairly certain the problem is that Snapins run under the System account, which cannot interact with the desktop, and thus you can’t “elevate” to administrator.

@gadams Look into unattended installations (unattend.xml)

@Baessens What about the files in /images/dev?

We can assume credentials are fine; otherwise it would complain about that before being unable to create a file (I assume, could be wrong)

@gadams If you used sysprep for the original base image, then it likely shut down the PC cleanly; thus avoiding the problem.

@gadams It’s common to confuse the two, but I think Sebastian is referring to Fastboot on the Windows 10 installation itself. (in the software, not the BIOS).

It’s an option under Power Management -> Behavior of power button (translated, could be called differently, it’s top on the left menu anyway)

Then you need to click on the thing to show all options, requiring admin access.

You can now uncheck “Fast boot”

The reason “Fast boot” can cause issues is because it stores certain things in the “hibernation” file so it can more quickly load on next boot. Unfortunately this causes issues for FOG (and certain drivers…) and is pretty pointless for SSDs anyway.

Alternatively, simply shutdown cleanly before capture. (Windows Key + R -> shutdown /s /t 0)

Some time ago, FOG changed the linux user to be ‘fogproject’ instead of simply ‘fog’.

This is the account the FTP tries to connect to.

Looks like it can log in successfully, but fails to move the files, indicating a permission problem.

sudo ls -lah /images

Will show you current permissions.

More than likely the owner is incorrect.

sudo chown -R fogproject:root /images

@kaywokke

type=down for deploy
type=up for capture

Simple as that.

But there are other potential parameters that may be necessary for it to function as expected.

@drumnj said in Error trying to restore GPT partition when deploying Image to smaller drive, Error Return Code: 4:

@Sebastian-Roth Overall the current solution isn’t bad, so no real rush to figure out. I just think it isn’t the best solution. I suppose another option for people is to always make a golden image on a drive smaller than any other drive they plan to deploy to. Doing this I have found does allow the recovery partition to be used (did this with 2004 to make a clean OOBE Win10 image…with Chrome included).

That works, but I believe you run into the problem of being unable to expand the size of the Windows partition itself since the recovery partition is blocking it.

I’m not sure how to resolve this at the moment, personally I don’t use recovery partitions, they don’t really offer that much in my experience, though of course in some environments they may be desired or needed, so a solution would be ideal.

@Trev-lchs No; they are applied recursively (-R)

Can you share a picture of where it hangs?

@Trev-lchs You may need to set the owner and permissions again since you’ve made a new folder and file.

So run the chmod and chown commands again.

@Trev-lchs Use single quotes instead of double round your echo command so the literal string is passed.

Or paste the script in its entirety using a text editor.