@george1421, @Wayne-Workman 's response is the correct answer. We already take into account execution policies with our snapin templates.

@adukes40 I will need to remote into a problematic machine to be able to identify exactly what is going wrong. Send me a chat message when you’re available for a remoting session (preferably using teamviewer).

@fry_p have you tried resetting encryption data for that host?

@Wayne-Workman I’ve been kept busy by my studies and patching the auto updating bug that affected many users (more work is still required to prevent it from happening in the future. The hotfix simply bought us 2 years to fix it).

@fry_p Yeah it’s bad. We’re starting to see this bug pop up now. I was hoping it was just a fluke as I am still unsure as what’s causing it.

@Wayne-Workman what is the content of settings.json?

@Albertus from the second log: 2016/12/14 2:33 PM Middleware::Response Invalid security token. This means your client is out of sync with the server. Select the problematic host and hit Reset Encryption Data in the web interface (optionally you can add all the hosts to a group and hit the same button on the group).

@michael_f @Wayne-Workman @Hanz a patch has been developed and verified for this issue. It will be released with 0.11.6 (along with a few other new features) once release candidate testing finishes for the client.

Some clarifications:

Snapins
A snapin is simply a way to get the client to run an executable. So why is there no EXE template? Well on windows .exe can simply be executed as is without a helper program. So no snapin fields have to be set. Imagine snapins like this:

• Open a CMD prompt
• How do you want to perform your action? Is it an EXE? If so you just type MyProgram.exe and it runs. Want to run a batch script? You’d type something like cmd.exe /c MyScript.cmd. The bottom Snapin Command shows the end result of your snapin configuration

Snapin Packs
Now snapins are pretty limited, but that’s what legacy FOG was built with so we kept it for compatibility. In your post you say I generated a “SFX” silent printer installer that’s a work-a-round that snapins forced onto people. And when the new client introduced Linux and Mac support things like the SFX work-a-round were no longer viable as it’s Windows only.

So we came up with a concept being being able to “pack” up multiple files and deploy them using the pre-built snapin system (ergo “Snapin Pack”). I’ll admit we don’t have the best documentation when it comes to things like Snapins and Snapin Packs but it’s community driven documentation. Where people think it lacks, they add to the documentation.

@Wayne-Workman has done an awesome job providing almost all of the snapin pack documentation we have (https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks).

The basic idea: zip up a bunch of files you need, and provide 1 runnable file/script in that zip to handle everything (e.g. a batch script to move all of your printer driver files in place).

You done messed up @Tom-Elliott.

@Tom-Elliott Logout is not “beat the clock”. User tracker’s code has not changed since sometime around 0.10.0.

@Brian-David well this is certainly strange. This is the best theory I can think of:

• Is one of the snapins specifically to blame? You state that this only happens when you run “All Snapins”; from the client perspective this is no different then running them individually. Are you running all of the snapins individually, and this issue is not present then?

If this is not the case let me know, and I can walk you through using the client’s debugger, it should help narrow down the issue pretty quickly.

@tom-langenfeld is this a fresh installation or an upgrade? What operating system is on the server? Is the server a fresh installation of the OS or was the server already responsible for something? We need more information.

@UWPVIOLATOR @x23piracy can you try the following stops on a problematic machine?

• In an administrative CMD, stop the fogservice if it is still running: net stop fogservice
• Download and extract this file anywhere on the machine: PowerDebugger.zip
• Run the Debugger.exe contained in the extracted folder as Administrator
• Type the following commands into the debugger’s prompt (one at a time, and pressing enter after each line)

bus mode server
power restart

The debugger will then schedule the client’s restart process in 60 seconds. Can you let me know if it successfully restarts the machine? If not I’ll need the full output of the Debugger window.

@tom-langenfeld could you try running sudo service apache2 stop ? What happens?

@hancocza

You can browse all the files here: https://build.jbob.io/Client/nightly/02-13-downloadredirect-01/

Here is the MSI: https://build.jbob.io/Client/nightly/02-13-downloadredirect-01/FOGService.msi

@davidedpg10 according to those logs user tracker is working properly and client updated is disabled. (User tracker only logs something when a login or logout event is detected). And client updated will only log something when an update is needed (and client updated is enabled).

As for the JIT message, that happens on every client startup to speed up things like the shutdown prompt’s response time. It does not install the old version of the client.

Could I get the full fog log from this computer? And could you double check on GPO? Generally whenever we see this issue there is a client policy somewhere.

@hancocza let me remote in and debug the issue. The installer had a bug which prevented it from pinning a server over https if port 80 was blocked. This has been fixed in v0.11.14, which will be released with the next server RC.

@mtanigawa if you’re hard coding the credentials in the snapin, there is another option. You can set Snapin Arguments Hidden and put the password in the script’s arguments, that way the password will never be stored on disk, only in RAM for a very brief amount of time.

@kyle.heath you need to fix this error:

1/10/2017 10:30 AM HostnameChanger Logon failure: unknown username or bad password, code = 1326

before anything else. You don’t need to keep on re-capturing or deploying either. Just set up a computer with the client, monitor the fog.log file until you fix your credentials.