Migrating from Kaspersky Security Center Cloud Console to Kaspersky Security Center running on-premises

August 19, 2024

ID 272560

This section describes the prerequisites and required steps to migrate from Kaspersky Security Center Cloud Console to Kaspersky Security Center running on-premises. You migrate to Kaspersky Security Center through backing up your Kaspersky Security Center Cloud Console data and further data restoration to Kaspersky Security Center.

Prerequisites and preparation

Before you begin, make sure that you have the following:

  • Commercial workspace of Kaspersky Security Center Cloud Console.
  • A backup of Kaspersky Security Center Cloud Console data. Please contact Kaspersky Technical Support to request and obtain a backup of your workspace. A backup consists of two files—hostedinst_<instance_ID> and hostedksc0_<instance_ID>. Ensure that the files have the BACPAC extension. If they do not, rename the files, and then type the extension manually. The files must have the following names: hostedinst_<instance_ID>.bacpac and hostedksc0_<instance_ID>.bacpac.
  • Two folders with data: hostedinst_<instance_ID> and hostedKSC0A_<instance_ID>. Please contact Kaspersky Technical Support to request and obtain the folders.
  • Installation files of Kaspersky Security Center and Kaspersky Security Center Cloud Console. Please contact Kaspersky Technical Support to request and obtain the installation files of the required versions.
  • Web plug-ins for the security applications. You can download the required installation files from the Kaspersky website.
  • A virtual machine with the following requirements:
    • Microsoft SQL Server and Microsoft Management Studio installed on the machine.
    • Minimum available disk space: 200 GB. The disk space must be divided into the following disks:
      • Disk С: 60 GB
      • Disk F: 10 GB
      • Disk G: 100 GB
    • The virtual machine is located in the DMZ. Alternatively, on the virtual machine, open the ports required for HDS.

Migration instructions

