I realize this post is a bit old, but I wanted to thank everyone for their suggestions and give our experience to back up what has been said in this topic already. We experienced an image that should have been about 120gb, but was showing in FOG as the full 500GB hard drive. After referencing this thread, it fixed the issue. The steps we took are below in order:

Verified that the PC didn’t have a second drive or second large partition it was capturing
Verified that bitlocker encryption was OFF using the command prompt command “manage-bde -off C:”
Ran Disk Cleanup (to get rid of old unused files)
Ran Tools > Check to scan for hard drive errors (may require reboot to fix)
Ran Tools > Tools > Optimize and defagment
Capture Image again

Once we did those steps, the newly captured image only takes up the actual amount used on the hard drive.

i solved my problem using undionly.kpxe file from a debian 10.4

@sysadmin How did you create this directory /opt/fog_stable Did you clone it from the git repository? Your error is not a very common one or one I’ve personally seen before.

Just to be clear (I can read your request 2 different ways), fog doesn’t care about the source image or how its setup. FOG only moves disk blocks from the source computer to storage on the FOG server and then from storage on the FOG server to the target computer. How you prepair the reference image before cloning and what happens to the target computer after FOG is done is up to the IT technician.

But in general terms, for MS Windows you will want to setup the computer in audit mode to perfect how you want the target computers to appear, then sysprep the reference image and power it off (using a sysprep command line option). Then you pxe boot the reference image with FOG and capture the image. On the target computer side, you register the target computer with FOG. Then you assign an image to the target computer and create a deploy task. When the target computer is pxe booting FOG will image the computer then reboot it. On the first reboot the target computer will startup OOBE/Winsetup to complete the installation on the target computer, at this point of the first boot of the target computer FOG is no longer involved with the imaging process (said knowing that if the target computer is configured appropriately the FOG client will carry out an required post install commands).

There is a wiki page that describes capturing your first image that you might want to look over: https://wiki.fogproject.org/wiki/index.php?title=Booting_into_FOG_and_Capturing_your_first_Image

@rubencarmo Are both systems (target you pull the image from and destination PC) set to UEFI?

That was it! I knew once you mentioned the configuration for both uefi and bios, that was where the trouble was. I have enabled dnsmasq per the instructions you linked and it booted into the fog menu without issue.

Thank you very much!

First of all its not the best place to put the recovery partition at the beginning of the disk. The MS recommends the efi partition be on disk 1 partition 1. It has been that way for years. Also I would question the logic of needing a recovery partition at all. With FOG its much faster to rebuilt the system then to try to recover it. I understand (as someone recently pointed out) that if the computer is at a remote location to the FOG server then the only option is to try to recover it. On my campus I don’t use/create the recovery partition at all. I do use MDT to build the golden image, with MDT I can chose how to create the disk layout for both bios and uefi systems. If I had a choice I would place the recovery partition before the 😄 drive partition, that would make the biggest resizable partition last on the disk where it can be easily resized.

@bradgillap Thanks for reporting! I have not heard about fog-client being detected by any anti virus program yet. Have done a quick search in the forums and found nothing either. So I don’t have an easy solution for you on this.

Good you have been able to deploy again and put it on the exclusion list!

Soooo … 🙂

After Resetting the Encryption it works.

So in this case uninstalling the FOG Client, then Reinstalling it, manually started the FOG Service in Window and reset the Encryption Data solved the problems for this client.

I have a second machine that seems to have the same problem at first glance, but have to check that to make sure it really is the same.

And the Thread you found from me at the beginning of my FOG journey … i still add the certificate manually during sysprep via the setupcomplete. On this client I havent imaged in quite some time and its only me using it. Really strange. 😕

I’ll check the other client and report back.

Thanks !

@ckasdf Are you still onto this?

@Real1987 What does this have to do with FOG imaging solution? Is this after deploying an image to the 3400? What version of FOG do you have? What OS is in the image? What type is it set to (resizable or non-resizable)? Is BIOS set to legacy mode or UEFI?

Many more questions arise, but we might start with those.

