If you change an ABP, the updated APB takes effect when a user restarts or reconnects their client app, or you restart the Mailbox server (specifically, the Microsoft Exchange RPC Client Access service in the backend services). When the ABP is created and assigned to the user, the ABP becomes the scope of the address lists that the user is able to view.ĪPBs take effect when a user connects to the Client Access (frontend) services on a Mailbox server. The user is assigned Address Book Policy A that contains a subset of address lists that are available in the organization. The following diagram shows how ABPs work. For more information, see Scenario: Deploying address book policies in Exchange Server. Implementing an ABP is a multi-step process that requires planning. For more information about address lists, see Custom address lists.įor procedures involving ABPs, see Procedures for address book policies in Exchange Server.ĪBPs create only a virtual separation of users from a directory perspective, not a legal separation. For more information, see Create and manage room mailboxes. It's not a room finder that you create with the RoomList switch on the New-DistributionGroup or Set-DistributionGroup cmdlet. Note that this room list is a custom address list that specifies rooms (contains the filter RecipientDisplayType -eq 'ConferenceRoomMailbox'). For more information about OABs, see Offline address books in Exchange Server. For more information about GALs, see Global address lists. The goal of an ABP is to provide a simpler mechanism for GAL segmentation (also known as GAL segregation) in on-premises organizations that require multiple GALs. Address book policies (ABPs) lets administrators segment users into specific groups to provide customized views of the organization's global address list (GAL).
0 Comments
Leave a Reply. |