Deployment schema for on-premises solution and slave servers
Deploy Kaspersky Security Integration with Autotask based on this schema if you use an on-premises version of a Kaspersky solution—Kaspersky Security Center—and if you use slave Administration Servers in your managed company infrastructure.
The components of Kaspersky Security Integration with Autotask are shown as orange rectangles in the following figure.
Deployment schema for on-premises solution and slave servers
The following list describes deployment prerequisites and data flow:
- One or more Administration Servers are used in the client's infrastructure. These Administration Servers are slave Administration Servers relative to the Administration Server that is installed in the MSP infrastructure. The Administration Server installed in the MSP infrastructure is the master Administration Server. You can use this type of deployment to decrease load on your master Administration Server.
- Kaspersky Security Integration Service for MSP must be installed on the computer on which the slave Administration Server is installed in the client's infrastructure.
- Kaspersky Security Integration Tool for MSP must be installed on the computer on which either Administration Console or the master Administration Server is installed and deployed.
- On your slave Administration Server, virtual servers must be created for each of the managed accounts. These virtual servers are then mapped to Autotask accounts, allowing you to integrate Kaspersky Security Center and Autotask.
- In your managed environment, you may have many different Kaspersky programs installed. Data on the number of programs is used by Kaspersky Security Integration with Autotask for automatic billing. Events and computer status changes sent from Kaspersky programs to Kaspersky Security Center are received by Kaspersky Security Integration Service for MSP and tickets are created based on them.