Layer Rebuilding Cycle - "Born On Dating"
tfronza
July 6th, 2007
How often do you rebuild your "Packages" or Layers? I ask myself that question and I really do not have an answer. But from personal experience I have found that I end up rebuilding packages on a 6 month to 1 year cycle UNLESS the software manufacturer ends up rolling in a patch that is required in the enterprise.
I have found that after about 1 year, packages or layers seem to have a "Born On Dating" and the become "Stale". It also helps to build the packages on a machine that has the current patches for compatibility with you current environment -- NOT one with patches from 6 months to 1 year ago.
Good Luck
Tom Fronza
State of Ohio
Dept. of Taxation
Track "born on date"?
Do you track the "born on date" of the packes somehow? Or is just after a year it is time to rebuild all of them?
Jonathan
Jonathan Jesse
Practice Principle
ITS Partners
I agree with this update
I agree with this update process, just a question about products that changes many times during the year,( such as MS Office ), how do you manage these packages ?
Regards
PM
Group the Patches
An update of a layer like office in our environment at this point is not in a layer so we update it using NS just like we update Windows. But I would assume a patch process like this one I would save all the patches and do 3 or 4 months of patches all at once!
Tom Fronza
State of Ohio
Dept. of Taxation
Properties
You can look at the creation date of the VSA and then determine weather it is time to rebuild or not, most packages will require some type pf attention before that...
Tom Fronza
State of Ohio
Dept. of Taxation
Would you like to reply?
Login or Register to post your comment.