Start with SQL Server 0 AlwaysOn first (AD domain vs. dns)

As business grows, companies need to improve their data security and performance needs, so they need to pre-research new technologies (first mining pits), and do technical accumulation:

Learn about AlwaysOn failover Clustering (hot standby), data Routing (ICX), Moebius (data routing for Morris)

decided to test Microsoft's proposed high availability AlwaysOn

Test environment:

Software preparation

(1) SQL Server 2012

(2) Windows Server - R2 DataCenter

(3) Vmware-workstation 12.0,vmware-workstation 14.0

Operating system: All Windows Server R2 DataCenter 64-bit (WIN2012/WIN2012R2 only DataCenter version to use failover clustering)

Computer name

Domain Control: long-ad

node1:long001

node2:long002

node3:long005

Failover cluster VIP is not the same as an AlwaysOn VIP

Failover cluster VIP (192.168.0.87) is used by a cluster that lets you connect to failover Cluster Manager instead of letting you connect to AlwaysOn

AlwaysOn VIP (192.168.0.97) is the one that lets you connect to AlwaysOn

So failover cluster VIP is not the same as AlwaysOn VIP!

Steps

Use Step by step to show how to install the domain control

Note: Turn off the firewall of each machine first (the virtual machine network is simply set to the bridge mode to the common network with the host)

Domain Control terminal

1, configure the domain control IP,ipv6 removed, because the DNS server is installed on the domain control, so the preferred DNS server completed: 127.0.0.1 loopback address

2. Install AD Domain Services

3. Install the. NET Framework 3.5 feature (prevent pit after installation, of course, can be installed later)

4. Note install the. NET Framework 3.5 Feature (Specify alternate path and installed system disk, red line)

5. Start installing the. NET Framework 3.5 features and domain environment

6. While the AD domain service is installed, the operating system installs the DNS server at the same time (click the small banner in the upper-right corner of Server Manager, and click "Promote this server to a domain controller" to promote domain control)

7. Configure DNS (go to the AD Domain Services Configuration Wizard, set the domain name long. com)

8. Set the DSRM password to 123456

The domain controller for the root domain of the first domain tree in the default forest must serve as a global catalog server and must have the DNS service installed, not a read-only domain controller

9. Next error, prompt condition not satisfied

10. You need to open the local security policy setting

11. Disabling passwords must meet complex requirements and re-step

12.NetBIOS name Default

The AD DS database file path remains the default, and of course, putting the log files and database files on separate disks helps improve performance, and more information can be learned in the last two books of this article

15. Note that the Administrator account does not have a password set to meet the prerequisites

14. After installing AD DS, the server will be restarted automatically after restarting the server and opening the DNS Manager

You can see that dynamic is turned on

Within the _tcp folder,_ldap Records and _gc records indicate that the server is properly registered as a domain controller and serves as a global catalog server

Note : If there are no records related to _LDAP records and _GC records within the _tcp folder, restart the Netlogon service to re-register

15. Check whether the AD domain service and the Netlogon service are starting properly

16. To add domain user dcadmin to AD users and computers, be sure to remember the password for dcadmin, since the second and third sections are required to dcadmin this domain user

Note: If the default Administrator local computer account on the domain-controlled machine is not disabled, after you install the domain control, Administrator local account will be moved from the local SAM local account to the domain account (this account is no longer present in the local account, unless the domain control is downgraded) administrator

At this time other non-domain control machine can use Administrator domain account to log in, but we generally do not use Administrator domain account, but create a new domain user to do, here is another new Dcadmin account

Detailed view of the Windows Server2012 System Configuration Guide Book

Create Dcadmin complete

17. Dcadmin assigned to new domain users, Domain Admins and computer administrators

18. Turn Off computer updates

Client

1, set the client IP,ipv6 Remove, note to set up the gateway, disable NetBIOS on TCP/IP

2. Add domain, fill in the domain name long.com, and enter just the AD domain user (dcadmin) and password

Add domain before the best in the client first ping DNS (long.com) and domain-controlled IP, see if it can ping, if the ping does not pass, the domain must be unsuccessful, need to further troubleshoot why Ping does not pass

Need to check the firewall first, is usually a firewall problem

After the domain is added, the host and IP address of the newly added machine can be seen in the domain controlled DNS Manager

The client computer restarts automatically after the domain is restarted, and when you log on to the computer using a local administrator user, do not log on to the computer with the Dcadmin domain user first .
The configuration of another two client computers is not described here, the steps are the same

Finally, the DNS and AD computers containers are viewed in the domain control, and two nodes have been added successfully

Reference to the Great God Information

Start with SQL Server 0 AlwaysOn first (AD domain vs. dns)