Owner's Manual
Tosetuptheobjectsforthismultipledomainscenario,performthefollowingtasks:
1. Ensure that the domain forest function is in Native or Windows 2003 mode.
2. Create two Association Objects, AO1 (of Universal scope) and AO2, in any domain. The figure shows the objects in Domain2.
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. GroupUser1andUser2intoGroup1.ThegroupscopeofGroup1mustbeUniversal.
6. Add Group1 as Members in Association Object 1 (AO1), Priv1 as Privilege Objects in AO1, and both RAC1 and RAC2 as Products in AO1.
7. Add User3 as Members in Association Object 2 (AO2), Priv2 as Privilege Objects in AO2, and RAC2 as a Product in AO2.
For Server Administrator or IT Assistant, the users in a single Association can be in separate domains without needing to be added to a universal group. The
following is a very similar example to show how Server Administrator or IT Assistant systems in separate domains affect the setup of directory objects. Instead
of RAC devices, you'll 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. Figure9-4 shows how to set up the Server Administrator Active Directory objects
for this example.
Figure 9-4. Setting Up Server Administrator Active Directory Objects in Multiple Domains
Tosetuptheobjectsforthismultipledomainscenario,performthefollowingtasks:
1. Ensure that the domain forest function is in Native or Windows 2003 mode.
2. Create two Association Objects, AO1 and AO2, in any domain. The figure shows the objects in Domain1.
3. Create two Server Administrator Products, sys1 and sys2, to represent the two systems. Sys1 is in Domain1 and sys2 is in Domain2.
4. Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (Administrator) and Priv2 has Login privileges.
5. Group sys2 into Group1. The group scope of Group1 must be universal.
6. Add User1 and User2 as Members in Association Object 1 (AO1), Priv1 as Privilege Objects in AO1, and both sys1 and Group1 as Products in AO1.