@Joe-Schmitt I can confirm printer-management is working flawlessly with the new client-version.
Printers are assigned correctly, setting default printer and renaming printers is working.
Only thing I didn’t test yet is if changed config-files are recognized.
I also appreciate a lot the new powermanagement module! This is really awesome!
Thank you so much, you and the other devs do a really great work!
I agree with @Wayne-Workman , meanwhile you could use setupcomplete.cmd as a workaround.
Do the following steps:
Before Sysprepping disable Fogservice as described here: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep
Create a file setupcomplete.cmd in C:\Windows\Setup\scripts and put your code inside
Add the lines
sc config FOGService start= auto
net start FOGService
after your code
setupcomplete.cmd is called by windows after setup is finished. As the fogservice is disabled, it can’t interrupt your script.
The last two lines enable and start the service.
@Wayne-Workman OK, I thought about installing the fog client after imaging by calling the msi-package from setupcomplete.bat, but this way is even easier.
I can confirm this working for me.
Thank you!
@Wayne-Workman Maybe i’ve got the clue. I too have a blanked settings.json file.
The windows eventlog shows an unexpected shutdown at 14:17:56
Windows Explorer shows, that settings.json was last changed at the same time
So I guess the file was opened to get updated while windows crashed.
@Wayne-Workman setupcomlete.cmd has to be placed under C:\Windows\Setup\scripts in the master system.
As the name indicates, the script is called by windows just after setup has finished.
Btw. l set the Fog service to delayed start, ie I put
sc config FOGService start= delayed-auto
into the script.
I don’t know, if this is really necessary with the new fogclient, but it doesn’t harm.
Reason for this is i’ve got some computers which require delayed start with the legacy client (afair network doesn’t come up fast enough)
@Tom-Elliott I’ve got the same problem (on ubuntu 14.04 and fog 1.3.3)
Here is the fog.log 0_1484747088387_fog.log
And error.log 0_1484747149856_error.log