vSphere4 Documentation Notes vReference.com
Version 1.0 Page 30 forbesguthrie@vReference.com
o When you remediate hosts against baseline groups containing upgrade & patch baselines, the upgrade is performed first. Host upgrade in a
high-latency network in which Update Manager & the hosts are at different locations might take a few hours because the upgrade file is
copied from the640 802 Dumps
Update Manager server repository to the host before the upgrade.
o When you upgrade a host, no third-party management agents or software applications are migrated to the ESX 4.0/ESXi 4.0 host.
o In the ESX 3.5 patch remediation process, cumulative rollups & updates are considered patches. If a rollup contains two patches installed on
the host, the state of the host is noncompliant against the rollup until the rollup itself is installed on the host.
o In the ESX 4.0 patch remediation process, Update Manager operates with vSphere Installation Bundles (*.vib files). A bundle is the smallest
installable unit on an ESX 4.x host. A bulletin defines a specific fix for a host, a rollup that aggregates previous fixes, or an update release.
When a host is compliant with all bundles in a bulletin, it is compliant with the vSphere bulletin that contains the bundles.
o Before the ESX host upgrade remediation, Update Manager runs a script on the host to check whether the host can be upgraded. If the host
can be upgraded, Update Manager copies the ISO file to the host. The ISO file contains the bits that are to be installed as well as a Linux kernel
& ramdisk, which serve as the installer environment. The host reboots into the installer, & the installer creates a service console virtual disk
(VMDK) to install the packages into the console VMDK. The host is rebooted, upgraded to ESX 4.0, & reconnected to the vCenter system. If the
upgrade fails, you can roll back to the previous version.
o For ESXi hosts, updates are all-inclusive.
o The ESXi image on the host maintains two copies. The first copy is in the active boot & the second one is the standby boot.
o The active boot contains the patched image & the standby boot contains the previous version of the ESXi host image.
o Take snapshots of templates before remediation, especially if the templates are sealed.
o After a template is started & remediated, the registry keys are restored, & the machine is shut down, returning the template to its sealed
o Staging patches for ESX/ESXi hosts allows you to download the patches from the Update Manager server to the ESX/ESXi hosts, without
applying the patches immediately.
o Staging patches 640-802 does not require that the hosts enter maintenance mode.
o Update Manager stores data about events. You can review this event data to gather information about operations that are in progress or that
o Because of limitations in the ZIP utility used by the Update Manager, the cumulative log file size cannot exceed 2GB, although the script seems
to complete successfully.
o To generate Update Manager log files, exclude the generation of the vCenter logs using the vumsupport. wsf script file:
o C:\Program Files\VMware\Infrastructure\Update Manager\cscript vum-support.wsf /n
o When you upgrade an ESXi host with less than 10MB of free space in its /tmp directory, although Update Manager indicates that the
remediation process completes successfully, the ESXi host is not upgraded.
vCenter Converter Administration Guide
o vCenter Converter does not support creating thin-provisioned target disks on ESX/ESXi 4.0.
o vCenter Converter Components:
o vCenter Converter server
o vCenter Converter CLI
o vCenter Converter agent
o vCenter Converter client
o vCenter Converter Boot CD
o When you import a physical system, vCenter Converter uses cloning & system reconfiguration steps.
o When you hot clone dual-boot systems, you can clone only the default operating system to which the boot.ini file points.
o You can clone remotely, as long as it is running & accessible to the network. With local cloning, vCenter Converter runs on the source machine
to perform the migration.
o During hot cloning, the machine you are cloning experiences no downtime.
o Disk-based cloning for cold cloning & importing existing VMs. Supports all basic & dynamic disks.
o Volume-based cloning for hot & cold cloning & for importing existing VMs. All volumes in the destination VM are basic volumes, performed at
the file level or block level, depending on your size selections.
o Only master boot record (MBR) disks are supported. GUID partition table (GPT) disks are not supported.
o Hot cloning supports all types of source volumes that Windows recognizes.
o You cannot schedule 640 802 braindumps
o Converter can restore VCB images of any guest operating system type on an ESX/ESXi host that vCenter Server manages. However, only disks
are preserved. It does not preserve certain hardware backup information from the original image, but rather substitutes default settings.
o You can schedule an unlimited number of physical-to-virtual recurring tasks & specify how the existing VMs are to be retained.For recurring
tasks, the vCenter Converter agent must be installed permanently on the source machine.
o You can keep multiple VMs as backups to an existing machine
o VM names have an 80-character limit. VMware recommends a maximum of 60 characters because the time stamp might make the name
exceed the limit.
o Applications might not work if they depend on specific characteristics of the underlying hardware.
vSphere4 Documentation Notes vReference.com