Problems with Qchain in NT4
Torgeir Bakken (MVP)
> I was using a NT 4 server.
I would not think there is any difference really for server and workstation in
this matter...
> Encountered this consistently with 3 servers.
> Wouter indicated previously that MS03-040 can't be qchained... is that true?
> I have seen some scripts with IE patch being qchained..
As long as the cumulative patch have no common files with the other updates,
it can safely be installed together with the other updates (and in the list
from you, it does not share any files with the other updates).
Even if it had shared files with the other updates, it would be ok to
install it as long as you run the standalone qchain.exe after the installs
*and* none of the shared files is listed under this registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\KnownDLLs
The standalone QChain.exe doesn't care about what type of install engine that
is used. The only thing QChain.exe does, is to enumerate all the entries in the
Pending File Rename queue (a.k.a. the PendingFileRenameOperations value under
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\) and if the same file
is to be replaced more than once, QChain.exe will let the newest version win
and
remove the other(s).
*But* if you have conflicting files that is listed under the KnownDLLs
key, you might end up with the oldest file (more about this in the
KB article http://support.microsoft.com/?kbid=296861)
But of course if you are only going to upgrade one or a few computers,
you would not bother doing all this checking, better just do a reboot or
two extra instead ;-)
> Must those patches be located locally on the server, or can they be located
> in a network drive?
I very often install hotfixes while they are located in a network drive.
--
torgeir
Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of the 1328 page
Scripting Guide: http://www.microsoft.com/technet/scriptcenter