Solved Snapins not working properly
-
Server
- FOG Version: 1.4.4
- OS: Kubuntu
Client
- Service Version: Smart Installer (11.12)
- OS: Windows 10 1703
Description
Hello,
I currently have been using FOG to deploy to Windows 10 to machines in mulitpile departments and have been able to do so successfully. I would like to try to start using the “Snapins” Feature FOG has to offer to deploy some software we use here at my company. I have not been able to successfully use any of the “snapin features” even somthing as simple as a run a batch script. I am aware that FOG uses the “system” or “root” user to run these files. I will post screenshots of the permissions to the TMP folder where the files are placed when deployed via snapin. I am able to see the files placed in the TMP folder and the fog installer says the program was installed “successfully” but the software was not. Just wondering if it’s a setting on my workstation or something to do with FOG why I am unable to deploy any snapins. It’s as if the file is deployed no matter what template or file type I use by the files are never ran. I’m assuming it has something to do with a permissions issue but I can really use some help on this! Let me know your thoughts! Thanks!
-
@msaglioc99
I would suggest using the following. It works also with Office 2k16. -
I want to install MS Project 2016 @Quazz
-
@msaglioc99 Permission issues would show up in the FOG client log.
That said, not all software can be installed by the SYSTEM user I believe, some require user interaction.
What we really need is to see what you’re actually trying to do.
-
Let’s go the simplest method.
Edit one of your batch scripts.
At the start have it do something like:
echo "Snapin BLAH BLAH beginning installation" > %systemdrive%\fog_snapin_install_snapinname.logAt the end, also have it run:
echo "Snapin BLAH BLAH ending installation" > %systemdrive%\fog_snapin_install_snapinname.logTry deploying the snapin that fails. When it shows as complete, look on that system to see if the log file was generated and has what you expect.
-
@Tom-Elliott
If I manually execute it creates a log file, if I deploy using FOG’s snapin feature a log is generated. Do you have a script that you can send me for a test? Or something you suggest? Something simple ? Just so we can pin point the problem. -
@msaglioc99 So your scripts are creating a log already?
-
@Tom-Elliott said in Snapins not working properly:
e to ask how you know it’s not being executed.
I ask because to know absolutely if it’s being run or not (and it’s running with an expectation the snapin system doesn’t have access to from the client). Can you make your script write to a log file somewhere on the machine. If the log is generated, then you know the script IS or isn’t running absoThe script is not being ran. The log was not generated.
-
@msaglioc99 I have to ask how you know it’s not being executed.
I ask because to know absolutely if it’s being run or not (and it’s running with an expectation the snapin system doesn’t have access to from the client). Can you make your script write to a log file somewhere on the machine. If the log is generated, then you know the script IS or isn’t running absolutely. What the executable being called does is a whole different thing.
-
@Wayne-Workman I am configuring the snapin correctly and followed the example. It works properly, i see the file placed in the TMP folder and FOG gives a message stating that the program was installed or the file was ran but any type of file (exe, msi, bat or any kind of script) is always placed in the folder but never ran/executed. This is why I believe it is a permissions issue.
-
@msaglioc99 This is most likely an issue with how you’re configuring the snapin. Have you looked over the examples here: https://wiki.fogproject.org/wiki/index.php?title=Snapin_Examples
For us to really help you get started with Snapins, we need to know what it is your trying to do with snapins, the files you’re working with, where they are, etc.
-
