Cisco Cisco IP Contact Center Release 4.6.1 Release Note
Enterprise ICM Child Domain Model
Staging Tasks
In this model of deployment, the Enterprise or Parent Forest/Root Domain must already be in place and the
customer must supply the Enterprise Forest administrator rights in order to create the ICM Child Domain.
customer must supply the Enterprise Forest administrator rights in order to create the ICM Child Domain.
Staging of an Enterprise ICM Child Domain must be done on site, with full network access to the Parent
Domain. A Cisco Certified Integration Partner can source and pre-stage the ICM Servers as “standalone”
prior to shipping them to the customer’s production locations. The ICM Servers must be Domain Members
and have network connectivity to the Child Domain Active Directory Domain Controllers. The Child
Domain Active Directory Domain Controllers, in turn, must have network connectivity to the Parent
Domain Active Directory Domain Controllers.
Domain. A Cisco Certified Integration Partner can source and pre-stage the ICM Servers as “standalone”
prior to shipping them to the customer’s production locations. The ICM Servers must be Domain Members
and have network connectivity to the Child Domain Active Directory Domain Controllers. The Child
Domain Active Directory Domain Controllers, in turn, must have network connectivity to the Parent
Domain Active Directory Domain Controllers.
Cisco also recommends that the ICM Child Domain provide DNS services locally within that domain.
The Visible Network Card, on the First Domain Controller created in the Child Domain, must temporarily
have the DNS Settings point to an Enterprise Level (Parent) DNS Server until a DNS Server is available at
the Child Domain level.
have the DNS Settings point to an Enterprise Level (Parent) DNS Server until a DNS Server is available at
the Child Domain level.
The Staging Tasks for a Child Domain are similar to the
First, follow Steps 1-3 featured on
of this document.
Note: The following caveat applies to step 2. The Visible Network Card, on the First Domain Controller
created in the Child Domain, must temporarily have the DNS Settings point to an Enterprise Level (Parent)
DNS Server until a DNS Server is available at the Child Domain level.
created in the Child Domain, must temporarily have the DNS Settings point to an Enterprise Level (Parent)
DNS Server until a DNS Server is available at the Child Domain level.
Now, continue by following the instructions below.
1. Click
Start > Run and enter DCPROMO. The Active Directory Installation wizard opens.
2. Under “Domain Controller Type,” select “Domain Controller for a New Domain.” The “Create
Tree or Child Domain” screen appears.
3. Select “Create a New Child Domain in an Existing Domain Tree.”
4. On the Network Credentials Screen, enter your username, password and fully qualified domain
name for the Parent (Forest Root) domain.
5. For the Child Domain Installation.
o
Enter the full DNS name of the Parent Domain.
o
Under Child Domain, enter the NETBIOS name for the Child and the full DNS name enters
at the bottom of the screen.
at the bottom of the screen.
6. Accept the Database and Log Locations defaults.
7. Accept the Shared System Volume default. You configure this server as a DNS Server in a later
step.
8. On the “Permissions” screen, select “Permissions compatible with pre-Windows 2000 servers.”
9. For “Directory Services Restore Mode Administrator Password,” enter the Administrator
password, as detailed in the 3
rd
Party Host Form.
10. Restart when the installation completes.
11. Delete the Child Domain subfolder on the Parent Level DNS Servers.
When the ICM Child Domain is created, Windows automatically creates a “subfolder” in the Enterprise
Root DNS tree as a container for the servers in the new Child Domain. Typically, these folders are
only used for a small number of servers, for ease of management and administration. Delete this
subfolder and create an individual DNS Zone by following the instructions below.
Root DNS tree as a container for the servers in the new Child Domain. Typically, these folders are
only used for a small number of servers, for ease of management and administration. Delete this
subfolder and create an individual DNS Zone by following the instructions below.
Step 5: Install DNS Server on First Domain Controller for Child Domain
Release 6.0(0) Staging on Windows 2000
47
47