Solved Migrating from "Windows 2012 R2 + 3CX 15.5.15502.6" ==> "Windows 2019 + 3CX 16 U5"

Status
Not open for further replies.

Eric Roberge

Forum User
Joined
Feb 15, 2017
Messages
17
Reaction score
4
Hello,

Our setup:
We are currently running a 3CX 15.5.15502.6 on Hyper-V VM Windows Server 2012 R2 with 2 network cards
Network card #1 : Prod Network + internet.
Network card #2 : DHCP for VoIP VLAN phones.

What we are looking to do:
We are planning to do an "in place" upgrade from Winodws 2012 R2 to Windows 2019 Server AND after update the 3CX 15.x to 16 U5.

Our questions :
Q1 : Is 3CX 15.x compatible with Windows 2019 ?
Q2 : Do we need to Uninstall the 3CX 15.x before doing the Winodws 2019 update ?
Q3 (3CX restore): If we do a 3CX 15.x full backup, after restoring the backup to the new installation of 3CX 16U5 do we need to reconfigure somthing (ex: SIP trunk username password) ?

Any help and positive comments will be greatly appreciated !
 
So, 3CX v15.5 is not compatible with WinServer 2019. Also, in-place upgrades are bad.

Here's the best way to do it:
- Backup 3CX with a full backup
- Spin up a new server/VM
- Install Windows Server 2019
- Install 3CX v16 U4 (latest official)
- Restore the 3CX backup during setup while you shutdown the old server.

This way, you have your old machine just-in-case something bad happens. If not, you're good to go with a brand new machine.

WS2012 is old, if you upgrade in-place, something will definitely go wrong!

Answer to Q3: If the backup is a full (all checkboxes), then no. Everything is restored. You'll just need to set your IP back to the old one once it's installed so your phones can provision (Unless you use split DNS).
 
Why not save a Windows Server 2019 license, use Win 10 Pro or even better Debian
 
  • Like
Reactions: Evolute IT
So, 3CX v15.5 is not compatible with WinServer 2019. Also, in-place upgrades are bad.

Here's the best way to do it:
- Backup 3CX with a full backup
- Spin up a new server/VM
- Install Windows Server 2019
- Install 3CX v16 U4 (latest official)
- Restore the 3CX backup during setup while you shutdown the old server.

This way, you have your old machine just-in-case something bad happens. If not, you're good to go with a brand new machine.

WS2012 is old, if you upgrade in-place, something will definitely go wrong!

Answer to Q3: If the backup is a full (all checkboxes), then no. Everything is restored. You'll just need to set your IP back to the old one once it's installed so your phones can provision (Unless you use split DNS).

Thanks for the advice !
We will plan a new Server/VM installation ;)

Do you know if we need to follow a procedure in order not to lose the license during the server transfer ?
 
  • Like
Reactions: Evolute IT
Thanks for the advice !
We will plan a new Server/VM installation ;)

Do you know if we need to follow a procedure in order not to lose the license during the server transfer ?
The Windows license is lost for sure. You'll need a new one for the 2019.

3CX: Just make sure to shutdown the old server right before restoring the backup on the new one. The license will transfer (must be checked in the backup).
 
Why not save a Windows Server 2019 license, use Win 10 Pro or even better Debian
a "Winodws 10 Pro" to run a production phone system.... Not sure about this one
Is There a limitation on how many users can connect to the 3CX running on a Winodws 10 Pro VM ?
 
a "Winodws 10 Pro" to run a production phone system.... Not sure about this one
Is There a limitation on how many users can connect to the 3CX running on a Winodws 10 Pro VM ?

What is your setup - number of trunks, extensions, queues, ring groups then someone should be able to answer your question
 
a "Winodws 10 Pro" to run a production phone system.... Not sure about this one
Is There a limitation on how many users can connect to the 3CX running on a Winodws 10 Pro VM ?
No limits other than Windows resources.
 
What is your setup - number of trunks, extensions, queues, ring groups then someone should be able to answer your question
We have :
30 extensions
2 sip trunks
6 Call queues
0 Ring groups
11 digital receptionist extension.
 
