From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_01F9_01C343A1.A937D4F0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   This has nothing to do with your claim.  You claimed you don't know =
what to install.  That is easy.  The already corrected typos mentioned =
below only apply to answer the question, was this already installed.  =
Maybe interesting but irrelevant to your stated interest.

Rich

  "Geo."  wrote in message
news:3f07ed0c{at}w3.nls.net...
  "Rich"  wrote in message news:3f07b5c5$1{at}w3.nls.net...

  >> The current patchwork has gotten so complex even MS can't keep it
  straight.
  >   Sure they can.


  Russ:

  with the recent release of MS03-021 (819639) we've been in another =
patch
  deployment flurry here.  Among the things we've noticed already:

  The bulletin at
  http://www.microsoft.com/technet/security/bulletin/MS03-021.asp
  says that a reg key =
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows
  Media Services\wm819639 will exist if you've installed this patch, =
which is
  erroneous.  It's not Windows Media Services.  If you extract the .inf =
from
  the .exe patch, you can see that the key is
  HKLM\SOFTWARE\Microsoft\Updates\Windows Media Player\wm819639.

  To make matters worse, the KB article says the file version should be
  9.0.0.3006 when in fact the version of the file in the patch, and the
  version recorded in the registry is actually 9.0.0.3008!  File sizes =
do
  match up, so that's a plus.

  We noticed this behavior on a clean install of Windows XP SP1 with =
WMP9
  deployed with the Enterprise Deployment Pack.  There is only one =
version of
  the patch, however, so I expect this behavior is the same on all =
platforms.

  Is this really how a sysadmin has to work?  Read everything microsoft =
says
  and then figure it out by hand anyway?

  -Brad



------=_NextPart_000_01F9_01C343A1.A937D4F0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   This has
nothing to do =
with your=20
claim.  You claimed you don't know what to install.  That
is=20 easy.  The already corrected typos mentioned below only
apply to = answer the=20
question, was this already installed.  Maybe interesting but =
irrelevant to=20
your stated interest.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:3f07ed0c{at}w3.nls.net..."R=
ich"=20
  <{at}> wrote in message news:3f07b5c5$1{at}w3.nls.net...=
>>=20
  The current patchwork has gotten so complex even MS can't keep=20
  itstraight.>   Sure they=20
  can.Russ:with the
recent release of MS03-021 =
(819639)=20
  we've been in another patchdeployment flurry here.  Among the =
things=20
  we've noticed already:The bulletin at
sa" target="new">http://www.microsoft.com/technet/security/bulletin/MS03-021.aspsa=
ys=20
  that a reg key =
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\WindowsMedia=20
  Services\wm819639 will exist if you've installed this patch, which=20
  iserroneous.  It's not Windows Media
Services.  If you =
extract=20
  the .inf fromthe .exe patch, you can see that the key=20
  isHKLM\SOFTWARE\Microsoft\Updates\Windows Media =
Player\wm819639.To=20
  make matters worse, the KB article says the file version should=20
  be9.0.0.3006 when in fact the version of the file in the patch, =
and=20
  theversion recorded in the registry is actually 9.0.0.3008!  =
File=20
  sizes domatch up, so that's a plus.We noticed this =
behavior on a=20
  clean install of Windows XP SP1 with WMP9deployed with the =
Enterprise=20
  Deployment Pack.  There is only one version ofthe patch, =
however, so=20
  I expect this behavior is the same on all platforms.Is this =
really how=20
  a sysadmin has to work?  Read everything microsoft saysand =
then=20
  figure it out by hand=20
anyway?-Brad

------=_NextPart_000_01F9_01C343A1.A937D4F0--

--- BBBS/NT v4.01 Flag-4