Hi i am running an exchange 2010 setup with DAG(2nodes) my cas,hub is in a diffrent servers i am having a registered domain in the name of web.mydomain.com and SSL has been done for this my cassserver (hostname is mycas.mydomain.com) while doing autodiscover sometime its give us error i want to use the same hostname web.mydomain.com to be taken automaticaly while connecting exchange user locally instead of mycas.mydomain.com ... how i can make it happen i am using two databases db1,db2

If you want to use a CAS array then it should NOT resolve externally. If it does, then it will cause problems with Outlook Anywhere. You should have a unique URL that works internally ONLY for the CAS array. This URL does not have to be in the SSL certificate because Outlook does not connect to it with SSL. What kind of SSL certificate have you purchased? A unified communications certificate or a single name certificate? If it was the latter, it really should have been the former. That would allow you to include the internal names of the CAS server/s in the certificate and avoid errors. The external name would then be used for all external traffic. Thus: The internal CAS array host would be outlook.example.local The external common name would be web.example.com The certificate would also have autodiscover.example.com and cas1.example.local and cas2.example.local Where example.com is the public domain name in your email address after the @ sign, example.local is the DNS name of your WINDOWS domain and CAS1 and CAS2 are the names of your CAS servers. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

no cas array is here cas - cas.example.com mbox1 - mbox1.example.com mbox2- mbox2.example.com dag configured and 2 database running DB1,DB2 internal hostname cas.example.com , external name - webmail.example.com bought SSL for webmail.example.com its not wild card , so without cas array if there is any other possibility to set internal rpcclientaccessserver name as webmail.example.com

I think there's some confusion with either setting the rpcclientaccessserver or the autodiscover AutodiscoverServiceInternalUri. I see your original issue is you're trying to fix an autodiscover error. You said it sometimes errors out going to mycas.mydomain.com. I'm assuming it's working internally but failing externally. Can you confirm when it fails and what errors you are getting when you perform the autodiscover test?James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

You don't set the rpcclientaccesserver to the external name. That will cause problems if you use Outlook Anywhere. Are you going to use Outlook Anywhere, Exchange ActiveSync? A wildcard certificate is NOT a unified communications certificate. Many people seem to think they are same but they are not. Exchange 2010 is designed to be used with a unified communications certificate. While it is possible to change the URL that the Outlook clients connect to, which is the autodiscover URI configured through set-clientaccessserver, if you are going to use Outlook Anywhere your external DNS provider MUST support SRV records - many do not. Your best option would be to change the certificate to a UC certificate. It will make the management and use of Exchange much easier. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.