@fog_client Well it depends. Did you download it from a microsoft VLK site (requires a login and account) or did you download it free of charge via the ms download site? If it was the later then its an OEM version that will activate itself using the OEM key if installed from the ISO image. The VLK media (different code than OEM download) comes with either a MAK key or KMS key to activate windows.

@chenguy I guess I would have to ask why are you not using an unattend.xml file?

At my company we don’t use the FOG client to manage the computers post imaging so that means FOG is not renaming the computer, connecting it to AD, or placing it in the correct OU. My environment is a bit complex so the hostname and AD OU location is calculated during imaging with the results updated in the unattend.xml file before FOG releases the computer and the target computer is rebooted. This is done before OOBE/WinSetup starts for the first time. Using this approach you can use the load and go method of image deployment where you don’t register the computer with FOG and FOG will forget about the computer once imaged. Understand using this method without the FOG client there is no post imaging management included including snapin deployment. We have other tools for that.

Using the unattend.xml file alone we can select the desired keyboard layout, computer name, connect to AD, etc.

thank you so much!you resolved my issue about PXE of windows 10 because i can now boot in uefi mode and also boot on windows 10…!
I still have a problem with windows 7.
I can boot pxe with uefi mode but after deploying windows 7, when it boots on windows 7, i have a screen with “refind” (see attached file please)![erreur UEFI win 7.png]. Whe i swith to “bios mode”, windows 7 boots…(/assets/uploads/files/1589268143874-erreur-uefi-win-7.png)

Thank you for your help
here is my dhcp configuration:

class "pxeclient" { match if substring (option vendor-class-identifier, 0, 9) = "PXEClient"; if substring (option vendor-class-identifier, 15, 5) = "00000" { # BIOS client filename "undionly.kpxe"; } elsif substring (option vendor-class-identifier, 15, 5) = "00006" { # EFI client 32 bit filename "ipxe32.efi"; } else { # default to EFI 64 bit filename "ipxe.efi"; } }

really weird…i copied and pasted a few times…I tried again and you were right…i feel stupid…:(
thank you so much!!!you are so helpful…:)

i undestood why it did not work…in you tutorial, you say that we have to remove space inside the name of the folder for driver’s path.
for example, we have to create a folder called “optiplex390” and not “optiplex 390”. But in my case, i need to put “space” in my folder…and now, it works like a charm!

@george1421

Thank you a lot. It worked. The backup PC works. There is also a connection to the AD (of course only if the Main-PC is offline).

So good news, figured it out. I did the win7 to win10 upgrade and took an image. When I deployed the image I received the “not activated” I then clicked the “change product key” and entered the unique product key on the decal on top of the dell box & was able to authenticate. So although it’s not off the bios & is an extra step at least its authenticated and legit. So glad that worked. Thanks for your help

@mwilcox said in Windows 10 Driver and Deployment Question:

So maybe that was the other unsigned driver which caused the hang. I can do more testing tomorrow

If there are any unsigned drivers or any reason why the driver install pops up with a question it will fail the install (probably not something you want to happen at a client’s place). There is a bcd edit command you can turn on in your golden image and then turn off in the setupcomplete file that will accept all drivers signed or not. Usually Dell only ships signed drivers. So I’m a bit surprised at the condition.

With that setup does it install drivers after the deployment while it’s booting up Windows?

Yes, but in the golden image we will typically deploy the Dell WinPE driver pack so the golden image has at least the basis drivers. If you are shipping the hardware with Win10 then most of the basic drivers are already built in.

Would there be a prompt or something somewhere in the FOG GUI that would ask for a activation key before image deploy?

If you are using the load and go approach, you are not registering the computers with FOG. Normally when you do a full registration you could enter the key there. But if you are using the load and go approach then you are not registering the machine with FOG so you have to be a bit more creative. In this case you would create in your post install script a prompt to enter the key value, then take that key and update the unattend.xml file using the fog.updateunattemd. Probably that script is where you would want to stop and ask the FOG installer for the key.

Testing is the key even if you eventually end up with a hybrid of FOG doing everything, except you turn the system on at your facility do a QC check (drivers: yes, activation: yes, etc) then ship it to the customer like you do today. The idea is to eliminate as much hands on stuff you do so you can build more systems faster.