Windows server 2016 new cluster mode use detailed explanation

In Windows
Server 2012 R2 and earlier, creating a cluster can only be done in a member server of the domain environment. But in the Windows
Server 2016 release, this barrier was broken and the clustering model diversified. A failover cluster can be configured as: a single domain cluster, a multi-domain cluster, a workgroup cluster. The following describes creating a cluster mode that does not depend on Active Directory Workgroup.
1 Prerequisites
1.1 Single Domain Clusters
The prerequisites for single domain clusters are unchanged from earlier versions of Windows Server: All servers must be Windows Server 2016 All servers must have failover clustering installed. The server must use Microsoft certified hardware or a server device that has been tested for cluster verification. 1.2 Multi-Domain Clusters and Workgroup Clusters
In addition to the prerequisites for single-domain clusters, in multi-domain or workgroup mode, the following conditions exist: Create a new cluster or join to a cluster node, relying on a local account It needs to meet the following requirements: Create a local user account on each node of the cluster. The username and password must be the same on each node. The local account needs to belong to the local administrator group on each node. If a non-built-in is used. The local administrator (local administrator includes administrator) account creates a cluster and needs to set the registry policy LocalAccountTokenFilterPolicy to 1 on all cluster server nodes. Configuration using the Failover Cluster Management Console and tools is not supported. Configuration tasks can only be performed with Powershell. Multi-domain or workgroup creation Failover clusters cannot create any computer objects, so each cluster node needs a DNS network name and needs to have A DNS suffix 2 environment preparation
The above mentioned prerequisites for building a cluster, here use VMware Workstation software to build a test environment. Physical Machine Operating System
: Windows 10 Install Virtual Software: VMware Workstation Install VMware Server 2016 TP5 virtual machine on VMware Workstation, and enable Hyper-v and enable iscsI target server function. Three Environment Construction
Install two windows server 2016 virtual machines on VMware Workstation. Create a local account on each server (using the new local account test here, without the built-in administrator) and join the Administrators group to install the failover cluster feature on the server. To add functionality, click Install. The Failover Cluster Manager that opens after installation is as follows: On the server, run Windows PowerShell as an administrator. Enter the following command: New-itemproperty -path HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\System -Name LocalAccountTokenFilterPolicy -Value 1 Name the registry location in the lower left corner, add LocalAccountTokenFilterPolicy, the value is 1. Restart the server after entering the command. Creating a failover cluster in this mode does not create any computer objects, and all of the cluster nodes require a primary DNS suffix. Make sure that all nodes on the server use the same local user account, and that the username and password are the same on all nodes, and add to the Administrators group. The server is added with a DNS suffix to use a server to create two iscsI virtual disks. And let the two cluster servers connect to the shared disk for later testing because there is no DNS server in the environment, so add a record on the Hosts file to run Windows PowerShell as an administrator. Enter the following command: New-Cluster –Name <Cluster Name> -Node <Nodes to Cluster> -–StaticAddress <Cluster IP> -AdministrativeAccessPoint DNS. Creating a cluster Specifying the DNS type using the AdministrativeAccessPoint parameter so that you do not attempt to create a computer object when you create a cluster Open the Failover Cluster Console and you can see that the nodes of the two servers are joined to the workgroup cluster when you connect to the cluster. Four tests
Because the shared disk was created above, a Nano server virtual machine was built on the cluster for migration test 4.1 Live migration
Workgroup cluster does not support live migration, error during migration 4.2 Rapid migration
Workgroup clusters support fast migration tasks, can successfully migrate virtual machines. Five workloads and deployment recommendations
5.1 Workloads
The following table summarizes workloads for workgroups or multi-domain clusters

Cluster workload support/Details are not supported. SQL Server support recommends that you use SQL Server Authentication File Server support, but Kerberos (which is not available) is not recommended. Authentication is Server Message Block (SMB) traffic. Select the authentication protocol Hyper-V server support, but it is not recommended to support live migration, but support fast migration message queue (MSMQ) does not support message queue to store attributes in AD DS
5.2 Deployment Recommendations
Arbitration configuration: Workgroup clusters and multi-domain clusters recommend cloud witness or disk witness. File sharing witnesses are not supported. It is recommended that nodes in the cluster have a consistent structure. Multi-domain and workgroup cluster configuration deviations are more risky to deploy. Ensure that: All cluster nodes preferably use the same set of Windows patches. Try to use the same group policy. Ensure that all nodes in the cluster can be resolved on the authoritative DNS server.