Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Invoke-CauRun

Updated: August 15, 2012

Applies To: Windows Server 2012

Invoke-CauRun

Performs a scan of cluster nodes for applicable updates and installs those updates via an Updating Run on the specified cluster.

Syntax

Parameter Set: DefaultParamSet
Invoke-CauRun [[-ClusterName] <String> ] [[-CauPluginName] <String[]> ] [[-Credential] <PSCredential> ] [-CauPluginArguments <Hashtable[]> ] [-ConfigurationName <String> ] [-EnableFirewallRules] [-Force] [-MaxFailedNodes <Int32> ] [-MaxRetriesPerNode <Int32> ] [-NodeOrder <String[]> ] [-PostUpdateScript <String> ] [-PreUpdateScript <String> ] [-RebootTimeoutMinutes <Int32> ] [-RequireAllNodesOnline] [-RunPluginsSerially] [-SeparateReboots] [-StopAfter <TimeSpan> ] [-StopOnPluginFailure] [-WarnAfter <TimeSpan> ] [-Confirm] [-WhatIf] [ <CommonParameters>]

Parameter Set: RecoverParamSet
Invoke-CauRun [[-ClusterName] <String> ] [[-Credential] <PSCredential> ] -ForceRecovery [-Force] [-Confirm] [-WhatIf] [ <CommonParameters>]




Detailed Description

The Invoke-CauRun cmdlet performs a scan of cluster nodes for applicable updates and installs those updates via an Updating Run on the specified cluster. The Updating Run process includes the following:
- Scanning for and downloading applicable updates on each cluster node.
- Moving currently running clustered roles off each cluster node.
- Installing the updates on each cluster node.
- Restarting cluster nodes if required by the installed updates.
- Moving the clustered roles back to the original nodes.
The Updating Run process also includes ensuring that quorum is maintained, checking for additional updates that can only be installed after the initial set of updates are installed, and saving a report of the actions taken.

Note: To run this cmdlet with the PostUpdateScript or PreUpdateScript parameter, Windows PowerShell® remoting must be enabled on each node. To do this, run the Enable-PSRemoting cmdlet. In addition, ensure that the Windows Remote Management - Compatibility Mode (HTTP-In) firewall exception is enabled on each node.

Parameters

-CauPluginArguments<Hashtable[]>

Passes a set of name=value pairs (arguments) for each updating plug-in to use. For example, to specify a Domain argument for one plug-in:
- @{Domain=Domain.local}
You can specify multiple pairs in a set separated with semicolons. For example:
- @{name1=value1;name2=value2;name3=value3}
These name=value pairs must be meaningful to the CauPluginName that you specify.
If you specify arguments for more than one plug-in, provide the sets of name=value pairs in the order that you pass values in CauPluginName, separated by commas. For example:
- @{name1=value1;name2=value2;name3=value3},@{name4=value4;name5=value5}

For the default Microsoft.WindowsUpdatePlugin plug-in, no arguments are needed. The following arguments are optional:
- 'IncludeRecommendedUpdates'='<Value>': Boolean value to indicate that recommended updates will be applied in addition to important updates on each node. If not specified, the default value is 'False'.
- A standard Windows Update Agent query string that specifies criteria used by the Windows Update Agent to filter the updates that will be applied to each node. For a name, use QueryString and for a value, enclose the full query in quotation marks.
If not specified, then the Microsoft.WindowsUpdatePlugin plug-in by default uses the following argument:
- QueryString="IsInstalled=0 and Type='Software' and IsHidden=0 and IsAssigned=1"
For more information about query strings for the default Microsoft.WindowsUpdatePlugin plug-in and the criteria such as IsInstalled that can be included in the query strings, see the topic about search criteria in the Windows Update Agent (WUA) API Reference.

For the Microsoft.HotfixPlugin plug-in, the following argument is required:
- HotfixRootFolderPath: The UNC path to a hotfix root folder in an SMB share with a structure that contains the updates to apply and that contains the hotfix configuration file

The following arguments are optional for the Microsoft.HotfixPlugin plug-in:
- RequireSmbEncryption=<Value>: Boolean value to indicate that SMB Encryption will be enforced for accessing data from the SMB share. If not specified, the default value is 'False'. To ensure the integrity of the data accessed from the SMB share, the plug-in requires that the share is enabled for either SMB signing or SMB Encryption.
- DisableAclChecks=<Value>: Boolean value to indicate that the plug-in will check for sufficient permissions on the hotfix root folder and the hotfix configuration file. If not specified, the default value is 'False'.
- HotfixInstallerTimeoutMinutes=<Integer>: The length of time in minutes that the plug-in allows the hotfix installer process to return. If not specified, the default value is 30 minutes.
. - HotfixConfigFileName=<name>: Name for the hotfix configuration file. If not specified, the default name DefaultHotfixConfig.xml is used.

