I'm running into an issue where Outlook isn't downloading the OAB from our CAS servers. We run Exchange 2007 SP2 Rollup 4 and all clients are Outlook 2007. We don't use Outlook offline, but I would like to clear up the error notice (0x8004010F) that displays everytime the server is contacted. I've been through http://blogs.msdn.com/dgoldman and validated that everything on the server side is working properly. My mailbox servers are generating the OAB properly, my CAS servers are picking up the OAB properly and permissions for IIS are set properly. The OAB is set to distribute v4 only and Web-based distribution is enabled for both our CAS servers. The timestamp on the OAB files (.LZX) is within the past few hours. Running get-oabvirtualdirectory| fl shows: IsValid : True RequireSSL : True InternalUrl : http://dmzexcas01.corp.com/OAB ExternalUrl : https://www.website.com/OAB However, when I run the Email Auto-configuration and look at the XML results, I don't see any OABURL value. How can I ensure this is added? Thanks, Greg

Hi, 1. Are the problematic users internal or external to your network? 2. Test Outlook Anywhere\AutoDiscovery from TestExchangeConnectivity.com and see if it succeeds or not. If not then post the error here. 3. Does your SSL ceritificate contains website.com as SAN? Regards,Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

Hi, Are there two CAS located in your environment? Did you check the OAB Virtual Directory on another CAS? Additionally, whether all users have this issur or just one user? And please run test-outlookwebservices |fl command in EMS, then post the information on the forum. If possible, please also paste the information that you tested in the Email AutoConfiguration. Thanks Allen

Sorry, I should have clarified that these are internal users on our network at the office. All of them run Outlook 2007. Your suggested step #2 fails because this is an issue affecting internal issue. The SSL certificate is configured properly, but not used in my scenario.

Hi Allen, There are indeed two CAS in our environment and from what I can see, both appear to be functioning/configured properly. The \Client Access\OAB directory is properly set up in IIS and has the correct OAB (based on GUID). When I rerun the Email Autoconfiguration this morning, I see that the OABURL value has populated. I'm going to do some testing to validate that it's working now, but perhaps there was just a big delay (4+ hours) between my reconfiguration of OAB yesterday and the change appearing in the xml file. Thanks, Greg

After testing, I can confirm the OAB issues have been resolved.

Hi, Glad to hear that is resolved. Thanks Allen