Creating custom installation packages

You can use custom installation packages to do the following:

• To install any application (such as a text editor) on a client device, for example, by means of a task.
• To create a stand-alone installation package.

A custom installation package is a folder with a set of files. The source to create a custom installation package is an archive file. The archive file contains a file or files that must be included in the custom installation package. While creating a custom installation package, you can specify command-line parameters, for example, to install the application in silent mode.

If you have an active license key for the Vulnerability and patch management (VAPM) feature, you can convert your default installation settings for the relevant custom installation package and use the values recommended by Kaspersky experts. The settings are automatically converted during the creation of the custom installation package only if the corresponding executable file is included in the Kaspersky database of third-party applications.

To create a custom installation package:

1. Do one of the following:
   • In the main menu, go to Discovery & deployment → Deployment & assignment → Installation packages.
   • In the main menu, go to Operations → Repositories → Installation packages.

   A list of installation packages available on Administration Server is displayed.

2. Click Add.

   The New package wizard starts. Proceed through the wizard by using the Next button.

3. On the first page of the wizard, select Create an installation package from a file.
4. On the next page of the wizard, specify the package name and click the Browse button.

   A standard Windows Open window in your browser opens to let you choose a file to create the installation package.

5. Choose an archive file located on the available disks.

   You can upload a ZIP, CAB, TAR, or TAR.GZ archive file. It is not possible to create an installation package from an SFX (self-extracting archive) file.

   If you want the settings to be converted during the package installation, make sure the Convert settings to recommended values for applications recognized by Kaspersky Security Center after the wizard finishes check box is selected, and then click Next.

   File upload to the Kaspersky Security Center Administration Server starts.

   If you enabled the use of the recommended installation settings, Kaspersky Security Center 14.2 checks whether the executable file is included in the Kaspersky database of third-party applications. If the check is successful, you get a notification informing you that the file is recognized. The settings are converted and the custom installation package is created. No further actions are required. Click the Finish button to close the wizard.

6. On the next page of the wizard, select a file (from the list of files that are extracted from the chosen archive file) and specify the command-line parameters of an executable file.

   You can specify command-line parameters to install the application from the installation package in a silent mode. Specifying command-line parameters is optional.

   The process to create the installation package is started.

   The wizard informs you when the process is finished.

   If the installation package is not created, an appropriate message is displayed.

7. Click the Finish button to close the wizard.

The installation package that you created is downloaded to the Packages subfolder of the Administration Server shared folder. After downloading, the installation package appears in the list of installation packages.

In the list of installation packages available on Administration Server, by clicking the link with the name of a custom installation package, you can:

• View the following properties of an installation package:
  • Name. Custom installation package name.
  • Source. Application vendor name.
  • Application. Application name packed into the custom installation package.
  • Version. Application version.
  • Language. Language of the application packed into the custom installation package.
  • Size (MB). Size of the installation package.
  • Operating system. Type of the operating system for which the installation package is intended.
  • Created. Installation package creation date.
  • Modified. Installation package modification date.
  • Type. Type of the installation package.
• Change the package name and command-line parameters. This feature is available only for packages that are not created on the basis of Kaspersky applications.

If you have converted the package installation settings to the recommended values for the custom package creation process, two additional sections may appear on the Settings tab of the custom installation package properties: Settings and Installation procedure.

The Settings section contains the following properties, shown in a table:

• Name. This column shows the name assigned to an installation parameter.
• Type. This column shows the type of an installation parameter.
• Value. This column shows the type of data defined by an installation parameter (Bool, Filepath, Numeric, Path, or String).

The Installation procedure section contains a table that describes the following properties of the update included in the custom installation package:

• Name. The name of the update.
• Description. The description of the update.
• Source. The source of the update, that is, whether it was released by Microsoft or by a different third-party developer.
• Type. The type of the update, that is, whether it is intended for a driver or an application.
• Category. The Windows Server Update Services (WSUS) category displayed for Microsoft updates (Critical Updates, Definition Updates, Drivers, Feature Packs, Security Updates, Service Packs, Tools, Update Rollups, Updates, or Upgrade).
• Importance level according to MSRC. The importance level of the update defined by Microsoft Security Response Center (MSRC).
• Importance level. The importance level of the update defined by Kaspersky.
• Patch importance level (for patches intended for Kaspersky applications). The importance level of the patch if it is intended for a Kaspersky application.
• Article. The identifier (ID) of the article in the Knowledge Base describing the update.
• Bulletin. The ID of the security bulletin describing the update.
• Not assigned for installation. Displays whether the update has the Not assigned for installation status.
• To be installed. Displays whether the update has the To be installed status.
• Installing. Displays whether the update has the Installing status.
• Installed. Displays whether the update has the Installed status.
• Failed. Displays whether the update has the Failed status.
• Restart is required. Displays whether the update has the Restart is required status.
• Registered. Displays the date and time when the update was registered.
• Installed in interactive mode. Displays whether the update requires interaction with the user during installation.
• Revoked. Displays the date and time when the update was revoked.
• Update approval status. Displays whether the update is approved for installation.
• Revision. Displays the current revision number of the update.
• Update ID. Displays the ID of the update.
• Application version. Displays the version number that the application will be updated to.
• Superseded. Displays other update(s) that can supersede the update.
• Superseding. Displays other update(s) that can be superseded by the update.
• You must accept the terms of the License Agreement. Displays whether the update requires acceptance of the terms of an End User License Agreement (EULA).
• Vendor. Displays the name of the update vendor.
• Application family. Displays the name of the family of applications to which the update belongs.
• Application. Displays the name of the application to which the update belongs.
• Language. Displays the language of the update localization.
• Not assigned for installation (new version). Displays whether the update has the Not assigned for installation (new version) status.
• Requires prerequisites installation. Displays whether the update has the Requires prerequisites installation status.
• Download mode. Displays the mode of the update download.
• Is a patch. Displays whether the update is a patch.
• Not installed. Displays whether the update has the Not installed status.