o Patch
o Patch baseline can be either dynamic or fixed.
o You can create baseline groups that contain both patch & upgrade baselines.
o Update Manager settings:
o When to check for updated patch information.
o When to scan or remediate.
o How to handle pre-remediation snapshots of VMs.
o How to handle failures to put VCP-410 exam hosts in maintenance mode.
o How to handle rebooting virtual appliances after remediation.
o Hardware Requirements:
o 2 or more logical cores
o 2GB RAM if Update Manager & vCenter are on different machines
o 4GB RAM if Update Manager & vCenter are on the same machine
o Supported Database Formats
o SQL Server 2005 SP1 (Use SQL Native Client driver for the client)
o SQL Server 2005 Express (Use SQL Native Client driver for the client)
o SQL 2008
o Oracle 10g Release 1 (10.1.0.2)
o Oracle 10g Release 2 (10.2.0.3)
o Oracle 11g Release 1 (11.1.0.6.0)
o It is not recommended to install Update Manager & vCenter on a VM that is managed by the same vCenter system. Upon scanning &
remediating, the VM on which Update Manager & vCenter are installed can reboot & the whole deployment system will shut down.
o If Update Manager does not have access to the Internet, install the Update Manager Download Service (UMDS) to download patches.
o You can export downloaded patches to a specific location that serves as a shared repository for Update Manager: C:\Program
Files\VMware\Infrastructure\Update Manager\vmware-umds --export –dest <repository_path>
o To set up a download of all available updates: vmware-umds --set-config --enable-host 1 --enable-win 1 --enable-lin 1
o Download the selected patches: vmware-umds --download.
o The Update Manager Web server listens on 9084 TCP & 9087 TCP. The Update Manager SOAP server listens on 8084 TCP.
o To obtain metadata for the patches, Update Manager must be able to connect to https://www.vmware.com & https://xml.shavlik.com, &
requires outbound ports 80 VCP-410 exam questions & 443.
o Update Manager connects to vCenter on port 80.
o ESX/ESXi hosts connect to the Update Manager Web server listening on HTTP port 9084 for host patch downloads.
o Update Manager connects to ESX/ESXi hosts on port 902 for pushing the VM patches & host upgrade files.
o The Update Manager Client plug-in connects to the Update Manager SOAP server listening on port 8084. It also connects to the Update
Manager Web server on HTTP port 9087 for uploading the host upgrade files
o Update Manager 4.0 supports Internet Protocol version 6 (IPv6) environment for scanning & remediating ESX/ESXi 4.0 hosts. For VM
scanning & remediation IPv6 is not supported.
o If you have ESX 3.X hosts in your inventory & the Update Manager is installed on a computer with IPv6, the scan & remediation operations on
the hosts fail.
o You can configure Update Manager to take snapshots of VMs before applying patches & Upgrades. You can choose to keep these snapshots
indefinitely or for a fixed period of time.
o Configure how Update Manager responds to failure to put hosts in Maintenance Mode:
o Fail
o Retry
o Power Off VMs & Retry
o Suspend VMs & Retry
o Smart rebooting selectively reboots the virtual appliances & VMs in the vApp to maintain startup dependencies & possibly reboots the
appliances that are not remediated. Smart rebooting is enabled by default
o Update Manager includes four VCP-410 study guide default dynamic patch baselines & four upgrade baselines. You cannot edit or delete default baselines.
o Critical VM Patches
o Non-Critical VM Patches
o Critical Host Patches
o Non-Critical Host Patches
o VMware Tools Upgrade to Match Host
o VM Hardware Upgrade to Match Host
o VA Upgrade to Latest
o VA Upgrade to Latest Critical
o Compliance status is displayed based on permissions.
o For ESX/ESXi hosts in a cluster, the remediation process is sequential.
o For multiple clusters under a datacenter, the remediation processes run in parallel.
o Patch baseline can be either dynamic or fixed.
o You can create baseline groups that contain both patch & upgrade baselines.
o Update Manager settings:
o When to check for updated patch information.
o When to scan or remediate.
o How to handle pre-remediation snapshots of VMs.
o How to handle failures to put VCP-410 exam hosts in maintenance mode.
o How to handle rebooting virtual appliances after remediation.
o Hardware Requirements:
o 2 or more logical cores
o 2GB RAM if Update Manager & vCenter are on different machines
o 4GB RAM if Update Manager & vCenter are on the same machine
o Supported Database Formats
o SQL Server 2005 SP1 (Use SQL Native Client driver for the client)
o SQL Server 2005 Express (Use SQL Native Client driver for the client)
o SQL 2008
o Oracle 10g Release 1 (10.1.0.2)
o Oracle 10g Release 2 (10.2.0.3)
o Oracle 11g Release 1 (11.1.0.6.0)
o It is not recommended to install Update Manager & vCenter on a VM that is managed by the same vCenter system. Upon scanning &
remediating, the VM on which Update Manager & vCenter are installed can reboot & the whole deployment system will shut down.
o If Update Manager does not have access to the Internet, install the Update Manager Download Service (UMDS) to download patches.
o You can export downloaded patches to a specific location that serves as a shared repository for Update Manager: C:\Program
Files\VMware\Infrastructure\Update Manager\vmware-umds --export –dest <repository_path>
o To set up a download of all available updates: vmware-umds --set-config --enable-host 1 --enable-win 1 --enable-lin 1
o Download the selected patches: vmware-umds --download.
o The Update Manager Web server listens on 9084 TCP & 9087 TCP. The Update Manager SOAP server listens on 8084 TCP.
o To obtain metadata for the patches, Update Manager must be able to connect to https://www.vmware.com & https://xml.shavlik.com, &
requires outbound ports 80 VCP-410 exam questions & 443.
o Update Manager connects to vCenter on port 80.
o ESX/ESXi hosts connect to the Update Manager Web server listening on HTTP port 9084 for host patch downloads.
o Update Manager connects to ESX/ESXi hosts on port 902 for pushing the VM patches & host upgrade files.
o The Update Manager Client plug-in connects to the Update Manager SOAP server listening on port 8084. It also connects to the Update
Manager Web server on HTTP port 9087 for uploading the host upgrade files
o Update Manager 4.0 supports Internet Protocol version 6 (IPv6) environment for scanning & remediating ESX/ESXi 4.0 hosts. For VM
scanning & remediation IPv6 is not supported.
o If you have ESX 3.X hosts in your inventory & the Update Manager is installed on a computer with IPv6, the scan & remediation operations on
the hosts fail.
o You can configure Update Manager to take snapshots of VMs before applying patches & Upgrades. You can choose to keep these snapshots
indefinitely or for a fixed period of time.
o Configure how Update Manager responds to failure to put hosts in Maintenance Mode:
o Fail
o Retry
o Power Off VMs & Retry
o Suspend VMs & Retry
o Smart rebooting selectively reboots the virtual appliances & VMs in the vApp to maintain startup dependencies & possibly reboots the
appliances that are not remediated. Smart rebooting is enabled by default
o Update Manager includes four VCP-410 study guide default dynamic patch baselines & four upgrade baselines. You cannot edit or delete default baselines.
o Critical VM Patches
o Non-Critical VM Patches
o Critical Host Patches
o Non-Critical Host Patches
o VMware Tools Upgrade to Match Host
o VM Hardware Upgrade to Match Host
o VA Upgrade to Latest
o VA Upgrade to Latest Critical
o Compliance status is displayed based on permissions.
o For ESX/ESXi hosts in a cluster, the remediation process is sequential.
o For multiple clusters under a datacenter, the remediation processes run in parallel.
