Help with Deployment

[Guest]

Can someone help me break down the steps of OS deployment over the network?

Am I right in breaking it down into?:

Load and configure OS on master machine
Load drivers on master machine
Load applications on master machine
Run sysprep to strip SID from machine
Create image via some resource (Ghost, RIPREP)
Deploy image via some resource (Ghost, RIS)

Thanks,
Kelly

 

[Adam Leinss]

Can someone help me break down the steps of OS deployment over the
network?

Am I right in breaking it down into?:

Load and configure OS on master machine
Load drivers on master machine
Load applications on master machine
Run sysprep to strip SID from machine
Create image via some resource (Ghost, RIPREP)
Deploy image via some resource (Ghost, RIS)

Looks right to me!

Adam

 

[Hunter01]

Honestly, I don't know what the fascination with Sysprep is, unless
you're deploying to multiple different hardware platforms sysprep is an
inefficient way to go. If the base hardware is the same, skip sysprep
and just use one of the freeware SID changers (sysprep to change the SID
is like using a chainsaw when a scalpel will suffice), much cleaner,
much quicker and you wont lose your customisations like you will with
sysprep (most will stay as the default user profile will be set by the
local admin profile with SP2, but there's plenty that wont because
Microsoft likes to tell you how to do things).

That being said we use Sysprep religiously, but ONLY because we have a
shitload of different hardware platforms, and the battle is hard to keep
a "one image fits all model", especially recently with the sound drivers
on Intel boards and getting the front panel gear to work (anyone who's
sussed that one out between 865 GBF and 915 GAG please let me know!). If
you have a single hardware platform, honestly, don't waste your time
with Sysprep.