Windows Server Failover Clustering (WSFC)
  • 08 Mar 2022
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Windows Server Failover Clustering (WSFC)

  • Dark
    Light
  • PDF

Windows Server Failover Clustering (WSFC) is a feature of the Windows Server platform for improving the high availability (HA) of applications and services. WSFC is the successor to Microsoft Cluster Service (MSCS).

NOTE

Types of Assets Fetched

This adapter fetches the following types of assets:

  • Devices

Parameters

  1. Failover Cluster Domain (required) - The hostname or IP address of the Windows Server Failover Clustering (WSFC) server.
  2. User Name and Password (required) - The credentials for a user account that has the Required Permissions to fetch assets.
  3. Verify SSL (required, default: False) - Verify the SSL certificate offered by the value supplied in Failover Cluster Domain. For more details, see SSL Trust & CA Settings.
    • If enabled, the SSL certificate offered by the value supplied in Failover Cluster Domain will be verified against the CA database inside of Axonius. If the SSL certificate can not be validated against the CA database inside of Axonius, the connection will fail with an error.
    • If disabled, the SSL certificate offered by the value supplied in Failover Cluster Domain will not be verified against the CA database inside of Axonius.
  4. HTTPS Proxy (optional, default: empty) - A proxy to use when connecting to the value supplied in Failover Cluster Domain.
    • If supplied, Axonius will utilize the proxy when connecting to the value supplied in Failover Cluster Domain.
    • If not supplied, Axonius will connect directly to the value supplied in Failover Cluster Domain.
  5. For details on the common adapter connection parameters and buttons, see Adding a New Adapter Connection.

image.png

Required Ports

  • 135(RPC)
  • 445 (SMB)
  • Random port in the range 1024-65535

Setting up a fixed port for WMI

The WSFC adapter uses WMI.
You need to set up a fixed port to work with WMI.
WMI runs as part of a shared service host with ports assigned through DCOM by default. However, you can set up the WMI service to run as the only process in a separate host and specify a fixed port. For more details, see Microsoft Documentation - Setting Up a Fixed Port for WMI.



To set up a fixed port for WMI:

  1. At the command prompt, type:
winmgmt -standalonehost
  1. Stop the WMI service by typing:
net stop "Windows Management Instrumentation"

or:

 net stop winmgmt
  1. Restart the WMI service again in a new service host by typing:
net start "Windows Management Instrumentation" 

or:

net start winmgmt
  1. Establish a new port number for the WMI service by typing (e.g. the following example will establish port TCP 24158):
netsh firewall add portopening TCP 24158 WMIFixedPort



To undo any changes you make to WMI, type:

winmgmt /sharedhost

Then stop and start the winmgmt service again.

Required Permissions

The value supplied in User Name and Password must be able to execute PowerShell code which queries the WSFC server for information on the systems managed by that server.
The supplied User Name must have the following permissions:

  • Access RPC on the WSFC server.
  • Execute PowerShell on the WSFC server and access the IPC$ share on the WSFC server.
  • Access ADMIN$ share on the WSFC server (preferred permissions).
  • RSAT-Clustering-PowerShell must be installed on each system to be queried.

Version Matrix

This adapter has only been tested with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.

Version Supported Notes
Windows Server 2012 R2, Windows Server 2012 or newer Yes



First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.