New-itemproperty -path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -Name LocalAccountTokenFilterPolicy -Value 1īecause I used the Administrator to log in to Windows Server 2016, I skipped the execution of the above command and directly run the following PowerShell script: Note: If the account used to log in to the Windows Server 2016 server is not Administrator, you need to run PowerShell as an administrator and execute the following script: Because a domainless cluster has no graphical interface to set up, it can only be created using PowerShell. Step 6: On the DB1 node, run PowerShell as an administrator and use the script to create a Windows cluster. Pay attention to the position of the tick after the option. Set according to the red box in the figure below. Step 5: Set to allow applications or functions to pass through the firewall. The host file needs to perform the same operation on the servers of both nodes.
The hosts file can be opened with Notepadįor the server name, fill in the full name of the computer, that is, the server name with the DNS name suffix set before, for example:. The path of the hosts file: C:\Windows\System32\drivers\etc Step 4: Add the server IP address and name, cluster IP address and name, and listener IP address and name of each node in the hosts file of each node, as shown below. The purpose of adding this user is to allow 2 servers to access the shared folder.
Step 3: Add a user on each node (the user name I added is DCAdmin), and the user name and password are the same for each node. Step 2: The computer of each node does not need to join the domain, but the DNS suffix needs to be added, and the suffix of each node must be the same (for example: test.cn), as shown in the following figure.
Step 1: Install Windows failover cluster (all nodes need to be installed) One: First configure Windows failover cluster (both nodes are logged in with Administrator) There are: JF-SQLDB01\administrator on the SQL Server of node 1 JF-SQLDB02\administrator on the node 2 these 2 login accounts can be created when SQL Server is installed. The databases of the two nodes have the login name of Administrator, that is, when using Administrator to log in to the server, Windows authentication can be used to log in to SQL Server. The SQL Server 2016 service startup accounts of both nodes are set to Administrator. The Windos Server 2016 of the two nodes are logged in with the Administrator account, and the Administrator password of the two servers is the same, which has no special meaning, just to facilitate subsequent operations.ģ.
The operating systems, security patches, and SQL Server versions of the two servers must be completely consistent.Ģ. Only the Windows Server 2016 operating system can configure a domain-independent cluster. SQL listener name: JFSQL01 IP address: 10.2.218.133 ( virtual IP )ġ. Windows cluster name: JF-AlwaysOn IP address: 10.2.218.130 ( virtual IP ) Node 2 ( physical server or virtual machine ): JF-SQLDB02 IP address: 10.2.218.132 Node 1 ( physical server or virtual machine ): JF-SQLDB01 IP address: 10.2.218.131 (2) Install SQL Server 2016 on both servers (or SQL Server 2012) Operating system: Windows Server 2016 Datacenter
(1) 2 physical servers, or 2 virtual machines.
Let's step by step to configure the non-domain SQL AlwaysOn of 2 nodes Windows Server 2016 and SQL Server 2016 have been out for a while, because Windows Server 2016 can configure non-domain Windows clusters, so it can also be used to configure non-domain SQL Server AlwaysOn high availability.