5/12/2015 3:27 PM FOG::SnapinClient Installation returned with code: 1

[Roger Saffle]

trying to push out a vbscritpt. Fog log shows
5/12/2015 3:27 PM FOG::SnapinClient Installation returned with code: 1

any idea what this means?
my snapin is attached.

[url="/_imported_xf_attachments/1/1991_Capture.JPG?:"]Capture.JPG[/url]

[Tom Elliott]

No payment but I mean requesting the ability to do a :runas override

[Roger Saffle]

To pay you or to run snapin as local user? Or both?

[Tom Elliott]

Maybe make this a feature request?

[Roger Saffle]

thanks. I dont mind paying for something if it makes our life easier.
In fact I am working with my school to see how I can make a payment to FOG, since we cannot make a donation. Hopefully we can do that as soon as next school year.

[Wayne Workman]

Look into EMCO MSI builder.

You can make your non-silent installations silent.

However, If you’re going to pay for it, I recommend the enterprise version. IMHO, the lesser versions aren’t worth having.

[Roger Saffle]

No domain. I just wish I could get fog to run a snapin as the logged in user. Would solve problems with some of my snapins that need user intervention. Not everything has a silent install.

[Wayne Workman]

If they are domain-connected clients, you can use powershell.

Alternatively, figure out how to install your fonts using the way FOG executes snapins.

[Roger Saffle]

Thanks.
I think its the problem again with fog doing things as system instead of as a user. I was trying to get my vbscript to install fonts. We have a program called fonts for teachers. If i have fog put a bat file in the windows startup folder, the fonts install fine on next boot. Guess that close but would like them to install strait from the snappin.

[quote=“Wayne Workman, post: 47233, member: 28155”]returning 0 means no errors.
returning 1 means errors.

Check with something else, first. Like a batch file or an MSI. confirm tthe snapin feature is working for you, first.

If it is, troubleshoot your vb-script.[/quote]

[Wayne Workman]

returning 0 means no errors.
returning 1 means errors.

Check with something else, first. Like a batch file or an MSI. confirm tthe snapin feature is working for you, first.

If it is, troubleshoot your vb-script.