Migration with virtual Administration Servers

If you have virtual Administration Servers in your existing Kaspersky Security Center on-premises infrastructure, you cannot migrate from Kaspersky Security Center on-premises to Kaspersky Security Center Cloud Console by using the Migration wizard. Also, you will be able to migrate only your customers' devices. You will have to create policies, tasks, and reports manually.

You can perform one of the following migration scenarios:

• By moving your client devices from virtual Administration Servers to a primary Administration Server
• By performing manual migration from virtual Administration Servers

Scenario: Migration with virtual Administration Servers by moving devices

To perform the migration from Kaspersky Security Center Web Console running on-premises to Kaspersky Security Center Cloud Console, you can move your devices from virtual Administration Servers to a primary Administration Server.

Prerequisites

Before migration, you must perform a number of actions, including upgrading Administration Server running on-premises to version 12 or later and upgrading the managed applications to versions supported by Kaspersky Security Center Cloud Console.

Migration scenario

The scenario proceeds in stages:

1. Creating an administration group for each of your virtual Administration Servers

   You create the group in your Kaspersky Security Center running on-premises.

2. Moving your customers' devices

   In Kaspersky Security Center running on-premises, move your customers' devices from each virtual Administration Server to the respective administration group created at the previous stage.

3. Migration

   Perform migration as described for the network without a hierarchy of Administration Servers.

4. Moving devices under management of virtual Administration Servers (optional step)

   If you want to manage your customers through virtual Administration Servers, move the devices from the administration groups under management of virtual Administration Servers.

5. Creating policies, tasks, and reports

   Create policies, tasks, and reports as required.

Results

Upon finishing with the migration, you can make sure that it was successful:

• Network Agent is re-installed on all managed devices.
• All devices are managed through Kaspersky Security Center Cloud Console.
• All object settings that were effective before migration are preserved.

Scenario: Manual migration with virtual Administration Servers

You can migrate from Kaspersky Security Center Web Console running on-premises to Kaspersky Security Center Cloud Console manually.

Prerequisites

Before migration, you must perform a number of actions, including upgrading Administration Server running on-premises to version 12 or later and upgrading the managed applications to versions supported by Kaspersky Security Center Cloud Console.

Migration scenario

The scenario proceeds in stages:

1. Creating an administration group for each of your virtual Administration Servers

   In Kaspersky Security Center Cloud Console, create an administration group that corresponds to each of your virtual Administration Servers.

2. Creating a stand-alone installation package for Network Agent

   Create a stand-alone installation package for Network Agent. During creation, specify the administration group that you created at the previous stage. This means that you must create an individual stand-alone installation package for each administration group.

   This stage occurs in your Kaspersky Security Center Cloud Console.

3. Downloading the stand-alone installation packages

   Download the stand-alone installation packages that you created at the previous stage. This stage occurs in your Kaspersky Security Center Cloud Console.

4. Creating an archive with each stand-alone installation package

   Available archive types are: ZIP, CAB, TAR, or TAR.GZ.

5. Creating custom installation packages for Network Agent

   Create custom installation packages for Network Agent. During creation, use archives that you created at the previous stage.

   This stage occurs in your Kaspersky Security Center running on-premises.

6. Creating remote installation tasks

   Create remote installation tasks to install Network Agent from the created custom installation packages.

   When creating a task, specify a corresponding administration group.

   This stage occurs in your Kaspersky Security Center running on-premises.

7. Running the created remote installation tasks

   Network Agents are updated. The Kaspersky Security Center Cloud Console Administration Server takes over the management of them.

   All devices are migrated to Kaspersky Security Center Cloud Console and are placed in administration groups that were specified when you created stand-alone installation packages for Network Agent.

8. Moving devices under management of virtual Administration Servers (optional step)

   If you want to manage your customers through virtual Administration Servers, move the devices from the administration groups under management of virtual Administration Servers.

9. Creating policies, tasks, and reports

   Create policies, tasks, and reports as required.

Results

Upon finishing with the migration, you can make sure that it was successful:

• Network Agent is re-installed on all managed devices.
• All devices are managed through Kaspersky Security Center Cloud Console.

  All object settings that were effective before migration are preserved.

Scenario: Moving devices from administration groups under management of virtual Servers

You may want to manage your customers through virtual Administration Servers. If you migrated devices and other items from Kaspersky Security Center on-premises to Kaspersky Security Center Cloud Console, the devices are located in administration groups. To manage the customers' devices through virtual Administration Servers, you must move the devices from the administration groups under the management of virtual Administration Servers.

Prerequisites

You have created a virtual Administration Server for each of your customers.

All devices of each customer are located in an individual administration group.

Stages

The scenario proceeds in stages:

1. Creating a stand-alone installation package for Network Agent

   Switch to each of the created virtual Administration Server, then create a stand-alone installation package for Network Agent. You can switch Administration Servers in the main menu by clicking the chevron icon () to the right of the current Administration Server name, and then selecting the required Administration Server.

2. Downloading the stand-alone installation packages

   Download the stand-alone installation packages that you created at the previous stage.

3. Create an archive with each stand-alone installation package

   Available archive types are: ZIP, CAB, TAR, or TAR.GZ.

4. Creating custom installation packages for Network Agent

   Create custom installation packages for Network Agent. During creation, use archives that you created at the previous stage.

   This stage occurs on the primary Administration Server.

5. Creating remote installation tasks

   Create remote installation tasks to install Network Agent from the created custom installation packages.

   When creating a task, specify a corresponding administration group.

   This stage occurs on the primary Administration Server.

6. Run the created remote installation tasks

   Network Agents are updated. The devices are moved under management of virtual Administration Servers.

7. Creating policies, tasks, and reports

   Create policies, tasks, and reports as required.

Results

You can now manage the migrated customers' devices by using virtual Administration Servers.