Fog driver injection in 2026.

[Paul Freeman]

My org used FOG many years ago and is now tired of Microsoft Autopilot, so I am setting up a new FOG site for our org.

I have added the fog.drivers script from the tutorial site: https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection

It looks like the script attempts to run, but indicates some errors preventing the script from running. (see screenshot). At first I was running a modified version of the script, attempting to simplify the machine identification, but I have since tried running the script as it came from the FOG tutorial and have the same result.

[Tom Elliott]

@Paul-Freeman \r is usually an indicator.

Like your script may have been opened/edited in Windows text editor/notepad, then saved and uploaded to /images/postdownloadscripts/fog.drivers

Why does this matter?

Windows likes to use “CRLF” line endings from the days of “Control Line Feeds” of automated typewriters.

\r\n is the typical sequence that Windows uses for a new line, which sends the line back to the beginning then moves to the next line.

*nix uses \n and tries to use \r as an actual key which is invalid in most scripts.

I might recommend replacing all \r items within the script to \n or '' (empty space)?

[Paul Freeman]

@Tom-Elliott Well I feel silly. I am using a Windows workstation to set this all up. I corrected this and now the script appears to run.

Now this errors out stating it did not find drivers, which in this case is true, I’m testing this on a VM. This also seems to fail the task and imaging restarts when the machine reboots. Is there any way to tell the task to “continue on error”?

I have a test laptop on the bench that I will play with next week. Thanks for your help.

[Tom Elliott]

@Paul-Freeman Do you mind posting yoru script?

I suspect your script is throwing a handleError (which will exit and restart the machine) and since postinit runs before the task gets to complete that explains what you’re seeing.