Hi guys,
Long time, first time, etc.
So I am configuring a Hybrid Deployment for migration to Office 365, and it turns out that the organization never fully set up public autodiscover, so I'm hitting a wall during configuration. I wanted to run this by you experts to see if you detect any major flaws in my master plan.
We have a single Exchange server environment with all roles on a single server - client access, hub transport, etc. Our public DNS for *.(domain).com points to a web server that has nothing to do with our Exchange server, so the autodiscover check fails since it's looking at our web server and not our Exchange server.
In order to get around this I wanted to create a public CNAME record that points requests for autodiscover.(domain).com to the location of our existing MX record in order for the autodiscover to function correctly, and have access to that secured with an SSL cert for autodiscover.(domain).com.
Does this make sense, and/or, can you guys see any issues arising from this?
Again, been lurking Technet for years now - haven't had to post until today. Great stuff.
-NS_sysadmin