reboot needed for FOG Client
-
@Jbob
Sure, Will do next time it happens. i’m deploying tests all day so it shouldn’t take long. -
@ITCC Any news on this?
-
Yep, sorry for the delay.
Noticed that if you just reboot the machine it works next time. Seems to be the 1st full windows boot it doesn’t work (not always)
I syspreped on 17/03/2016 @ 11:57 (so anything after is a deployment record)
-
@ITCC is the service running when you perform the sysprep, or do you stop
fogservicefirst? -
The service is still running.
-
should I be stopping it 1st?
-
@ITCC It may be worth trying to stop the service before running the sysprep command. I am not sure if it will make any difference, but it’s worth a shot.
-
While I didn’t read the entire thread (sorry being a bit lazy), so if this is a bit off-point just ignore me.
When we install the fog client through mdt, I’ll stop the service right away and then using sc set the service to disabled. We don’t want it mucking about with the reference image before we’re ready.
Then in the setupcomplete.cmd on the target (deployed) system we’ll use the sc command again to set it to auto start and then do the net start on the service. That way the seutp is fully done before the fog client is functional.
-
Sounds like a plan. I’ll complete anyway and report back next week sometime.
-
@Jbob @ITCC While the OP is not new I somehow stumbled upon a missing backslash in the reg key just now!! Didn’t see that before. Shouldn’t it be
SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName\ComputerName(the OP missed the last one)…? -
@Sebastian-Roth that registry key is perfectly fine. The reason it looks like it’s missing a backslash is because of a bug in the registry handler logging mechanism in pre-0.9.12. But even if it was missing that slash, that registry key will not affect anything of importance