Show Posts
1
Mitel MiVoice Business/MCD/3300 / Mitel Licensing
« on: December 10, 2024, 11:27:02 AM »
I am a newbie to Mitel installs and upgrades. (Lifelong NEC tech trying to learn another brand quickly, lol)
Is there such a thing as 'Temporary' licensing, or license allocation allowed for testing of a system before deployment?
We have a customer with:
1 MiVB CXi/II Controller (GARID)
1 MiVB MXeII Controller
1 vMiVB
1 vMBG
1 vMiCollab
All on Rev 7.2
They would like to upgrade to 10.1 and consolidate all users onto a single vMiVB, vMBG, and vMiCollab.
We were wondering if we could install new virtual machines at 10.1, manually add users, configure and test - before shutting down the existing 7.2 systems.
To do this would require both the old and new systems to be licensed simultaneously, correct?
Would over-allocation or using the customer's existing GARID/ARID setup even work for this?
Engineering suggests using Migration Tool on all MiVB, but short of moving licensing to 10.1 I don't understand the advantage and it sounds like a whole lot to do in a single cutover night.
(Especially since each system will require using it twice - one to get to 9.0, the other to get to 10.1, yes? Also one would need a RAM upgrade, only to remove all users when done.)
Does anyone have a recommended method?
Or if you could get out the crayons and tell me why the Migration Tool is the best way to go, even when it can only be used on the hardware systems - that are going away. I do not understand this. (?)
Is there such a thing as 'Temporary' licensing, or license allocation allowed for testing of a system before deployment?
We have a customer with:
1 MiVB CXi/II Controller (GARID)
1 MiVB MXeII Controller
1 vMiVB
1 vMBG
1 vMiCollab
All on Rev 7.2
They would like to upgrade to 10.1 and consolidate all users onto a single vMiVB, vMBG, and vMiCollab.
We were wondering if we could install new virtual machines at 10.1, manually add users, configure and test - before shutting down the existing 7.2 systems.
To do this would require both the old and new systems to be licensed simultaneously, correct?
Would over-allocation or using the customer's existing GARID/ARID setup even work for this?
Engineering suggests using Migration Tool on all MiVB, but short of moving licensing to 10.1 I don't understand the advantage and it sounds like a whole lot to do in a single cutover night.
(Especially since each system will require using it twice - one to get to 9.0, the other to get to 10.1, yes? Also one would need a RAM upgrade, only to remove all users when done.)
Does anyone have a recommended method?
Or if you could get out the crayons and tell me why the Migration Tool is the best way to go, even when it can only be used on the hardware systems - that are going away. I do not understand this. (?)