Recipient update service 2016 not updating when online dating isnt working
Analysis: You checked the Exchange log (Exchange Setup.log).
It showed: Error ONE: [2/16/2015 AM]  [ERROR] Unexpected Error [2/16/2015 AM]  [ERROR] The operation could not be performed because object ‘exchserver01’ could not be found on domain controller ‘adserver01.domain.com’. [2/16/2015 AM]  [ERROR] The Windows Firewall service must be started before Setup can continue.
There are at least two Recipient Update Services in an Exchange organization, the Enterprise RUS and the Domain RUS (one per domain).
Navigate to CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=First Organization/CN=Address Lists Container/CN=Recipient Update Services.
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.
While it hasn't been updated yet, it may still be applicable to Exchange 2013. Microsoft Exchange setup requires that each domain in the existing Exchange organization have an instance of the Recipient Update Service.
To resolve this you have two option, manually update the Address Book or customize the update schedule.
Last Updated: March 14, 2018 ISSUE After updating to Version 1803 (Build 9126.2072), you may find that when you open an existing meeting in the calendar and send an update with updated location the recipient still sees the old location.
You verify from the Domain Controller adserver01.that the Exchange server object is there.
You also verify that the Exchange Server is able to communicate with the adserver01.Error TWO: “.” You will need to remove the RUS manually.
You can confirm by reviewing the item in the Sent Items folder.