![]() ![]() When implementing ABPs, Microsoft recommends to use custom attributes (1-15) instead of the standard Active directory Attributes. ![]() Note also that you can enforce ABP in your Lync client (for more information see source link at bottom of the article). You can implement this restriction through Transport rules. It’s important to understand that the ABPs will not prevents users within one virtual entity to send mail to other users located in a different virtual entity. If you are not using this feature, you can always create an empty one and associated it to the ABP you are creating. In fact, you should know that a ABP is a combination of the following elements :Īll ABPs must contains a room address list. In order to implement this GAL segregation, Address Book policies approach consists of creating custom Address List objects. If not, have look here to see how to install SP2Īddress Book policies offers a way to segment Global Address list and to present different address lists to different entities within your Exchange 2010 Organization. Note : In this post, we assume that you have already installed the service pack 2 within your organization. So, in this post, we will have a quick look on how to use this ABP feature. When we’ve started the deployment of the Exchange infrastructure, we were using Exchange 2010 SP1 and at that time there was no way to segregate Address Lists. I was particularly interested in this feature because in one of my project, there was a need to divide the organization into multiple virtual entities. This Service pack introduces a new feature called Address Book Policies (ABPs). In a previous post, we have mention that Exchange Service Pack 2 was available for download. ![]()
0 Comments
Leave a Reply. |