Changing your 3CX key to a New Key: 1) When you Take the Backup of the server, you *must* uncheck the option to 'Include license key information and FQDN' as shown below. 2) Once the Backup has been completed and you have downloaded the backup to a safe location, you can simply uninstall the 3CX Server. What happens when your 3CX V15 license key is already bound to another FQDN? The solution is simple and is outlined in this guide.

Write something about yourself. No need to be fancy, just an overview. No Archives Categories. Shablon v verde ramka so shtampom gorizontaljnij a4.

Hi, I'm trying to upgrade the 3CX v12.5 to v15.5 and we are doing a test upgrade in our organisation as of now. I'm trying to restore the backup that we took from our Production server(v12.5) on the test system(v15.5), but during the backup process it was asking for the Licence Key.

But the issue is that, the backup that we are using have the Licence key and FQDN of production server. We have 2 Licence Key's available (First - Production server, Second - Test server) and I would like to know what will happen if I provide the Second Licence Key we have with us. We wont be able to provide the licence Key of the Production server to the test system. If I provide the 2nd licence Key, will the test server overwrite the first licence Key with this one or will it be the First one that gets activated. I cant take any risks with this as if something goes wrong, then it will effect whole operations. Can someone provide me some information about this?

Guessing the license keys are registering back to 3CX and are tied to MAC address of the hardware or VM. If you restore to another box or a different hypervisor the MAC will change and break your registration as being detected as pirated.

On my commercial asterisk based system the system locks down within 30 minutes of a MAC address change and I have to call support and get them to release it. Typically, for sandbox projects where you have a couple keys, you follow the process you described.

The issue is that you don't normally jump versions. Most systems will break in unpredictable ways if you attempt to restore a different version of the software over an existing one.

Also, be aware that backups of phone systems are not like a backup of a computer OS unless you are using third party disk imaging. Amy (3CX) Exactly what I was looking for. Thank you so much for providing the information.

Also, will this remove the FQDN information from the backup? Or is it even possible to separate Licence Key from FQDN? I have heard that Licence key will be bound to the FQDN. So while taking the backup should I include the option 'Backup HTTPS(SSL) Configuration (Includes FQDN configuration, webserver certificate, Private Key and Client certificates)? Will including this option get the Licence Key included in the backup?

This option in V12.5 was used to backup the Web Server Certificate that was used, not the License Key information, that was always included. But by following the instructions previously mentioned the License Key will not be in the Backup file. Checking the backup option you mentioned, as you will be restoring it onto a V15.5 will not make any difference because the V15.5 configuration wizard will ignore it. If, when installing the V15.5 after resting the backup, you choose to use a 3CX FQDN, the wizard will generate all necessary files, while if you choose to use your own FQDN, you will have to re-import it when asked by the wizard.