Recipient update service 2016 not updating
Then check the mailbox Exists (See Check for existence of mailbox sections below).1. The Mailbox SHOULD be in the right hand window (Providing you are in the correct administrative group, on the correct server, and in the correct mailbox store! Remember with Exchange 2007 / 2010 you create the mailbox with the Exchange system Manager anyway! On the Exchange Server, Start Ensure “Hide From Exchange Address Lists” is NOT ticked.
If you receive an error message then you can investigate further (Note: Set your Outlook client to send you a delivery report on the test email as well).
For web-based distribution make sure the site is up.
Exchange 2013/2016Exchange 2013/2016 will only be distributing the OAB via web-distribution. For all versions of Outlook (since 2003) you have two choices, either take Outlook out of cached mode* (so it queries the ‘live’ global address list).
You can confirm by reviewing the item in the Sent Items folder.
To resolve this issue, verify that an instance of the Recipient Update Service exists for each domain and create an instance of the Recipient Update Service for the domains that do not have one and then rerun Microsoft Exchange setup.So there are three factors stopping you seeing that new user on the GAL (, however if that’s not an option, read on). Force your Outlook Client to Download the Offline Address book. Check that the OAB is getting distributed from the Exchange/CAS server. Note: Make sure the Generation Server is set to a server that exists, and it’s online.Support for Outlook 2000 was dropped with Exchange 2007, Exchange 2010 only supports Outlook 2003 (post SP2). In the diagram below you can see this server is performing public folder AND web based distribution, this is probably because you ticked this box when you installed the product.Exchange 2013 only supports Outlook 2007 (post SP3 and cumulative update), and Outlook 2010 must be at SP1 with cumulative update. For public folder distribution ensure the public folder database is mounted, and at least one server holds a replica.Also in the properties of the mailbox database, your users are using, make sure it points to the correct public folder database.