Windows 10 Deployment stuck

[Quazz]

@Mr-Pinguin777 It not rebooting is annoying, but not the main issue.

FOG deployment seems to have gone as expected.

Do you use an unattend.xml file during sysprep?

Is FOG client installed before sysprep?

If yes, is the service disabled before sysprep?

[Mr.Pinguin777]

@Quazz

Yes, we use an unnattend.xml file, fog client is installed in VM before sysprep… strange thing is it works on like 200 computers (Desktops/laptops). I just fails on this type of laptop…

And no service isn’t disabled before sysprep…

[Quazz]

@Mr-Pinguin777 https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep

Unattend.xml problems can also cause this issue, especially in combination with not doing the above.

If you didn’t choose to “generalize” hardware during sysprep, then it’s possible one of the drivers is causing issues as well.

Some antivirus software has been known to cause this as well and must be installed post OOBE (once client reaches the desktop in other words)

[Sebastian Roth]

@Mr-Pinguin777 Re-reading your initial message I see that I obviously missed the details. You seem to have this reboot hang issue only on this particular hardware (HP notebook 250 G3).

Check out my answer in this topic: https://forums.fogproject.org/topic/12922/computer-not-restarts-shutdowns-after-deploy

[Mr.Pinguin777]

@Quazz

I Did generalize imao? no 3the party antivirus installed, we push AV after deployment…

I do think its a driver issue now just looking for solution to insert the drivers, I’m justed to MDT…

[Sebastian Roth]

@Mr-Pinguin777 Did you read my message as well?

[Mr.Pinguin777]

@Sebastian-Roth

Yes I did, well maybe I wasnt 100% clear, the reboot isn’t the only problem, windows doesn’t boot. When I forced reboot windows installation error… I presume this is a driver issue? So I think the reboot problem is solved now… thx Sebastian!!! the kernel argument fixed the reboot problem… now i just have to get Windows to boot, how can I insert drivers in deployment process… Like is said I’m used to MDT, I’m new to FOG…

Grtz

[Sebastian Roth]

@Mr-Pinguin777 This is not really a FOG issue. FOG doesn’t care about drivers at all. It simply captures an image from one system and deploys it to another systems drive. You need to take care that all the drivers are included before capturing the image.

I am not a Windows guy and can’t help you much on this issue. See if there are other people in the forums who might be able to help you with this.

Though you have not even told us about this particular laptop you see the issue on. In the picture it looks like a HP device. Which one exactly? Spinning hard drive? SSD? UEFI or legacy boot?

[Mr.Pinguin777]

@Sebastian-Roth said in Windows 10 Deployment stuck:

Yeah, i kn this is’nt really a fog problem… its the same laptop as the reboot problem, legacy boot, spinning HD…
i could try not? but nvm thx for the help with the reboot problem…

[Sebastian Roth]

@george1421 Are you keen to help out here with information on Windows driver stuff?

[george1421]

@Mr-Pinguin777 Well I would have to ask a few questions here;

1. How are the drivers for this specific model getting into the image? Are you preloading them into the image before capture, are you using a post install script, or are you just letting the native windows drivers do the job?

2. After the image is loaded and the target system reboots (is restarted), what happens?

3. What error message do you see? Does Winsetup/oobe ever run?

4. Does the system spontaneously reboot during OOBE?

[Sebastian Roth]

@Mr-Pinguin777 Did you ever get this solved? Any more help you need from us? See George’s questions.