Figure 3. Setting Up RAC Active Directory Objects In Multiple Domains
Setting Up RAC Active Directory Objects In Multiple Domain
To set up the objects for this multiple domain scenario, perform the following tasks:
1.
Ensure that the domain forest function is in Native mode.
2.
Create two Association Objects, AO1 (of Universal scope) and AO2, in any domain.
3.
Create two RAC Device Objects, RAC1 and RAC2, to represent the two remote systems.
4.
Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (Administrator) and Priv2 has Login
privileges.
5.
Group User1 and User2 into Group1. The group scope of Group1 must be Universal.
6.
Add Group1 as Member in Association Object 1 (AO1), Priv1 as Privilege Object in AO1, and both RAC1 and RAC2 as
Products in AO1.
7.
Add User3 as Member in Association Object 2 (AO2), Priv2 as Privilege Object in AO2, and RAC2 as a Product in
AO2.
Setting Up Server Administrator Active Directory Objects In Multiple Domains
For Server Administrator, the users in a single Association can be in separate domains and need not be in a Universal
group. The following is a very similar example to show how Server Administrator systems in separate domains affect the
setup of directory objects. Instead of RAC devices, you will have two systems running Server Administrator (Server
Administrator Products sys1 and sys2). sys1 and sys2 are in different domains. You can use any existing Users or Groups
that you have in Active Directory. The following figure shows how to set up the Server Administrator Active Directory
objects for this example.
72
Summary of Contents for Server
Page 1: ...Server Administrator Version 7 2 Installation Guide ...
Page 8: ...8 ...
Page 14: ...14 ...
Page 30: ...30 ...
Page 44: ...44 ...
