I have followed, as far as possible, DGoldman's notes to configure my OAB, hosted on my Exchange 2007 server (my comments in red: For Outlook 2007 (all service packs) If you have installed Exchange 2007 in to an Exchange 2003 organization you need to make sure that you have added the replicas of OAB to the Exchange 2007 server. Yes! Make sure public folder replication is working between servers. Yes! An Autodiscover DNS record has not be setup by your ISP therefor will break HTTP/RPC because you will not be able to connect. Used a local hosts file on the client PC with an entry with the IP address of the autociscover (CAS server) IP address, since I have no control over my ISP You have set an invalid proxy settingin IE. Windows, Outlook and IE all use the same WinHTTP Proxy settings and if this proxy is incorrect all Outlook WinHTTP calls fill fail. None configured. Make sure the OAB is public folder enabled and you have OAB Version 2, OAB Version 3 and OAB Version 4 checked off so your legacy clients can download the OAB files from the public folder store. Yes! Make sure that if you are using an Outlook 2007 client, your OAB is Web Distribution enabled and the OAB files have been replicated over to the Client Access Server. Yes! If you are removing your last Exchange 2003 server from the org, please make sure that you follow our documentation on this process. It is still there. The OAB may not exist is if you have a cluster and that node that is currently inactive, and alsois the only one set to generate the OAB. No cluster. What else can be done to make it work for my numerous Outlook Anywhere client PCs? Or will it remain broken for them as far as Microsoft's plans for the future?

Hi, Would you please let me know? 1. Whether the users are able to download OAB files when Outlook 2007 connects to Exchange server through RPC instead of RPC over HTTP 2. Whether the users are able to download OAB files when you configure the Outlook 2007 (in the internal network) connects to Exchange Server through RPC over HTTP. 3. Whether the Outlook 2003 is able to download by using the above two methods 4. If the user mailbox is on the Exchange 2003 server, whether he is able to download OAB file by using Outlook 2007 through RPC over HTTP. Please also help me gather the following information: 1). on the problem client, launch Outlook 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 post the result under the Results tab and the Log tab. Mike

No new configurations will work, inside or outside the firewall and the only difference between the two is that the ones that work say \Global Address List in the Choose Address drop-down (Tools, Send/Receive, Download Address Book) versus having Download Offline Address Book List in the drop-down, which doesn't inside or outside the firewall. 1. Whether the users are able to download OAB files when Outlook 2007 connects to Exchange server through RPC instead of RPC over HTTP Yes 2. Whether the users are able to download OAB files when you configure the Outlook 2007 (in the internal network) connects to Exchange Server through RPC over HTTP. It depends: No new configurations will work, inside or outside the firewall and the only difference between theones that work (old configurations)and the new configurations (which don't work) is that the ones that work say \Global Address List in the Choose Address drop-down (Tools, Send/Receive, Download Address Book) versus having Download Offline Address Book List in the drop-down, which doesn't work inside or outside the firewall. 3. Whether the Outlook 2003 is able to download by using the above two methods Yes 4. If the user mailbox is on the Exchange 2003 server, whether he is able to download OAB file by using Outlook 2007 through RPC over HTTP. Yes As far as testing Autodiscover, the results vary, depending if the client was setup before or after the OAB was moved from the Exchange 2003 to 2007 server. The ones that were configured before the move had no errors, ones afterward had some. Where does Microsoft hide the files from the Results and Logs since I can't copy and paste the results and since I can't paste a picture here adn so far can't find a .log or .xml file with results in it? I would be more than happy to post if I could find a reasonable way to do it.

Arrggh! Hit post too soon - question one - answer again varies, depending if the profile was created before or after the OAB move - yes if created before, no if created after.

