applying all availible QFE's

  • Thread starter Thread starter Johannes Stratmann
  • Start date Start date
J

Johannes Stratmann

what is best to apply all of the current QFE's ? I have to reinstall XPe
Tools and DB and also all the QFE's. Is there a complete Download availiable
?

I had also to reinstall my newsreader...
 
thanks, is there already a release date for the SP2 ? I guess it depends on
the results of the XP Pro SP2 with a lot of additional security features ?
 
D'oh to the ordering XPEApplicator, I was sitting here at about 2:00am installing them one at a time and surfing on another computer when I read your post and sighed relief that I did it the correct way.

Without having to compare the downloads that are available on the MSDE community site and the OEM site, am I safe downloading all of the QFE's from the OEM section and applying those? I chose the OEM to spend time downloading from because they are all in order on one page which I think is wise.

A couple of questions about these QFE's:

1. How do we know what QFE's we have on our images when we include them with target designer and then build the image?

2. Is it accurate to say that we can tell what QFE's we have on our images when applying a fix after a deployment by the registry key entries? Isn't there a better way?

From what I have learned I understand that we should be able to tell what QFE's we have when QFE's are deployed 'in the field' by looking at registry keys. However, knowing what updates we have on each machine would require a custom registry check script since Baseline analyzer 'isn't for us'.

Again, is this true?

-A

p.s. Anyone got a good QFE batch file maker that can parse from RTF files? That would be shweet. (Office space impression) 'Yeah.' *sip*
 
astyles,
A couple of questions about these QFE's:

1. How do we know what QFE's we have on our images when we include them
with target designer and then build the image?
2. Is it accurate to say that we can tell what QFE's we have on our images
when applying a fix after a deployment by the registry key entries? Isn't
there a better way?
From what I have learned I understand that we should be able to tell what
QFE's we have when QFE's are deployed 'in the field' by looking at registry
keys. However, knowing what updates we have on each machine would require a
custom registry check script since Baseline analyzer 'isn't for us'.
Again, is this true?


For me those quesitons sounded the same.
Yes, you can check what QFEs you applied to the image by anylizing registry
and/or files that got changed with QFE. What else does get changed with
QFE?!

Btw, the script (or app) should be pretty simple and easy to develop. It has
just check for/enumarate all the Qxxxxx subkeys of
[HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix] registry key.
-A

p.s. Anyone got a good QFE batch file maker that can parse from RTF files?
That would be shweet. (Office space impression) 'Yeah.' *sip*

Are you extracting QFE file&registry info from the
"Additional_Info_Q....rtf" files supplied along QFEs?
Then yio may want to take a look at the QFE Installer component.
Since you mentiod you have got the access to MS OEM site:
https://microsoft.embeddedoem.com/content.asp?path=/downloads/winxp/qfe/installer10

they were published (don't make the same mistake like me and install them by
sort them by their QFE-Number).
 
Note:

My experience was that it's important to install all QFEs in the order
they were published (don't make the same mistake like me and install
them by sort them by their QFE-Number).

I'm curious, as order of application shouldn't make a difference (with
the exception of 811279, of course). What did you see when you
installed them in numerical order v. date order?

One thing that may cause problems is when a QFE tries to copy files that
are already in the QFE repository. You can get around that by setting
the \Windows Embedded Data\Repositories share permissions to give your
user account full permissions, and setting the ACL on the folder to give
your user account full control. This will allow you to overwrite
previous files and prevent problems.
 
thanks, is there already a release date for the SP2 ? I guess it
depends on the results of the XP Pro SP2 with a lot of additional
security features ?

No, no release date yet.

Yes, it is highly dependent on the release of desktop SP2. We're
shooting for 30-60 days after desktopSP2 releases.
 
Back
Top