OK, i have an exchange 2007 server setup to recieve emails for a few email addresses. We've purchased another company and have moved their email to our server and kept their old email addresses. I have that working fine. The only problem I'm having is the other company can't seem to download the offline address book. I have the autodiscover service working fine for them to see free/busy time on Outlook 2007 but their clients hang when trying to get the address book.We only have one address book for both organizations on the server and no permissions have been changed. I thought that it would use the address book url from company A and allow company B to get it since they are on the same server but it doesn't seem to work.Does any one have any idea as to why this would happen and what I need to do to allow company B to download an offline address book?

Are you sure that autodiscover is set up correct for both smtp domains? use the https://www.testexchangeconnectivity.com/and autodiscover test to verify.

Yes, I've used that tool to test the Outlook 2007 AutoDiscover Connectivity with both company A and company B and they both come back successful.I don't think it's a problem with the autodiscover service since i can see the free/busy time from Outlook 2007 with a user from each company.

Hi, Please check whether I understand your environment configuration correctly: The Exchange Server is configured to host two domains for CompanyA and CompanyB. Only one Offline Address Book is configured on the Exchange Organization. The users of CompanyA are able to download the OAB file. Nevertheless, the users of CompanyB failed. At this time, would you please let me know whether the mailboxes of CompanyBs user are located on a separated mailbox store? If I am right, please check whether the mailbox store is configured associated with the correct OAB file. Please also attempt the following method to troubleshoot the issue: 1). Launch Outlook 2007 using the profile of companybs user.2). Hold down the CTRL key on your keyboard and click the Outlook icon in the notification area of the Windows taskbar, also known as the notification area.3). In the menu that appears, click Test E-mail AutoConfiguration.4). Enter your E-mail Address and Password (if not logged into the domain) in the respective edit boxes.5). Choose the desired auto configuration methods with Use Autodiscover, clear other selection.6). Click Test. Please check whether the user is able to get the OAB URL correctly. If the Outlook connects to Exchange server through RPC, check the related RPC URL. If the Outlook conncts to Exchange through RPC over HTTPs, please check the related Exchange HTTP URL. Mike

Yes you do have the scenario correct for my problem.Company B's users are on a different Mailbox Database than Company A, but they are on the same Storage Group.When doing the autodiscover test, the users from Company B have the same OAB URL as Company A. All the URL's related to the autodiscover are the exact same as Company A.One thing that I don't think matters as it works fine is the autodiscover.companyB.com url I have redirected to autodiscover.compnayA.com. I've run the autodiscover test just fine and everything comes back fine with the redirection and the autodiscover service.

OK, after checking more things that you suggested, I found one thing.When I go to my OAB url from internal, I get a "HTTP 403 Forbidden" page; however, when I try it from my home PC I'm getting a "page cant be found" error page.So it looks like I might have a permissions problem on my OAB IIS site. Can someone tell me what the permissions should be set to so I get it correct?

Alright, I have my answer. When we setup Exchange 2007, we didn't buy a unified certificate and chose to create different sites to get around that and have multiple certificates.Turns out the External site that I have for Exchange didn't have the OAB folder. After a quick save of the Internal OAB and import of the OAB to the External IIS site, I'm able to download the address book. So it wasn't even working for our people outside our network and I never knew it.