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).

@AngryScientist that log indicates your client is not authenticated with the server. To fix this, go to the host in the web portal and hit Reset Encryption Data.

@AngryScientist fog.log is found one the host computer (usually C:\fog.log or C:\Program Files (x86)\FOG\fog.log)

@AngryScientist that is the .fog_user.log file, printer adding is done in the main log (fog.log).

@cojohnson 12/14/2016 12:35 PM Middleware::Authentication ERROR: Could not get security token just means the client has never successfully authenticated before. It only receives a token after the first successful authentication.

In general we recommend installing the client IN the image, as the tokens are automatically reset when an imaging task is performed. However, you should never have to continuously reset encryption data, only when you manually install / uninstall the client.

@AngryScientist we need more information. For example, providing the fog.log (or even just the printer manager section) would help. Also a screenshot of the printer configuration on the server would be of help as well.

You can also try using the PrinterManagerHelper (https://github.com/FOGProject/fog-client/releases/download/0.11.7/PrinterManagerHelper.exe). Simply enter your printer configuration into it and hit add. It should provide an error message if there is one.

@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).

Unfortunately I have a very busy schedule for the next couple weeks and limited time to work on internationalization. When I get some free time I’ll post a list of phrases in this thread so people can start translating though it could be a few days.

@dureal99d until 0.11.7 is released (which should be within a day), you can simply delete the Mono.Security.dll file present in the fog-service directory. Then restart the service.

I’ve verified that the issue started with 0.11.5 on mono systems. It’s an issue with a library that I use requesting a specific version of mono to be present. I’ll start working on a patch.

We are currently in the process of adding internationalization support to the client (i.e. all text your end user sees will be in their language). We are looking for people to help with the translations of a small set of phrases the client uses into other languages.

We currently have translations / translators for:

• Basque
• Dutch
• French
• German
• Hungary
• Norwegian
• Spanish (Spain)

If you’re interested in adding an additional language to the client, when you translate, please put the language above the phrases, and leave the phrases in the original ordering and format (basically just copy and paste the phrase list, replacing text), this will help me greatly.

Below is a list of phrases that should be translated:

### SHUTDOWN PROMPT ###
{company} needs to perform maintenance on this computer.
Please save any work and close all programs.
Cancel
Hide
Postpone
Restart Now
Shutdown Now 
Postpone for
X hour(s) Y minute(s) Z second(s)

### NOTIFICATIONS ###
Shutdown Aborted
Shutdown has been aborted
Shutdown Delayed
Shutdown has been delayed for {time}
Shutdown will occur in {time}

You are about to be logged off
You will be logged off if you remain inactive

Installing {snapin name}
Please do not shutdown until this is completed

{snapin name} installed
Installation has finished and is now ready for use

@AngryScientist a snapin is just a way of executing any file, it can be whatever you want. Make something that when run updates the host file(e.g. a batch or powershell script). Then just use the snapin template matching your script type.

@blkspade please upload one of the C:\Program Files (x86)\FOG\settings.json of a problematic host along with its fog.log file.

@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.

@THEMCV , @Wayne-Workman one note about that batch script (or any script for that matter). I would avoid hard coding the path of the files as it can change based on your machine’s architecture. Instead use your scripting language’s command to get its directory.

For batch %~dp0 returns the script’s directory (including the last \). So to re-write wayne’s examples the commands would be:

msiexec.exe /i "%~dp0installer.msi" /quiet

copy "%~dp0your.xml" "C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Profile\your.xml"

@george1421 while I completely agree that the client looks exact like a root kit, the difference is all the client binaries are signed by a trusted certificate authority. All major anti virus software first look to see if a PE binary contains a valid authenticode before performing analysis on it.

@plegrand 0.9.12 should upgrade just fine 0.11.5 (you may have to reset encryption data though). The auto updating protocol is compatible with all versions of the new client (starting with the initial release of 0.7.0).

@michael_f A windows crash would explain it (especially if the disk was in the middle of a write request). I’ll push out a patch to try and address this issue.

@Hanz where did that error log come from? Event viewer? If its from the client’s log please upload the entire log file.

@FlareImp the new client locks itself into the server it was installed with. Either you can make all your servers share the same identity or you can install the new client on first boot up . so one way of doing it would be to have your post download script set the silent installation arguments for the client and when windows boots up have it run that installation command.

Edit: just saw George’s post, his suggestion is correct.