Deputy

Concept

When you drag an application program file into the Licenses window, KeyConfigure gives you the option to transform the file into a "keyed" copy (in addition to imposing license control). The keyed copy will not run unless granted a "key" so it can be deployed freely with less vulnerability to piracy. But the original installer for the program creates un-keyed program copies, so deployment of the keyed program copy cannot be done directly using the original installer.

The Deputize 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 supported for Macintosh OS9 and Windows (.exe or .msi) only. Deputizing Mac OS X installers is not supported. If the program can simply be copied from a shared volume or cloned from an image, this may provide a simpler deployment solution.

Deputize Steps

1. Run the original program installer on a computer which has KeyConfigure installed.
2. Drag the program file(s) into the licenses window and select the "Control as Keyed Program" option.
3. Use the Deputize Installer ... item from the File menu to transform the installer and to create a special "installer license" to control it.*
4. Make the deputized installer available for use on your KeyServer client computers.

An installer can only be deputized after the program itself has been keyed, so it is important to follow the steps above in order. If the installer creates a suite of programs, you may want to key several executables under the control of one or more licenses before proceeding to step 3.

Since a deputized installer is itself under the control of the KeyServer as a "keyed installer", the "Deputize Installer..." dialog first requires you to give a name to the installer license that KeyConfigure is about to create. This dialog also requires that you browse to select the installer program for deputizing - or just drag it into the dialog. The programs that the deputized installer will install as "keyed" are inferred from the Licenses window - programs that are under KeyServer's secure control (keyed) when the installer was deputized will be transformed to keyed versions as the deputized installer is run.

Deputizing an installer can take quite a bit longer than keying a program, especially on Windows. 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 - except it is keyed so a connection to KeyServer is required. If the original installer requires that an install code must be entered, the deputized installer will likewise have the same requirement. (You may want to convey this install code information to clients using a "post launch message" attached to the deputized installer program.)

Note: the controlling license for a deputized installer cannot be checked out for portable use.

Related Topics