If the GAL is kept up to date, you might be ready to dial to the business phone and mobile phone.
This next post is going to talk in detail about GAL segmentation setup in Office 365.
The original idea was borrowed from this Microsoft blog post, but since not all of the steps were covered there in sufficient detail, I am expanding them here, and adding two specific examples: how to segment GAL based on distribution lists membership, and how to segment GAL based on Office attribute.
This morning I was asked to update the Global Address List and Offline Address Book in an Exchange environment.
You could wait for Exchange to do it automatically (the default schedule is once a day) but what when you want to force the update to take place right now?
It doesn’t matter if smartphone users are on the road, or in the office.
Mobile users on the corporate Exchange Server occasionally use the Global Address List (GAL).
There are four ways to view contacts in the i OS address book.
You can generate an email or invite someone to a meeting using the calendar.
When I look up the conference room in the Global Address List, it doesn't show up. So as I understood from our Sys Admin, the oab files are generated on one server, and rely on the file replication service on the global catalog servers (we have 2 of them) to copy the oab files to each of the servers.
However, if I delete my files (Offline Address Book) then I can see the new conference room in the Global Address List. The service was not started on one of the servers and therefore some users were getting old oab's while other users were getting fresh copies. if you're having this issue, make sure the file replication service is started. Chances are good that OAB generation is failing for some reason.
This blog dives into topics related to Unified Contact Management for smartphones in the enterprise.