Managing Kerio Connect Server [closed]

Question

I've just inherited about 30 Kerio Connect Servers, and I have to administer them. Now, I do not have that much experience using Kerio, but managing an email server/groupware server, isn't really rocket science.

I've found myself in a position where I would like to write some basic guidelines for administering these servers, because on all of these sites, I have to place engineers, most of which have not used Kerio Connect before.

I have noticed that Kerio Connect is not as trouble free as the bare metal solutions, I would normally use custom built systems, with Postfix, Exim, or others.

I've asked around my tech circle of friends, and no one can give me a straight answer as to administering Kerio, every says, when it breaks you can do google to fix stuff. Well, that's great and all that, but to be honest, I prefer when my systems don't break, and that comes with TLC, and also a half decent check list!

I need help building my TLC checklist!

Answer 1

Kerio Connect (7.3) is rather easy to administer for day-to-day tasks; the web administration interface is really powerful and complete and at the reach of any self-respecting sysadmin. It offers all the instruments you need (fine-grained spam filter setup, SMTP delivery options, batch user creation and so on) and a decent log search facility. I've been using for three years and although not trouble-free, I consider it superior to other solutions and their support is helpful in most cases. Of course, if you could plan the deployment (choosing hardware specs and network configuration) it would be easier, and inheriting someone's else system is never ideal, but you should be able to make it work properly without too much hassle. And the forums are a good source of information!