Snapin not working properly

[Olduser]

Tom,
I have upgraded my fog to latest 1.3.0 RC37. I installed FOG client on Dell790 pc. I Created snapin. It is just batch file and should copy 2 files from network drive and copy in to c:\temp dir. I manually tested the batch script and it is working fine. Active task showed Startin to Queuedin. Sometime FOG_SNAPIN_PATH will list the file, other time I do not see it. I get message on task bar “Please do not shutdown computer…” I have attached snapin screenshot. Fog Client is 11.7 .

What Am i doing wrong?

Thanks,

Olduser

[Joe Schmitt]

@Olduser please check out the Snapin Template drop down. Simply select Batch Script and all of the fields will be taken care of for you (minus the file of course). Normal snapins do not use [FOG_SNAPIN_PATH] as there is nothing to extract.

[Olduser]

Joe & Tom,

Thank you for your reply. OK. I changed my snapin as you suggested but my script file did not show up under C:\Program file\FOG\tmp folder. I re-image this dell790 and tried snapin again. This time script file was listed in C:\Program file\FOG\tmp folder. Then I realized I made some mistake in batch file and corrected batch file and tried to snapin again but this time script was not listed under C:\Program file\FOG\tmp. Active tasks had nothing in it. The client machine had a message “Installing copyuap/bat file” Do not shutdown this computer " I “reset Encryption Data” before snap, still I do not see the file. Snapin currently showing ‘Checked in’. I waited almost 15 minutes still no luck.

olduser

[Olduser]

Joe& TOm,

I have also checked fog log from snapin client.This is what it says:

---------------------------------SnapinClient---------------------------------

12/20/2016 1:12 PM Client-Info Client Version: 0.11.7
12/20/2016 1:12 PM Client-Info Client OS: Windows
12/20/2016 1:12 PM Client-Info Server Version: 1.3.0-RC-37
12/20/2016 1:12 PM Middleware::Response Success
12/20/2016 1:12 PM SnapinClient Snapin Found:
12/20/2016 1:12 PM SnapinClient ID: 161
12/20/2016 1:12 PM SnapinClient Name: copyuap
12/20/2016 1:12 PM SnapinClient Created: 2016-12-20 18:11:53
12/20/2016 1:12 PM SnapinClient Action:
12/20/2016 1:12 PM SnapinClient Pack: False
12/20/2016 1:12 PM SnapinClient Hide: True
12/20/2016 1:12 PM SnapinClient Server:
12/20/2016 1:12 PM SnapinClient TimeOut: 0
12/20/2016 1:12 PM Middleware::Communication Download: http://10.106.12.197/fog/service/snapins.file.php?mac=18:03:73:E6:62:43||00:00:00:00:00:00:00:E0&taskid=161
12/20/2016 1:12 PM SnapinClient C:\Program Files\FOG\tmp\copyuap.bat
12/20/2016 1:12 PM Bus {
“self”: true,
“channel”: “Notification”,
“data”: “{\r\n “title”: “Installing copyuap”,\r\n “message”: “Please do not shutdown until this is completed”\r\n}”
}
12/20/2016 1:12 PM Bus Emmiting message on channel: Notification
12/20/2016 1:12 PM SnapinClient Starting snapin…
12/20/2016 1:12 PM SnapinClient Snapin finished
12/20/2016 1:12 PM SnapinClient Return Code: 1
12/20/2016 1:12 PM Bus {
“self”: true,
“channel”: “Notification”,
“data”: “{\r\n “title”: “copyuap Installed”,\r\n “message”: “Installation has finished and is now ready for use”\r\n}”
}
12/20/2016 1:12 PM Bus Emmiting message on channel: Notification
12/20/2016 1:12 PM Middleware::Communication URL: http://10.106.12.197/fog/service/snapins.checkin.php?taskid=161&exitcode=1&mac=18:03:73:E6:62:43||00:00:00:00:00:00:00:E0&newService&json

As you can see, snapin occured but I donot see the file.

[Joe Schmitt]

@Olduser the log indicates the batch script ran, and you stated:

copy 2 files from network drive

