MiCollab on Hyper-V

[smithm03IP]

Just moved a customer from VMWare to Hyper-V and did an upgrade but now the MiCollab Client will not start.
I am getting the following: MiCollab Client Service failed but JBOSS was running.

I cannot access the Configure the MiCollab Client Server, it just hangs.

Help!!

 

[kwbMitel]

How did you build the Server on Hyper-V?

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

 

[LoopyLou]

Don't think you can really migrate. Need to start from scratch.

You can't duct tape stupid.

 

[Billz66]

I have done this for a customer that decommissioned their esxi and wanted to run micollab in hyper-V

- Backup of Micollab in esxi - shut it down
- manual installation of Micollab in Hyper-v, restore backup
- have to create hyper v server ( as per bp virtualisation )
- boot from msl , install like it was a physical server , step by step

worked fine

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

 

[db5]

Just came across this same issue while installing a MiCollab on Hyper-V.

Turned out I only had 1 vCPU assigned to the virtual instance. Assigned another vCPU, rebooted and the MiCollab service started.

All has been good with the server now

 

[Billz66]

there are some specific requirements on Hyper v Virtual appliance config that are listed in the Best practices guide

if you build the machine as per the docs it should run ok.

Pity their isnt a pre built package as per Vmware .

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

 

[db5]

I had consulted the virtualization guide before installing but turns out when you're busy with multiple faults and trying to install a virtual appliance something like that was easily missed.

Having the OVA's is a wonder when doing VMware deployments.