From: "Rich" 

This is a multi-part message in MIME format.

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

   You tell me what it is and provide a URL like the KB article and =
maybe I can.  It's not like it is difficult to keep track of.  I gave = you
how to keep up to date for security.  If you want all the published =
updates since SP4 and not just those from security bulletins, see =
http://support.microsoft.com/common/canned.aspx?R=3Dd&H=3DMicrosoft%20Win=
dows%202000%20Post-SP4%20Fixes&LL=3D&Sz=3DkbWin2000preSP5fix&Fr=3D&DU=3D&=
SD=3DGN&LN=3DEN-US&CND=3D1&VR=3D&CAT=3D&VRL=3D&SG=3D&MaxResults=3D250.
 = The bit in red is the significant bit.

Rich

  "Geo."  wrote in message =
news:3f088986$1{at}w3.nls.net...
  Then explain js56nen2K_SP5.exe

  Geo. (whoops, guess the guys running technet forgot about the java =
patch
  huh?)

  "Rich"  wrote in message news:3f084d78{at}w3.nls.net...
     Yep.  SP4 and MS03-22.  You can see this yourself by visiting
  http://www.microsoft.com/technet/security/current.asp.

  Rich

    "Geo."  wrote in message =
news:3f07e5cc$1{at}w3.nls.net...
    It's got nothing to do with remembering what I installed, if I were =
to
  setup
    a new W2K server today, can you list the patches required to bring =
it
    current? Go for it Rich, lets see if you are capable of doing such a
  simple
    task.

    Geo.

    "Rich"  wrote in message news:3f07b5fa$1{at}w3.nls.net...
       Why can't you remember what you installed?  Do you pay attention? =
 If
  so,
    why is it so difficult for you to remember what you did?

    Rich

      "Geo."  wrote in message =
news:3f075f40{at}w3.nls.net...
      What I'm looking for is for Microsoft to assume the responsibility =
of
      accounting for a current  build. I'm tired of having to track this
  fricken
      nightmare patch work of fixes.

      Geo.

      "Glenn Meadows"  wrote in message
      news:3f072a14$1{at}w3.nls.net...
      I also think that what George is looking for, is a source to get a =
full
      image of the OS that already has the hotfixes/sp's installed ready =
to
  go,
    so
      when deploying or adding a new machine, you don't have to apply =
all the
      hotfixes/sp's above the level you're installing.

      So, if all you have is a Win2kPro SP0 (No SP installed) disk, but =
have a
      site license that allows 40 clients, and you're now adding client =
#35,
    he'd
      like to be able to get a full image of the latest distribution =
(not have
    to
      re-purchase same), so when he installs the software on the new =
computer,
    he
      doesn't have to take the next several hours adding SP's, hot =
fixes, etc.

      --=20
      Glenn M.


        "Rich"  wrote in message news:3f071faf{at}w3.nls.net...
           Put aside George's silly idea that full installs be made =