Remember that snapins run as SYSTEM. You have to configured your network shares to allow SYSTEM access to it (often called anonymous read), since SYSTEM is not technically a domain user or any other type of user you would have given read access to. Often what people do is make 1 folder in the share anonymous read and use that, OR use snapin packs to deploy the files and skip the network share altogether.

[Olduser]

Joe,

I gave ‘anonymous’ logon’ access to read & write on this file. I was able to see this file in ‘C:\Program Files\FOG\tmp’ folder but not now. I am not sure if this permission is correct or not. I have attached screen shot of security tab.

[Joe Schmitt]

@Olduser the network share must be configured for anonymous read access, not the snapin file, because the unauthenticated SYSTEM account executing your batch script must have rights to read your restricted share.

[Wayne Workman]

This is what Joe is talking about. Took me a while to figure it out when I started having FOG based scripts start accessing network resources. So these pictures should help you not waste hours on it.

[Olduser]

Wayne & Joe,

I have shared my batch script with Anonymous & Everyone users with read only access. This is how I did it. I went Admin Tools–>Computer Management -->Share Folder and created new share and added Anonymous & Everyone with Read access for this batch file. Once I submit the snapin client computer displayed “Testsnap Installed and installation has finished and now is ready for use”. But I went to C:\Program Files\FOG\tmp folder no files listed. I searched it on C drive for that folder but nothing was found. I have attached screenshot for File sharing. I checked the FOG log. Snapin client there were no error. .

Thanks,
olduser

[Olduser]

Wayne & Joe,

I tried this snap in again with “Snapin Run With Argument”=/i instead of default /c . I saw the file was uploaded.

Thanks,

Olduser

[Joe Schmitt]

@Olduser /c is the correct argument. C:\Program Files\FOG\tmp is a temporary folder, as soon as the client is done processing your batch script, it gets deleted.

[Wayne Workman]

@Olduser use the advanced sharing area to do the sharing please. It’s exactly as shown in the screenshots.

[Olduser]

Joe-Schmitt & Wayne

Thank you for the replay. I did not know that batch script file gets deleted. Just few more questions.
(1) Do I have to select ‘Reset Encryption Data’ on host because once I reset encryption data, the snapin works quickly.
(2) Can I combine ‘/i and /c’ for Snapin Run With Argument? I am using Normal Snapin.
(3) What arguments should be for ‘Snapin Arguments’? I put /qn. Is this correct? I could not find these arguments value.

Thanks,

Oldusers

[Wayne Workman]

@Olduser said in Snapin not working properly:

(1) Do I have to select ‘Reset Encryption Data’ on host because once I reset encryption data, the snapin works quickly.

That only seldom needs done, it’s for when the encryption between the server and host gets screwed up. The intention is for the encryption to not auto-heal thus putting the admin in charge. Because if it auto-healed this would be a vulnerability that could be exploited.

As a rule of thumb though, before I do anything concerning a single host or large groups in fog, I reset the encryption on that host/group prior to deploying my work. This seems to make things go a lot more smoothly but it might not be best practice. Maybe the @Senior-Developers can weigh in on why we need to reset encryption so often.

(2) Can I combine ‘/i and /c’ for Snapin Run With Argument? I am using Normal Snapin.

Try it first. At the bottom of the snapin area, you’ll see the sanpin command. If you take your snapin file and put it in a directory on your computer, and then cd from an elevated command prompt to that directory, and then run this snapin command, it will run just as the FOG Client would run it, minus running as the SYSTEM user.

(3) What arguments should be for ‘Snapin Arguments’? I put /qn. Is this correct? I could not find these arguments value.

Whatever you need them to be. For instance, with Smartboard Drivers and SmartNotebook you can pass the license key as an argument. For Faronics Insight you can pass the channel number. For an old typing program called MicroType you can pass the server address. You are not limited in what you can pass or how many things. Fog will use what you put in there, but if it’ll work or not with the file your pushing is entirely dependent on the exact thing your pushing. Read about deployment strategies on the vendor’s site and look for examples. Also, any error codes in the C:\fog.log file after a snapin runs is not an error from FOG or the FOG Client, the error code is from the program you ran with snapins.

Does this make sense? Feel free to ask more questions.