Windows OS Hub
  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu

 Windows OS Hub / Windows Server 2016 / Windows Server 2016: Workgroup Failover Cluster without Active Directory

May 3, 2018 Windows Server 2016

Windows Server 2016: Workgroup Failover Cluster without Active Directory

In older Windows Server versions prior to Windows Server 2016, you could create a failover cluster only between the servers in the same Active Directory domain. The new version allows to create two- (or more) nodes failover cluster between servers joined to different domains, and even between workgroup servers (not AD domain joined) – a so-called Workgroup Cluster.

Obviously, Windows Server 2016 has to be installed on all cluster nodes. The following cluster scenarios are supported:

Service Status Comment
SQL server Supported It is recommended to use the integrated SQL Server authentication
File server

 

Supported, but not recommended Kerberos authentication for SMB is not supported
Hyper-V

 

Supported, but not recommended Live Migration is not supported, only Quick migration is available
Message Queuing (MSMQ) Not supported MSMQ stores its properties in Active Directory

 

On all future cluster nodes, you have to:

  1. Install Failover Clustering role: Install-WindowsFeature Failover-Clustering –IncludeManagementTools<
  2. Create a local account with the administrator privileges (or use the integrated administrator account) with the same passwords:
    net user /add clustadm Sup33P@ssw0Rd!
    net localgroup administrators clustadm /add
    powershell install Failover Clustering feature on workgroup servers
  3. If the error Requested Registry access is not allowed appears, edit the remote UAC parameter in the registry (this parameter enables the remote access to the administrative shares):
    New-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -Name LocalAccountTokenFilterPolicy -Value 1
  4. Set the same primary DNS suffix. It enables the cluster servers to communicate each other by FQDN names. setting the same primary dns suffix
  5. Uncheck Register DNS connection addresses in the Advanced TCP/IP Settings.dont register connection in dns
  6. Make changes to hosts file so that the servers could resolve the names of other cluster members and the name of the cluster (including FQDN names). You can add the names to c:\windows\system32\drivers\etc\hosts as follows:
    Set file="%windir%\System32\drivers\etc\hosts"
    echo 192.168.1.21 clust-host1 >> %file%
    echo 192.168.1.21 clust-host1.mylocal.net >> %file%
    echo 192.168.1.22 clust-host2 >>  %file%
    echo 192.168.1.22 clust-host2.mylocal.net >> %file%
    echo 192.168.1.20 cluster1 >> %file%
    echo 192.168.1.20 cluster1.mylocal.net>> %file%

hosts file with cluster nodes addresses

To validate cluster nodes, you can use the following command:

test-cluster -node "clust-host1.mylocal.net"," clust-host2.mylocal.net"
To create a cluster using PowerShell, run this command:

New-Cluster -Name cluster1 -Node clust-host1.mylocal.net, clust-host2.mylocal.net -AdministrativeAccessPoint DNS -StaticAddress 192.168.1.20

Now you can check the status of the cluster and its components with the help of get-cluster and get-clusterresource cmdlets.

To connect (and remotely manage) the cluster through a GUI, you need to use Failover Cluster Manager snap-in (included in RSAT for Windows 10).

Now, using Connect to cluster menu item, you can connect to the created cluster. If the cluster has even number of servers, you will have to configure a witness resource. Note that you cannot use the SMB shared folder as a quorum witness. Two modes are supported: Disk Witness — a shared disk (with the simultaneous access to it from both nodes), or Cloud Witness — a cloud disk resource in Azure.

3 comments
0
Facebook Twitter Google + Pinterest
previous post
VSS Writer Failed: Re-registering VSS Writers on Windows Server
next post
Error 0x0000007e: Windows cannot connect to network printer, Operation failed

Related Reading

Fix: Remote Desktop Services Is Currently Busy

March 15, 2023

Configuring User Profile Disks (UPD) on Windows Server...

February 6, 2023

Fix: The Requested Certificate Template is Not Supported...

January 9, 2023

PowerShell: Unable to Resolve Package Source

December 14, 2022

How to Install and Configure Free Hyper-V Server...

November 22, 2022

3 comments

Akhmet May 21, 2019 - 6:38 am

What is the purpose of creating the user “clustadm” ?

Reply
admin May 21, 2019 - 8:25 am

This local account needs to be provisioned on the all cluster nodes (with the same password) for mutual authentication in order to add nodes to the cluster or to create a new WSFC cluster.

Reply
Jay August 10, 2022 - 3:38 pm

When I follow this step:

Uncheck Register DNS connection addresses

.. the machine loses network access entirely, and since it’s a VM I have to reimage it. Any idea why this happens?

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange Server
  • Microsoft 365
  • Azure
  • Windows 11
  • Windows 10
  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016
  • PowerShell
  • VMWare
  • Hyper-V
  • Linux
  • MS Office

Recent Posts

  • How to Run Program without Admin Privileges and Bypass UAC Prompt?

    March 24, 2023
  • Configure Network Settings on Windows with PowerShell: IP Address, DNS, Default Gateway, Static Routes

    March 24, 2023
  • Exchange Offline Address Book Not Updating in Outlook

    March 21, 2023
  • Attaching Host USB Devices to WSL or Hyper-V VM

    March 20, 2023
  • Sending an E-mail to a Microsoft Teams Channel

    March 17, 2023
  • How to Restore Deleted Users in Azure AD (Microsoft 365)?

    March 16, 2023
  • Fix: Remote Desktop Services Is Currently Busy

    March 15, 2023
  • Send-MailMessage: Sending E-mails with PowerShell

    March 14, 2023
  • Clear Cache and Temp Files in User Profiles on Windows (RDS) with PowerShell and GPO

    March 13, 2023
  • Prevent Users from Creating New Groups in Microsoft 365 (Teams/Outlook)

    March 6, 2023

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • Managing Printers and Drivers with PowerShell in Windows 10 / Server 2016
  • Windows Server Licensing for Virtual Environments
  • Configuring SSO (Single Sign-On) Authentication on Windows Server RDS
  • Installing a Free Let’s Encrypt TLS/SSL Certificate on IIS Web Server / RDS
  • “Downloading updates 0%” Issue on Windows Server 2016 and Windows 10
  • Anonymous File and Printer Sharing Without Password in Windows 10 / Server 2016
  • The Disk is Offline Because of Policy Set by an Administrator
Footer Logo

@2014 - 2023 - Windows OS Hub. All about operating systems for sysadmins


Back To Top