To migrate from Kaspersky Security Center Cloud Console to Kaspersky Security Center running on-premises:

  1. On the created virtual machine, copy folder hostedinst_<instance_ID> to disk F.
  2. Open the hostedinst_<instance_ID>/1093, and then check if the folder contains the .working folder. If the .working folder does not exist, create it manually.
  3. On the created virtual machine, copy the folder hostedKSC0A_<instance_ID> to disk G.
  4. Open the hostedKSC0A_<instance_ID>/1093, and then check if the folder contains the .working folder. If the .working folder does not exist, create it manually.
  5. Create two configuration files—fileshostedinst.cfg and hostedksc0.cfg, and then place them on disk C:
    • Example of the fileshostedinst.cfg file:

      KSCH_UNATT_HOSTED_TYPE="2"

      KLSRV_UNATT_DBMS_TYPE="sqlserver"

      KLSRV_UNATT_DBMS_INSTANCE=".\sqlexpress"

      KLSRV_UNATT_DBMS_PORT="1433"

      KLSRV_UNATT_DB_NAME="hostedinst_1866a923c58d4cd2a4199acc375d0028"

      KLSRV_UNATT_DBMS_LOGIN="DB_user"

      KLSRV_UNATT_DBMS_PASSWORD="DB_password"

      KSCH_UNATT_DATASTORAGE_DIR="F:\hostedinst_1866a923c58d4cd2a4199acc375d0028\"

    • Example of the hostedksc0.cfg file:

      KSCH_UNATT_HOSTED_TYPE="1"

      KLSRV_UNATT_DBMS_TYPE="sqlserver"

      KLSRV_UNATT_DBMS_INSTANCE=".\sqlexpress"

      KLSRV_UNATT_DBMS_PORT="1433"

      KLSRV_UNATT_DB_NAME="hostedksc0_8c6b92dea60e4a00a355666f2730ad41"

      KLSRV_UNATT_DBMS_LOGIN="DB_user"

      KLSRV_UNATT_DBMS_PASSWORD="DB_password"

      KSCH_UNATT_DATASTORAGE_DIR="G:\hostedksc0_8c6b92dea60e4a00a355666f2730ad41\"

  6. On the virtual machine, install Kaspersky Security Center by running KSCHosted.msi.
  7. Open Microsoft Management Studio.
  8. Under the virtual machine name, right-click the Databases folder, and then select Import Data-tier Application.
  9. Select and then import the hostedinst_<instance_ID>.bacpac and hostedksc0_<instance_ID>.bacpac files. Ensure that the imported databases appear in the Databases folder.
  10. Open the DBMS properties window, go to the Security page, and then ensure that the SQL Server and Windows Authentication mode option is selected.
  11. Add a database user by using the following SQL queries:
    • SQL query for adding a user into the master branch:

      DECLARE @Username NVARCHAR(50)

      DECLARE @Password NVARCHAR(50)

      SET @Username = N'DB_user'

      SET @Password = N'DB_password'

      DECLARE @SqlCommand NVARCHAR(MAX)

      IF NOT EXISTS (SELECT name FROM sys.sql_logins WHERE name = @Username)

      BEGIN

      SET @SqlCommand = 'CREATE LOGIN [' + @Username + '] WITH PASSWORD=''' + @Password + ''''

      PRINT 'Creating Login with command: ' + @SqlCommand

      EXEC(@SqlCommand)

      END

      ELSE

      BEGIN

      SET @SqlCommand = 'ALTER LOGIN [' + @Username + '] WITH PASSWORD=''' + @Password + ''''

      PRINT 'Changing Login password with command: ' + @SqlCommand

      EXEC(@SqlCommand)

      END

      IF NOT EXISTS (SELECT TOP 1 * FROM sys.database_principals WHERE name = '' + @Username + '')

      BEGIN

      SET @SqlCommand = 'CREATE USER [' + @Username + '] FOR LOGIN [' + @Username + ']'

      PRINT 'Creating User with command: ' + @SqlCommand;

      EXEC(@SqlCommand)

      END

    • SQL query for adding a user into the database branch:

      DECLARE @Username NVARCHAR(50)

      SET @Username = N'DB_user'

      DECLARE @SqlCommand NVARCHAR(MAX);

      IF EXISTS (SELECT name FROM sys.database_principals WHERE name = @UserName)

      BEGIN

      SET @SqlCommand = 'DROP USER [' + @UserName + ']'

      EXEC(@SqlCommand)

      END

      IF NOT EXISTS (SELECT TOP 1 * FROM sys.database_principals WHERE name = '' + @Username + '')

      BEGIN

      SET @SqlCommand = 'CREATE USER [' + @Username + '] FOR LOGIN [' + @Username + ']'

      PRINT 'Creating User with command: ' + @SqlCommand;

      EXEC(@SqlCommand)

      END

      ELSE

      PRINT 'User already existed'

      SET @SqlCommand = 'EXEC sp_addrolemember N''db_owner'', ''' + @Username + '''';

      PRINT 'Granted DB Owner rights for User with command: ' + @SqlCommand;

      EXEC(@SqlCommand)

  12. Restart the database service, and then check that you can connect to the database by using the credentials of the created user.
  13. In the Command Prompt, change your current directory to the KSCHosted folder (by default, it is located in C:\Program Files (x86)\Kaspersky Lab\KSCHosted), and then run the following commands:

    klcsctlb2b.exe -attach "C:\hostedinst.cfg" --stp hostedinst_1866a923c58d4cd2a4199acc375d0028 -tl 4-

    klcsctlb2b.exe -attach "C:\hostedksc0.cfg" --stp hostedinst_1866a923c58d4cd2a4199acc375d0028 -tl 4-

  14. Use the installation file to install Kaspersky Security Center Cloud Console on the virtual machine.
  15. Open the MMC-based Administration Console, open the Administration Server properties window, then in the Security section, add an internal user account.
  16. Sign in to Kaspersky Security Center Cloud Console by using the credentials of the added user.
  17. Use the installation files to install web plug-ins for the security applications.
  18. Restart all of the services that relate to hostedinst and hostedksc0. The services have the following prefixes:
    • kladminserver_hostedinst
    • kladminserver_hostedksc0
    • klnagent_hostedinst
    • klnagent_hostedksc0
  19. Sign in to Kaspersky Security Center Cloud Console.

Migrating from Kaspersky Security Center Cloud Console to Kaspersky Security Center running on-premises is completed.

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.