muzzammilhussain
asked on
updates for ESX 4.1
Hello Experts,
I am using ESX 4.1 update 3 and I want to bring my ESX infrastructure to the most update do date level. I have seen the following article that provides list of Releases and Builds
http://www.virten.net/vmware/esx-release-and-build-number-history/
According to the article the most up to date version of ESX 4.1 is:
ESX410-201410001 4.1.0 Patch 11a 2014-10-01 2168595
My question is, do I need to install every single patch from 4.1.0 Patch 6 to 4.1.0 Patch 11a in order to keep the ESX hosts up to date and secure or I can skip some of them and install just the latest one?
Many Thanks,
I am using ESX 4.1 update 3 and I want to bring my ESX infrastructure to the most update do date level. I have seen the following article that provides list of Releases and Builds
http://www.virten.net/vmware/esx-release-and-build-number-history/
According to the article the most up to date version of ESX 4.1 is:
ESX410-201410001 4.1.0 Patch 11a 2014-10-01 2168595
My question is, do I need to install every single patch from 4.1.0 Patch 6 to 4.1.0 Patch 11a in order to keep the ESX hosts up to date and secure or I can skip some of them and install just the latest one?
Many Thanks,
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Build number should have changed.
which do you apply ?
which do you apply ?
ASKER
I installed ESX4.1 update 3 and bash patch on ESX4.1 update 2. The build is showing 800380. I did this through the update manager of vCenter.
ASKER
Patch 11.0a is only 1.9 MB so I have this feeling that is does not cover everything except the bash patch itself. The Vmware article says this:
"VMware packaging policy dictates that the content of a patch RPM or VIB is cumulative throughout the product support life cycle"
The bash patch was released in October last year that was after the product support life cycle. Can this be the reason why this is not cumulative ?
"VMware packaging policy dictates that the content of a patch RPM or VIB is cumulative throughout the product support life cycle"
The bash patch was released in October last year that was after the product support life cycle. Can this be the reason why this is not cumulative ?
It's possible, it's also worth checking the size of 11.0, and it may not have caused a build change.
ASKER
I have installed the latest patch on ESX4.1 update 3 and on ESX 4.0 update 4 hosts. The path is very small and only updates bash. The build numbers on ESX hosts also have not changed. I have got the feeling that this installation did not include the patches that came in between ESX4.1 update 3 and the bash or ESX 4.0 update 4 and the bash so I may still be missing important updates. Can you please confirm if this is the case?
Many Thanks