K2 Client Deployment

Concept

At sites that have a large number of K2 client installs to perform, manually running the client installer on each computer may be impractical. This document references some techniques, tools, and documentation that facilitates large scale deployment.

Note: deployment of the K2 client on file servers (for the purpose of auditing only) is covered in the Server Audits document.

Large scale deployment methods

• K2 client components can be installed as part of a master cloned image for new computers - consult the Cloning document for important cautions and details.
• a general purpose file deployment tool (e.g. SMS) can be configured to install or upgrade the K2 client files and settings - consult the complete File List document, the cloning document, and the OS Details appendix for details concerning client components and settings.
• an "Application server" such as WTS (Windows Terminal Server) or WinFrame may be used to serve out the K2 client along with server hosted application programs - consult the OS Details appendix for WTS support information. Note: the "Add/Remove" programs control panel should be used when installing KeyAccess in order to ensure that "Install mode" is enabled.
• the client installer can be customized with site specific preferences for silent execution when logging onto the network - consult the documentation notes below.

Creating a Customized Windows Client installer

k2clientconfig.exe is a DOS command line utility found in the Installers\Windows Installers\Misc\ folder of the K2 image archive – or click here to download the latest version from the Sassafras web site. Note: you must use the k2clientconfig.exe from the 2007.12.01 image (or better) when customizing the 6.1.3.x client installer.

The example steps below illustrate the use of k2clientconfig to create a "silent" MSI install package that can be used as a Group Policy Object or with a logon script to transparently deploy the K2 client with default settings:

• make a duplicate a copy of the K2Client.exe file and place it in the same folder with the k2clientconfig.exe utility.
• from the DOS command prompt, cd into the directory containing k2clientconfig.exe and the duplicated K2Client.exe
• type the following command line (where <keyserver_host> is either the DNS name or ip address of the KeyServer)
           k2clientconfig -s 3 -h <keyserver_host> K2Client.exe 

Now when you launch the customized K2Client.exe on a client computer with MSI support, it will automatically use the pre-configured KeyServer host address. Further customization options for the client installers (or for the extracted MSI package) are described in the built in command line help (type k2clientconfig.exe) and also in the document k2clientconfigW.html.

In addition to pre-configuring various options for computers supporting MSI, the k2clientconfig.exe utility can also extract the stand-alone MSI install package, KSClient.msi from the K2Client.exe installer:

• to extract the customized MSI component, KSClient.msi, from the installer type the command:
        k2clientconfig -e K2Client.exe

This stand-alone MSI install package can be used as a "Group Policy Object" to automate client deployment. Microsoft's documentation at the following link may be helpful:

           http://support.microsoft.com/kb/302430

One potential problem with using the .msi instead of the .exe is that you will not be able to install a minor upgrade over an existing installation using the .msi (e.g. 6.2.0.1 followed by 6.2.0.2). Instead of simply double-clicking the msi, or running msiexec with just the /i option, you should use the command line:

           msiexec /i KSClient.msi REINSTALL=ALL REINSTALLMODE=vamus

Creating a Customized Mac OS X Client installer

Related Topics