Hosted Exchange keeps “resolving” the CAS server FQDN when setting up Outlook…NOT GOOD

exchangeexchange-2010fqdnoutlookoutlook-2010

In our exchange 2010 environment when setting up Outlook with one of the mailbox accounts, check name resolves the FQDN of our Client Access Server. We do not want employees/customers to see this information. I have a subdomain whos name record is pointed at the CAS server, so all is great until you hit the "check name" button during setup and it resolves to the FQDN of the server.

exchange.mysite.com turns to EX-CAS01.mysite.local
alt text

I am trying to figure out how to keep this from happening because it doesn't look as good, but more importantly for security purposes.

Best Answer

You can get around this by setting up a singe server CAS Array if that's what you really want to do.

Create a DNS entry for exchange.mysite.com on your internal DNS server and point it to your Exchange server. Then do this:

New-ClientAccessArray –Name “CAS Array” –Fqdn “exchange.mysite.com” –Site “Default-First-Site-Name”
Set-MailboxDatabase DatabaseName -RpcClientAccessServer “exchange.mysite.com”

You may even be able to get that to work without the CAS Array part, I just haven't tried it and probably wouldn't recommend it as Microsoft probably wont' support it.