Migration of virtual appliance, changing licence and IP address

[VLSV 0]

Hello.

Currently I am using ESMC (virtual machine) which is located in diffrent location, with diffrent IP address - we are sharing one ESMC, diffrent networks, diffrent devices.
I want to create independent instance of ESMC (also virtual). My idea is to copy the virtual machine, change IP address and cut out devices from diffrent location.

I am not sure if that will work and is possible, but after copying the virtual machine and hosting it in our network I will create new policy in old server, which will point agents to new server (with new IP address).

I want to ensure myself that this solution will work. If there is a better way I would be grateful for help.

Of course we will have two diffrent licenses for each server.

Edited June 9, 2021 by VLSV
more info

[Marcos 5,271]

Do you want to keep the data for clients that will be moved to the new EP server? If so, following this KB should do the trick (haven't tried it myself so please wait until someone else from ESET confirms it here):

https://help.eset.com/protect_install/80/en-US/migrated_database_same_ip.html

After migration, just delete machines from server 1 that won't be reported to server 1 after migration and vice-versa.

[VLSV 0]

Yes, I want to keep data, but it looks like this:

- network A in location 1 (class 192.0.0.0), currently ESMC is here, 200 devices
- network B in location 2 (class 10.0.0.0), using ESMC in location 1, also 200 devices
Locations are directly connected and communicate both ways.

Now I want to copy whole ESMC, run it in my network with IP address (network B, class 10.X.X.X), but only with my devices (from network B). And my plan after cloning ESMC and changing IP address is to create policy in "old ESMC" for all agents created for devices in network B, to simply point "new" server and then cut out devices which belong to network A.

Edited June 11, 2021 by VLSV