Moving users from MCD to vMCD 1

[StardataMitel]

Hi All,

We currently have an MCD at 6.0 SP1 running on a 3300 cx with enterprise licensing.
Users are managed from a vMAS system (5.0) with vUCC licensing.

The plan is to build a vMCD and network the two.
We want to migrate all the users from the MCD to the vMCD as the home element.
Then making the MCD the the secondary element.

Has anybody attempted this before?
My initial thought is to:
1. network the systems
2. Delete user on MCD
3. Create user on vMCD

As there is over 100 user i was hoping for a procedure that was a little less hands on.

 

[MitelEngineering]

You could Export the users, then block delete on the MCD. Then import the users to the vMCD with the MCD as the secondary element on the import form...simple, and should only take about an hour or so for 100 users. Since the removal of Ops Manager and the TASMAC form, I think this is the only way to do it now.

 

[Billz66]

Yep , i agree , do exports of all the relevant forms ( dont forget Mulitline keys )

Clear the keys delete the users , import on vmcd


If I never did anything I'd never done before , I'd never do anything.....

 

[LoopyLou]

Is there any ability to take the database from the CXi and put it on the vMCD ( after removing elements not supported in the vMCD ).

An apple a day keeps the doctor away. Anyone else and you need to throw it harder.

 

[kwbMitel]

Yes there is a migration path for any 3300 chassis to any other 3300 chassis.

I've done this many times

It takes about an hour all told to create a backup that can be imported directly to the vMCD.

I suspect that in this case, the CXi will remain in the network as a PSTN gateway. That being the case, it can be very difficult to fully remove all the existing programming on the CXi.

If the CXi is being abandoned, then I would strongly recommend the migration path.

If the CXi is being retained then I would manually move the users.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[LoopyLou]

Yes I thought there was a process. Seen it documented somewhere but can't find it. The advantage of moving the database is that you would have less to worry about with users having to recreate speed dials on their phones etc.

Think the process as I remember it is move licensing to the vMCD. Restore the physical database to the vMCD. Unplug physical from network and bring vMCD on line. Boot phones. Do a manual software install on the physical controller to wipe system and reset licenses. Cluster physical controller to the vMCD and use SDS to populate programming. Add ARS if needed. You are going to have to do the clustering anyway so it doesn't add time to the job.

An apple a day keeps the doctor away. Anyone else and you need to throw it harder.

 

[kwbMitel]

@LoopyLou

Before capturing the backup to be used to restore to the vMCD you MUST MUST MUST remove all programming associated with non-IP devices and equipment.

All programming associated with embedded analog main board
ALL programming associated with CIM connected units
ALL programming associated with PRI or other trunking

You can retain embedded voicemail, IP sets, cluster programming and IP trunks but not much else.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[TheMitelGuy]

To keep the customer up and running during the translation - 1) we do a DB back up.

2) We go back to our office and load the DB on a CX/MXe controller.
3) We remove all TDM programming (as mentioned above).
4) Do a new backup.
5) Setup vMCD and restore DB.
6) Setup licensing on vMCD and make sure we are all good there.
7) Create a new cluster on vMCD.
8) Blow away the software on the CX/i controller by installing the latest MCD software.
9) Join the new cluster and setup the TDM portions required (analog trunks, PRI, ONS phones etc.).

That is the best way for us. That saves all the key programming which is the hardest and lengthiest part.

Best of luck! Let us know if you have any questions.

 

[LoopyLou]

kwbMitel. Agree with what you say. Would also have to remove DHCP and likely a few more things. The point I was trying to make is that it is not that hard to take an existing database and convert it. It also might save a lot of post cut issues by maintaining things like speed dials on keys call forwarding etc. "The Mitel Guy" outlines a good method to do so. I would only add you need to setup a license manager or manually move licenses from the app record of the CX to the vMCD.

An apple a day keeps the doctor away. Anyone else and you need to throw it harder.