Question about testing v18 to v20 On-Prem

[tdhaslett]

Hey All,
I established a 60-day trial to test the upgrade to v20 for our on-prem v18 system on Windows. I am using a temp virtual machine for testing, which is off-site from the production system. This is not a clone of the production 3CX VM, it is a fresh install of Windows Server 2022.

I took a full backup (vmails, recordings, and all) of v18. During setup, I selected the backup from v18 and I disconnected the network on the VM, as I was not sure if it would mess up our production system. I don't know if there's any sort of system registration with 3CX servers that happens during setup that might cause issues.

It would not let me proceed through the setup since it could not contact DNS.

So, my question is: Can I leave the network enabled on the test upgrade without it affecting the production system?

 

[SteveITS]

It's going to activate the license key which changes/moves the key to v20. It would also update DNS, if the new one is on a different public IP.

 

[tdhaslett]

Okay, thanks. Is there a safe way to test the upgrade process before going forward with the prod upgrade?

 

[SteveITS]

The backup includes the FQDN and license now so I'm not sure there is a way to fully upgrade and test, all in a lab.

If you're using a VM anyway, consider installing and restoring to Linux...it can directly self-upgrade, and doesn't require an Enterprise license.

 

[tdhaslett]

We don't have any Linux admins, so I prefer to keep it on Windows.

I have two more questions:

1. If I run the upgrade on production and something doesn't work right, how can I go back? Once the license is moved to v20, the VM clone of v18 won't work any longer, correct?
2. What are you referring to with the Enterprise license? Do I need to upgrade to Enterprise if I'm keeping it on Windows? We're at Pro 16SC right now.

Thank you so much for the help you've been providing! I greatly appreciate it! I inherited this system from the previous admin, so I'm learning it as I go.

 

[SteveITS]

re: backups, yes the snapshot would be more appropriate if the upgrade actually failed.

Linux is a bit more of an "appliance" in that upgrades can be done in the 3CX web GUI, as opposed to Windows which requires an uninstall/reinstall. If there's a problem on Linux, one can just reinstall and restore from backup during the install. We almost never log in to a client's server via SSH past the initial install, and that's only because we set up a few initial things like rsync. It also doesn't need a Windows Server license (which is built in from the host, in some cases).

re: Enterprise, it will be required at some point:

Thread 'V20 & Windows'

Mar 7, 2024

Not sure this is the right thread, but....

I have just received an email saying V20 is now released for Linux and that a Windows installer will be released shortly.

However, it then goes on to say if you are using Windows (which I am), then I will need an Enterprise license (I am a PRO user) however then goes onto say PRO users will upgraded free to Enterprise edition for the duration of the subscription.

But words are a funny thing. What does it mean my duration of the subscription? I have an annual subscription, so do I lose out at the end of the year? or does it mean providing I...

• Hayward-i1
• Replies: 18
• Forum: Phone System / PBX

Thread 'V20: 3CX Re-engineered'

Feb 28, 2024

Taking control of your business communications has never been easier.​

More than 2 years in the making, on a journey that started nearly 20 years ago, today’s V20 Final release signals the future of 3CX - and heralds a new dawn for global business telephony. 3CX architecture has been fully re-designed from the ground up, deliv...

Continue reading the Original Blog Post.

• N_G
• Replies: 153
• Forum: Product Releases

• 
• 

And, you're welcome.