From: "Rich" 

This is a multi-part message in MIME format.

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

   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_01E8_01C343A1.1EF51640
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








  
Yep.  SP4 and =
MS03-22.  You=20
can see this yourself by visiting http://www" target="new">http://www=">http://www.microsoft.com/technet/security/current.asp">http://www=
.microsoft.com/technet/security/current.asp.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:3f07e5cc$1{at}w3.nls.net...It's=20
  got nothing to do with remembering what I installed, if I were to =
setupa=20
  new W2K server today, can you list the patches required to bring=20
  itcurrent? Go for it Rich, lets see if you are capable of doing =
such a=20
 
simpletask.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
  If so,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; What=20
  I'm looking for is for Microsoft to assume the responsibility =
of =20
  accounting for a current  build. I'm tired of having to track =
this=20
  fricken  nightmare patch work of
fixes. =20
  Geo.  "Glenn Meadows" <gmeadow{at}comcast.net>">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net>
wrote =
in=20
  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 =
installed=20
  ready to go,so  when deploying or adding a
new machine, =
you don't=20
  have to apply all the  hotfixes/sp's above the level you're=20
  installing.  So, if all you have is a
Win2kPro SP0 (No SP =

  installed) disk, but have a  site license that allows 40 =
clients, and=20
  you're now adding client #35,he'd  like to
be able to get =
a full=20
  image of the latest distribution (not
haveto  re-purchase =
same),=20
  so when he installs the software on the new
computer,he  =
doesn't=20
  have to take the next several hours adding SP's, hot fixes, =
etc. =20
  --   Glenn
M.   
"Rich" <{at}> =
wrote in=20
  message news:3f071faf{at}w3.nls.net...&nbs=
p;     =20
  Put aside George's silly idea that full installs be made available=20
  to  him because he is too lazy to create them
himself. =20
  (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 users =
and =20
  existing software remain.  This is how I almost always install=20
  servicepacks  when at
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 current=20
  builds 
and      software do
NOT =
allow=20
  you to keep installed software, user, etc.  I've =20
  tried      that,
mostly to no =
avail.  The=20
  ONLY way to get the install to run, =
isto     =20
  allow it to delete the NT folder, and all the users, etc.  You =
have=20
  to      re-install your=20
 
software.     
I've found this to be =
true=20
  when trying to do a re-install of Win2KPro =20
  the      SP3 CD
build.  There is NO =
upgrade=20
  Install option, of Win2kPro is =20
  currently     
installed.  The ONLY =
option=20
  is to blow away the current install,=20
 
andgo     
through the hassle of a=20
  re-install.  I have NOT tried doing=20
 
theSysPrep     
based install yet. =
which=20
  allows taking a fully installed system, =
and     =20
  converting it to what is called an OEM image style install.  =
There=20
 
isan     
option to force full =
hardware=20
  detect again, so you can roll up =20
  pre-installed     
systems with all the =
software=20
  installed to new machines.  This MIGHT  work=20
  to      allow you
to change hardware on =
an=20
  existing system and not have
to     =20
  backup/restore, which doesn't properly bring back stuff (or I've =
not =20
  figured      out
the magic=20
 
incantation.     
On the original =
Win2kPro=20
  NON SP based version CD, you can do a =20
  re-install     
over the top of the =
existing OS,=20
  and nothing is lost on installedapps. =20
  MS      made a
change somewhere along the =
line of=20
  Win2KPro to prevent a  =
re-install.     =20
  I have a Non-SP Win2kPro CD, and on a system that would NOT =
allow =20
  without     
deleting the existing =
installation=20
  (didn't format the disk, justdeleted =20
  all      the Win2K
files and started =
over), I=20
  used the original Win2KPro CD,and =20
  I      was able to
re-install the =
OS.  Then=20
  had to apply SP3, but that's no =20
  real      big=20
 
deal.     
Heck, I've got a license =
for the=20
  machine, a license for the software,  but=20
  it      just won't
allow an =
upgrade/repair style=20
  install that goes over thetop =20
  of      the existing=20
  install.     =20
  --      Glenn=20
 
M.     
"Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote in =
messagenews:3f06fe1c$1{at}w3.nls.net...=
     =20
  > somehow I don't think we are communicating here.. I was saying=20
  Ithink 
MS      >
should =
be=20
  putting out a current build full distribution ISO=20
  insteadof     =20
  this      >
stupid barrage of patches =
and=20
  service packs. What I want is to go to =20
  the      =
MS     =20
  > website, type in my serial number and download in iso build of=20
  NTthat 
is      >
current =
up to=20
  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 =
Windows, MS=20
  and their pirate paranoia will never allowus =20
  to      =
do      >=20
  >  Ge> the current distro thing so we have to
suffer with a =
3=20
 
yearold     
> >  Ge>=20
  distribution, a service pack, a download of current drivers,  =
and=20
  a      >
>  Ge> boatload of =

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

------=_NextPart_000_01E8_01C343A1.1EF51640--

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