(I apologize for being so non-responsive lately.  My "real job" has
become unpleasantly busy lately.)

> So now to the question, how shall I add them in the script? By the Q
> article number ascending or release date?

I usually just add them in the order I find them.  To be honest, I do
not know the right answer.  Release date might be best.  For most
hotfixes, it probably does not matter.  After all, any user could go
to Windows Update and pick & choose any subset to install at any time,
and in theory it should "just work".

I wish Microsoft would release service packs more often.

> In the old days when I used the traditional Windows Update it sometimes
> appeared more updates at the same time you were rebooting to install the
> once you couldn't install at the same time?

Some hotfixes fix other hotfixes, which creates dependencies.

As for installing multiple hotfixes, here is what I know.  Microsoft
has an old utility called "qchain" which is supposed to let you
install multiple hotfixes without rebooting.  Recent hotfixes have
qchain's logic built in, so you can install most of them without
rebooting.  See <http://support.microsoft.com/?kbid=296861> for

You will probably still need to reboot at the end to actually pick up
the fixes, because hotfixes often need to replace files which are in
use by Windows.

When a hotfix wants to reboot the machine, but you passed the "/z"
option, it exits with status 194.  This is from observation; I do not
know whether this is documented anywhere.  But it is very consistent.

Personally, I never trust Microsoft to get anything right, so I do not
trust qchain.  (And guess what I just found?  Until four months ago,
qchain was broken; see <http://support.microsoft.com/?kbid=815062>.
But I'm sure it's perfect now...  Could someone remind me why anybody
uses Microsoft products?)

I also do not care how many reboots it takes to install a machine.  So
when I download a hotfix that wants a reboot, I add it to the script
with ".ignore-err 194" and then do ".reboot" myself.

As a result, winxpsp1-updates.bat is up to 14 reboots and counting.
Better safe than sorry.

 - Pat

This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
unattended-info mailing list

Reply via email to