Global address book not updating the 7 day dating and relationship
First, let’s go over what is happening and why it is and then we’ll go over how we can force the OAB (Offline Address Book) or GAL to update with these users.So, you added Joe Smith to the company and you’ve right-click updated the “All Users” address list so he can be included in distribution lists and so that he receives emails on dynamic distribution lists. But wait, Joe is not appearing inside the GAL/OAB you just updated! If you’re using the web distribution of the offline address book, the Exchange Client Access Server waits for a ‘polling time’ to arrive before it updates…just like any standard DFS (distributed file system) in Active Directory.Download and install the utility, then inspect your mail queues, monitor the Exchange server's memory, confirm there is enough disk space and check the CPU utilization. Solar Winds provides this fully-functioning freebie, as part of their commitment to supporting the network management community.Free Download of Solar Winds Exchange Monitor As an alternative to clicking in the Exchange Management CONSOLE, you could type commands in the Exchange Management SHELL.This is the master list of all the Exchange 2007 objects, and the operating system won't let you mess with it.Fortunately, there is a well respected work-around, create a new Global Address List, and then 'update' the mailbox. Here is a free tool to monitor your Exchange Server.Through trial and error, I’ve found out WHY the user is not put into the Global Address List right away and how you can force it there.Please note that I’m using Exchange 2007 with a separate CAS, HT, and Mailbox Server.
If using Outlook, query the GAL directly, or download the latest OAB. Before you do anything send the user you created a 'Test Email' from your own account.These are most likely users that have only recently been added…because the minute that Exchange does it’s standard maintenance window, it will most likely update.But what if, like me, you need to have it update right away due to something like a Black Berry server?Now that we know it isn’t working by design, how do we fix it? We do this through the Exchange Management Shell: Make sure you substitute in your Client Access Server where the OAB is distributed with ‘servername’ above.The overall process is basically the same as what Office Communications Server does, but with added flexibility of easily customizing some of the timing of the different events.