- Introduction
- Windows Clustering 101
- Forest Creation Process
- Installation
- Installation of Root Domain
- Quality Assurance
- Forest Preparation, DNS, and Exchange
- Installation of Bridgehead Servers and the Child Domain
- Installing DHCP and WINS Services
- Patching and Updating Domain Controllers
- Exchange Domain Preparation
- Creation of Initial Service and Administration Resources
- Clustering
- Time-Out
Installation
Upon installation of the support server to the isolated network, proceed to the installation procedures.
Rack and stack your servers in the production racks or on the data center floor with access to the isolated network.
Power up the support/installation server.
Log on to the installation server as Administrator on the isolated subnet.
Reset the Administrator password.
Change the IP configuration to statically assigned addressing.
Assign the IP address of 10.10.20.23 (on a /22 subnet where the 10.10.20.0 space is reserved for the data center servers).
Assign the same IP address as the gateway and DNS.
Install DHCP and configure the new scope for the subnet (see Table 6.3).
At this point, the installation and provisioning of the support server is complete.
Table 6.3 Example Configuration of DHCP on the Support Server
Scope |
Split |
Excluded Range |
Default Gateway |
CIDR |
WINS |
DDNS |
10.10.20.0 to 10.10.20.254 |
NA |
10.10.20.1 to 10.10.20.20 |
NA |
/22 |
10.10.20.23 |
10.10.20.23 |
After the DHCP server has been installed on the support server, reserve IP addresses for the root domain controllers. This ensures the root DCs obtain the correct IP addresses as soon as their IP configuration is changed from static addressing to DHCP-assigned.
One note to consider before we move on: The subnet we have used here will provide sufficient addresses to meet the needs of a high availabilty network. Don't short change yourself with IP addresses. You should be good to go with a subnet that provides more than a thousand IP addresses. High availability systems use a lot of IP addresses. A typical two-node cluster should be allocated a block of about 24 addresses for future expansion.