How to create a standalone installation package in Kaspersky Security Center 9

Published on 29 Jan 2020 / In Security & Protection Software

Installation using standalone packages

A standalone package in Kaspersky Security Center is a file that includes the installation files and installation parameters of the product (for example, Kaspersky Endpoint Security). Such a file runs the installation without prompting the user for anything. This allows trusting the users with the installation without fear that they will select the wrong settings. If it is the administrator who installs the product, a standalone package saves time.

Creating a standalone package

If for some reason the incompatible applications cannot be removed using regular tools, the administrator may use Kaspersky Security Center functionality for this purpose:

1--click packages are created from regular installation packages available on the Administration Server. A special wizard is used for this purpose that prompts for the installation parameters.

When the Kaspersky Endpoint Security standalone installation package is created, the wizard will prompt to include the Network Agent, so that the target computer could immediately connect to the Administration Server.

Regardless of the selected product, computers should be moved into the managed category right after the installation. Leaving protected computers in the unassigned category usually does not make much sense.

If it is necessary to modify the default settings of Kaspersky Endpoint Security or select the specific components to be installed, it needs to be done beforehand in the properties of the regular package, before starting the standalone installation package wizard. The parameters of the installation packages are described later in this chapter.

After all the parameters are specified, the wizard generates a setup.exe installation file and places it in the PkgInst subdirectory of the shared folder on the Administration Server. The wizard suggests that the administrator takes one of the following actions:

Open the folder containing the package—for example, to copy it on a flash drive or move it to another shared resource
E-mail users an invitation to run the package—Administration Server starts the default e-mail client and automatically fills in the message subject and body providing a link to the package located in the shared folder; the only thing the administrator has to do is to specify the receivers' addresses
Place a link to the package on a web resource—a text window opens, which contains HTML code of the link to the standalone package that can be added on a web page

Later, the list of created standalone packages can be opened via the shortcut menu of the installation packages repository. You can delete unnecessary packages or send another e-mail message to the users.

Show more
0 Comments sort Sort By