AutoDiscover runs every 15 minutes. "Something" is wrong with your AutoD config. Check out exrca.com to test.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dave Lum Sent: Friday, September 26, 2014 9:00 AM To: [email protected] Subject: [Exchange] Exchange 2010 question Setup: Our live CAS box (CAS2) is set up behind a load balancer and mail.mydomain.org points back to CAS2. Outlook Anywhere is pointed to mail.mydomain.org It has been working this way for a couple of weeks now. Related, our CAS servers have the SSL binding set to a wildcard certificate. Yesterday I flattened and built a new "old" CAS1 server, giving it the name/IP of our original one. Our plan is to put it into an array, but currently it's just hanging out there, supposedly idle. I enabled/configured Outlook Anywhere to also respond to mail.mydomain.org. Issue: This morning I came to work (I typical leave my PC on overnight, logged in, but locked) and I got a certificate error from Outlook stating that the certificate for CAS.mydomain.org did not match the certificate it presented - which is the wildcard cert. We had not seen this since the first day of standing up the new CAS, so I am sure its related to me doing something with CAS1 What's confusing to me is why would my Outlook even look for this CAS server? Would it have anything to do with me enabling Outlook Anywhere on it? Or is it simply due to the fact that it's a part of the Exchange organization? I was working off the assumption that if DNS wasn't pointing back to a CAS server, then clients wouldn't go looking for it. I'm guessing there are some AD-specific items that hook it in?