For more information about required and optional arguments for the Microsoft.HotfixPlugin plug-in, see the content about Cluster-Aware Updating plug-ins.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-CauPluginName<String[]>

Specifies one or more plug-ins to use when performing updates. You can specify multiple values separated with commas. The default is the Microsoft.WindowsUpdatePlugin plug-in. This plug-in coordinates the Windows Update Agent software resident on each cluster node, the same software that is used when updates are downloaded from Windows Update or Microsoft Update, or from a Windows Server Update Services (WSUS) server. For more information about how plug-ins work with CAU, see the content about Cluster-Aware Updating plug-ins.


Aliases

none

Required?

false

Position?

2

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-ClusterName<String>

Specifies the name of the cluster on which to install updates.


Aliases

none

Required?

false

Position?

1

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-ConfigurationName<String>

Specifies the Windows PowerShell session configuration that defines the session in which scripts (specified by PreUpdateScript and PostUpdateScript) and cmdlets are run, and can limit the cmdlets that are available to be run. If either a pre-update or post-update script is specified but a configuration name is not specified, then the default session configuration that is built into Windows PowerShell ("Microsoft.PowerShell") is used.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Credential<PSCredential>

Specifies the administrative credentials for the target cluster.


Aliases

none

Required?

false

Position?

3

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-EnableFirewallRules

Enables the Remote Shutdown Windows Firewall rule group on each cluster node, if it is not already enabled. If the EnableFirewallRules parameter is specified, CAU will also automatically re-enable the Remote Shutdown rule group each time the CAU clustered role performs an Updating Run, in case the rules are disabled manually in the intervening time. Enabling this rule group permits inbound communication to each cluster node during each Updating Run that allows CAU to shut down and restart the node remotely (if the installation of an update requires a restart). If Windows Firewall is in use on the cluster nodes and the rule group is not enabled, the Updating Run will fail. The Remote Shutdown Windows Firewall rule group is not enabled when it will conflict with Group Policy settings that are configured for Windows Firewall.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Force

Runs the cmdlet without prompting for confirmation. By default the cmdlet will ask for confirmation from the user before proceeding.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-ForceRecovery

Recovers from a previous failed run that left the cluster in a Locked state.
Note: This switch defeats the synchronization mechanism used to prevent two update coordinators from accidentally trying to update the same cluster at the same time. Use with care.


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-MaxFailedNodes<Int32>

Specifies the maximum number of nodes on which updating can fail. If one more than this number of nodes fails, then the Updating Run is stopped. The range is from zero (0) through 1 less than the number of cluster nodes. The default for most clusters is approximately one-third of the number of nodes.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-MaxRetriesPerNode<Int32>

Specifies the maximum number of times that the update process (including any pre-update and post-update scripts) will be retried per node. The maximum is 64 and the default is 3.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-NodeOrder<String[]>

Specifies the names of the cluster nodes in the order that they should be updated.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-PostUpdateScript<String>

Specifies the path and file name for a Windows PowerShell script to run on each node after updating finishes, and just after the node is brought out of Maintenance mode. The file name extension must be .ps1 and the total length of the path plus the file name must be no longer than 260 characters. As a best practice, the script should be located on a disk in cluster storage, or at a highly available network share, to ensure that it is always accessible to all of the cluster nodes.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-PreUpdateScript<String>

Specifies the path and file name for a Windows PowerShell script to run on each node before updating begins, and before the node is put into Maintenance mode. The file name extension must be .ps1 and the total length of the path plus the file name must be no longer than 260 characters. As a best practice, the script should be located on a disk in cluster storage, or at a highly available network share, to ensure that the script is always accessible to all of the cluster nodes. If a pre-update script fails, the node is not updated.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-RebootTimeoutMinutes<Int32>

Specifies the time in minutes that CAU will allow for the restarting of a node (if a restart is necessary). If the restart does not complete within this time, then the Updating Run on that node will be marked as failed.


Aliases

none

Required?

false

Position?

named

Default Value

15

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-RequireAllNodesOnline

Specifies that all cluster nodes must be online and reachable before updating begins.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-RunPluginsSerially

When multiple plug-ins are used during an Updating Run, specifies that CAU will scan each cluster node for applicable updates and stage the updates for each plug-in in the plug-in order passed in CauPluginName. By default, CAU scans and stages the applicable updates for all plug-ins in parallel. Regardless of the configuration of this parameter, CAU installs the applicable updates for each plug-in sequentially.
Note: The parameter is valid only when multiple plug-ins are specified in CauPluginName. If a single plug-in is specified, a warning appears.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-SeparateReboots

