Hfnetchk scans every file

From: Greene, Michael (MGreene@lrs.com)
Date: 05/20/02 

From: "Greene, Michael" <MGreene@lrs.com>
To: "'Darren W. MacDonald'" <darrydoo@aci.on.ca>, "Greene, Michael" <MGreene@lrs.com>, "'Dennis M. Depp'" <dwd@ornl.gov>
Date: Mon, 20 May 2002 14:23:04 -0500

Darren, thank you for your reply. I have posted these same questions on the
Microsoft partner newsgroups and have gotten much better information from
this listserv. In response to your comment about hfnetchk. You are exactly
right! After further review I found this FAQ claiming that hfnetchk does
examine EACH file applied in a hotfix. This means that it is possible to
scan a server using the hfnetchk tool and determine if any hotfixes have
been overwritten. This completely answers my question and settles my
worries. Thanks.

Q : Does Hfnetchk validate the existence of hotfixes by checking only
registry keys?
A : Hfnetchk examines several values before it reports on the status of a
patch. The registry key that is associated with the patch is checked first.
If this registry key does not exist on your computer, the patch is
considered to not be installed. If the key does exist, Hfnetchk examines the
file version and file checksum for each file in the hotfix. If all of these
values match, the patch is considered to be installed. If any one of these
tests do not work, the patch is either considered to not be installed, or it
is flagged as a warning (depending upon the results of the check).

In addition there were some areas of your response that I happened to
disagree with. If you can provide support for your argument that the
service pack files are cached locally (they may be if installed from the
web, but what about other cases?) I would be very happy to listen. You
obviously proved a flaw in my argument above, so I am hoping you can prove
me wrong again.

//////////////
Michael, your statement, "...Windows should prompt for a service pack
installation point. ...", directly conflicts with my experience, and what's
documented in the quoted KB article -- service packs are locally cached, and
fully known to the OS, so no prompting for location should occur. 

----
The Layout.inf file is updated with an additional source for Windows 2000
service pack files so when you add or change additional components the
Layout.inf file points to the correct source. The source location is stored
in the following registry key: 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePa
ckSourcePath 
The source could be a network share of the Windows 2000 service pack, the
Windows 2000 service pack CD-ROM, or if you install the Windows 2000 service
pack by using the Express Installation from the Web, the source is set to
the %systemroot%\servicepackfiles folder.
----
To test this procedure, install Windows using a CD that is not slipstreamed.
Install Service Pack 2 from CD.  Now add a component.  I cannot cite a
specific example for a component to test, I apologize, I only know that it
has happened to myself and to colleagues.  The server should prompt for the
Windows 2000 cd, and then at the appropriate time, it should prompt for a
Service Pack 2 CD.  If the server is installed from a slipstreamed
installation point, the prompt for a Service Pack 2 cd does not occur
because the system is able to find the files without having to change CDs.

/////////////
As to why things are done differently for hotfixes, I believe the short
answer would be "time". The QFE group (Quick Fix Engineering) works to
create hotfixes quickly, and because of this time limitation, certain
shortcuts are taken (like regression testing, as documented for each and
every hotfix).
----
I'm not sure what you are saying here, but I would disagree that it is ok to
release a poor solution simply because of time constraints.

Relevant Pages

  • "Access is denied." While Installing XP Pro SP3
    ... Windows XP Service Pack 3. ... Finally, there was a message box that said, "Service Pack 3 ... again, there was a lengthy installation, followed by the same message boxes, ... This rollback requires a reboot. ...
    (microsoft.public.windowsupdate)
  • RE: "Access is denied." While Installing XP Pro SP3
    ... Windows XP Service Pack 3. ... Finally, there was a message box that said, "Service Pack 3 ... again, there was a lengthy installation, followed by the same message boxes, ... This rollback requires a reboot. ...
    (microsoft.public.windowsupdate)
  • Re: Windows XP Home SP3 update failed
    ... Windows XP Service Pack 3 Overview ... The hard disk space requirements for Windows XP Service Pack 3 ... XP SP3: Post Installation Cleanup: ... 6422.675: User Input: OK ...
    (microsoft.public.windowsupdate)
  • Re: Reinstalling SP2
    ... Antivirus software should be turned off during SP2 installation. ... Windows 2000 and Windows XP. ... Windows XP Service Pack 2 Resources for IT Professionals ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • RE: hotfix overwrite; hfnetchk
    ... hotfixes, we don't have to worry about overwriting the service pack files ... the service pack files come from is a bit less relevant. ... CD install, or a network install where the source isn't available, new ... drivers (anything done through Windows Setup or Control Panel, ...
    (Focus-Microsoft)