But you should kill first the greenshot.exe because if not it isn't silent.
Greenshot use a binary config file in %APPDATA%. That's a big problem when you want to preconfigre it in a deployment environment. But it's possible to create it with your settings an deploy this file for the end user.
Active setups are a cleaner way to install the config file fo each user as they will automatically run when the user logs on for the first time after they are installed.
Create an directory in your install folder below your install script called ActiveSetup
In your install script include the lines:
;Active setup to copy files to each users profile
$AppName = "Greenshot 0.8.0"
$EXEName = "Greenshot_ActiveSetup.exe"
DirCreate("C:\Temp\ActiveSetup\" & $AppName) ;This location to store the active setup is an example, it can be anywhere all users can access, just rememebr to change it in all locations in the script
FileCopy(@ScriptDir & "\ActiveSetup\" & $EXEName, "C:\Temp\ActiveSetup\" & $AppName & "\" & $EXEName,1)
RegWrite("HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\" & $AppName,"StubPath","REG_EXPAND_SZ",C:\Temp\ActiveSetup\" & $AppName & "\" & $EXEName)
RegWrite("HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\" & $AppName,"Version","REG_SZ","1")
Then write another script call Greenshot_ActiveSetup, with the following lines and copy it into your ActiveSetup folder (remember to keep your config file in the same location as the script when compiling as it will copy the config file into exe.
DirCreate(@AppDataDir & "\Greenshot")
FileInstall( ".\config.dat",@AppDataDir & "\Greenshot\config.dat",1)
I've solved the pr. user setting by deploying the configuration file to the default user profile and created a DOS script that check for the config file when greenshot is loaded by a new user.
The greenshot package is installed with the parameters in the note above this one.
The configuration file is copied to "C:\Users\Default\AppData\Roaming\Greenshot\config.dat".
The DOS script is located in "C:\program files\greenshot\" and named greenshot.cmd
A link to greenshot.cmd is created and put in "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\". Greenshot is then started by the "startup" folder, this is done to run the DOS script checking for the config.dat pr. user.
And that's it !
The installation has only been checked in Windows 7 32x