Remote installation of applications using Kaspersky Security Center
A large number of articles describes how to remotely install an application on several computers in a domain network (AD). But many are faced with the problem of finding or creating suitable Windows Installer (MSI) installation packages.
Really. In order to install to all users of the group, for example, FireFox, you must either build the MSI package yourself ( described in some detail in this article ), or download the appropriate one on the appropriate site . The only thing, in the first case - in actual fact - is the task, not quite trivial, and in the second - we get the package configured in such a way as its creator wanted, and in fact modified (questionable, but minus).
If your organization uses Kaspersky Lab products as anti-virus protection - and you use an administration server - you can install programs remotely even from * .exe packages using keys - to manage installation settings.
')
Most programs can be installed in “silent” mode, for example, there is a table with a large number of frequently used programs, and the supported parameters are transmitted during installation. Also here you can find a large number of transmitted installation parameters.
Administration Panel - gives full controllability (during installation) comparable to administration through Win-server group policies, and for me it’s even more convenient - less of any tricks - less likely to make a mistake;)
If you assign manual installation of programs, or all users use the same set of programs, you can skip this section, but if you have different software installed in different departments, you can assign different groups to these departments for which different tasks will be used .
User groups in KSC are divided - similar to the structure used in AD - directories and sub directories. Tasks and policies used in parent groups are applied to all child groups.
Thus, for example, all users of the company can install FireFox and Chrome, and only Photoshop designers.
1) To create an installation package, go to the “Installation packages” subsection of the “Storage” section in the KSC control panel. There we will see a list of created IP, the ability to create a new one, as well as edit or delete an existing one.
A new installation package is created simply: you specify its name (how it will be displayed in the KSC), select “UI for the program specified by the user”, specify let it to the program (exe, bat, cmd, msi) and specify the launch parameters (silent keys installation).
Then the specified package can be used for installation on remote computers.
2) Now we need to create a task to install the created package. If you have previously worked with KSC, or with its previous analogue Adminkit. That process of creating a task is not difficult for you.
You can either create a task by going to the folder of the corresponding group, and going to the tab “Tasks” - create a new task. Or Go to the section “Tasks for specific computers” - create a new task.
We set the name of the created task, and select the type of task “Remote installation of the program”.
Select the program we want to install, which groups of users this task will be assigned to, and specify the user who is allowed to install the software on all of the computers used (usually the domain administrator).
The only thing in terms of settings is that we limit ourselves only to the parameters that the developer permits when installing the program, and we are unlikely to configure the proxy server in the browser via the command line. But here we go to the aid of the already standard group policy AD. After all, usually alternative browsers use system proxy settings, and we can assign them to the right users via AD. ;)
Really. In order to install to all users of the group, for example, FireFox, you must either build the MSI package yourself ( described in some detail in this article ), or download the appropriate one on the appropriate site . The only thing, in the first case - in actual fact - is the task, not quite trivial, and in the second - we get the package configured in such a way as its creator wanted, and in fact modified (questionable, but minus).
If your organization uses Kaspersky Lab products as anti-virus protection - and you use an administration server - you can install programs remotely even from * .exe packages using keys - to manage installation settings.
')
Silent installation options
Most programs can be installed in “silent” mode, for example, there is a table with a large number of frequently used programs, and the supported parameters are transmitted during installation. Also here you can find a large number of transmitted installation parameters.
So we need to:
- Download the standard distribution of the program you need from the developer’s site (or where you usually get them from)
- Find on the Internet which keys of the “silent” installation are supported by the program used.
- Install the program on a user PC using Kaspersky Security Center
Administration Panel - gives full controllability (during installation) comparable to administration through Win-server group policies, and for me it’s even more convenient - less of any tricks - less likely to make a mistake;)
If you assign manual installation of programs, or all users use the same set of programs, you can skip this section, but if you have different software installed in different departments, you can assign different groups to these departments for which different tasks will be used .
User groups in KSC are divided - similar to the structure used in AD - directories and sub directories. Tasks and policies used in parent groups are applied to all child groups.
Thus, for example, all users of the company can install FireFox and Chrome, and only Photoshop designers.
So let's start:
1) To create an installation package, go to the “Installation packages” subsection of the “Storage” section in the KSC control panel. There we will see a list of created IP, the ability to create a new one, as well as edit or delete an existing one.
A new installation package is created simply: you specify its name (how it will be displayed in the KSC), select “UI for the program specified by the user”, specify let it to the program (exe, bat, cmd, msi) and specify the launch parameters (silent keys installation).
Then the specified package can be used for installation on remote computers.
2) Now we need to create a task to install the created package. If you have previously worked with KSC, or with its previous analogue Adminkit. That process of creating a task is not difficult for you.
You can either create a task by going to the folder of the corresponding group, and going to the tab “Tasks” - create a new task. Or Go to the section “Tasks for specific computers” - create a new task.
We set the name of the created task, and select the type of task “Remote installation of the program”.
Select the program we want to install, which groups of users this task will be assigned to, and specify the user who is allowed to install the software on all of the computers used (usually the domain administrator).
The only thing in terms of settings is that we limit ourselves only to the parameters that the developer permits when installing the program, and we are unlikely to configure the proxy server in the browser via the command line. But here we go to the aid of the already standard group policy AD. After all, usually alternative browsers use system proxy settings, and we can assign them to the right users via AD. ;)
Source: https://habr.com/ru/post/139420/
All Articles