From one that can't download the OAB (new configuration since the OAB move), thanks to Kleptomainia: Results tab: Autoconfiguration has started, this may take up to a minute Autoconfiguration found the following settings: Display Name: Shenan Stanley Protocol: Exchange RPC Server: email2.tees.tamus.edu Login Name: shenans Availability Service URL: https://teesmail2.tees.tamus.edu/ews/exchange.asmx OOF URL: https://teesmail2.tees.tamus.edu/ews/exchange.asmx OAB URL: https://teesmail2.tees.tamus.edu/oab/f74d99ce-79ab-46ac-bf10-f1c7583faf98/ Unified Message Service URL: https://teesmail2.tees.tamus.edu/UnifiedMessaging/Service.asmx Auth Package: Unspecified Protocol: Exchange HTTP Server: teesmail2.tees.tamus.edu Login Name: shenans SSL: Yes SSL: Yes Mutual Authentication: Yes Availability Service URL: https://teesmail2.tees.tamus.edu/EWS/Exchange.asmx OOF URL: https://teesmail2.tees.tamus.edu/EWS/Exchange.asmx OAB URL: https://teesmail2.tees.tamus.edu/oab/f74d99ce-79ab-46ac-bf10-f1c7583faf98/ Auth Package: Basic Certificate Principal Name: msstd:teesmail2.tees.tamus.edu LOG tab: Autodiscover to https://tees.tamus.edu/autodiscover/autodiscover.xml starting Autodiscover to https://tees.tamus.edu/autodiscover/autodiscover.xml FAILED (0x800C8203) Autodiscover to https://autodiscover.tees.tamus.edu/autodiscover/autodiscover.xml starting Autodiscover to https://autodiscover.tees.tamus.edu/autodiscover/autodiscover.xml succeeded (0x00000000) Results tab: Autoconfiguration has started, this may take up to a minute Autoconfiguration found the following settings: Display Name: Shenan Stanley Protocol: Exchange RPC Server: email2.tees.tamus.edu Login Name: shenans Availability Service URL: https://teesmail2.tees.tamus.edu/ews/exchange.asmx OOF URL: https://teesmail2.tees.tamus.edu/ews/exchange.asmx OAB URL: https://teesmail2.tees.tamus.edu/oab/f74d99ce-79ab-46ac-bf10-f1c7583faf98/ Unified Message Service URL: https://teesmail2.tees.tamus.edu/UnifiedMessaging/Service.asmx Auth Package: Unspecified Protocol: Exchange HTTP Server: teesmail2.tees.tamus.edu Login Name: shenans SSL: Yes SSL: Yes Mutual Authentication: Yes Availability Service URL: https://teesmail2.tees.tamus.edu/EWS/Exchange.asmx OOF URL: https://teesmail2.tees.tamus.edu/EWS/Exchange.asmx OAB URL: https://teesmail2.tees.tamus.edu/oab/f74d99ce-79ab-46ac-bf10-f1c7583faf98/ Auth Package: Basic Certificate Principal Name: msstd:teesmail2.tees.tamus.edu LOG tab: Autodiscover to https://tees.tamus.edu/autodiscover/autodiscover.xml starting Autodiscover to https://tees.tamus.edu/autodiscover/autodiscover.xml FAILED (0x800C8203) Autodiscover to https://autodiscover.tees.tamus.edu/autodiscover/autodiscover.xml starting Autodiscover to https://autodiscover.tees.tamus.edu/autodiscover/autodiscover.xml succeeded (0x00000000) On one that was configured before the OAB was moved, the only difference was in the Log tab: Attempting URL https://teesmail2.tees.tamus.edu.autodiscover/autodiscover.xml found through SCP Autodiscover to https://autodiscover.tees.tamus.edu/autodiscover/autodiscover.xml starting Autodiscover to https://autodiscover.tees.tamus.edu/autodiscover/autodiscover.xml succeeded (0x00000000)

Mike, Here is one more peice of information. From the synchronization of a newly configured Outlook 2007 PC: 15:37:03 Microsoft Exchange offline address book 15:37:03 Not downloading Offline address book files. A server (URL) could not be located. 15:37:03 0X8004010F Besides enabling the Web OAB, is there configuration to IIS7 that also needs to be done?

