And the journey I am now referring to is the quest to really, properly, fully and completely understand how Microsoft updates, manages installs, and makes changes to Vista and Windows 2008 desktop and server platforms. I understand from reliable sources that the starting point for this epic quest is Microsoft's "Component Based Servicing" or CBS which is turn part of the setup architecture.
Here is a handy (but possibly too simplistic) diagram/view of the Setup Infrastructure for Windows Server 2008 and Vista.
As a personal note, you can tell about a lot about me and my friends because we started at the bottom of the diagram... Instead a nice high-level starting point, we go for the deep dive straight away.
Now let's try to find out about each component...
From the Microsoft reference website, there are some good high-level descriptions for each "block" in the diagram above including;
- Optional Component Setup: "Optional Component Setup (OCSetup.exe) is a command-line tool that installs and uninstalls Windows optional components. This tool replaces Sysocmgr.exe. You can use OCSetup.exe to install, update, and remove Windows Installer (MSI) components and Component-Based Servicing (CBS) components."Further information is found here: http://go.microsoft.com/fwlink/?LinkId=91915
- Package Manager: "The Package Manager is a tool that installs or removes packages or Windows components. It is called by Windows Setup during normal installation, including unattended installation, and runs transparently while updating or installing Windows. Further information can be found here: http://technet.microsoft.com/en-us/library/cc753368.aspx
- Language Pack Installation: Language Packs help with the display of dialog boxes, wizards, menus and help documentation in different languages.
- Component Based Servicing: This is a critical component to installing, updating and removing applications on the Vista and Windows Server 2008 Platforms. The Microsoft Component-Based Servicing (CBS) is part of the servicing stack which is defined by Microsoft as "a set of files and resources that are required to service a Windows image or operating system"
OK, so what is the big deal? Sounds simple enough.
Well, I just can't get enough information on Microsoft's Component Based Servicing for the following reasons;
- There aren't any publicly available API's (maybe there is - can you help?
- No clear cut definition of what a "component" is
- No documentation on how "I" (meaning anyone) might create a component
- No clear description on what happens when you update, remove or install a component
- NO DOCUMENTATION!
As Won Yoo said in his IIS blog (http://blogs.iis.net/wonyoo) , "when it comes to servicing, a component is the smallest unit of measure and this creates an interesting patching behaviour. A component may contain several files. So, even if a fix for a particular bug is localized to one file, if the file belongs to a component that consists of other files, the patch will contain all files in the component."
I read an MSDN article that indicated that CBS was the most important management advance in Vista and that CBS was really, very important. OK, I have downloaded the Windows Automated Installation Kit (WAIK. Found here: www.microsoft.com/downloads/details.aspx?FamilyID=C7D4BC6D-15F3-4284-9123-679830D629F2) and did not find any further documentation on CBS.
For a laugh, have a laugh and have a read of the Microsoft CBS "documentation" found here: http://msdn.microsoft.com/en-us/library/aa903048.aspx
To really drive the point, here is a screen-grab of the page.
For the definition of sparse, look here; http://dictionary.reference.com/browse/sparse. To experience it in real life, to live it, is to search for CBS.