OP had AntiVirus installing inside SetupComplete.cmd before the FOG Client was re-enabled and started. The specific AntiVirus installation caused a reboot, which left the SetupComplete.cmd un-finished, and therefore all these other problems happened.

Consider building a snapin for the AntiVirus, which will auto-queue for any computer that is told to image and has the snapin associated with it, and the snapin will deploy after imaging is completed.

@MattPayerle said in FOG Client on Windows does not create host record on server:

the GIT pull runs but then doesn’t change the version number.

You have to re-run the installer.

@kyle.heath Does the bios updates only run in windows or is there a DOS option?

In our case we use a WinPE boot disk that has all of our dell bios drivers on it. We boot from usb flash drive that has WinPE on it then we launch the proper bios driver to update the system. We have scripted an automated process for this now, but that is the basics of how we install a consistent bios version on all of our bare metal computers (we use a winpe boot disk).

@PageTown I know it was a long path to get to this point, BUT know in your heart you are in a better place for the pain you went through. (just channeling Dr. Phil).

You are on a current and supported release of the your OS and for FOG. When 1.3.0 stable is finally released you will be on a solid platform that you can use for a few years.

@Tom-Elliott I have tried a VBScript and have been unable to run it on the domain without having admin rights. How would I set admin rights with VBscript?

@Wayne-Workman I thought about something like that but did not know if it would work or not.

I’ll be working on this stuff more later this week. I may try that.

Cheers,

Joe Gill

@Wayne-Workman See post! I just updated it. Ha!

At this moment I have very less time to investigate (reasons which I don’t want to share on a public forum).
From the supplier I got a response:
Why “create partition primary” would not work as expected (=reserve all available space for a single partition), is not quite clear to me. It might depend on the version of “diskpart” (and its specific flaws), as well as the cyl/head/sector information read from the SSD, or the C/H/S mapping the BIOS applies which may differ from what the SSD tells (yes, this mapping stuff is still around after all these years of LBA…), and may as well depend on the setting of ACPI vs. IDE in BIOS (not sure if the hardware has this at all).

The suggestion to use the tools lsblk and fdisk is very interesting, to see the information which Linux reads from the SSD.
I’m not familiar with Linux, but we can learn. Takes only time.
I have still the idea, there is a mismatch between the SSD configuration, the BIOS information about the SSD, the information windows is using during diskpart and the Linux information.
I’m using FOG very basic. With the Windows Tooling I’m creating an working setup on my golden hardware model (8GB SSD and 16GB SSD). With the FOG tooling I create an image (Multiple Partition Image – Single Disk, Windows 7, not resizable).
The created image is distributed to many identical hardware models (without any modification on the image).
Now, if I create the 16GB image with the windows tooling, while I use the Create partition primary with the size parameter set to 15.2GB, everything works. FOG is not generating any error.
Later (September) I will check in more detail the mismatch ….

@Wayne-Workman Its been a long road but I finally have everything working. Tested on 3 different systems. A Daktech, An old Gateway, And an older Dell Optiplex all deployed perfectly with 1 Golden image. Drivers and all. The solution i came up with was to create a reboot.bat using “shutdown -t 0 -r -f” and at the end of setupcomplete.cmd place “CALL C:\xx\xx\reboot.bat”. It seems the slow systems just need a reboot to get the service to load properly as Joe suggested and of course we all want it to be automated. The delay could possibly work as well but i cant confirm since i came up with my solution before seeing this. At least the information is there if someone else stumbles across this. Thank you everyone for helping me tackle this. I greatly appreciate it.

@george1421
I"m betting it’s the order in which the script performs it’s tasks. I have the fog client reactivation set at the very end of the script. I’ll try adjusting the script and re-imaging.

This image is being used on identical hardware for this test.

@JoeG I have debated on just installing AV with a plugin. We’ve installed it with group policy in the past. It does work that way.

We have had a multitude of issues this summer and I’m trying to just get things ironed out on the last part of my installs before the school year starts next month. I’ve been thrown into the role of network admin after many years of being out of the tech world and I"ve been trying to learn the “proper” way of doing things.

Thanks for all of the advice!!! I appreciate the help!

Cheers,

Joe

To answer your question that article was written specifically for windows 7. So yes you need to use winpe10 drivers for windows 10 (its on the same dell driver page). Everything still works as documented , with the exception of the registry change. For windows 10 you have to add a section to your unattend.xml file to tell windows 10 OOBE to look for the drivers in a location you choose.

@george1421 This is also true for Windows 8 and 8.1.

@Tom-Elliott Thanks Tom You guys rock Love FOG and Thanks for getting back to me so fast Its all up and running

@Wayne-Workman Thanks that setting was already done But I had to change it at the host level and now it work Thanks everybody for there help Now have a bigger problem will open a new tread Again Thanks

@Wayne-Workman But sharing is caring. And it’s so much easier to maintain just one file in a shared location.

@Boyan-Biandov I also have basically re-used my Win7 unattend, though I did run it through the Win10 SIM to validate it. The only place I put it is in C:\Windows\Systems32\Sysprep folder. However, I have had the “Windows could not parse…” error and in looking at the setuperr.log in C:\Windows\Panther\UnattendGC folder (this one is different than the setuperr.log in C:\Windows\Panther, I don’t recall how though), it pointed me in the general direction of the <ProductKey>xxx</ProductKey> entry in “Specialize” pass. I ended up removing all product key entries and don’t have the error anymore. I have never really used audit mode, I just enter product key during installation and run “c:\Windows\System32\SLMGR.VBS” /ato" to re-activate after imaging (in setupcomplete.cmd). Good luck!

Edit: Forgot to mention that it always seemed to me that the unattend in C:\Windows\Panther was a post-sysprep record with all the sensitive data removed from the file by Windows as it processed it. I never before ran into any instructions to put it both places so I never have. Now if someone could tell me how they make the Win10 Default User profile keep the pinned icons on the taskbar I’d be the happiest camper alive.

@kc7mdl Beside the already requested information a picture of the error will speak more than a thousand words. Please take and upload one.

I don’t see any relevant reads on this issue at this time.

Well I do find a lot of posts on surface 3 - have you read through all of those?
https://forums.fogproject.org/topic/6227/surface-3-fails-to-image
https://forums.fogproject.org/topic/6116/surface-pro-3-fog-1-2-compatibility
https://forums.fogproject.org/topic/5689/surface-3-imaging
https://forums.fogproject.org/topic/3662/surface-pro-3-pxe
https://forums.fogproject.org/topic/2432/surface-pro-pxe-boot-need-to-image-for-mass-deployment
…

Great thanks I’ll give it a try.

It’s a 2008 R2 DHCP server.
Joe’s suggestion is a great idea. I’ll try that!
Thanks again!

I might have to try it. I’ll have to play with it.

Thanks!!