This is a pretty common software practice not just at Microsoft... I don't see what's so byzantine about it.
The article is missing a simple tree illustration which would likely make it a lot easier to understand. Thanks, Brian Desmond [email protected] c - 312.731.3132 -----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Thursday, May 21, 2009 7:52 PM To: NT System Admin Issues Subject: Microsoft update release methodology (RTM, GDR, LDR, QFE, etc.) This just came across the patch management list. It's highly informative and useful, so I thought I'd re-post here. Thanks to Susan "The SBS Diva" Bradley for the link (and many other useful ones in the past). It explains Microsoft's update release methodology and nomenclature, including all those TLAs like RTM, GDR, LDR, QFE, etc. http://blogs.technet.com/mrsnrub/archive/2009/05/14/gdr-qfe-ldr-wth.aspx Of particular interest to me is the statement that $NtUninstallKB folders are used for more than just uninstall. They reportedly contain all the possible versions of a file that might be needed to support *future* updates. I thought that's what $hf_mig$ was supposed to be for? I have to say... while I really appreciate someone taking the time to write all that up, I don't think I've ever seen a better illustration as to just how Byzantine Microsoft's release practices are. Anything that confusing is not a good design, as far as I'm concerned. :-( -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
