It is possible to migrate a entitlement key from one Hivemanager NG VA implementation to another?

[ricardo_barron]

We are in the middle of a Hivemanager NG VA implementation. 

One of our implementation teams has used by mistake the entitlement key destined to one site (let's call it Site  implementation into another site (let's call it Site A). Both sites requires a different number of AP. 

On site A we have used: hmva-signed-12.8.0.3-NGVA-2018-04-10-dell.ova

On site B we want to deploy : hmva-signed-12.8.2.2-NGVASEP18-2018-09-19-dell.ova

We want to explore the options we have in order to fix this issue:

1.- Load the right entitlement on site A (which is operational right now) and remove the entitlement key that corresponds to site B in order to install it on that site.

2.- Upgrade the Hivemanager VA on site A from 12.8.0.3 to 12.8.2.2 and move this VA from Site A to site B. Perform a fresh implementation of the VA on site A with the right entitlement key and re-associate the all the implemented APs (bear in mind this implementation is operational right now). 

3.- Open a case with tech support in order to fix the issue.

Please give us your feedback about the right way to fix this issue,

Thanks in advance

[ricardo_barron]

Thank you for the feedback Sam, asI understand TS is the only one qualified to intervene the shell. That's correct?

[samantha_lynn]

For HiveManager Virtual appliances that have a key we need to remove, we'd need to reach the shell of the VA to remove the key from there. You'd want to open a technical support case for this as you'll need a shell password that a technician will have to generate for you.