windows 10 21H2 FOGService not starting

[kallum.redgrave]

I have an image built with the FOGService startup set to delayed-auto as well as starting the service configured in the setupcomplete.cmd. However, this does not run after image deployment without a manual restart.

how can I check/make it so the service starts as this is required for the pc to join the domain?
client version: 0.12.0

[george1421]

@kallum-redgrave In regards to the setupcomplete.cmd

1. Is it actually running after WinOOBE? If you are using OEM media that may be the issue. OEM master media (at least in my experience) doesn’t execute the setupcomplete.cmd file. (you are saying a reboot solves this, so it kind of sounds like it is executing). There is ways around this too, but lets continue.

2. What commands specifically are you executing in your batch file?

[kallum.redgrave]

@george1421

1. I’m using education media , and i know the setupcomplete script is running as it completes other tasks.

2. the commands im using from the wiki, however, I have tested it on the image before Sysprep and it needs administrative permissions in order to run the commands below successfully, is this the issue?

sc config FOGService start= delayed-auto	
   shutdown -t 0 -r

[george1421]

@kallum-redgrave You are missing the command to start the service. You set the configuration to auto start delayed but issue commands to start the service now if you need it running before the reboot (you got the next reboot covered)

The other thing you don’t need delayed start only start the service.

Now if upon reboot its not starting I think I’ve seen another post in the forum with this condition. I don’t remember off the top of my head.

[EduardoTSeoane]

@kallum-redgrave I recomend to do an unattended installation of fog-client from the setupcomplete.cmd instead install it on the image:

https://docs.fogproject.org/en/latest/getting_started/install_fog_client.html

and execute this commands, after installation:
sc.exe config FOGService start=delayed-auto
sc.exe failure FOGService actions= restart/60000/restart/60000/restart/ reset= 120
net start fogservice

this configure the service to start delayed and restart on failure.

[falko]

@george1421 @EduardoTSeoane thanks guys, picking up from Kallum here as he is not on site.

In this new Image Build, we are experiencing the same issue as discussed here where it seems the SetupComplete in Windows 10 21H2 runs but does not run as administrator so unable to change service settings.

Is anyone able to confirm this?

[george1421]

cross linking posts that appear to have similar issues: https://forums.fogproject.org/topic/16330/service-status-of-fogservcie-cannot-be-changed-after-deployment

[george1421]

@kallum-redgrave said in windows 10 21H2 FOGService not starting:

sc config FOGService start= delayed-auto
shutdown -t 0 -r

Just for reference: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-a-custom-script-to-windows-setup?view=windows-11

*Warning

You can’t reboot the system and resume running SetupComplete.cmd. You should not reboot the system by adding a command such as shutdown -r. This will put the system in a bad state.*

Since I don’t use the fog client on my campus I can’t verify. The original post can be read a few ways.

1. Is the SC program failing to configure the FOG Service to start?
2. The SC program is working correctly and the service is set to start but the FOG Service fails to start?

Which is the case?