Fog 1.2.0 Instant Deployment tasks not starting on client

[zta104]

I have Fog 1.2.0 running on a Ubuntu 14.04 Server that overall working fine in regards to actually cloning and deploying images when a task is already in queue before the client is turned on. The problem is that when a task is assigned for instant/delayed/chron deployment while the client is already on the task just stays as queued and the client remains at the desktop or login screen. Upon restarting the machine, the task will execute through PXE boot no problem. Does anyone have any idea why my clients wont restart and perform their tasks? (clients are assorted dell win 7 machines)

[Tom Elliott]

Does your image have the FOG Client installed?

[zta104]

@Tom-Elliott Yes it is currently running the stock 0.1 Client Tray

[Tom Elliott]

@zta104 And TaskReboot service is running?

[zta104]

@Tom-Elliott Yes the management console showing the service is enabled on both the server and the client, and the service was checked off during client install as well.

edit: double checked client services from management console

[Wayne Workman]

@zta104 The next step is to upload a copy of the c:\fog.log from an affected system. Setup a task as you described, let it go for a bit, then grab the log.

[zta104]

@Wayne-Workman Can do I’ll post the log in the next hour

[zta104]

@Wayne-Workman @Tom-Elliott here is the log from a Download with Instant Deployment selected:

0_1481899987293_fog.log

edit: Re-uploaded log

[Tom Elliott]

404 Means that it cannot communicate to the FOG Server.

So either your client is not configured appropriately to look at the server (maybe it’s looking for fog-server instead of ip of fog server?)

Please post the C:\Program Files (x86)\FOG\etc\config.ini (64 bit windows) or C:\Program Files\FOG\etc\config.ini

[zta104]

@Tom-Elliott
0_1481904964760_config.ini

[Tom Elliott]

And 192.168.1.203 IS the fogserver IP address?

[zta104]

@Tom-Elliott Oh no, the server is set to 192.168.1.230. Should I change the address in the config.ini directly?

[Tom Elliott]

@zta104 Yes. Once you do that, though, you’ll need to restart the “FOG Service”

This can be done with cmd as administrator with:

net stop "FOG Service" && net start "FOG Service"

[zta104]

@Tom-Elliott That did not work, a task was assigned at 12:32p for a upload scheduled for instant deployment with no response on the client machine.
0_1481913703197_fog.log

[zta104]

@Tom-Elliott Never mind I got it taken care of, it would seem that in the config.ini file underneath the taskreboot section the force restart the value must be set to 1. It also didn’t hurt to shorten the checkin time as well. Thank you and @Wayne-Workman for the help!