troubleshooting Question
Exchange 2010 Autodiscover and Outlook 2010 Profile Creation
asked on
I have a new exchange 2010 build. 2 Mailbox servers, 2 CAS/HUB servers.
CAS Servers are setup with Windows NLB. NLB is using common name (mail.domain.com) and common IP.
Everything is working regarding mail flow internal and external etc.
My problem is this....whenever a new user that wasn't migrated from 2003 attempts to setup an Outlook profile, the searching for server settings is pulling the Mailbox server name and not the common CAS name of mail.domain.com.
This has something to do with the Autodiscover service I'm sure. The only issue I know of is the autodiscover name isn't on the certificate (as specified by the client). They don't use Outlook Anywhere or ActiveSync so they wouldn't need Autodiscover (according to them, even though I warned about not having it).
We are only concerned with getting this work internally on the same domain as the mail servers. Is this issue due to not having the autodiscover name on the cert?
I've already checked everything I can think of with autodiscover and RPCClientAccess, etc...
A proper SCP record exists and is found by Outlook. I have tried removing my Autodiscover A records and creating and SRV record in DNS but that didn't work either.
The error from Test-Email AutoConfiguration is "GetLastError=12152; httpStatus=0"
Any ideas?
CAS Servers are setup with Windows NLB. NLB is using common name (mail.domain.com) and common IP.
Everything is working regarding mail flow internal and external etc.
My problem is this....whenever a new user that wasn't migrated from 2003 attempts to setup an Outlook profile, the searching for server settings is pulling the Mailbox server name and not the common CAS name of mail.domain.com.
This has something to do with the Autodiscover service I'm sure. The only issue I know of is the autodiscover name isn't on the certificate (as specified by the client). They don't use Outlook Anywhere or ActiveSync so they wouldn't need Autodiscover (according to them, even though I warned about not having it).
We are only concerned with getting this work internally on the same domain as the mail servers. Is this issue due to not having the autodiscover name on the cert?
I've already checked everything I can think of with autodiscover and RPCClientAccess, etc...
A proper SCP record exists and is found by Outlook. I have tried removing my Autodiscover A records and creating and SRV record in DNS but that didn't work either.
The error from Test-Email AutoConfiguration is "GetLastError=12152; httpStatus=0"
Any ideas?
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 4 Comments.
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 4 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.