We have :
30 extensions
2 sip trunks
6 Call queues
0 Ring groups
11 digital receptionist extension.
You're good on either. The only difference between Windows 10 Pro and Windows Server 2019 is Windows Update. One is updating by itself (annoying), the other is always outdated.
 
We support Windows 10 Pro or Ent as seen here: https://www.3cx.com/docs/manual/

Indeed it is better to install a fresh OS than upgrade the one in place
In windows hosts, 3CX will need to be fully uninstalled anyway before upgrading to the next major version (ie. V15.x to V16.x)

Just run a full backup to catch everything, then take the backup off the machine for safe keeping.

Build your new VM as per these instructions: https://www.3cx.com/docs/installing-microsoft-hyper-v/

You can shut down your old VM now, and proceed to install V16SP4 on the new one. Change the IP's on the the NICs of the new machine to match those of the old machine and ensure you pick the correct one during setup.

When the 3CX web config tool starts, provide it with the backup (not a "new install") and go ahead. Once it's up and running the phones and trunks should register automatically. Check your Backup options and setup your automatic backups again (if you had automatic backup).

Some phones may get new firmware that needs to be installed afterwards. If you have any issues with that, start a new thread but make sure you check the guides for each model before posting,they will already contain the answers to your questions: https://www.3cx.com/sip-phones/
 
We support Windows 10 Pro or Ent as seen here: https://www.3cx.com/docs/manual/

Indeed it is better to install a fresh OS than upgrade the one in place
In windows hosts, 3CX will need to be fully uninstalled anyway before upgrading to the next major version (ie. V15.x to V16.x)

Just run a full backup to catch everything, then take the backup off the machine for safe keeping.

Build your new VM as per these instructions: https://www.3cx.com/docs/installing-microsoft-hyper-v/

You can shut down your old VM now, and proceed to install V16SP4 on the new one. Change the IP's on the the NICs of the new machine to match those of the old machine and ensure you pick the correct one during setup.

When the 3CX web config tool starts, provide it with the backup (not a "new install") and go ahead. Once it's up and running the phones and trunks should register automatically. Check your Backup options and setup your automatic backups again (if you had automatic backup).

Some phones may get new firmware that needs to be installed afterwards. If you have any issues with that, start a new thread but make sure you check the guides for each model before posting,they will already contain the answers to your questions: https://www.3cx.com/sip-phones/
Thank you so much !
 
You're welcome! If you have any other concerns before you proceed, ask away! :)
 
  • Like
Reactions: Eric Roberge
You're welcome! If you have any other concerns before you proceed, ask away! :)
We are currently using Polycom IP550... i hope they will be compatible with 3CX v16.x
 
As you can see from our guide they are supported as legacy phones, but with the limitations listed below
https://www.3cx.com/sip-phones/polycom-soundpoint-450-550-560-650-670/

However, with V16 you get an upgraded webclient, windows client and mobile clients that are also good options to use if you are looking to move away from deskphones. Of course you can keep deskphones and upgrade them to non-legacy, fully supported devices in the future so you can use more features that the PBX has to offer.
 
  • Like
Reactions: Eric Roberge
Why not save a Windows Server 2019 license, use Win 10 Pro or even better Debian

If its Hyper-V as he says - licenses are reusable for 2 virtual machines - or he has Datacenter - which is unlimited VM licenses.
 
  • Like
Reactions: Eric Roberge
Our setup:
We are currently running a 3CX 15.5.15502.6 on Hyper-V VM Windows Server 2012 R2 with 2 network cards
Network card #1 : Prod Network + internet.
Network card #2 : DHCP for VoIP VLAN phones.
Doable but far better ways to get the doing done, and this job was far better left to the firewall/router or core switch to handle the VLAN routing and DHCP for the phone vlan.

What we are looking to do:
We are planning to do an "in place" upgrade from Winodws 2012 R2 to Windows 2019 Server AND after update the 3CX 15.x to 16 U5.
Absolutely terrible idea, do not do this, and if you do, i wouldn't tell others about it, very bad practice.
 
Thanks everyone (specialy JohnS_3CX), I did the installation of a new server as well as the installation of the 3CX with the recovery of the backup and everything went very well !
 
Glad to hear!
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,945
Messages
589,866
Members
164,835
Latest member
Firefox Technologies