Commercial GAL segregation wasn’t been Supported in Exchange 2003 and Exchange 2007
It was supported in HMC 4.5 in Exchange 2007, Where you got to buy a license for it separately
In Exchange 2007 only Internal GAL segregation was supported as per the white paper
http://technet.microsoft.com/en-us/library/bb936719(v=exchg.80).aspx
In spite of more complications
Exchange 2010 Hosting was introduced But No Upgrade will be provided by Microsoft
http://blogs.technet.com/b/exchange/archive/2011/10/13/future-of-hosting-mode.aspx
Now Exchange 2010 SP2 or later is the one of the Best solution for GAL segregation commercially and internally which is more efficient and easy it implement.You need to Perform Some Check Lists before going into implementation of Address Book Policies
1. Address book Policies will work only on Exchange 2010 Service Pack 2 or later.
2. Exchange 2010 should not be installed on a GC or DC , Especially Client Access Server
(Address book policies won’t work for Outlook but It will work for OWA alone,)
3.Any Client Device or Client Software access Active Directory directly for Directory Access then ABP won’t work Like , Outlook is hard coded to GC & Entourage 2008
4. Outlook clients should be at least – Outlook 2007, Outlook 2010
Outlook 2003 with Latest Service pack does recognize Address book policies but we might face little complications , its my personal experience ,Like , login credentials should be the exact same as the Email Credential
Those are the most important Check lists before you going to implement it
Now will Explain how to Deploy Address book policies in Different Scenarios as per the TechNet
Before Getting into Address book Policies we should first plan how we are going to Segregate the users
There are Various filters you can use to segregate users ,
Refer Link – http://technet.microsoft.com/en-us/library/bb738157%28EXCHG.80%29.aspx
But we have something called Custom Attributes
We have 14 Custom attributes where we can use to Segregate users
Personally , Segregation is much more easier and Easily manageable using Custom attributes
In Simple Words Experts Prefer Custom Attributes
Now will explain how to segregate users in the below scenario
Scenario 1: Two Separate Companies in One Exchange Organization
First we will plan to segregate the Users
For Organization A , I will use Custom attribute1
Custom attribute1 = OrgA
For Organization B , I will use Custom attribute2
Custom attribute2 = OrgB
We got to Create a Separate Address book policy for Every Organization.
Organization A people should not see Organization B People in their Global Address list
We got to Create 4 things for the Organizations to Implement Address Book Policies
1. Global Address list
2. Address list
3. Rooms list
4. Offline Address book
Once we create that we can Assign it to the Users , Every User can have only one Address book policy.
1. Creating a Global Address list
Need Exchange Management Shell to create Global Address list ,
Where users with Custom attribute 1 with value ORGA , Only they will show up in the Global Address list
New-GlobalAddresslist "Organization A" –ConditionalCustomAttribute1 "OrgA" –IncludedRecipients "AllRecipients"
2 . Creating a Address list
Where users with Custom attribute 1 with value ORGA , Only they will show up in the Address list
Creating a New Address list for ORGA users
Setting the Domain as Default Domain
Setting the Custom Attribute1 value as ORGA
Now Address List have been Created Successfully.
3. Creating a Rooms list
New-AddressList -Name ORGA-Rooms -RecipientFilter {(Alias -ne $null) -and (CustomAttribute1 -eq "ORGA")-and (RecipientDisplayType -eq 'ConferenceRoomMailbox') -or (RecipientDisplayType -eq 'SyncedConferenceRoomMailbox')}
4. Creating Offline Address book
Have a keen look at it , Am not using GUI , Because I want to have the users see the New GAL which I have created for Organization A
Using GUI , I won’t have an option to add the New GAL created
New-OfflineAddressBook -Name "ORGA-OAB" -AddressLists "Organization A"
Created Offline address book Successfully
Am not going to use PF distribution in the OAB properties in the GUI cause there is no Outlook 2003 clients.
If you still have it , Go ahead and check that option , Make sure you have a PF database
Now Going to Create an Address book Policy for Organization A users
Created an Address book policy successfully !!
Now will Learn how to Apply Custom attributes for Users and other Active Directory objects
Open Exchange Management Console – Recipient Configuration – Mailbox – Properties of User Mailbox
You can have the Custom Attribute 1 Value Set for One User for Testing Purposes
Or
You can run in Exchange Management Shell
Get-mailbox "User1" | Set-mailbox –customattribute1 "ORGA"
To apply for all the mailboxes –
Get-mailbox | Set-mailbox –customattribute1 "ORGA"
To apply for the Users in a Specific Database –
Get-mailbox –database "Database Name" | Set-mailbox –customattribute1 "ORGA"
Example –
Allocated OrganizationA users in ORGA-Database
Applying the Custom Attribute in bulk for ORGA users
To Apply for one Distribution group –
Get-DistributionGroup "Group1" | Set-Distributiongroup –customattribute1 "ORGA"
To Apply for one Dynamic Distribution Group –
Get-DynamicDistributionGroup "Group1" | Set-Distributiongroup –customattribute1 "ORGA"
Now to View and Understand Better – Click on View – Add/Remove Columns
Choose Custom Attributes which you want to view in Recipient Configuration
Now you can see the Custom Attribute Values to the Assigned Users
Now we can Apply Address book Policy for a Specific User
Exchange Management Console – Recipient Configuration – Mailbox – Properties of User Mailbox – Mailbox Settings – Address Book Policy
To apply in Bulk for all the Users in a Database
Get-mailbox –Database "Database Name" | set-mailbox –addressbookpolicy ORGA-ABP
Now Logging into OWA as Test1-ORGA am seeing ORGA users alone in the Global Address list
Now Logging into Outlook as Test1-ORGA am seeing ORGA users alone in the Offline Address book
Now Coming in to Email Addresses for the organizations
If you are planning to Give Different Domain Names for this Organizations
Custom attributes will make things Simple for us
First we will Create a Accepted Domain for ORGA –
Clicking on New will get the Accepted Domain Ready
Now will create a Email Address Policy where it will Stamp only for ORGA users
Now stamping Email Address for only ORGA users, CustomAttribute1 – ORGA
Now Choosing the Accepted Domain –
Now you can see that our OrgA users are Stamped with ORGA.com
Great !!
Now ORGA is Ready
Lets make the ORGB ready – Its just the same thing but am going to use CustomAttribute2 as ORGB and going to use Commands as you are familiar now
As We know already we need to Create 4 things for an Organization to Implement Address Book Policies
1. Global Address list
2. Address list
3. Rooms list
4. Offline Address book
1. Global Address list
Creating a Global Address list
Need Exchange Management Shell to create Global Address list ,
Where users with Custom attribute 1 with value ORGA only will show up
New-GlobalAddresslist "Organization B" –ConditionalCustomAttribute2 "OrgB" –IncludedRecipients "AllRecipients"
2. Address list
New-Addresslist ORGB-AL –ConditionalCustomattribute2 ORGB –IncludedRecipients "AllRecipients"
3. Rooms list
New-AddressList -Name ORGB-Rooms -RecipientFilter {(Alias -ne $null) -and (CustomAttribute2 -eq "ORGB")-and (RecipientDisplayType -eq 'ConferenceRoomMailbox') -or (RecipientDisplayType -eq 'SyncedConferenceRoomMailbox')}
4. Offline Address book
New-OfflineAddressBook -Name "ORGB-OAB" -AddressLists "Organization B"
Now will Create an Address Book Policy –
New-AddressBookPolicy -Name "ORGB-ABP" -AddressLists "\ORGB-AL" -OfflineAddressBook \ORGB-OAB -GlobalAddressList "\Organization B" -RoomList "\ORGB-Rooms"
To apply in Bulk for all the Users in a Database –
Get-mailbox –Database "ORGB-Database" | set-mailbox –addressbookpolicy ORGB-ABP
Now Login into Outlook web app as Test1-ORGB am seeing ORGB users alone in the Global Address list
Now Logging into Outlook as Test1-ORGB am seeing ORGB users alone in the Offline Address book
New-AcceptedDomain –name “ORGB.com” –DomainName “ORGB.com” –DomainType “Authoritative”
Now Creating an Email Address Policy
Great !
Now Both the Organizations are Ready
And They have been Segregated with different GlobalAddresslist
Will Get Back with More Interesting Scenarios !!
New Series Available for Exchange 2010/2013/2016 – Office365 –
How to Implement Address Book Policies in Office 365/Exchange 2013/2016 Effectively
How to Implement Address Book Policies in Office 365/Exchange 2013/2016 Effectively – Part 2
How to Implement Address Book Policies in Office 365/Exchange 2013/2016 Effectively – Part 3
