2 ms·
How do you mean? I've never personally dealt with software that licenses to a network interface (and the idea does seem silly...), so I can't fully comment on
by Alupis 10y ago
How do you mean?
I've never personally dealt with software that licenses to a network interface (and the idea does seem silly...), so I can't fully comment on your situation, but it seems you could find out what specifically the license is attaching to and set that up again (if it's MAC, you just override the MAC, etc...).
The software I've used that bound to the CPU (which is silly as well) always had a mechanism to "de-register" the software specifically for migrating to new hardware. So you could setup your vm, install all your software, etc... then de-register the software (but leave it installed). Make your "appliance" image (OVA), import to the new "cloud" and re-register your application.
- sithadmin 10y ago>I've never personally dealt with software that licenses to a network interface (and the idea does seem silly...) This is super, super common with legacy software products narrowly scoped to very specific business functions.
- toomuchtodo 10y agoVery common with niche analysis/grid computing apps: https://en.wikipedia.org/wiki/FlexNet_Publisher https://en.wikipedia.org/wiki/FlexNet_Publisher
- Keyframe 10y agoI've never personally dealt with software that licenses to a network interface (and the idea does seem silly...) This was super super super super fun on IRIX when NIC died. Usually in the midst of work chaos.