available
  to
      him because he is too lazy to create them himself.  (See


  =
http://www.microsoft.com/technet/prodtechnol/windows2000serv/support/spde=
ploy.asp
      and =
http://www.microsoft.com/technet/security/tools/tools/hfdeploy.asp).

           Running a slipstream install does upgrade in place and all =
users
  and
      existing software remain.  This is how I almost always install =
service
    packs
      when at work.

        Rich

          "Glenn Meadows"  wrote in message
      news:3f071d64$1{at}w3.nls.net...
          BUT, the problem with doing a "re-install", is that the =
current
  builds
      and
          software do NOT allow you to keep installed software, user, =
etc.
  I've
      tried
          that, mostly to no avail.  The ONLY way to get the install to =
run,
  is
    to
          allow it to delete the NT folder, and all the users, etc.  You =
have
  to
          re-install your software.

          I've found this to be true when trying to do a re-install of
  Win2KPro
      the
          SP3 CD build.  There is NO upgrade Install option, of Win2kPro =
is
      currently
          installed.  The ONLY option is to blow away the current =
install, and
    go
          through the hassle of a re-install.  I have NOT tried doing =
the
    SysPrep
          based install yet. which allows taking a fully installed =
system, and
          converting it to what is called an OEM image style install.  =
There
  is
    an
          option to force full hardware detect again, so you can roll up
      pre-installed
          systems with all the software installed to new machines.  This =
MIGHT
      work to
          allow you to change hardware on an existing system and not =
have to
          backup/restore, which doesn't properly bring back stuff (or =
I've not
      figured
          out the magic incantation.

          On the original Win2kPro NON SP based version CD, you can do a
      re-install
          over the top of the existing OS, and nothing is lost on =
installed
    apps.
      MS
          made a change somewhere along the line of Win2KPro to prevent =
a
      re-install.
          I have a Non-SP Win2kPro CD, and on a system that would NOT =
allow
      without
          deleting the existing installation (didn't format the disk, =
just
    deleted
      all
          the Win2K files and started over), I used the original =
Win2KPro CD,
    and
      I
          was able to re-install the OS.  Then had to apply SP3, but =
that's no
      real
          big deal.

          Heck, I've got a license for the machine, a license for the
  software,
      but it
          just won't allow an upgrade/repair style install that goes =
over the
    top
      of
          the existing install.

          --
          Glenn M.


          "Geo."  wrote in message
    news:3f06fe1c$1{at}w3.nls.net...
          > somehow I don't think we are communicating here.. I was =
saying I
    think
      MS
          > should be putting out a current build full distribution ISO
  instead
    of
          this
          > stupid barrage of patches and service packs. What I want is =
to go
  to
      the
          MS
          > website, type in my serial number and download in iso build =
of NT
    that
      is
          > current up to the minute patched so after installing I'm =
current.
          >
          > Geo.
          >
          >  wrote in message
          > news:f09845.e36000{at}harborwebs.com...
          > > -=3D> Quoting Geo. to Mike '/m' <=3D-
          > >
          > >  Ge> With Windows, MS and their pirate paranoia will never =
allow
    us
      to
          do
          > >  Ge> the current distro thing so we have to suffer with a =
3 year
    old
          > >  Ge> distribution, a service pack, a download of current
  drivers,
      and a
          > >  Ge> boatload of hotfixes. 
          > >
          > > What do you find unacceptable in Slipstreaming?
          > >
          > > Richard
          > >
          > > ... If this post also applies to you, then that's =
unintentional
          > >
          > > --- FMail/386 1.02
    (2:254/235)
          >
          >





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








   You tell
me what it is and =
provide a=20
URL like the KB article and maybe I can.  It's not like
it is=20 difficult to keep track of.  I gave you how to keep up to
date for=20 security.  If you want all the published updates since
SP4 and not = just=20
those from security bulletins, see http://support.microsoft.com/common/canned.aspx?R=3Dd&H=3DMic=
rosoft%20Windows%202000%20Post-SP4%20Fixes&LL=3D&Sz=3DkbWin2000pr=
eSP5fix&Fr=3D&DU=3D&SD=3DGN&LN=3DEN-US&CND=3D1&VR=
=3D&CAT=3D&VRL=3D&SG=3D&MaxResults=3D250">http://support.microsoft.com/common/canned.aspx?R=3Dd&H=3DMi=
crosoft%20Windows%202000%20Post-SP4%20Fixes&LL=3D&Sz=3DkbWin2000preSP5fix&Fr=3D&DU=3D&SD=3DGN=
&LN=3DEN-US&CND=3D1&VR=3D&CAT=3D&VRL=3D&SG=3D&=
;MaxResults=3D250.  The bit in = red is the=20
significant bit.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:3f088986$1{at}w3.nls.net...Then=20
  explain js56nen2K_SP5.exeGeo. (whoops, guess the guys running =
technet=20
  forgot about the java
patchhuh?)"Rich" <{at}>
wrote in =
message=20
  news:3f084d78{at}w3.nls.net...&nbs=
p; =20
  Yep.  SP4 and MS03-22.  You can see this yourself by =
visitinghttp://www" target="new">http://www=">http://www.microsoft.com/technet/security/current.asp">http://www=
.microsoft.com/technet/security/current.asp.Rich =
;=20
  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
=
wrote in=20
  message news:3f07e5cc$1{at}w3.nls.net...=
 =20
  It's got nothing to do with remembering what I installed, if I were=20
  tosetup  a new W2K server today, can you
list the patches =

  required to bring it  current? Go for it Rich, lets see if =
you are=20
  capable of doing such asimple 
task. =20
  Geo.  "Rich" <{at}>
wrote in message news:3f07b5fa$1{at}w3.nls.net...=
    =20
  Why can't you remember what you installed?  Do you pay =
attention? =20
  Ifso,  why is it so difficult for you to
remember what =
you=20
  did? 
Rich    "Geo."
<georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote in =
message news:3f075f40{at}w3.nls.net...&nbs=
p;  =20
  What I'm looking for is for Microsoft to assume the responsibility=20
  of    accounting for a
current  build. I'm =
tired of=20
  having to track
thisfricken    nightmare
patch =
work of=20
  fixes.   
Geo.    "Glenn =

  Meadows" <gmeadow{at}comcast.net>=20">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net>=20
  wrote in message    news:3f072a14$1{at}w3.nls.net...=
   =20
  I also think that what George is looking for, is a source to get a=20
  full    image of the OS that already has the =
hotfixes/sp's=20
  installed ready togo, 
so    when =
deploying or=20
  adding a new machine, you don't have to apply all =
the   =20
  hotfixes/sp's above the level you're =
installing.    So,=20
  if all you have is a Win2kPro SP0 (No SP installed) disk, but have=20
  a    site license that allows 40
clients, and =
you're now=20
  adding client #35, 
he'd    like to be =
able to get=20
  a full image of the latest distribution (not have =20
  to    re-purchase same), so when he
installs the =
software=20
  on the new computer, 
he    doesn't have =
to take=20
  the next several hours adding SP's, hot fixes, =
etc.   =20
  --     Glenn =
M.     =20
  "Rich" <{at}> wrote in message news:3f071faf{at}w3.nls.net...&nbs=
p;       =20
  Put aside George's silly idea that full installs be made=20
  availableto    him because
he is too lazy to =
create=20
  them himself.  (Seehttp://www.microsoft.com/technet/prodtechnol/windows2000serv/supp=
ort/spdeploy.asp">http://www.microsoft.com/technet/prodtechnol/windows200=
0serv/support/spdeploy.asp   =20
  and http://www.microsoft.com/technet/security/tools/tools/hfdeploy.as=
p">http://www.microsoft.com/technet/security/tools/tools/hfdeploy.asp;=
).        =20
  Running a slipstream install does upgrade in place and all=20
  usersand    existing
software remain.  =
This is how=20
  I almost always install service 
packs    =
when at=20
  work.     =20
 
Rich       
"Glenn Meadows" =
<gmeadow{at}comcast.net>">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net>
wrote =
in=20
  message    news:3f071d64$1{at}w3.nls.net...=
       =20
  BUT, the problem with doing a "re-install", is that the=20
  currentbuilds   =20
 
and       
software do NOT =
allow you to=20
  keep installed software, user,
etc.I've   =20
 
tried       
that, mostly to no =

  avail.  The ONLY way to get the install to
run,is =20
 
to       
allow it to delete =
the NT=20
  folder, and all the users, etc.  You=20
 
haveto       
re-install =
your=20
 
software.       
I've found =
this to=20
  be true when trying to do a re-install =
ofWin2KPro   =20
 
the       
SP3 CD build.  =
There is=20
  NO upgrade Install option, of Win2kPro
is   =20
 
currently       
=
installed.  The=20
  ONLY option is to blow away the current install, and =20
 
go       
through the hassle of =
a=20
  re-install.  I have NOT tried doing the =20
 
SysPrep       
based install =
yet. which=20
  allows taking a fully installed system,=20
 
and       
converting it to =
what is=20
  called an OEM image style install. 
Thereis =20
 
an       
option to force full =
hardware=20
  detect again, so you can roll up   =20
 
pre-installed       
systems =
with all=20
  the software installed to new machines.  This =
MIGHT   =20
  work
to       
allow you to =
change=20
  hardware on an existing system and not have=20
 
to       
backup/restore, which =
doesn't=20
  properly bring back stuff (or I've not   =20
 
figured       
out the magic=20
 
incantation.       
On the =
original=20
  Win2kPro NON SP based version CD, you can do
a   =20
 
re-install       
over the top =
of the=20
  existing OS, and nothing is lost on installed =20
  apps.    =
MS       =20
  made a change somewhere along the line of Win2KPro to prevent=20
  a   =20
 
re-install.       
I have a =
Non-SP=20
  Win2kPro CD, and on a system that would NOT =
allow   =20
 
without       
deleting the =
existing=20
  installation (didn't format the disk, just =20
  deleted   =20
 
all       
the Win2K files and =
started=20
  over), I used the original Win2KPro CD,  =
and   =20
 
I       
was able to re-install =
the=20
  OS.  Then had to apply SP3, but that's
no   =20
 
real       
big=20
 
deal.       
Heck, I've got =
a=20
  license for the machine, a license for =
thesoftware,   =20
  but
it       
just won't allow =
an=20
  upgrade/repair style install that goes over the =20
  top    =
of       
the=20
  existing
install.       =20
 
--       
Glenn=20
 
M.       
"Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote in=20
  message  news:3f06fe1c$1{at}w3.nls.net...=
       =20
  > somehow I don't think we are communicating here.. I was saying=20
  I  think   =20
 
MS       
> should be =
putting out a=20
  current build full distribution ISOinstead =20
 
of       =20
 
this       
> stupid barrage =
of=20
  patches and service packs. What I want is to =
goto   =20
 
the       =20
 
MS       
> website, type in =
my=20
  serial number and download in iso build of NT =20
  that    =
is       =20
  > current up to the minute patched so after installing I'm=20
 
current.       =20
 
>       
>=20
 
Geo.       =20
 
>       
> <Richard.Town{at}harborwebs.commailto:Richard.Town{at}harborwebs.com">Richard.Town{at}harborwebs.com
A>>=20
  wrote in
message       
> news:f09845.e36000{at}harborwebs.=
com...       =20
  > > -=3D> Quoting Geo. to Mike '/m'=20
 
<=3D-       
>=20
 
>       
> >  =
Ge> With=20
  Windows, MS and their pirate paranoia will never allow =20
  us    =
to       =20
 
do       
> >  =
Ge> the=20
  current distro thing so we have to suffer with a 3 year =20
 
old       
> >  =
Ge>=20
  distribution, a service pack, a download of=20
  currentdrivers,    and=20
 
a       
> >  Ge> =

  boatload of hotfixes.=20
 
<sigh>       
>=20
 
>       
> > What do =
you find=20
  unacceptable in =
Slipstreaming?       =20
  >
>       
> >=20
 
Richard       
>=20
 
>       
> > ... If =
this post=20
  also applies to you, then that's=20
 
unintentional       
>=20
 
>       
> > --- =
FMail/386=20
 
1.02       
> >  * =
Origin:=20
  Another message via PackLink +44(0)2082972486 =20
 
(2:254/235)       =20
 
>       =20
>

------=_NextPart_000_02F4_01C343DD.CCACDCA0--

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