Deputize an Installer

KeyConfigure supports a "legacy" option to transform a copy of a program into a "keyed" variant so it can be recognized and managed separately from other members of its program family.

A keyed program cannot run unless granted a "key" so in cases where online updaters are not available to revert to an unkeyed version, the keyed copy can be deployed freely with less vulnerability to piracy. But deployment of the keyed program copy cannot be done directly using the original installer since it creates unkeyed program copies.

The "Deputize an Installer ..." item from the File menu lets you transform the original installer so that it will install a keyed program version instead of the original version. Note: deputy is currently only supported for certain installer formats - generally speaking, .exe or .msi on Windows, and .pkg or .mpkg on Mac. In cases where the program can simply be copied from a shared volume or cloned from an image, this method may be simpler than deputizing and installer.

Deputize Steps

*Note: many windows installers consist of a “setup.exe” which simply points to an “.msi” file that does the real work. It is the msi that you need to deputize.

Deputizing an installer can take quite a bit longer than keying a program. This is because KeyConfigure must open all of the installer's compressed files in order to examine all executables that the installer is capable of installing. These executables are then compared with the list of programs which have been keyed on the KeyServer.

When you make the deputized installer available for use on your KeyServer client computers, it will behave just like the original installer. If the original installer requires that an install code must be entered, the deputized installer will likewise have the same requirement.