Hard drive cloning standard desktop

  • Thread starter Thread starter mrleek13
  • Start date Start date
M

mrleek13

I want to implement a standard desktop at work. My goal is to have an
image that I can use on any workstation or laptop. The question is how
do I accomplish this?

What tools can I use to make sure that after the image is loaded it
will go trough first time setup process configuring device and adding
the PC to the domain?
 
mrleek13 said:
I want to implement a standard desktop at work. My goal is to have an
image that I can use on any workstation or laptop. The question is how
do I accomplish this?

What tools can I use to make sure that after the image is loaded it
will go trough first time setup process configuring device and adding
the PC to the domain?

There are a number of ways this can be achieved, Each method has its
requirements and limitations. Search for the following key words in google:
winnt.sif, unattend.txt, Remote installation Services (RIS) and Sysprep.

Sample unattend files:
http://www.microsoft.com/technet/prodtechnol/windows2000pro/reskit/part8/pro
appb.asp

Keep in mind that the fastest way is to deploy with Sysprep (version 1.1 or
better). The limitation is that each image is reserved for similar hardware.
The advantage with sysprep is that add-on software is installed and
preconfigured with the image as well.
http://www.microsoft.com/windows2000/techinfo/planning/incremental/sysprep11
..asp

More often than not, in the case where some common system models are found
throughout the location, a mix of deployment methods like Sysprep, RIS and
winnt.sif will meet the needs.

Its not for the faint of heart, testing and modifying the image, $OEM$
driver directory or unattend file is a neccessary evil. The advantages of
deploying a standard image using any of these methods is well worth the
effort.

There are yet other options available like a CDRWin bootable W2K CD with SP
sleapstreaming.

Note: none of these methods will protect you from hardware compatibility.
 
Back
Top