LANSA runtime Licensing problem with VM's

[LANSAfolks]

Hi Guys,
I wonder if this is an issue that other LANSA folks face, using VM's? It causes an unacceptable downtime when it happens.

Say you have 5 development servers, all of which are VM's. Residing in a hybrid Cloud environment. Developers compile and test changes on these. All 5 VM's are all licensed for runtime (to allow for developers to test) and use a central development license server with an adequate amount of development seats.

The issue we face is that these VM's can migrate to other Host Servers and whenever that happens, it breaks LANSA runtime licensing. In our case we have over 40 Host servers in this cluster. It's impossible for us to babysit these VM's and stop their migrations. LANSA runtime licensing is quite restrictive and in many ways obsolete, when it comes to handling such large environments. Are other LANSA folks facing the similar issues? How are you managing this?

[Dino]

What version/epc of LANSA runtime licensing?

[LANSAfolks]

We are using V13SP2 EPC133200, V14SP2 EPC142040 without the new licensing implementation EPC and V15 too with EPC140030.