You can't use hierarchical address books (HABs) and ABPs simultaneously. You can run Exchange 2013 server roles on a global catalog server and have ABPs work correctly, however we don't recommend installing Exchange on a domain controller. Doing so results in Active Directory being used for Name Service Provider Interface (NSPI) instead of the Microsoft Exchange Address Book service. Teachers can see all other teachers and the principal.ĭistribution groups are created for each class's parents and the faculty.ĪL_ClassAAL_AllTeachersAL_AllGroupsAL_PrincipalĬonsider the following when using ABPs in your organization:įor ABPs to work correctly, the user mailbox to which you apply the ABP must be on an Exchange 2010 SP3 or an Exchange 2013 server.ĭon't run the Exchange 2010 Client Access server role on the global catalog server. Teachers can only students in their own classrooms. Students in each class can only see other students in their class, their teacher, and the principal. The Education scenario has the following characteristics: This scenario is applicable to schools or universities where a division of class rooms is necessary to ensure the privacy of the students. The CEO can create distribution groups that span both companies and will be visible within each company's GAL, but members of the distribution group will only be able to view the members of the group that are within their own organization. When the CEO is added to the distribution groups in each organization and falls within the scope of each company's ABP, then the CEO becomes visible to each company. Three ABPs are created: Fab, Tail, and CEO. They won't see groups not in their own company. Users who look at the CEO's group membership will only see groups that belong to the user's company. In each company, there is a SeniorLeaders distribution group that includes the senior leaders of that company and the CEO. The users in Fabrikam can only see Fabrikam users when they browse the GAL. The users in Tailspin Toys can only see Tailspin Toys users when they browse the GAL.
This scenario requires three ABPs that have the following characteristics: The CEO is the only common person between the two companies. In this scenario, Fabrikam and Tailspin Toys share the same Exchange organization and the same CEO. Because the two companies are separate without any interaction between the two, there aren't any address lists in common. The Contoso and Humungous Insurance ABPs were created using the following address lists, global address lists, room lists, and OABs, which were created using a recipient filter that grouped the objects with a filter such as Custom Attribute. In addition, no users will be members of distribution groups that span the entire organization. In this scenario, two address book policies (ABPs) are created where employees can only see members of the same organization when the view the GAL or look at membership of other distribution groups. In addition, the divisions don't have any special security or privacy concerns. This scenario is applicable to government agencies, divisions, or departments that share infrastructure, but no reporting chain and have no common employees. Scenario 1: Two separate companies - one Exchange organization The address lists and global address lists (GALs) in these scenarios were created based on filters, such as Custom Attributes, that grouped the objects logically. Although there are many more scenarios, the most popular ones are covered here. The following three scenarios describe possible deployment solutions for three different organization types. Applies to: Exchange Server 2013 Deployment Scenarios
0 kommentar(er)
