sysprep

[Brian]

what would happen if i dont use sysprep when deploying our images?
Brian

 

[Carey Frisch [MVP]]

The Microsoft Policy Concerning Disk Duplication of Windows XP Installations
http://support.microsoft.com/default.aspx?scid=kb;en-us;314828&Product=winxp

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/default.aspx

--------------------------------------------------------------------------------

:

| what would happen if i dont use sysprep when deploying our images?
| Brian

 

[chriske911]

Brian outputte 't volgende:

what would happen if i dont use sysprep when deploying our images?
Brian

I never use Sysprep, too many troubles with it,
especially now with SP2 and SATA drivers
just look for the messages about all of these problems in this NG alone

just clone a full install with all the tweaks, apps, hacks, ACL's and
so on
and use "newSID" to ceate a new SID for a new client or even duplicate
an existing SID

I'm using "NewSID" for more than 4 years now and never had any troubles
with it

I even restored a domain master server with a fresh install and this
tool
all this without having to build the entire domain from scratch or
having to do any kind of registry hacking and whatever MS KB tells you
to do if the master server has crashed

grtz

 

[Guest]

You could skip using sysprep. I find it works great. I use sysprep to
deploy the same image across multiple hardware models and vendor products.
With sysprep and some work in audit mode I have one image for the enterprise
that works on everything with no followup hacking required.