Fog Service does not start due to time-out
-
Is it only not starting after imaging? If so is your image syspreped? Did you follow the sysprep guide with client in the wiki?
-
@Tom-Elliott There is no task currently. The task indicated in log file was a capture, which finished ok. After that, fog agent has not started at boot time.
-
@Tom-Elliott I’ve optimized disk and agent have started at boot. So it seems strongly related to system performance. I’m goig to make another capture just to check.
-
Is it possible an Antivirus program is preventing startup of the client? (Just going on a wild guess here.)
-
@Frank Please answer @Joe-Schmitt’s questions below - he’s the guy that wrote the fog client.
-
@Joe-Schmitt The image is not syspreped. I have optimized disk, and after that agent have started again on boot. But after capturing image once again, problem have risen again, and agent does not start on boot.
-
@Joe-Schmitt After a second boot, agent started. I guess it is a difficult issue to track.
-
@Frank Do you have an AV client on the system? (I’m just asking because I, too, want to figure out what’s happening.)
-
@Tom-Elliott Sorry for the delay. Nom client does not have any AV client but windows defender, that I have taken off the scheduler. I’m wondering if it’s something related to any driver. I’m going to apply latest patches and see what happens.
-
@Tom-Elliott Hi again.
I’ve tested another (smaller) image and all the tests (capture, deploy, fog agent boot start) went ok. So I think it’s strongly related to client computer capabilities. I’m testing with an old HP dc5700 Core2 Duo 2 GB RAM. I guess there won’t be issues on a little newer computer. -
Just wondering if this is still a problem with newer versions of the client?
-
@Tom-Elliott I will try to test it with the old machine again.
-
@Frank Is this still an issue with the newer client?
