Managing Failover Clusters with Windows PowerShell (Part 2)

Start by firing up Windows PowerShell and importing the failover clusters module.

image

To get a list of commands available for the failover clusters module (or any other module), use the get-command cmdlet with the module parameter, as shown below:

image

You can get help on any particular command using the get-help cmdlet and specifying the name of the cmdlet, as shown below:

image

You can add the –detailed or –full parameters to get-help for more information, example: get-help test-cluster –detailed

To test a cluster configuration either before or after implementation, you can run the test-cluster cmdlet. The –list parameter lists all available tests.

image

You can include and exclude tests using the –Include and –Ignore parameters respectively.

image

In the one-line command below, I include only the validate software update levels check and specify a destination filename for the report (notice it is missing the .mht file extension in the first command). Then I invoke the report in the default browser, separating each command with a semi-colon:

image

In part 3 of this series I will cover adding resources to a cluster and managing virtual machines, including scripting live migration. It’s going to be awesome!

Popular posts from this blog

Get local computer UUID/GUID using Windows Powershell

Use the following syntax to get the local computer's UUID/GUID using Windows Powershell: get-wmiobject Win32_ComputerSystemProduct  | Select-Object -ExpandProperty UUID Add -computername after the WMI class to find a remote computer's UUID, example: get-wmiobject Win32_ComputerSystemProduct -computername RANTPC | Select-Object -ExpandProperty UUID
Read more

gPLink and gPOptions

gPLink is a property for sites, domains and organisational units that contains a prioritised list of GPOs linked to the node. gPOptions is a property that contains all Block Policy Inheritance settings for the node. To manage GPO links on a node, you must have read and write access to the gPLink and gPOptions properties.
Read more

PSLoggedOn Getting Started on Windows Server 2008 R2

Image
PSLoggedOn is a tool I downloaded to allow me to find out which computers a user is currently logged on to. Getting it up and running wasn’t exactly easy. I’m running a Windows Server 2008 R2 test environment. The first error I encountered was: Error browing network: The list of servers for this workgroup is not currently available. Note: I kept the spelling mistake from the error message to make it easier to find via search engines. To get past this error, you have to enable and start the “Computer Browser” service. Then I started getting the error telling me that the Administrator is not logged on. That’s simply not true because I am logged onto another server (Name: ELARA): I turned the firewall OFF OFF OFF (It is a test network after all). I enabled Network Discovery and to do that I went on a service starting frenzy: DNS Client, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host, Computer Browser After all that, I ran the script against the se
Read more