even though I realize that a multi domain unified communications certificate has been the way to go since Exchange 2007, it has always been possible to also work with a single-domain-certificate.
SBS2008 and 2011 did it, and it was could also be done with Exchange Standard in both versions.
I now have my first Exchange 2013 and I am struggeling with this. A certificate is already there and paid for for 5 years, and I would hate to waste it.
This is the setup:
Exchange 2013 on Server 2012 R2 Standard, One DC running Exchange locally (I know it is not recommended).
AD-Domain "company.local", hostname "server.company.local", external domain "remote.company.com". Certificate issued to the external name.
There will be roughly 40 mailboxes on this host. No other servers are involved.
Features required include Outlook Anywhere.
When opening Outlook it connects and syncs fine, then after a rather longer while than I expect, it complains that the certificate, which is valid and issued by a trustworthy CA, was not issued for server.company.local.
I proceeded with the setup the way I always did in 2010 and worked through several of the tutorials including this:
which has helped me get 2010 up and running with single domain certificates more than once.
Does anybody know if this can be done at all with 2013 and if so then in what way it works different from 2010?