Hi, Thanks for your prompt response and detailed information. Firstly, regarding the message: Attempting URL https://teesmail2.tees.tamus.edu.autodiscover/autodiscover.xml found through SCP I would like to explain it is normal that you do not get the message when connecting to Exchange server through RPC over HTTP. The SCP record is only used when a domain-connected client connects to Exchange Server. Obviously, the external client which connects through RPC over HTTP is not able to query Active Directory to get the SCP record. Instead, it uses following two URL connect to autodiscover service as show in your Test E-mail AutoConfiguration log: https://domain.com/autodiscover/autodiscover.xml https://autodiscover.domain.com/autodiscover/autodiscover.xml In addition, from your test result, I notice the Outlook Anywhere is able to get the OAB URL to download OAB files. Therefore, I think the issue does not relate to the Autodiscover Service. Base on the current situation, I suggest you firstly check the following two points: 1. Whether the problem client is able to resolve the FQDN (teesmail2.tees.tamus.edu) into your external IP address correctly. 2. If the FQDN (teesmail2.tees.tamus.edu) can be resolved correctly, please attempt to connect the following URL from the problem client: https://teesmail2.tees.tamus.edu/oab Please let me know whether any Certificate related warning/error is encountered. Mike

NSLOOKUP resolves the external address fine. We get a 403 - Forbidded: Access is denied message when going to the OAB directory - we never are prompted for credentials. Is this normal?

I think the behavior is not normal. According my test environment, we should be asked for user/password. At this time, would you please let me know whether the Outlook 2007 is able to view others Free/Busy information through RPC over HTTP? I would like to explain Outlook 2007 gather others Free/Busy information from the following URL: https://teesmail2.tees.tamus.edu/EWS/Exchange.asmx Therefore, if the Free/Busy information can be gathered with no problem, I think we need to focus on the OAB virtual directory. 1. Please help me check whether any computers/IP addresses are denied to access the OAB virtual directory. Note: I attempt to access the URL (https://teesmail2.tees.tamus.edu/OAB) from my end. I am asked for username and password. Therefore, would you please let me know whether you attempt to access the URL from a remote problem client. 2. Please run following command to gather configuration on the OAB virtual directory: Get-OABvirtualdirectory |fl Mike

I give up. I get different results depending on which client computer I use for testing, even though they are configured identically. I will block out time on my calendar and call support on Thursday. I appreciate your attempts to help, but I have got to get this to work.

After working with Technical Support, here is what it took to fix the client issues downloading the OABs. First, some background information. We use an alias email system where the campus email gateway then looks up our address adn then forwards it to our Exchange system. FOr everyone who uses that alias, there are 2 email addresses, the id@tamu.edu alias address and also the id@domain.name.edu address. Typicaly, the user has their alias set as the reply to address. All of this screws autodiscovery completely in several ways, adn without letting autodiscovery setup Outlook Anywhere, it won't work. In addition, our certificate request for our CAS server was done correctly, but the certificate we got back from our authority was munged - specifically, it did not have the autodiscover.domain.name.edu listing, so we also get certificate errors. Not a show-stopper, but an added hassle in configuration. So, here are the steps required to make an account get configured for Outlook Anywhere. I hope this helps somebody else. I see lots of folks asking for help, calling MS support, then not sharing the answer, so here goes: Go to the Exchange 2007 GUI adn set the user's reply to address to their id@domain.name.edu (not their alias). Go to Control Panel, Mail, and create a new email profile, filling in the name, id@domain.name.eduemail address and password In my case until I get the certificate fixed, answer yes to the prompt about name not matching on the certificate, since autodiscover is missing Autodiscover successfully configures the profile, and click Finish Run Outlook, login in and let it get the cache filling process started Go to Tools, Send/Receive, Download Address Book and choose Full Download, and it works Go back to the GUI and reset the Reply To address back the the alias - and OAB downloading still works Apparently the reply to address being the id@domain.name.edu is critical during autodiscovery, and possibly during the first OAB download, but after that, it can be set back to the alias with no ill effects. I hope this helps someone out there!

Yes, this fixed my problem. My default policy was just "@domain.com" and i changed it to user@domain.com. In this case, user was first name last name initial, like mikeh I didn't have to apply the default policy, just set it correctly. I tested it on one existing profile, and one new profile, It worked for both of them. Both can downlaod the offline address book, oab.