We have just moved one of our customers from one domain (au.domain.com with SBS2003 and it's exchange server) to another domain ( domain.com existing with Windows 2008 R2 and stand alone Exchange 2010 SP3). As this branch is in Australia, we have created another Exchange server (not in DAG) which can see the other (global) exchange but mail for local users will be delivered to this exchange.
One issue we are now experiencing is once the users have been set up in the new domain (domain.com) and they are connected to exchange via outlook, they keep getting prompted for certificates.
One thing we think may be causing this is that we have it set up as mail.au.domain.com
The signed certificate is a wildcard for domain.com
Do wildcard certificates cover a double sub domain?
We have temporarily changed it so that it goes to mailau.domain.com which still causes an issue within outlook, however, OWA is now happy and not reporting any certificate issues.
Does anyone know how to cure these certificate errors in outlook pointing to the .local name of the local server?
Another issue we face is that because the company is international, they already have a autodiscover entry for domain.com
We were thinking of putting an autodiscover for autodiscover.au.domain.com to point to mailau.domain.com - will this work?
I know this description is fairly ambiguous, however, I don't want to publicly give too much info away.