I am seeing the same issues with FOG 1.0.1 and a Win7 client that used to work with snapins. For example, fog.log on client shows that is it downloading my notepad.exe test snapin and “Starting FOG Snapin Installation.” but it never pops up notepad, and I never see a "Snapin installation complete"in the log.
A couple quick suggestions to aide in debugging snap-ins, and a couple possible bugs reports:
the fog.log lists the ID, and some other info about the snap-in, however, it does not list the snap-in file downloaded. It just says "starting FOG Snapin download then Download complete. Would help to know that it was requesting the correct file in the client-side log
The fog.log shows FOG::SnapinClient ID:x (where x is the task’s ID in the DB)
however, no where in the FOG web interface does it list a snapin’s ID nor the taks’s ID. I can query the db directly, but another column (task ID) in the task lists would be helpful I think to normal end-users. Also, maybe list the snapin’s ID in snapins lists.
BUG 1: If I queue a snapin to be deployed to a client, I see the snapin in “active snapin tasks” and in “active tasks” OK, so far so good.
If I delete the task from “Active tasks” it is still listed in “Active snapin tasks” list
BUG 2: And finally I am noticing something odd in the FOG Client
On startup (Win 7) it goes through all the module startups and delays, etc… Then, after it finds and downloads the first snapin, logs “downloading complete” and “starting FOG Snapin INstallation.” the only module that logs to the file is the FOG::TaskReboot which logs over and over again every 5 mins:
FOG::TaskReboot Attempting to connect to fog server…
FOG::TaskReboot No task found for client.
No other modules seem to be doing anything after that. It’s like the Snapin module did not complete its task, and is holding every other module back from running - Except for the TaskReboot module.