Micollab setup in LAN only mode.

[snithinkumar]

Hi all,

I have few questions regarding Micollab (version 9.1.3) LAN only installation.
1. The Micollab server I set up has only one internal (LAN IP) IP address. Will Android Android and IOS clients work in this case?
2. How do I build the FQDN? Should I point the FQDN in the Godaddy(for example) portal to this internal Micollab address and generate the SSL certificates?
3. As the micollab server is not reachable from public internet, will the deployment profile test succeed? If the deployment test is not working, is there a way around?

[lrjones198]

I am currently running my MiCollab in internal LAN only mode.
I do not believe your cell phones will work without having an external IP on the server. We set ours up to utilize MiCollab's softphones within our business.
Your FQDN you can create internally in your DNS and use whatever CA you choose. For example you can point your FQDN to internal server address and this will work fine.
Your deployment profile will succeed on first test only as other two require external IP setup.

[ZuluAlpha]

You don't have to have an external IP specifically on MiCollab if your firewall can route the DNS of the FQDN in your network. So you would need AN external IP for your domain, but wouldn't necessary need one specifically for MiCollab.

[johnp]

MiCollab in LAN only is not a supported configuration, I think it has a warning to that effect. I most often add the MBG and cluster the 2. MBG proxies the necessary urls and IMHO is worth the extra $250 to be in a supported mode.

[lrjones198]

That is weird as I never saw a warning during setup. I did forget to mention I set this up through MBG as well but still only using on LAN with no external IP.

[Dogbreath]

"MiCollab in LAN Mode (Server-only)" is listed as a deployment option in the Engineering Guidelines doc for 9.1.
It doesn't specifically say that deployment won't work, so I would assume it does? I don't like making assumptions with MiCollab however, as it seems to confound many of the assumptions I make of it.

[sunspark]

for one of our customers we use micollab client in Lan mode only.

you should resolve the dns micollab.mycompagny.local

+ Mbg deployement profile
+ export the micollab auto sign certf and import (gpo) on all your computers.

that all.