Upgrading from 15.5 to 16 - Windows Server

[usat]

Hello all,

We currently have 15.5 running on a Windows 2012 R2 server. We have been waiting to upgrade to V16, and gave it a few weeks for early adopters to notice any bugs that may be in the system. It looks like everything is good to go, and we will be upgrading this weekend. I wanted to reach out to the community and see what, if any, caveats there are to upgrading on Windows. I am aware that we must first uninstall 15.5, then install 16 and restore from a backup. Is that all there is to it? Any best practices or information that would help smooth along the process? I have not seen / found a Windows upgrade guide, so any advice would be greatly appreciated.

Thank you!

 

[craigreilly]

make sure you copy your backup to another location... so if the 3cx folders are blown out during uninstallation - you still have the file.

 

[usat]

make sure you copy your backup to another location... so if the 3cx folders are blown out during uninstallation - you still have the file.

Excellent advice. We actually keep copies of the backups on a separate device.

 

[AWS2P]

Add a reboot after uninstall V15.5

 

[cmp1]

How did it go? Encounter any issues?

 

[StefanW]

make sure you copy your backup to another location... so if the 3cx folders are blown out during uninstallation - you still have the file.

a relic from the past, the backup folder will not be removed anymore ;-) But always be save then sorry and keep it in another place, which is not the same host/pc/vm is a good idea.

 

[usat]

The transition went pretty smoothly. There were issues in getting the FQDN registered initially, but it worked after retrying a couple of times. That was the only major hurdle. Everything seems to be running as expected!

 

[AWS2P]

Just take care about schdeduled backup if you previously used in V15.5, the V16 installer erase all and you retrieve in basic backup task once a day on local pc, so you need to re-set manually

 

[usat]

I noticed that this morning when the backup was created. It only retained the FQDN and the license information. I went ahead and readjusted the backup settings back to what they were previously