Could you eliminate the prompt that says “An instance of FOG Tray is already running.”? In my organization, it’s common for people to move around between PCs. If multiple people log in to the same PC using Switch User, the subsequent users will all get the error. It confuses people, and I can’t think of any purpose for the message. It seems adequate for duplicate instances to silently fail or write it to the log rather than display an error.
Also, +1 vote for finding a way to handle snapins that are multiple files. A relatively simple way might be this:
Instead of supporting only executable snapins, make it also possible to upload two files: a ZIP of the package and an accompanying script (batch file, VBS, .CMD, etc.) that will execute. The script will be responsible for unzipping the package, running any installers, and doing any other installation tasks.
Also also, I’d vote for making FOG more aggressively check that a snapin installed correctly. If a machine gets shut down or rebooted in the middle of deploying a snapin, it can get stuck as “In Progress” in the FOG console, never fully deploy, and the machine may have a corrupt snapin that only installed halfway. Similarly, if a user is running an application while FOG tries to deploy an update to it, it can fail. Making FOG more intelligently retry to deal with these scenarios would be great.