Exchange 2007 and OAB error
 

So, in an effort to short-cut the many Technet articles and MSExchange.org posts i'd have to trawl through, I thought i'd post this query here for your edification :)

For several years i've run a MS Exchange 2003 front/back-end hosted pair of servers.
Recently I built Exchange 2007 servers next to them and migrated all the user mailboxes across, and pointed the HTTPS ports for the router at the new front-end server.
The old servers are still live, albeit with no mailboxes, but now the Outlook clients are getting the errors on send/receive indicating they can't download the OAB.
I've tried:

- Migrating the public folders across servers
- Configuring the new server to generate the OAB
- Rebuilt the OAB
- Configuring the OAB URLs to point correctly at the external address

....all to no avail.

Any ideas?

Bit advanced for your average PPRuNe readership ! :eek:

Disclaimer: I'm no Exchange guru...

What Outlook client version are you using ? 2k3, 2k7,2k10 ?

If 2k3 you might want to try deleting local offline OAB files.

Might also want to consider the steps in this thread : Outlook 2003 Offline Address book sync failed with error code 0X8004010F Exchange 2007

This might also be of interest :
Earlier Outlook clients cant connect to Exchange 2007 Server

Might also want to look at turning up logging

Something like ......

Set-EventLogLevel "MSExchangeSA\OAL Generator" -Level high

Followed by OAB recreation

Followed by

Get-EventLog Application | Where {$_.Category -eq "OAL Generator"}

Caveat emptor.

2k3 and 2k7. Not bothered unwrapping 2k10 yet :)

Bit difficult with ~80 geographically dispersed clients :)

It's definitely the 0x8004010F error. I've tried re-picking the OAB, but was holding off deleting and re-creating it for fear of having to re-visit the certificate signing of OAB delivery. That's reserved for last resorts!

Not applicable as the Exchange organisation was 2003 previously, so I was never asked the question upon install.

Cheers, think i'll try this first.

Does the issue occur with both.

Try one and then use the wonders of scripting ... :cool:


Good luck with the logging... looking forward to hearing how you get on.

Yup, and with brand new client installs as well as previously-established clients.