Administrator Guide

\\< Prex >CON01\PUShare<CPSPU Folder Name>\PU\Framework\PatchingUpgrade\Invoke-PURun.ps1 -
PUCredential (Get-Credential)
To change to Prompt or Continue, specify the –ScomAlertAction parameter with the desired value, for example:
\\< Prex >CON01\PUShare<CPSPU Folder Name>\Framework\PatchingUpgrade\Invoke-PURun.ps1 -
ScomAlertAction "Continue" -PUCredential (Get-Credential)
4 When prompted, enter the account credentials of the account that you used when you logged on.
5 The patch and update process should begin, with verbose output of the progress. During the patching process, note the following:
• If P&U fails with a message similar to the following, this indicates that you did not initiate the P&U run from an elevated Windows
PowerShell session.
The log registration failed for task Init-Logging-< Prex >CON01. Error:
System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server < Prex >CON01 failed
with the following error message: Access is denied.
• If you click inside the Windows PowerShell window during the patching process, the screen output freezes, although the update
process is still running. Press Enter to continue the scrolling of output.
• Some component updates do not output status to the Windows PowerShell console. See the next step (6) for other ways to
monitor progress.
• Updates of the physical cluster nodes may take a while. For example, a task that involves the compute cluster (CCL) or storage
cluster (SCL) may take some time, and the output may not update for a while. You can use the following steps to view the
progress of cluster updates in Failover Cluster Manager.
1 Open Failover Cluster Manager.
2 Connect to the cluster:
• In the navigation pane, right-click Failover Cluster Manager, and then click Connect to Cluster.
• In the Select Cluster dialog box, click Browse.
• Click the desired cluster, and then click OK two times.
3 In the navigation pane, right-click the cluster name, point to More Actions, and then click Cluster-Aware Updating
4 In the ClusterName -Cluster-Aware Updating dialog, click the Log of Updates in Progress tab to monitor what is happening.
NOTE
: After Cluster-Aware Updating (CAU) completes, you can click Generate a report on past
Updating Runs to view details about what was installed through CAU.
5 In the navigation pane, right-click the cluster name, point to More Actions, and then click Cluster-Aware Updating.
6 In the Cluster Name — Cluster-Aware Updating dialog box, click the Log of Updates in Progress tab to monitor what is
happening.
NOTE
: After Cluster-Aware Updating (CAU) completes, you can click Generate a report on past Updating Runs
to view details about what was installed through CAU.
• If you have the VMM console open, and it reconnects, patching of the VMM server may be in progress. This behavior is expected.
6 To monitor the progress, you can use the following methods:
a View the verbose output on the screen.
b View the P&U events in Event Viewer. You can nd P&U events under Applications and Services Logs > PUEventLog >
Operational.
c To retrieve logs with more details, view the Temp folder. To determine the Temp folder, run the following command in Windows
PowerShell: [System.IO.Path]::GetTempPath().
The Temp folder path is something similar to this: C:\Users\username\AppData\Local\Temp\2\
If the temp folder path includes a numbered folder, such as 2,3, or 4, you must go up one folder level to the \Temp folder. If you
browse in File Explorer, note that AppData is a hidden folder. You can type the folder path to get to it, for example:
Figure 39. Temp folder
100
Operations