Re-release of ESX 4 update 1
Vmware Re-released the Update 1 of ESX 4.
After the troubles with the latest update – the Update 1 for ESX 4 (ESXi 4 is not affected), VMware just released Update 1A, which fixes the troubles.What has been fixed? The thing that when there has been 3rd party agents on ESX Server installed on the COS, your server might not “digest” the update 1 correctly and instead you might be just left with PSOD (purple screen of death).
Note that only HP Proliant systems with a supported version of HP Insight Management Agents running are affected. The host might became unusable and you’ll have to reinstall the host. And if this happens and you were running a Virtual machines on local storage. On your local disks.Those VMs might not be retained…
ESX 4.0 Update 1 has been re-released with changes to avoid this issue. The installation process checks for running agents and stops them before proceeding. The re-released ESX 4.0 Update1 is referred to as ESX 4.0 Update 1a and is available via vSphere Update Manager (VUM) and the VMware Downloads site.
Source: VMware
Other posts from Server Virtualization
- Create your own Provider Virtual Data Center
- Measure some perf benchs with VMark
- VMware partners with Symantec on ApplicationHA
- Andre Leibovici's Linked cloning storage calculator
- SIOC yes, but not in the SMB kit...
- Best practices KB on how-to install ESX 4.1 and vCenter
- Hyper-V and new linux integration tools
- How to Fix “Transaction log for database ‘VIM_VCDB’ is full” errors
- How to change from ACPI Multiprocessor HAL back to ACPI Uniprocessor HAL in Windows 2003
- AD Integration for ESXi 4.1
- vCenter converter with Hyper-V import
- Serial Port handling in ESXi 4.1
- Four memory optimization techniques available in vSphere 4.1
- Activating remote access via SSH in ESXi4.1
- vSphere Compatibility Matrixes
- 150 new features or enhancements in vSphere 4.1
- Personalized install of VMware tools
- VMware tools download from VMware Website
- How to change virtual SCSI controler
- Microsoft's patch for .NET breaks VI client connection
