Why won't my activation key activate after moving my installation to new hardware?
If you are using a subscription for OpenVPN Access Server, then you may use that subscription key on multiple Access Servers at the same time. If it doesn't work after migrating to new hardware, the most likely cause of the problem is that access to the software licensing server is not possible in the new situation. Possibly the network configuration needs to be verified and you should ensure that asb.sts.openvpn.net is reachable on port TCP 443.
On Amazon AWS we offer tiered instances that should be billed and licensed through Amazon AWS directly. These are recognizable from the (xx connected devices) in the title of the offering on the Amazon AWS Marketplace. These should be automatically licensed even if you make an AMI image of it and relaunch it. If you have made an image of it and relaunched it and it doesn't get licensed automatically, then the most likely problem is that contact with the software licensing server was not possible. Make sure that the server can reach awspc1.openvpn.net on port TCP 443. There are also backup licensing servers available (awspc2.openvpn.net, awspc3.openvpn.net, awspc4.openvpn.net).
If you are using the fixed license activation key model that follows the format of 4 characters in 4 groups (LICE-NSEK-EYIN-HERE) then the most likely cause of software license failure is that these fixed license keys locked to the software/hardware machine facts of your installation. Changing the hardware or moving the installation to other hardware would mean that this activation key will now fail to function. In this case you will need to open a ticket in our Support Center and request that your fixed license activation key be reissued. Please let us know the activation key that you need reissued.
More information and details on the licensing models are available on the troubleshooting problems software licensing page.