When you want to deploy hosted Exchange/multi domain Exchange, there are several things to take in consideration.
One of the things is certificates. To be honest the only thing needed is that your certificate is valid for YOUR domain, so not the client’s. When that is the case the client will be able to connect using outlook anywhere(rpc over http) however , for the clients to be able to use the “out of office assistant” and other funtions. You need to set up an autodiscover record for THEIR domain on their dns servers.
You’d think that you’ll just create an A record of Cname pointing autodiscover.clientmaildomain.com to your mailserver, no it’s not that easy.
If you do this, then autodiscover will work, as well as all the OOOF functions etc… But your clients will receive an annoying certificate mismatch popup everytime they start outlook!
This can’t be helped, since the client will lookup autodiscover.clientmaildomain.com but will be retargeted to autodiscover.YOURdomain.com , this is why there is a certificate mismatch.
Installing the certificate won’t help and nothing else will.
The only VALID solution to this, is to make an SRV record on the client’s dns as follows:
Then remove all the A and CNAME records for autodiscover!
Last I came across an issue which looking back at it was obvious enough, but not at the time:
I needed to export some mailboxes to pst files on exchange 2010 NOT SP1 using the EMS (Shell), so as you might (not) know you need Outlook x64 installed on the server where you want to do the export from.
No problem, I just installed outlook and proceeded with my exports. But then it turbed out that my BES Express which was on the same server stopped working. The BES Services wouldn’t start anymore.
So after some digging in the event logs it turns out that outlook overwrites the mapi32.dll file that you installed as a BES Prerequisite (MAPI CDO 1.2.1 pack).
-Uninstall outlook , then reboot the server.
-Then go to control panel –> Add/Remove programs –> select the MAPI/CDO pack from the list and remove it.
-Download the pack again from here
-Reinstall the pack
-That’s it, the BES Services should start now and you should be up and running again.