FOG 1.2.0 and the legacy fog client does not support windows 10. You need the newer version of fog (1.3.0-rcX at the time of this post) and the new fog client (0.9.X or newer) for win10 support.

For sure you will need the 1.3.0 series for native FOG server support for uefi firmware, gpt disk format, NVMe disks, and Win10 support running on current hardware (i.e. latests FOS engine running linux 4.7).

Well it looks like this is definitely a problem with this model of laptop. The Windows 7 Enterprise installer finished copying and expanding all of it’s files and then as soon as the first reboot happens the computer hangs at the same black screen I receive after imaging it. Looks like I’m destined for the HP support line to kick this up the chain for a fix :(.

Edit: I just rebooted without the network cable plugged in and now the installer continued without an issue. More testing needed but maybe an issue with how the FOG boot menu is handing back off to the boot cycle on this model. I’ll update once I’ve done more thorough testing.

Edit 2: The solution for this is that the “Host Bios Exit Type” for this model must be set to “GRUB” or it will hang before the OOBE portion of the Windows install process starts. “SANBOOT” causes this 100% of the time on our units and “EXIT” returns an error. Presumably any of the “GRUB” options would work but I haven’t verified any other than the basic “GRUB” option.

For future readers - FOG 1.2.0 has poor support for Windows 10, and the legacy fog client that comes with FOG 1.2.0 isn’t supported on Windows 10.

To gain full support for Windows 10, GPT disks, UEFI, newer nvme type disks, SSD disks, and numerous other hardware support to include Surface Pros, and better support for non-standard partition layout, along with incredible performance improvements, new features, and security benefits,

Please install the latest FOG 1.3.0 Release Candidate, and use the new FOG Client that comes with it.

25% Packetloss… Guess China’s firewall doesn’t like it…

Sorry for the prolonged absence. I’ve created a new legacy image, using the same driver deployment process. This image deploys successfully to the Z70-80. There are some other machines that we absolutely do need the legacy image for, so it’s not too much overhead to just use that image for the Z70-80.

@Wayne-Workman We do. 🙂 I tried that, we’ll see what happens! As you know our domain setup needs improvement. I’m doing my best to straighten it out. Ugh!

@BedCruncher said in Host does not boot into PXE after reboot:

@Joe-Gill
I would suggest setting network boot as first priority and then setting a timeout of 5 seconds on the menu so that if there is no task, then at most your boot time is impacted maybe 40 seconds.

You can also “hide” the fog boot menu. It’s an option inside Web Interface -> FOG Configuration -> iPXE Boot Menu

There’s also the “no menu” option.

There’s a hide timeout, and a regular timeout. The regular time out applies when hiding isn’t being used.

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