Deploying GreenShot screen capture software with SCCM 2012

GreenshotA colleague of mine asked if i could make a handy screen capture tool available to our users. I said ‘Sure – piece of cake!’. Well it was for the most part, aside from the installer loading the website post install.

I will document how i successfully completed the deployment of this software to users who opted to install it via Software Catalog website.

Getting the software

The first thing i tried to do is use the packaged installer they provide (an INNO installer package) however there really was no way to remove the website from loading post install. Instead i decided to use the zip version of the software.

Download the latest ZIP package of the software:

Preparing the package

The source files

Extract the files to your deployment source location. I use the following directory structure:

— \Server
—- \SoftwareSource
—— \Greenshot
——–\Greenshot1.1.7.17      <— This is where i keep the installation scripts/config file
———-\Greenshot                 <— This is where i extract the source files

The config file

I pre-configure and deploy the file greenshot-fixed.ini so that users can’t override the settings. The settings i put in it are to simply disable automatic updates and to show the Tray icon. Source code is below:


The install/uninstall scripts

Below are the installation and un-installation scripts i use to install the software. To update the script for the next available version, you simply update the log file name.


StartupShortcut.vbs – The correct way to create a shortcut

To Uninstall the software i use the below script


To install the software, you simply run the Install_greenshot.bat file, with elevated permissions on the client PC. Likewise to uninstall you do the same with the Uninstall script.

Supported deployment methods:

  • SCCM Deployment – I deploy this software as an application to my users as an Available app. They choose to install it via the Software Catalog.
    The Application is configured with the above install and uninstall scripts. The detection method i use (to determine the software is installed) is the version of file %programfiles%\Greenshot\greenshot.exe to be exactly
  • GPO Startup Script – This will work as a startup script installation, however i would modify it by adding two lines to the code. The very first line of the code should say:
    IF EXIST "%ProgramFiles%\Greenshot\Greenshot.exe" GOTO END
    The very last line of the code should say:

    What this will do is skip the installation every time they boot up, if its already present. If you were updating versions you would remove this line for the new version (or write a clever bit of script to check the file version, or to keep things copy a blank text file for the current version to the program files folder, and simply copy that across with the install. That way if the file is there(greenshot1.1.7.17.txt), then the latest version is installed.

  • Other deployment solution – generally the SCCM method would work, but have not tested it.
  • Manual install – Right click on install, and select Run As Administrator.


Couple of things i would note about the script:

  • Its a simple script written in BATCH to help others use/modify it easily. Yes it could be neater if written in Powershell but i chose to do it this way for others
  • The script checks that .Net4 is installed, and if so will NGEN the two files. I didnt add any checking to see if .Net2/3/3.5 were installed and find their ngen paths as its a fair amount of code in BATCH so i decided to use the .Net4 which i know all my clients have installed.
  • If you think its great software – then donate to them for their wonderful work. I personally did not want the website to load on my PC’s so i wrote this script. If you dont mind then you can use the INNO setup file.


2 thoughts on “Deploying GreenShot screen capture software with SCCM 2012”

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

QR Code Business Card
%d bloggers like this: