Snapins seem to not function at all, how might I reinstall the component that does them.
fog 0.32 hosted on a linux mint server that’s not tha tup to date.
I can create snapin and assign them to machines, creating them fog knows if I’ve uploaded that file before or not however.
The snapin page does not show any at all, only the various drop down boxes to add snapins to machines list them.
My clients with snapins applied, in their log file the SnapinClient finds no tasks for its MAC.
This particular snapin is a reg file if that matters.
I just started messing with snap-ins. I’ll give you some of my observations.
I’m running FOG on Ubuntu 10.04 LTS Server i386. I have some mods to my FOG setup to help with proxyDHCP, but other than that, it’s mainly stock code.
A snap-in has to be defined, then assigned to hosts, either individually or by groups. This still does not make the snap-in active, meaning it isn’t going to do anything yet.
To get the snap-ins to work, you either have to image a machine that has snap-ins associated with it, or deploy snap-ins using the advanced tasks menu available through the host details page or through the tasks page.
If you go to the FOG web UI and go to tasks, active snap-ins, and you have something listed there, then something should happen for the hosts listed. If nothing is listed there, you have not deployed any snap-ins for any hosts, or they have already run. You can check the c:\fog.log on the clients to see if the snap-ins ran.
Also, snap-ins run in the background and you cannot really do any user input while they run. Sometimes I get the interactive services detector prompt and can switch to the snap-in, but other times I know the snap-in is waiting on me to push a button but I cannot see the window.
So snap-ins need to be completely silent installs to run correct.
If you are creating registry files, you need to specify the path and program to run them with and make sure to specify the silent install option.
[CODE]regedit.exe /s regchanges.reg[/CODE]
[QUOTE]To get the snap-ins to work, you either have to image a machine that has snap-ins associated with it, or deploy snap-ins using the advanced tasks menu available through the host details page or through the tasks page.[/QUOTE]
I suspect this was the step I’m missing.
You’ll have to forgive my late reply I’ve not been in work since the post and now the domain is down so doing much like this is quite cobbled together.
Do the snapins add anything to the log files to say if they’re having problems and what they might be or is the only entry along the lines of “snapin completed”. Will the log tell me if it didn’t have enough privilegesto run the snapin for example.
How might I test the connection to make sure fogService is checking in properly.
finally, I see a snapin I made a long time ago I’ve put the full path to run it; “C:\Windows\System32\msiexec.exe” to run an MSI. Does it have to be a full path or could I just have put msiexec.exe.
Likewise do I need the exe file or will what works in win key + R run too. eg. “c:\windows\system32\regedt32.exe” changes to just “regedit”
Searching for a specific snapin, then going back to listing all snapins will now show all the snapins. I don’t know what that problem was about…
I get that behavior also. I just search for * and they all show up, and from that point on, they all show up. Wierd…
Snap-ins run in the context of the FOG Service user. Which I believe runs as the system user by default. Snap-ins themselves do not add anything to the c:\fog.log. The snap-in manager may add when a snap-in is executed, but I’m not sure.
While just calling the exe with no path may work now, it’s not the safest approach to take. Try using your system variables if you don’t want to hard code the path. %systemroot%, %comspec%, %windir%, etc.