Windows 10 Client 0.11.4 Windows Service
-
@Joe-Schmitt Hi,
In this Textfile you see the Hardware of two diffrent machines, the Bluechip with the SSD work with the auto and delayed auto option, the HP 6300 Pro Clients with the WD Hdd only working with the delayed-auto option.
0_1469777655120_Spec 112 113.rtf
Unattend:
0_1469777856949_unattend.xmlSetupComplete:
sc config FOGService start= delayed-auto
net start FOGServiceSoftware:
Windows 10 education 64 bit
Office 2016 32 bit
AndroidStudio
Eclipse IDE
VLC
OpenOffice
Chrome
Firefox
All updates of Office and Windows are installed, also it is the current Version of the other Software. -
Can you update your setup complete to restart as described in the updated wiki article?
-
@Joe-Schmitt I did. I’ve tried with the reboot - didn’t work. I’ve tried with automatic-delay - didn’t work either.
-
@RLane are there any entries in fog.log?
-
@Joe-Schmitt There isn’t because the service is not starting until a manual reboot. In event viewer, it shows that the service failed to start after 3000 ms or something, failed twice like this.
Good news though… works well on an SSD. Any machine with a 7200 HDD, it doesn’t start the service in time. I haven’t had a computer fail yet with an SSD.
-
Yes I understand, I need to see if any entries are being made in the fog.log on the failed start.
-
@RLane You can’t expect support for the new FOG Client without giving the senior developer of the new FOG Client a log, which he needs to give support.
-
The v0.11.5 release candidate should fix this issue. More testing needs to occur before I mark this as solved though.
-
@Joe-Schmitt Do you think it’s safe to solve this thread?
-
v0.11.5 of the client prevents premature startups of the service. You will still need to disable the client before syprepping and restart the computer when sysprep is complete though (as described in the updated FOG Client wiki article).