Exchange 2010 - cant download OAB sometimes
Hi, Im having issues with Exchange 2010, the OAB and https over RPC (Outlook anywhere). I have 2 domains (A and B), and only one with exchange (A). The users with computers in domain A using Outlook anywhere can download the OAB fine. But the users with computers in domain B get a error 0x8004010F saying an object cannot be found. Any idea ? The rest works fine. They can send emails, etc. I can setup their mailbox in outlook 2007 or 2010 with no problem. They just never can download the OAB. In Exchange, i have the OAB set to public folder and OWA.
August 8th, 2011 11:16pm

Can the user from Domain B resolve the Internal URL from the Get-OABVirtualDirectory? Can you do the following: 1) Get-OABVirtualDirectory | fl from Exchange server 2) Crtl-rightclick the outlook icon in your system tray, select Test Email AutoConfiguration, uncheck the two Guessmart box and post the results from the problem client machine.Tim Harrington | MVP: Exchange | MCITP: EMA 2007/2010, MCITP: Lync 2010, MCITP: Server 2008, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington
Free Windows Admin Tool Kit Click here and download it now
August 9th, 2011 3:48am

Hi Bepe, Andy update for your issue, Tim gave some good suggestion, please post the information here, then we could do more research about your issue. I want to verify other information about your scenario. 1. Are the domain A and domain B in the same forest? 2. Do the users in the domain B use internal network(IP, DNSserver) to connect to the exchange server? 3. Do the two domains trust each other? 4. If 3 is false, how do you configure the outlook anywhere in domain B, automatically or manually? In my opinion, maybe you could add some autodisciver SRV&A record on the DNS server, the issue could be resolved. Regards! Gavin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
August 10th, 2011 10:20am

Thanks. I corrected the issue with your help. But it's a bit weird. I dont really understand why it happens that way. I found out that when doing the autoconfiguration test, the client in domain B (using a email address @anotherdomain.com), were looking for autodiscover.anotherdomain.com, but i only have autodiscover.domaina.com setup. I just added an cname in the dns record to point autodiscover.anotherdomain.com to mail.domaina.com and it worked. But now, the clients have a certificate error when they launch outlook but it works anyway. I just dont understand why outlook look for autodiscover.anotherdomain.com when in Exchange, i only have domaina.com setup, the anotherdomain.com is only a 2nd domain registered for email and web server. Thanks for the help
Free Windows Admin Tool Kit Click here and download it now
August 10th, 2011 11:18pm

Domain a and b are not in the same forest. the users in domain B use https over rpc to connect to exchange server in domain A the 2 domains have no trust relationship. i configure the outlook manually. And yes, it is related to autodiscover. I just dont understand why (look at my answer to Tim). But knowing that i also use this exchange server for other domains (like domainc.com, domaind.com, etc) and none have the autodiscover.domainx.com setup, i wonder if ill have to set it up, and also if ill have to change the certificate so that no error shows when users open outlook. Thanks again for the help
August 10th, 2011 11:22pm

Hi BePe, If they are two forests, that means the users worked as a external users, and we must configure some record for the external users, and it is better to use a CERT. About how outlook end to use the autodiscover you could refer to below: http://technet.microsoft.com/en-us/library/bb124251.aspx If you have multiple accepted domain, and it is needed to have the autodiscover.domainname.com record. And the outlook error related the CERT, the name also needed to be contained in the CERT, and the outlook client end should be installed with the CA ROOT CERT. Regards! Gavin TechNet Subscriber Support in forum If you have any feedback on our support, please contacttngfb@microsoft.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
August 11th, 2011 6:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics