KSC does not start after VM cloning (Keyset does not exist)

[Pcom]

Hello,

We're converting our datacenter from Vmware ESXi to Proxmox. Now it's time to convert our VM with KSC: Win Server 2016 + KSC 13.2.

First step is to change storage controller and disk size using VMware Coverter. Task works, new VM starts but Security Center installed inside does not.
Trying to investigate i found that service "Kaspersky security center administration server" does not start even if is set on "automatic" start. I tried to manually start it but it stops immediately.
So i check on event viewer for errors and I found everytime I try to start the service i have this error:

"Service 'kladminserver' has been stopped due to an error. #1181 (-2146893802) System error 0x80090016 (keyset does not exist)"

 

Any idea about what this means and how to solve?

Don't know if this helps but chatgpt says "This error typically occurs when the cryptographic keys required for the operation of the service are missing or inaccessible. The keyset refers to a set of cryptographic keys that are used for various purposes like encryption and decryption."

Thanks

[ElvinE5]

 

the first thing that could be is that Proxm is not included in the supported platforms (compatibility has not been checked quickly)

https://support.kaspersky.com/KSC/14.2/en-US/255791.htm

 

the second is that KSC also does not support such migration options and any kind of snapshot recovery.

The correct transfer method is to restore the system from a backup taken by the KSC server itself

You just need to set up a new server in your new environment and try restoring it from backup.

https://support.kaspersky.com/KSC/14.2/en-US/236441.htm

 

during such a transfer, make sure that when deploying a new server, its IP, server FQDN, as well as the SQL platform used (MSSQL, MardiDB, Postgres), the database name (what you specified during the first deployment) coincide with the previous ones

otherwise, if the name of the database and platform form differs from the original, the system will not be restored from backup.

and if the IP or FQDN is different (depending on how your agents are connected), client devices will not be able to connect to the restored server... and they will have to be reconnected... separately

 

or if it is not possible or you do not want to restore from a backup, the server can be fully deployed and configured again and reconnect clients to it using the “change administration server” task

Edited September 22, 2023 by ElvinE5