Administrator Guide

In the Temp folder, look for the le that is named PUProgressDetails.txt.
d View running jobs in the VMM console (in the Jobs workspace).
7 At the very end of the patching process, the Console VM automatically restarts, closing the Windows PowerShell session. To verify
that P&U successfully completed, look for the following event in the
Event Viewer under Applications and Services Logs >
PUEventLog > Operational on the Console VM. You can search for CompletePU.
Figure 40. Event Viewer
8 If you disabled DPM agents on the DPM servers earlier, do the following to restart any canceled jobs and enable the DPM agents:
a On the Console VM, make sure that you are logged on as the account that is a member of < Prex >-Setup-Admins.
b Open an elevated Windows PowerShell session, and run the following commands. Press Enter after each command.
cd "\\<Prefix>CON01\PUShare\<CPSPU Folder Name>\PU\Framework\PatchingUpgrade"
Import-Module .\PatchingUpgrade\DPM.psm1
Set-DPMBackupMode -BackupMode Enable -Credential (Get-Credential)
c When prompted, enter the account credentials of the account that you are logged on as.
When the updates complete, compliance reports are generated at the following location:
\\<Prex>CON01\PUShare\<CPSPU Folder Name>\PU\AggregatedLogs
This folder contains all logs and compliance reports. The top-level folder is a named with a GUID. Sort by date modied to see the
latest. You can open each subfolder to review the compliance report to verify what was installed.
NOTE
: If you open the Windows Server Update Services (WSUS) console to view update status, understand that the P&U
process does not apply Endpoint Protection denition updates. Therefore, you may see denition updates with a status of
Needed or No Status. Anti-malware updates are applied automatically by WSUS. By default, Endpoint Protection checks for
updated anti-malware denitions every eight hours.
Monitoring the Patch and Update process (optional)
If you want to monitor the P&U process, follow the optional steps described here.
1 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. View the progress of cluster updates in Failover Cluster
Manager by doing the following:
a Open Failover Cluster Manager.
b Connect to the cluster.
1 In the navigation pane, right-click Failover Cluster Manager, and then click Connect to Cluster.
2 In the Select Cluster dialog box, click Browse.
3 Click the desired cluster, and then click OK two times.
c In the navigation pane, right-click the cluster name, point to More Actions, and then click Cluster-Aware Updating.
d In the ClusterName — 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.
2 If you have the VMM console open, and it reconnects, patching of the VMM server may be in progress. This patching in progress
scenario is expected behavior. Monitor the progress by using 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.
Operations
101