Workgroup clusters for Windows Server 2016

Before Winows server R2, we must create the cluster in a member server of the domain environment. But breaking this rule in Windows Server 2016, there is no need to rely on ad or you can create a failover cluster in a workgroup.

The following types of clusters will be supported in Windows Server 2016:

• Single-domain cluster: Join all cluster nodes to the same domain

• Multi-domain clusters: cluster nodes in different domains

• Workgroup cluster: Workgroup node cluster (no domain)

So today we mainly introduce the workgroup cluster to everyone to see exactly what it is, but there are prerequisites for doing a workgroup cluster:

• All servers must be Windows Server 2016

• All servers must have the Failover Clustering feature installed.

• The server must use Microsoft-certified hardware or a server device that has been tested for cluster validation.

I will use this version of Windows Server TP4 to demonstrate that we need to do some configuration:

To create a new cluster or join a cluster node, local accounts need to meet the following requirements:

• Failover Cluster Management console and tools are not supported for configuration and can only be used with PowerShell

• Create a local user account on each node of the cluster

• The user name and password must be the same on each node

• The account needs to belong to the local Administrators group on each node

• If you create a cluster with a non-built-in local administrator account, you need to set the Localaccounttokenfilterpolicy registry policy for all nodes to 1. The built-in Administrator account contains administrator.

Run PowerShell as an administrator on each cluster node:

New-itemproperty-path Hklm:\software\microsoft\windows\currentversion\policies\system-name Localaccounttokenfilterpolicy-value 1

650) this.width=650; "height=" 273 "title=" clip_image001 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image001 "src=" http://s3.51cto.com/wyfs02/ M00/79/8c/wkiol1aumaij8vqfaafykgta5sg480.png "border=" 0 "/>

This is the location:

650) this.width=650; "height=" 377 "title=" clip_image002 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image002 "src=" http://s3.51cto.com/wyfs02/ M01/79/8e/wkiom1aul9vafhs-aah8ofa8xne851.png "border=" 0 "/>

Remember to restart the server when you are finished adding it.

Creating a failover cluster cannot create any computer objects, so each cluster node needs to have a DNS network name, and a DNS suffix is required

650) this.width=650; "height=" 484 "title=" clip_image003 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image003 "src=" http://s3.51cto.com/wyfs02/ M02/79/8e/wkiom1aul93ishlmaafg1ulsif4582.png "border=" 0 "/>

650) this.width=650; "height=" 280 "title=" clip_image004 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image004 "src=" http://s3.51cto.com/wyfs02/ M02/79/8e/wkiom1aul9_tkre3aacpxdyv-pa889.png "border=" 0 "/>

2 workgroup servers have a common DNS server address to register (or add a record themselves) that contains the DNS suffix. If you do not have a common DNS server to register, write the host record on each one.

Next we can deploy a workgroup cluster, and of course the steps for a workgroup cluster and a multidomain cluster are similar:

First we need to create a consistent local user on all nodes to ensure that the user name password is consistent and that the account belongs to the local Administrators group.

650) this.width=650; "height=" 268 "title=" clip_image005 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image005 "src=" http://s3.51cto.com/wyfs02/ M00/79/8e/wkiom1aul-gdp7gtaafkp8whim4237.png "border=" 0 "/>

650) this.width=650; "height=" "title=" clip_image006 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image006 "src=" http://s3.51cto.com/wyfs02/ M00/79/8e/wkiom1aul-lgy2ulaaei6zttqs8758.png "border=" 0 "/>

Ensure that all servers that need to join the cluster node have a DNS suffix

650) this.width=650; "height=" 430 "title=" clip_image007 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image007 "src=" http://s3.51cto.com/wyfs02/ M00/79/8c/wkiol1aumbsaexflaaddwghucq8078.jpg "border=" 0 "/>

Check if the protocol for the firewall response is open.

650) this.width=650; "height=" "title=" clip_image008 "style=" margin:0px;border:0px;padding-top:0px;padding-right : 0px;padding-left:0px;background-image:none; "alt=" clip_image008 "src=" http://s3.51cto.com/wyfs02/M02/79/8E/ Wkiom1aul-wypvf1aaa2spbs7jq181.png "border=" 0 "/>

650) this.width=650; "height=" 276 "title=" clip_image009 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image009 "src=" http://s3.51cto.com/wyfs02/ M00/79/8e/wkiom1aul-fqjttqaadzowyirja283.png "border=" 0 "/>

Creating a cluster uses Administrativeaccesspoint to specify the DNS type so that the cluster is created without attempting to create computer objects.

New-cluster–name <cluster name>-node <nodes to cluster>-–staticaddress <Cluster IP>-AdministrativeA Ccesspoint DNS

650) this.width=650; "height=" 136 "title=" clip_image010 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image010 "src=" http://s3.51cto.com/wyfs02/ M01/79/8c/wkiol1aumbjwojlsaaccsfxdqxq388.png "border=" 0 "/>

650) this.width=650; "height=" 231 "title=" clip_image011 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image011 "src=" http://s3.51cto.com/wyfs02/ M01/79/8c/wkiol1aumbmqda6raadfu9urqtg894.png "border=" 0 "/>

The following table summarizes the workload for a workgroup cluster:

650) this.width=650; "height=" 179 "title=" image "style=" margin:0px;border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/79/8E/ Wkiom1aumfqswmwdaadoc__0x_4679.png "border=" 0 "/>

Quorum configuration:

Witness types troops and workgroup clusters and multi-domain clusters recommend cloud witness or disk witness. File share witness is not supported.

The following information can be ignored in cluster validation:

• Cluster configuration-Verify resource status

• System configuration-Verify AD configuration

It is recommended that each node in the cluster use the same configuration, such as the same patch, the same policy, and so on.

Ensure that information for all nodes of the cluster can be resolved on authoritative DNS servers.

The get-clusterdiagnostics command is not supported for cluster diagnostics in a workgroup cluster.

When you open the Failover cluster console, you can see the workgroup cluster that we created.

650) this.width=650; "height=" 484 "title=" clip_image012 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image012 "src=" http://s3.51cto.com/wyfs02/M00/79/8E/ Wkiom1aul-yilrgjaagmwr-kpzk339.png "border=" 0 "/>

Well, let's share this with you today, if there is any wrong place also please point out, thank you.

This article is from the "Zjunsen Microsoft Virtualization" blog, so be sure to keep this source http://rdsrv.blog.51cto.com/2996778/1734152

Workgroup clusters for Windows Server 2016