Installation guide

11. Click Next again to either schedule the deploy job or to instruct VCM to run the job immediately.
12. On the Reboot Options page, select to not reboot the machine and click Next.
13. On the confirmation page, click Finish to deploy the patch.
When the deployment finishes, VCM runs a delta collection of the Patching Security Bulletins filter set
to update the assessment information.
14. In the assessment template data grid view, run another assessment and confirm that the machines you
patched are marked as Patched in the assessment results.
If a machine is in a pending reboot state, the patch status for the machine is Not Patched.
What to do next
n
For more information about scheduling patch deployments for Windows managed machines, see the
online help.
n
To view the status of the patch deployment job, click Patching and select Job Management > Windows
> Job Manager > Running.
n
If you scheduled the job to run later, to view the status of the scheduled deployment, click Patching and
select Job Management > Windows > Job Manager > Scheduled > Deployments.
n
VCM retains the Windows patching change actions in the change log. These actions are available in
VCM Compliance and VCM Reports. You can view the patch assessment changes by data type in the
Change Management node of the VCM Console. VCM Change Management reports changes on the
Patch Assessment and Patch Deployment data types.
Configuring An Automated Patch Deployment Environment
To automate the patching of Linux, UNIX, and Windows managed machines in your environment, you
configure the patching repository and optional alternate location machines used to store and distribute the
patches, either geographically or across firewalls. Automated patching includes both event-driven and
scheduled patch assessment and deployment. After you configure the environment, no additional
intervention is required to deploy the patches to managed machines.
When managed machines are distributed geographically or by firewalls in a Linux and UNIX
environment, VCM supports primary and secondary patch repositories to store patches for staging and
deployment to target managed machines. The primary patching repository Red Hat Linux machine has
the Software Content Repository (SCR) Tool and the VCM Agent installed. One or more geographically
distributed alternate location Red Hat Linux machines serve as secondary patch repositories that VCM
uses to patch managed machines.
vCenter Configuration Manager Administration Guide
156
VMware, Inc.