When multiple plug-ins are used during an Updating Run, specifies that CAU will shut down and restart a cluster node after each plug-in installs updates on the node, if the installation of an update by a plug-in requires a restart. By default, during an Updating Run, all plug-ins complete the installation of updates on a cluster node before the node restarts one time (if a restart is necessary).
Note: The parameter is valid only when multiple plug-ins are specified in CauPluginName. If a single plug-in is specified, a warning appears.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-StopAfter<TimeSpan>

Specifies the time in minutes after which the Updating Run will be canceled if it has not completed. The time span can be expressed in the standard ways available in Windows PowerShell, for example, 01:30:00 represents one hour and thirty minutes. By default, the Updating Run is allowed an unlimited amount of time to complete.
Note: If pre-update or post-update scripts are specified, then the entire process of running scripts and performing updates must be complete within this time limit.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-StopOnPluginFailure

When multiple plug-ins are used during an Updating Run, specifies that if a failure occurs during the application of updates on a node by any plug-in, subsequent updates on the node that are coordinated by the remaining plug-ins are stopped. By default, a failure by one plug-in does not affect the application of updates on a node by other plug-ins.
Note: The parameter is valid only when multiple plug-ins are specified in CauPluginName. If a single plug-in is specified, a warning appears.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-WarnAfter<TimeSpan>

Specifies the time in minutes after which a warning will be logged if the Updating Run (including any pre-update and post-update scripts) has not completed. By default, no warning will be logged, regardless of the time taken by the Updating Run.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Confirm

Prompts you for confirmation before running the cmdlet.


Required?

false

Position?

named

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet is not run.


Required?

false

Position?

named

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see    about_CommonParameters.

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

  • None

Outputs

The output type is the type of the objects that the cmdlet emits.

  • Microsoft.ClusterAwareUpdating.ActivityIdMap
  • Microsoft.ClusterAwareUpdating.ClusterResult
  • Microsoft.ClusterAwareUpdating.NodeResult
  • Microsoft.ClusterAwareUpdating.NodeStatusNotification
  • Microsoft.ClusterAwareUpdating.UpdateInfo
  • Microsoft.ClusterAwareUpdating.UpdateInstallResult
  • Microsoft.ClusterAwareUpdating.UpdateStagingResult

Examples

EXAMPLE 1

This example performs a scan and a full Updating Run on the cluster named CONTOSO-FC1. This cmdlet uses the Microsoft.WindowsUpdatePlugin plug-in and requires that all cluster nodes be online before the running this cmdlet. In addition, this cmdlet allows no more than three retries per node before marking the node as failed, and allows no more than one node to fail before marking the entire Updating Run as failed. This cmdlet is performed without confirmation prompts.


PS C:\> Invoke-CauRun -ClusterName CONTOSO-FC1 -CauPluginName Microsoft.WindowsUpdatePlugin -MaxFailedNodes -1 -MaxRetriesPerNode 3 -RequireAllNodesOnline -Force

EXAMPLE 2

This example performs a scan and a full Updating Run on the cluster named CONTOSO-FC1. This cmdlet uses the Microsoft.WindowsUpdatePlugin plug-in with the default configuration, and the Microsoft.HotfixPlugin plug-in using the hotfix root folder \\CauHotfixSrv\shareName and the default hotfix configuration file. If it is not already enabled, the Remote Shutdown Windows Firewall rule group is enabled on each cluster node before the Updating Run. If a failure occurs during the installation of updates on a node by Microsoft.WindowsUpdatePlugin, updates will not be applied by Microsoft.HotfixPlugin plug-in. If the installation of updates by Microsoft.WindowsUpdatePlugin requires a node to restart, the node will restart before Microsoft.HotfixPlugin plug-in installs updates. The cmdlet runs without displaying confirmation prompts.


PS C:\> Invoke-CauRun -ClusterName CONTOSO-FC1 -CauPluginName Microsoft.WindowsUpdatePlugin, Microsoft.HotfixPlugin -CauPluginArguments @{ }, @{ 'HotfixRootFolderPath' = '\\CauHotfixSrv\shareName' } -EnableFirewallRules -StopOnPluginFailure –SeparateReboots -Force

EXAMPLE 3

This example recovers from a previous Updating Run that failed and left the cluster in a Locked state for the cluster named CONTOSO-FC1. The recovery is performed without confirmation prompts.


PS C:\> Invoke-CauRun -ClusterName CONTOSO-FC1 -ForceRecovery -Force

Related topics

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.