From: "Rich" 

This is a multi-part message in MIME format.

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

   Yes followed by a claim that you don't know what to install.  I =
refuted both.  You have supported neither.

Rich

  "Geo."  wrote in message =
news:3f088a3f$1{at}w3.nls.net...
  No, I claimed that the patchwork is so complex that even MS can't keep =
it
  straight.

  Geo.

  "Rich"  wrote in message news:3f084e5f$1{at}w3.nls.net...
     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_02FF_01C343DD.EF85C2A0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Yes
followed by a claim =
that you don't=20
know what to install.  I refuted both.  You have
supported=20 neither.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:3f088a3f$1{at}w3.nls.net...No, I=20
  claimed that the patchwork is so complex that even MS can't keep=20
 
itstraight.Geo."Rich"
<{at}> wrote in message =
news:3f084e5f$1{at}w3.nls.net...=
  =20
  This has nothing to do with your claim.  You claimed you don't =
know=20
  whatto install.  That is easy.  The already corrected =
typos=20
  mentioned below onlyapply to answer the question, was this already =

  installed.  Maybe interestingbut irrelevant to your stated=20
  interest.Rich 
"Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote in =
message news:3f07ed0c{at}w3.nls.net...&nbs=
p;=20
  "Rich" <{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
  it  straight. 
>   Sure they=20
  can. 
Russ:  with the recent release of =
MS03-021=20
  (819639) we've been in another patch  deployment flurry =
here. =20
  Among the things we've noticed already:  The
bulletin=20
  at  
&n" target="new">http://www.microsoft.com/technet/security/bulletin/MS03-021.asp&n=
bsp;=20
  says that a reg key=20
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows  Media=20
  Services\wm819639 will exist if you've installed this patch,=20
  whichis  erroneous.  It's not Windows Media =
Services. =20
  If you extract the .inf from  the .exe patch, you can see =
that the=20
  key is  HKLM\SOFTWARE\Microsoft\Updates\Windows Media=20
  Player\wm819639.  To make matters worse, the
KB article =
says the=20
  file version should be  9.0.0.3006 when in fact the version =
of the=20
  file in the patch, and the  version recorded in the registry =
is=20
  actually 9.0.0.3008!  File sizes do  match
up, so that's =
a=20
  plus.  We noticed this behavior on a clean
install of =
Windows XP=20
  SP1 with WMP9  deployed with the Enterprise Deployment =
Pack. =20
  There is only one versionof  the patch,
however, so I =
expect this=20
  behavior is the same on
allplatforms.  Is this really =
how a=20
  sysadmin has to work?  Read everything microsoft
says  =
and then=20
  figure it out by hand anyway? =20
-Brad

------=_NextPart_000_02FF_01C343DD.EF85C2A0--

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