- EXL302 Archiving and Discovery in Microsoft Exchange 2010 SP1 and Exchange Online (Krish Sundaresan)
- EXL305 Best Practices for Successfully Transitioning to Microsoft Exchange 2010 (Rand Morimoto)
- EXL306 Best Practices for Virtualization of Microsoft Exchange 2010 (Jim Lucey, Jeff Mealiffe)
- EXL307 Load Balancing with Microsoft Exchange Server 2010 (Andrew Ehrensing)
- EXL309 Microsoft Exchange Online in Microsoft Office 365: Migration Case Study (John Logan, Danny Kim, Ann Vu)
- EXL310 Microsoft Exchange Online in Microsoft Office 365: Simple Migration Live! (Ram Poornalingam)
- EXL311 Microsoft Exchange Server and Microsoft Office 365: How to Set Up a Hybrid Deployment (Jim Lucey)
- EXL312 Designing Microsoft Exchange 2010 Mailbox High Availability for Failure Domains (Ross Smith)
- EXL313 Microsoft Exchange Server 2010 Tips and Tricks (Scott Schnoll)
- EXL322 Microsoft Exchange Online: Unified Messaging in Microsoft Office 365 (Michael Wilson)
- EXL326 What’s New in Microsoft Exchange Server 2010 SP2: Featuring GAL Segmentation (Greg Taylor)
- EXL327 Real-World Site Resilience Design in Microsoft Exchange Server 2010 (Robert Gillies)
- EXL401 Exchange Server 2010 High Availability Management and Operations (Scott Schnoll)
An interesting post today on the Microsoft Exchange Team blog. Some, mainly large, organizations require the possibility of having creating different GAL (Global Address List) views or subsets. This way, users will be able to view a customized GAL with relevant addresses instead of the organization-wide GAL.
In Exchange 2007 (or earlier versions) customers had this possibility by implementing the Virtual Organizations and Address List Segregation whitepaper or utilizing Andy Grogan’s Address List Segregation Tool for example. Apparantly, Microsoft listened and are going to offer similar functionality as of Exchange 2010 SP2, which the article states is scheduled for Q3/Q4 2011.
The Exchange team speaks of a “Global Address Segmentation feature”, offering segmentation through the Exchange management interfaces, providing organizations a way to create views of the global address book. The mechanism for these views are called “Address Book Policies”, which are going to use an assignment model instead of the ACL-based GAL segmentation. Note that the team states that Address Book Policies won’t replace the tenant isolation feature found in Exchange 2010’s hosting mode. Address Book Policies are to be used to segment and grant access to GAL segments, with hosting mode tenants are isolated.
I wonder if it will be possible to assign multiple Address Book Policies to a user to create cumulative views. For example, the manager of two departments can view the assigned GALs of these departments as being his GAL. If not, you may be required to create a separate address book policy for each level of access which might pose an administrative challenge.
Another thing: I expect it may require some form of change or requirement on clients as well since address lists are contained in the LDAP://CN=All Global Address Lists,CN=Address Lists Container,CN=<Exchange Organisation>,CN=Microsoft Exchange,CN=Services,.. container. The Default Global Address List element in that container is often accessed through a hard-coded lookup on its name and since it resides in Active Directory I don’t see how Exchange 2010 SP2 will manage that.
But of course this is all speculation; how Address Book Policies will be implemented and what the consequences are for migrations from an ACL-based Exchange environment remains to be seen.
Note that because of this announcement, Andy Grogan has ceased development on an Exchange 2010 version of the Address List Segregation Tool. Also, Microsoft will not release an Exchange 2010 version of the Virtual Organizations and Address List Segregation document.