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)
