New feature with VMware vSphere Update 1
VMware vSphere Agent Pre-upgrade Check
One of the visible thinks you can see when you first execute the installation of vCenter Server is Agent Pre-Upgrade check.
What is it? This feature just ensure that the update process will go well. It check if all the hosts in your environment are having the necessary pre-requisites, so the upgrade process will be fine.
After you upgrade your vCenter server, the upgrade of your VI client will be automatically detected and installed too. (at least in my case that what’s happened). If not login through a webacess and download a the updated
The VI client has been updated and you have also the choice to install the vSphere host update utility. I did that to be able to upgrade my hosts in my environment.
FYI, I had to reinstall and re-enable the vSphere update manager Plug-in after my upgrade. (You go to Menu Plugins > Manage Plugins.




4 Comments
Trackbacks and Pingbacks
Leave a Reply
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






















Did you run esx4.0U1 in ws7?
I get a message TSC: 73051603 cpu0:0)NUMA: 706: cant boot system as genuine NUMA. Booting with 1 fake node(s)
Any idea what this mean?
this is same in VM on ESX4, look for this
http://communities.vmware.com/thread/244537;jsessionid=7A3A7905B52B11BA3CF1FA8981E42318?tstart=150
Thanks Petr for pointing this out.. Apparently in this thread I saw that the issue was solved… -:)
Vladan