Get-DbaWsfcResourceType

Want to see the source code for this command? Check out Get-DbaWsfcResourceType on GitHub.
Want to see the Bill Of Health for this command? Check out Get-DbaWsfcResourceType.

Synopsis

Retrieves available resource types from Windows Server Failover Cluster for SQL Server FCI configuration.

Description

Retrieves detailed information about all resource types available in a Windows Server Failover Cluster. Resource types define what kinds of cluster resources can be created, including SQL Server instances, network names, IP addresses, and shared storage. This information is essential when configuring or troubleshooting SQL Server Failover Cluster Instances (FCI), as it shows which resource types are installed and their dependencies.

Returns resource type properties including display names, DLL locations, and required dependency relationships. This helps DBAs understand the available building blocks for creating clustered SQL Server resources and diagnose configuration issues.

All Windows Server Failover Clustering (Wsfc) commands require local admin on each member node.

Syntax

Get-DbaWsfcResourceType
    [[-ComputerName] <DbaInstanceParameter[]>]
    [[-Credential] <PSCredential>]
    [-EnableException]
    [<CommonParameters>]

Examples

Example: 1

PS C:\> Get-DbaWsfcResourceType -ComputerName cluster01

Gets resource type information from the failover cluster cluster01

Optional Parameters

-ComputerName

Specifies the target Windows Server Failover Cluster by providing either a cluster node name or the cluster name itself.
Use this when connecting to a specific cluster to retrieve its available resource types for SQL Server FCI planning or troubleshooting.
Defaults to the local computer name if not specified.

-Credential

Allows you to login to the cluster using alternative credentials.

-EnableException

By default, when something goes wrong we try to catch it, interpret it and give you a friendly warning message.
This avoids overwhelming you with "sea of red" exceptions, but is inconvenient because it basically disables advanced scripting.
Using this switch turns this "nice by default" feature off and enables you to catch exceptions with your own try/catch.