To accomplish this we use both a postinstall_script and a preuninstall_script in the Munki PkgInfo file for Photo Mechanic.įirst the postinstall_script will get executed after PM is installed by Munki. It also insures that a computer is deactivated when the software is removed so we don’t exceed our license limit and run into activation failures on reinstallation.

I immediately knew I wanted to incorporate the capability into Munki.Īutomating the activation and deactivation as part of the installation and removal of PM through MSC allows us to keep the registration information private as well keeping our staff from having to do it manually. I had no need for the feature at that time and forgot it existed until it came up in a forum post last year. Read on for the details.Ĭamera Bits added the ability to activate, deactivate and query activation status from the command line to Photo Mechanic back in March of 2014 with the release of Build 15419. Thankfully we can programmatically activate and deactivate Photo Mechanic when employees install or uninstall the program via Managed Software Center (MSC). Of course this is an awful practice in regards to securing our paid licenses. In the past we simply emailed the registration information for PM to staff as needed. I have been using PM for almost 17 years and it is an essential part in the workflow of our photographers here at the newspaper.Īs our staff has grown so has the need to automate installations of software. It has unrivaled speed for downloading, sorting and captioning images on deadline. Photo Mechanic (PM) has long been the software of choice for photojournalists worldwide.

Photo Mechanic 5 Serial Number