Oab not updating cached mode
When you update an Offline Address Book on the Exchange server via the Exchange Management Console or the Exchange Management Shell, one would suspect that updating the Outlook client after that would directly get you this fully up-to-date copy. After the OAB gets updated on Exchange, it still needs to distributed to the web services first, even in a single server environment.The process of updating and distributing the OAB is achieved by the following two schedules.Renaming just a single or some of the files will result in an OAB corruption. A benefit of manually deleting the oab-file is that before they are being re-downloaded, you are working with the Online Address Book.
While changing rebuild schedule for the OAB isn't recommended by Microsoft, but you may wish to make the change.Hello Exchange Experts, I have one user whose mailbox was created about a week ago that is not showing up in the global address list in Outlook.Here is what I have done to troubleshoot the issue: 1. Thanks, Nick Have you tried seeing this user from different Outlook profiles, or just your own?nothing you do from server side or client would fix it for us, but deleting the OAB locally and letting it rebuild was the only way we could get it to work. If the name is not seen in any outlook then you got to check on the server 2.Run the below command and check if addresslistmembership attribute has the value "\Default Global Address List" Get-Mailbox | Select addresslistmembership 3.
Search for oab not updating cached mode:
Due to various synching schedules, it can take up to 48 hours before you could actually see a change in Outlook after a modification has been made on the Exchange server or in Active Directory.