@luilly23 thanks for the reply. It was a working script before and I had updated it to comment areas and operations recently and added regions within the powershell script. There were no reboot options that I can remember (fairly sure) inline in the script but will double check.

There was a reboot option on the snapin itself.

Is there any log of the fog client to server comms that could say “this caused the reboot” or just more detail. I was thinking of turning the reboot off of the snapin properties to see if it would progress.

Just wondering if someone can point me to the docs on how the snapins actually function under the hood and signal their completion?

Any help would be a ppreciated.

So we have been running fog for about a year and I have picked it up from someone that has left. It was working well but we have an issue with a snap in (maybe more) that does seem to complete.

The snap in downloads some files and sets some registry settings and then the machine should reboot after the task.
In fog it is saying it is checked in then in progress but once the machine reboots it then goes back to checked in and then in progress and then it reboots.

I cannot see something obvious in the (x86)fog log file but can see the download file appear in tmp folder each time. The script itself is doing a PowerShell transcript lot and seems to be find and doing its thing but for whatever reason the snap in task is not marked as complete so it loops and does not progress.

Couple of questions

• What controls when a snapin is marked is completed?
• Is it the windows client talking back to the fog server? Is there a log of where this happens?
• Is there any further debug logging I can put on that may be helpful?