Shulou(Shulou.com)06/02 Report--

More than 10 years ago, I studied domain controllers on windows2003 and ended in failure. For so many years, domain controllers have been a nightmare for me. Even though I have successfully deployed them in the production environment today, I still don't quite understand many details. Due to limited energy, I can only go so far as to deploy horizon7.1, and more details will be studied in practice.

There are a few important points to figure out before deployment:

1. Root domain name: if it is only used in private network environment, it is recommended to use xxx.local or xxx.internal.

2, DNS server: I directly deploy to the domain controller, the advantage is that it can do dynamic resolution, do not have to join the domain of every computer to manually resolve the domain name.

3. In production environment, at least two domain controllers should be deployed to ensure redundancy. It is recommended to put them in different vsphere hosts and different storage.

Deployment steps:

I. installation services

1. Change the full name of the computer to DC1 and restart.

2. Add roles and functions, and select AcitveDirectory domain service and DNS service.

3. Then go on to the next step until the installation.

Configure the domain controller

1. Promote the server to a domain controller

2. Add a new forest and configure the xxx.local domain name

3. I don't know what the password is for. Follow the default configuration.

4. Proceed to the next step by default

5. The location of the file here is recommended to be placed in different locations. It is said that it has something to do with performance. I will only partition and put the D disk.

6. Continue the next step by default until the installation is complete and restart the computer

Third, check the configuration

1. The computer was successfully joined to the domain

2. DNS parses the address of dc1

3. Dc1 is the domain controller

4. Configure the preferred DNS of the network card as the native IP address and the standby DNS as the IP address of DC2.

Deploy the second domain controller

1. If you are a virtual machine cloned with vmware, there will be a big pit waiting for you to promote the domain controller later, prompting you to repeat SID.

2. Open "run" and enter "sysprep" to find the tool, follow the figure below, restart and reset the password and network.

3. Change the full name of the computer to DC2, change the preferred DNS to the IP address of DC1, and restart.

4. Repeat DC1 operations, add roles and functions, and select active Directory domain service and DNS service.

5. Then go on to the next step until the installation.

Fifth, configure the second domain controller

1. Add the domain controller to the existing forest, where there is also a pit, and enter the password of xxx\ Administrator,DC1 for the user name. Otherwise, it will prompt "you must provide the user account name".

2. Default configuration, continue to configure password

3. Select dc1.xxx.local here

4. Continue to configure the directory

5. Default to the next step until the computer is restarted.

Check the configuration of the second domain controller

1. Change the DNS setting of DC2. First, DNS configures the IP address of DC2, and the alternate DNS configures the IP address of DC1.

2. Check whether the configurations of the two domain controllers are synchronized.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.