One of our employees did not get updates for the offline address book (OAB) from the Exchange server. However, all those PC had no problem showing that contact on the list.
One person was missing from there and it was just one PC that had this issue. Internet suggested 0x8004010F being a common problem and proposed tons of things to do. The Exchange was 2007 SP1, previously upgraded from 20 before that, and our clients were running Outlook 2003/2007 with latest updates.
Many steps were taken to find what is happening and how to solve it, and I'm not going to waste your time on each.
Instead, here is a list, which helped, with some It was quite a long journey for me to get it right!
If autodiscover records aren't published, your administrator will need to publish them so Outlook can find the account. If you want to use Outlook 2016 with an Exchange account, you'll need to let Outlook set the account up automatically.
This OST to PST Converter is not only easy-to-use ost recovery application but also powerful converter tool to convert corrupt or damaged file to file.
A user was trying out the new Office 2016 and ran into a problem.
He wanted to configure his Exchange account manually, by entering the server names, but Outlook 2016 doesn't have that option for Exchange accounts: I recently upgraded to Office 2016 from Office 2013 and the Exchange account wouldn't work.
When I disable cached mode, I see the updated address book. This happens on more than one computer/user account.
Now you would wonder why it is showing Exchange 2013 OAB name. This is one of the OMG situation because you saw the warning that you can’t install Exchange 2013 any more while updating active directory and Exchange 2013 is there.