Messages

1

Mitel Software Applications / Re: Migration of MiCollab VM to a New VMware Cluster

« on: January 05, 2024, 07:37:33 PM »

I'm reporting back that the migration of the vMiCollab virtual machine, using the VMware OVF Tool, was successful.  All features, including NuPoint Voice Mail and MiCollab Client are functional, and licensing was preserved.  Thank you all for your help.

2

Mitel Software Applications / Re: Migration of MiCollab VM to a New VMware Cluster

« on: November 09, 2023, 03:37:02 PM »

Thank you for such a quick response!  As a precaution, I suspect I should retain the old VM until I verify that the migrated VM is working correctly.  In case I encounter an issue with the migrated VM, is it likely that I can power up the old VM on the existing ESXi 5.1 host and it will work fine?

3

Mitel Software Applications / Migration of MiCollab VM to a New VMware Cluster

« on: November 09, 2023, 03:30:45 PM »

Good afternoon, and thank you to all those who support this community!  We have a MiCollab virtual machine (VM) [version MiCollab 8.0.2.101] currently running in a VMware ESXi 5.1 cluster that is being retired.  If I power off the VM and then use the VMware OVF Tool to directly copy this VM to a host in our newer VMware ESXi 6.5 cluster (a fully separate cluster), is it expected that our licensing will be preserved and the VM will continue to function as before?  Our software maintenance with Mitel has long since expired, and it is costly (10K+) to renew according to a price quote from our local phone support company.  So, if I have to, I'll keep the old cluster running, but I'd much rather migrate the VM onto our newer cluster.

If licensing is not preserved, is there a way for me to contact Mitel to get a new license key or take whatever steps are needed to reactivate the licenses?  (Which include NuPoint voice mail, MiCollab, and UM Advanced licenses.)

And a quick side question -- the feature to have NuPoint voice mails delivered as e-mail messages no longer functions after recent security changes in Microsoft Exchange Online.  Has anyone out there found a workaround?