https://docs.microsoft.com/en-us/archive/blogs/josebda/mapping-cluster-exe-commands-to-windows-powershell-cmdlets-for-failover-clusters-extended-edition

The following default resource types are included with all failover clusters. Cluster Name DFS Replicated Folder DHCP Service Distributed File System Distributed Network Name Distributed Transaction Coordinator File Server Generic Application Generic Script Generic Service IP Address IPv6 Address IPv6 Tunnel Address iSNS Message Queuing Message Queuing Triggers Physical Disk Print Spooler Scale Out File Server Storage Pool Task Scheduler Virtual Machine Virtual Machine Configuration Virtual Machine Replication Broker WINS Service Cloud Witness Health Agent Storage Policies Storage QoS Policy Manager Virtual Machine Cluster WMI **Windows Server 2008 R2 and Windows Server 2008:  ** The following resource types are not supported: DFS Replicated Folder Distributed File System Distributed Network Name File Server iSNS Message…

Using the Windows Server Failover Clustering WMI provider from within script is a simple approach to avoid dealing with the complexities of the clustering native C APIs, however WMI does has some limitations.  In this blog I am going to discuss the impersonation of the security contexts.  Since WMI uses DCOM to communicate to the remote machines it is limited to impersonation issues imposed by DCOM and the domain policies.  More information about impersonation and delegation is available at: http://msdn2.microsoft.com/en-us/library/ms680054(VS.85).aspx For security reasons, many domains impose a policy which allows only a single remote impersonated connection.  Therefore, additional remote connections cannot impersonate the connection.  Unfortunately, with the nature of clustering being…

WMI Service First check that the ‘Windows Management Instrumentation’ Service has started on each node by opening the Services console on that node.  Also check that its Startup Type is set to Automatic. WBEMTest or directly on the server ·         Launch CMD · CMD > WBEMTest ·         The Windows Management Instrumentation Tester will launch ·         Select Connect ·         Namespace: Root\MSCluster ·         Select Connect o   If you see more options available, it means you are connected and WMI is working §  Feel free to try a query to confirm, such as selecting ‘Query’ and enter: SELECT * from MSCluster_Resource o   If you see an error, there is a WMI issue PowerShell or remotely…

Service principal name (SPN) of “MSClusterVirtualServer” from deletion Get-NetAdapterBinding | Where-Object {$_.DisplayName -eq “Microsoft Failover Cluster Virtual Adapter Performance Filter”} | FT Name,DisplayName,Enabled Get-netadapter | Disable-NetAdapterBinding -DisplayName “Microsoft Failover Cluster Virtual Adapter Performance Filter”

Windows Server Failover Cluster Log Generating the Cluster.log  Get-ClusterLog   => The output looks like for all node in the cluster:  The Cluster.log files can be found in the \cluster\reports directory (usually c:\windows\cluster\Reports) on each node.  You can use the –Destination parameter to cause the files to be copied to a specified directory with the Server’s name The time stamps default to UTC (which some people call GMT) For instance, if you are in that time zone and a problem occurred at 1:38pm (13:38), UTC time stamp in the cluster log would be (21:38) The –UseLocalTime parameter for Get-ClusterLog causes the cluster.log to write timestamps that are already adjusted for the server’s time zone instead of using UTC Tip: The sections of the…

This is a sample of the event you will see in the System Event Log in Event Viewer: One specific problem that I have seen a few times lately is with the VMXNET3 adapters dropping inbound network packets because the inbound buffer is set too low to handle large amounts of traffic. We can easily find out if this is a problem by using Performance Monitor to look at the “Network Interface\Packets Received Discarded” counter. Once you have added this counter, look at the Average, Minimum and Maximum numbers and if they are any value higher than zero, then the receive buffer needs to be adjusted up for the adapter.…

The CLIUSR account is a local user account created by the Failover Clustering feature when it is installed on Windows Server 2012 or later. Well, that’s easy enough, but why is this account here? Taking a step back, let’s take a look at why we are using this account In the Windows Server 2003 and previous versions of the Cluster Service, a domain user account was used to start the Cluster Service. This Cluster Service Account (CSA) was used for forming the Cluster, joining a node, registry replication, etc. Basically, any kind of authentication that was done between nodes used this user account as a common identity. A number of…

Quite a while back I wrote a blog on a new functionality in Windows Server 2008 Failover Clusters called ‘file share scoping’ (http://blogs.technet.com/b/askcore/archive/2009/01/09/file-share-scoping-in-windows-server-2008-failover-clusters.aspx). I was informed recently that our Networking Support Team refers to this blog frequently when working with customers who are migrating to Windows Server 2008 Failover Clusters and discover that CNAME (Canonical Names) records in DNS, that had been in-place to support their Windows Server 2003 File Server clusters, no longer work with Windows Server 2008 Failover Clusters. Users keep asking if there is a way to disable this functionality or if it can be changed by adding a registry key or something. At this time, there…

What is a Microsoft Failover Cluster Virtual Adapter anyway? A question often asked is, “What is the Microsoft Cluster Virtual Adapter and what can I do with it?” The typical, and correct answer, is to leave it alone and let it just work for you. While that answer satisfies most, others may want just a little more by way of an explanation, so hopefully, this blog will provide that. The networking model in Windows Server 2008 Failover Clustering was rewritten to accommodate new functionality which included being able to obtain IP addresses from DHCP servers and being able to locate Cluster nodes on separate, routed subnets. Additionally, communications went from…