Put the machines into a group. From the group, update the ad information as needed and save. That should update all your machines with the necessary information.

@hauser said in Issues using driver path in sysprep - Windows 10:

It may be that this method just doesnt work any more as I am fairly unfamiliar with the changes in sysprep of Windows 10, but I also was curious if this is even the best way to add drivers to the images.

You are rigth, M$ broke this handy feature of defining where the drivers are. What I’ve found to be reliable is using the pnputil command in the setupcomplete.cmd batch file to load in any remaining hardware specific drivers. So for my campus I have 2 golden images (one bios and one uefi) for 15 different hardware models, where the hardware specific drives are transferred to the target computer using a post install script, then I run the pnputil program to load the drivers.

ref: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed/4

@Gilberto-Ferraz said in Boot Option Issue (PXE booting):

Hello @Brendan-Clemente!
I have the same problem I tried to solve with the suggestion of @george1421 using Dell CCTK tool kit. But I could not. Are all your machines from Dell for this tool to work? Do you have any tutorials to follow?

Tools for working with BIOS configuration options are both manufacturer dependent and model dependent. Most manufacturers are moving toward some kind of wmi-acpi support, but each manufacturer has their own timetable for switching and that switch requires a new tool. You will likely want to consult the support pages for the manufacturer(s) of your machines as there is no universal solution.

@tech49 In this topic there is more than one issue being discussed. So “exact same issue” is not clear. As this was on FOG 1.5.6 I suppose things might be different anyway. Please open a new topic and post all your details: FOG version, Linux OS/version, error message (picture)…

@Joe-Gill Are you still around? Would be great to hear if you still see this issue on some of your machines. I have tried to replicate this problem but wasn’t able to. See here: https://forums.fogproject.org/topic/13902/fog-service-and-interventions

@Borega Try this file: https://github.com/FOGProject/fog-client/releases/download/0.11.16/Modules_SnapinPack_empty_dirs.dll

Should have the fix in it as well.

@mikeakin44 Please read trough this topic: https://forums.fogproject.org/topic/13922/dell-optiplex-aio-5270

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

@Scott-Boucher This issue is definitely not fog related. I have seen this on multiple occasions and usually comes down to a UEFI machine with a SSD. either try disabling sleep is the advanced power settings, try disabling hibernation, Disable fast boot in bios, or theres a “turn off hard disk after” setting that you may want to see if thats disabled. I have linked this issue to usually the computers bios misidentifying the SSD as a HDD making windows use the wrong things to sleep/hibernate.

If you are using a HDD then try to see if there is a bios update for your machine and/or driver updates from the manufacturers website. Good Luck, this problem is proprietary to your type of device. Do some research in that and also look at disabling the settings.

I have also learned that 5400 rpm 2.5" HDD are absolutely horrible. If that is what you have within those machines, try to put in a SSD for a test and see if you get the same results.

@Gael et al.

I’m post a more descriptive post to summarize what the issue is. I don’t know how to fix (so I’ll start there.)

TL;DR;

Linux Kernel is putting a volatile Firmware on the NIC. This happens when FOS loads and the kernel begins associating the drivers. On restart, the firmware is still existing on the NIC from the Kernel. When Windows Boots, it re-flashes the volatile firmware so subsequent elements will work. Or a full power pull will do too (completely cold boot.)

Basis:

This particular issue, is due to Linux Kernel having a firmware defined for the NIC. This is volatile. This means when power is pulled, the firmware will no longer be present and normal actions will work properly.

While the machine is in FOS, the linux kernel hands it a temporary Firmware File and this is what’s causing the strangeness with the NIC.

Pulling the power cord causes the firmware to wipe. Similarly, if booting to Windows immediately after, and then powering off the machine, it should WOL. This is because Windows has a FW being applied when it loads, overwriting whatever the Linux Kernel pushed.

@Wayne-Workman Worked for me

@samuel You can set a kernel parameter in the iPXE menu options to make machines shut down on deploy (or other tasks). Go to the FOG web UI -> FOG Configuration -> FOG Settings -> General Settings and add shutdown=1 to the field FOG_KERNEL_ARGS.

@Sebastian-Roth hi, yes: they have the same settings, they are all from the same batch (production wise)

I believe the system partition is the issue. I tried imaging on legacy and uefi, issue doesn’t change.

Tried to wipe the disks first, also no change.

Will try the full copy tomorrow, thanks for your suggestion.

@agray You said you set the machine to legacy, and secure boot is off, but
1 did you enable CSM support?
2 did you change your boot order?
Please take a picture of your BIOS/UEFI settings so i can help as well.
Im interested in your boot page, CSM, boot order, and secure boot pages

@kralon @Sebastian-Roth

I force the windows 10 activation on Windows 10 Pro with a script like this Script. It’s Writed thinking in WindowsUpdate disabled.
It Works to me on all License Types, except LV’s that is not tested.

If (-NOT ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) { $arguments = "& '" + $myinvocation.mycommand.definition + "'" Start-Process powershell -Verb runAs -ArgumentList $arguments Break } # License $serviceName = "wuauserv" $hostinfoFile = "c:\nntt\hostinfo.txt" # this is the hostinfo file downloaded from the postdownload $COAProductKeyPattern = "(?<=hostproductkey=).*" $COAProductKey = Select-String -Path $hostinfoFile -Pattern $COAProductKeyPattern | ForEach-Object {$_.Matches.Value -Replace "'",""} $BIOSProductKey = (get-wmiObject -query 'select * from SoftwareLicensingService').OA3xOriginalProductKey.Trim() Set-Service -Name $serviceName -StartupType Manual Start-Sleep -s 5 Start-Service -InputObject $serviceName (Get-Service -InputObject $serviceName).WaitForStatus('Running') If ($BIOSProductKey) { Invoke-Expression -Command "changepk.exe /productkey $BIOSProductKey" } ElseIf ($COAProductKey) { Invoke-Expression -Command "changepk.exe /productkey $COAProductKey" } Invoke-Expression -Command "$env:SYSTEMROOT\System32\cscript.exe //B $env:SYSTEMROOT\system32\slmgr.vbs /ato" Start-Sleep -s 10 Stop-Service -InputObject $serviceName (Get-Service -InputObject $serviceName).WaitForStatus('Stopped') Start-Sleep -s 5 Set-Service -Name $serviceName -StartupType Disabled Start-Sleep -s 5 # End License

@sokhanh21xn Mind responding to my questions?

This topic is being discussed on github in detail: https://github.com/FOGProject/fog-client/issues/110

@Sebastian-Roth the domain alunos.sc.br is a sub-domain of sc.br. I will test it as you mentioned, only with user. Soon notice the return here, thanks for now!

@mm-Ekimia From what I read between the lines I can imagine this being a UEFI vs. legacy boot issue or something.

If you still need help with this I ask you to post the information I asked for. Marking as solved for now.

@Quazz I know that I can capture and deploy UEFI images in Legacy mode, but I have to go in front of the PC turn it on, go in setup page, set network boot, then deploy, then go again in setup page, set windows boot manager … and do it 300 times.
So at the moment I’ve made a Legacy installation image, and I leave all pc in network boot, so when I want to deploy I just select the group and fire a multicast deploy.
I’m working on YASHI for booting in legacy mode I’ve ask to their support.