surroundings:
Two Win2k Server, configured as follows
1. Computer name: Server1
IP: 192.168.0.1
2. Computer Name: Server2
IP: 192.168.0.2
---------------- situation 1: single field, single field controller --------------
aims:
Do Server1 domain controllers, domain name TEST.COM, Server2 as MEMBER SERVER
The AD requires the support of DNS, and DNS can be installed in front of the AD installation, it is recommended to configure it in the AD installation and manually.
1A
) Install DNS (SERVER1)
1. Install the DNS service. (If you do DNS for ForeSTROOT, it is recommended to uninstall the original DNS on the machine, including the DNS directory under System32. Re-installation service)
2. Create Forward Lookup Zone for Test.com. Reverse lookup zone fills the network number 192.168.0
3
.
Set two zone allows Dynamic Update
4
.
Point DNS addresses in local connections 192.168.0.1
5. Set primary DNS Suffix for TEST.COM
6
.
According to the prompt, RESTART, it is recommended to have a certain weight.
Seduce
.
After restarting, it is found that there is a record of Server1 in TEST.COM, which means that everything is normal. PTR record in the reverse zone
(It should be noted that the domain name first and computer names should not be the same, if you don't do abc.com on your computer ABC, otherwise Domain's NetBIOS name and computer's NetBIOS name will be the same.
(1B)
According to normal DCPROMO, choose the domain controller, new tree, and new forest installed as a new domain.
No information such as "DNS can't find" during the installation process is normal.
After the AD is installed, see if there is four directories placed in the SRV record in the Test.com of the DNS. The directory is named TCP, UDP, MSDCS, and Sites. If one is not, restart the NET Logon service, if
Still not, there is a problem. It should generally be normal.
At the same time, check if there is any error log for Directory Service in the Event Viewer.
(1C) Set Server2 into Member Server
Point DNS to Server1 on Server2, modify Primary DNS SUFFIX to Test.com, stronger, then add Server2 to Domian, open the AD user and computer on Server1, where the Computer2 can be seen. Computer account. There is also a record of Server2 in the DNS. Check out the event viewer to ensure no bad records.
---------------- Act 2, single field, two domain controllers --------- Target: Server1 as the first domain controller, Server2 as Two domain controllers, domain name TEST.COM
The installation of Server1 is 1A, 1B.
For Server2.
(2A) 1. This machine is not related to the Domain or the working group before installation.
2. Point DNS to Server1 (192.168.0.1)
3. Modify Primary Suffix to Test.com (SUFFIX can be automatically changed, but manual reform is always rest assured)
4. Repeart the machine, it is recommended to have heavy.
5. Check the DNS on Server1, which will find the A record of Server2 within Test.com. If not, there is a problem with the configuration, you can use ipconfig / registerdns to manually register, and then do it, if there is still no, there is a problem (DNS is not set according to 1A).
(2b)
1. DCPROMO, launch wizard
2. Select, another domain controller installed as an existing domain
3. Follow the prompts, enter your identity, this identity is Enterprise Admins, which is now Test.com's Administrator and its password.
4. Select Domain to join, here is Test.com
5. Complete other options
(3C)
1. Computer account for Server1 and Server2 can be seen in Domain Controller OU in AD User and Computer (Ad U & C) after installation.
2. The four directories of the DNS Test.com (TCP UDP MSDCS Sites, which can be found in SRV records), which can be found in SRV records. If not, restart the Netlogon service on Server2, and you can try to re-register with IPCPNFIG / RegisterDNs.
3. You can add new objects on both domain controllers and then look at whether mutual replication is normal.
4. Of course, other tools such as DCDIAG, RepMonitor can be used to check some problems, but this is a simple post, I don't say it.
5. View the event viewer to ensure no bad records.
---------------- Avoid 3, a forest, a tree, two fields -------
After installation, there is a tree in the forest, two Domain: Test.com, Sub.Test.com, where Server2 is the SUB DC.
About TEST. COM installation method, still referring to 1A, 1B
Below is the DC of Server2 to Sub.Test.com.
(3A) DNS configuration 1. On the DNS of Server1 (simple practice), create a Sub.Test.com's zone, set up dynamic update to Yes
2. Point DNS of Server2 192.168.0.1
3. Modify Server2 Primary DNS Suffix for Sub.Test.com
4.
5. Find the a record of Server2 in Sub.Test.com this zone
(3B)
DCPROMO
2. Select the domain controller installed as a new domain - put it into a tree already existing
3. Fill in the identity information of Enterprise Admin (Administrator / Password / Test.com)
4. Out of an interface, let the fill the domain name, the top is the name of the parent domain (Test.com), fill in the Sub in the middle, the following is complete, display full name Sub.Test.com
5. Complete other options
(3C)
1. After completing, you can find a computer account of Server2 in the Domain Controller OU in Server2's AD User and Computer.
2. Srv record (four directories) about Server2 can be found in the Sub.Test.com of DNS, if not, register at 3C-2 method
3. Take a look at the SUB.TEST.com Domain in the Ad domain and trust tool on Server2 (there is a SUB under Test.com)
4. Open the AD Site and Service to see if there is all Site information, there is, indicating that the CONFIGURATION partition is roughly no problem.
5. View the event viewer to ensure no bad records.
6. There are other questions, ask questions to the forum ^ _ ^
---------------- - A situation 4, a forest, two trees, two fields ---------
After the installation is complete, Server1 is the DC of Test.com, Server2 is the DC of Lab.com.
(4A) Preparing
1. Create a lab.com this zone on the DNS of Server1, set up dynamic updates
2. Point DNS of Server2 192.168.0.1
3. Modify Server2 Primary DNS SUFFIX to Lab.com
4.
5. Find the a record of Server2 in Lab.com this zone
(4b)
DCPROMO
2. Select the domain controller installed as a new domain - a new tree - put it in an existing forest
3. Fill in the identity information of Enterprise Admin (Administrator / Password / Test.com)
4. Fill in the tree name to lab.com
5. Complete other options
(4C)
1. After completing, you can find a computer account of Server2 in the Domain Controller OU in Server2's AD User and Computer.
2. Lab.com in DNS You can find the SRV record (four directories) for Server2, if not, if not, the method of 3C-2 is registered once 3. Take a look at whether the Ad domain and trust tool on Server2 is available. Show Lab.com this Domain
4. Open the AD Site and Service to see if there is all Site information, there is, indicating that the CONFIGURATION partition is roughly no problem.
5. View the event viewer to ensure no bad records.
