From: "Rich" 

This is a multi-part message in MIME format.

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

   It does.  Upgrades however do not apply the same security as clean =
installs.  They can't without the risk of breaking things.  The machine =
admin can apply any of the security templates after the upgrade.

Rich

  "John Cuccia"  wrote in message =
news:m3hr3vs1e8la92ddts19l6hohj4cpq2ifq{at}4ax.com...
  On Sun, 2 Feb 2003 16:17:16 -0500, "Geo."  wrote:

  >"John Cuccia"  wrote in message
  >news:0gkq3vsfh9f08potgmphlvjl9mqr7b6jj1{at}4ax.com...
  >
  >> You can copy the W2K CD  (the \I386 directory tree is all you need, =
I
  >> believe) to a hard drive, apply SP3 to those installation files, =
and
  >> burn that "slipstreamed" installation back to CD. 
Easy enough, for
  >> SPs, after extracting the service pack run
  >
  >Nope, that doesn't work because SP3 also contains some changes to the
  >security settings for registry keys and those won't get updated if =
you just
  >copy the files over the install CD files.

  So you are saying that if I "slipstream" an \i386 directory with the
  SP3 install command that I posted, and then burn those files to CD,
  and then use that CD to install W2K on a new machine, that the
  registry security will be different than if I installed from the
  original CD and then applied SP3?    Hope that makes sense .

  Is so, sounds like a bug.  Microsoft's slipstream process should
  update installation config files as well as other source files.


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








   It
does.  Upgrades =
however do not=20
apply the same security as clean installs.  They can't without the
= risk of=20
breaking things.  The machine admin can apply any of the security
= templates=20
after the upgrade.
 
Rich
 

  "John Cuccia" <jcuccia{at}bigfoot.com>">mailto:jcuccia{at}bigfoot.com">jcuccia{at}bigfoot.com>
wrote =
in message=20
  news:m3hr3vs1e8l=
a92ddts19l6hohj4cpq2ifq{at}4ax.com...On=20
  Sun, 2 Feb 2003 16:17:16 -0500, "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net> =
wrote:>"John=20
  Cuccia" <jcuccia{at}bigfoot.com>=20">mailto:jcuccia{at}bigfoot.com">jcuccia{at}bigfoot.com>=20
  wrote in=20
  =
message>news:0gkq3vsfh9f08potgmphlvjl9mqr7b6jj1{at}4ax.com...>=
>>=20
  You can copy the W2K CD  (the \I386 directory tree is all you =
need,=20
  I>> believe) to a hard drive, apply SP3 to those =
installation files,=20
  and>> burn that "slipstreamed"
installation back to =
CD.  Easy=20
  enough, for>> SPs, after extracting the service pack=20
  run>>Nope, that doesn't work because
SP3 also contains =
some=20
  changes to the>security settings for registry keys and those =
won't get=20
  updated if you just>copy the files over the install CD =
files.So=20
  you are saying that if I "slipstream" an \i386 directory with =
theSP3=20
  install command that I posted, and then burn those files to CD,and =
then=20
  use that CD to install W2K on a new machine, that theregistry =
security=20
  will be different than if I installed from theoriginal CD and then =
applied=20
  SP3?    Hope that makes sense
<g>.Is so, =
sounds=20
  like a bug.  Microsoft's slipstream process shouldupdate =
installation=20
  config files as well as other source =
files.

------=_NextPart_000_009A_01C2CAF4.C956B8D0--

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