Windows Server R2 Enterprise AD domain Control server installation

Preface

1. For a server that will be installed as a DC, its system configuration and basic disk planning are not described here, but critical network connection properties must be noted. You can configure its IP properties by opening the properties of the local area connection. As the IP address of the server DC must be a static IP address, although you do not necessarily need to configure the default gateway, but the DNS server points to be configured correctly, because the work of ad is closely dependent on the DNS service. In this example, the entire Microsoft network environment is self-made, considering that the first DC as a DNS server in the corporate network, it is necessary to configure its preferred DNS server address as the IP address of this computer.

2. Because the WIN08R2 default firewall configuration is filtered based on the type of connection network, it is a good idea to change the public network whose network type is recognized by default to private network through network and Sharing Center.

3. Of course, in addition, the current computer's NetBIOS name, that is, the computer needs to be set up, because after the DC installation, it is not advisable to modify the operation.

4. The 1th means that before upgrading to domain control, the machine's IP, DNS, wins and other configuration is correct, if static, do not let the machine automatically get.
5. The 2nd is to choose a different network type, its firewall open port is not the same, public network firewall to consider security issues, open a few ports, more restrictions, so it is best to choose a private network.
6. Before upgrading to domain control, computer name to determine down, up to domain control, and then change the computer name can be unpredictable problems, so it is best to upgrade to domain control before the computer name is determined, and then do not change.

Windows Server R2 Ad Server Setup

I. Introduction to Windows AD

http://technet.microsoft.com/zh-cn/library/cc758535 (ws.10). aspx

Second, Windows server R2 AD build a detailed plot

    2.1 首先准备一台Windows server 2008 R2的计算机，此服务是要做域控制器的，如果是实际生产环境的话建议配置稍微高一点，测试环境满足按照Windows 2008 R2的最低要求就好了，注意了，Windows 2008 R2只有64位的版本，您老人家的机器最低也要支持64位。

2.2 Look at the system version, start running, Cmd,systeminfo, you can see the information

2.3 以管理员权限运行  -->  dcpromo略等片刻，就会出现以下界面了，上面有一个“使用高级模式安装”；直接点击下一步就可以了，刚入门的小菜鸟暂时不要点啦，稍后研究的深一点在进行操作。

2.4 Click Next

2.5 Click Next, we start to build the ad configuration phase, here you need to note that if you are the first to build your entire intranet in the first domain controller, then be sure to select the second item "new domain in the New Forest", The above item is used when there is an ad environment in your intranet and you want to build an additional domain controller.

2.6 After the next, configure the name of your domain, this should be careful, because this configuration after the change is very cumbersome, and the risk of domain renaming is not generally large;

2.7 After the next step, configure the functional level of your domain, children's shoes attention, it is important to note that if your ad in the future may appear in the Server 2003 system domain controller, be sure to select the domain functional level of 2003, or you later those server 2003 of the server can not do the domain controller, insurance, when the first DC installed, all choose a lower bar, the future to upgrade to 2008 of the domain functional level is no problem, but selected 2008 of the functional level, later to downgrade is difficult!

2.8 Click two times after the next step, you need to set up DNS.
After setting the domain functional level is your ad in the more important DNS server installation, by default is recommended DC and DNS installed on a server, DNS does not account for what resources, you do not have to worry about it consumes your server resources, and DC installed together can facilitate subsequent maintenance and data synchronization and backup, Highly recommended! In this step, the children's shoes must check the configuration of their servers, the server's DNS is pointing to their own, this is very important, or your DNS installation will be problematic. Check that the local DNS settings are consistent with the local IP address.

After 2.9 clicks the next step, will pop up a very scary warning, you still ignore it, point is! This is actually a matter of Windows Server, forget it! To study this warning of children's shoes, you can go to Microsoft TechNet Search, there is not much to say

3.0 over the DNS alarm flaming, we will start the end of the next configuration, the ad database files and log files, Microsoft installation Interface said the recommended installation in different locations, is simply nonsense, children's shoes This position do not change, all kinds of tests and the wrong find, All of Microsoft's configuration here is by default, you change the system with other systems when it is easy to make mistakes (this is true)

3.1 By default the next step is your old man to remember a password "domain restore password", this password is very important, follow-up database migration, backup, collation, recovery can be used, do not casually engage in a

3.2 After the next step is to check the configuration information of your entire DC, you can export to a location to keep up, for subsequent error checking, but also as a DC installation of the unattended installation of the script (AD unattended installation here does not say, interested children's shoes can go to find some relevant information to learn, Application is not very extensive)

3.3 After the next step is a few minutes waiting for you to be done

Windows Server R2 Enterprise AD domain Control server installation