New MiCollab with Flow-through provisioning

[VinceWhirlwind]

I'm having problems getting this to work.
Following the I&M, these are the steps:
(p95)
1. Install and licence the MiVB server. (I don't have an MiVB server, I have an MXe, but the I&M guide doesn't talk about MXe, so I'm assuming this info applies to that as well)
2. Make sure MiVB Server SDS sharing scopes match what is listed on p215.
3. Run MICW tool against MiVB server and MiCollab together as per p167
 
Is this all that is required, or have I missed some trick somewhere?

[acejavelin]

I'm having problems getting this to work.
Following the I&M, these are the steps:
(p95)
1. Install and licence the MiVB server. (I don't have an MiVB server, I have an MXe, but the I&M guide doesn't talk about MXe, so I'm assuming this info applies to that as well)
2. Make sure MiVB Server SDS sharing scopes match what is listed on p215.
3. Run MICW tool against MiVB server and MiCollab together as per p167
 
Is this all that is required, or have I missed some trick somewhere?

Those steps are required... MiVB (MiVoice Business) is the new name for MCD (Mitel Call Director), MXe is a hardware variant that would have MiVB/MCD installed on it (it's the operating system so to speak). As a correlation, it is kind of like your computer (MXe), the hardware platform is the same, but it was on Windows 7 (MCD) but now is on Windows 10 (MiVB).

So in your mind, just substitute MXe wherever it says MiVB, as in this case they refer to the same thing.

[martyn]

Is this a greenfield site or a brownfield? You need to ensure that the whole MiVB cluster is up to the correct release if it is a brownfield before you can add the MiCollab in to the cluster.

I assume that since you are doing this yourself, you work for a VAR, so I would suggest that you get your MCD/MiVB training up to date as it is covered in there along with your MiCollab.