There are major change on the up coming version of Update Manager on vSphere 5. I was quite surprise with the change which I found out during the training today. In previous version, the update manager was able to provide patch update to virtual machine and ESX host. Which allow users to patch the virtual machine for both windows and Linux easily without require to purchase additional software management tools. With the new version of update manager, this capability had removed. It will only support the patch capability for ESX host level. You will no longer enjoy the benefits to perform patch update for virtual machine with Update Manager vSphere 5.
I was quite disappointing with this changes as I had used to the patch capability on virtual machines in the previous version. I will need to clarify further with the local representative about the changes on this.
Read more »
Today I was setting up the Nexus 1000V with Cisco UCS, and this was my 2nd time of experiencing the nexus 1000V. Previous experience when I did the 1st installation and configuration on Nexus 1000V, it take me few days to get it done, but it only took us 1 few hours to do so with a help from my colleague who are the networking expert. I was using the Nexus 1000V version 1.2 which is greatly enhance and simplify VS the version 1.
Read more »
Posted on November 26th, 2009 in Tips | No Comments »
Just found the note from VMware today about the possibility of upgrade fail if you are trying to update you ESX 4 to update 1 with update manager.
When attempting to upgrade ESX 4.0 to ESX 4.0 Update 1, you may experience the following symptoms:
Read more »
After couple of months we had performed the patch activities for our ESX hosts and VM guests by using the Update Manager, here is my review of the Update Manager from VMware.
Update Manager had simplified the life of the system engineers who manage the VM farm with the huge number of VM guests and ESX hosts which may require a frequent patch update. Before the Update Manager released, most of the time we had patched the server by using satellite servers, Altiris, SMS and others patching tools. That will require additional cost required to be implemented on the VM guests or ESX host due to the licensing agreement from the vendor.
Update Manager is fully compatible with VMware ESX patches update for ESX 3.0, 3.5 and ESX 3i. From the Host level, you will able to get all the patches downloaded by the update manager schedule task once the VMware had officially release their patch on their official system. Update Manager had also integrated well with Microsoft patches as well as others famous software patches like Red Hat, Adobe and etc. It even allow us to patch the template image which we store for deployment purpose, without manual interaction to convert the template back to virtual machine. If you try to patch a windows 2003 template image, the entire process is fully automated. This is really impressive. I had also patch my DR servers which is 30 miles away from my major Data Center, and we had 30 Mb MPLS across the WAN, it worked perfectly without any issue at all, and of course, the patching timing will be slightly longer due to the location of the DR servers.
To get the update manager deployed in your environment, here are couple of steps you may need to configure before it could fully function.
A dedicated DB for update manager in the SQL or Oracle – Depend on the choice of database servers you are using. This Database will store all the information and patches to be used for patching purpose. If you have proxy server in your environment, you need to configure the proxy address and port number in the virtual center configuration for Update Manager. Schedule task to refresh and check the latest patches release from the official site, recommend to run the schedule task at least once in a week. I do schedule it to be run on weekly basis, to ensure you getting the latest patches when you try to patch you VM guest or ESX host.
Read more »
