On 17 Jun, 09:30, Anteaus <Ante...@discussions.microsoft.com> wrote:
> Bottom line is, whatever approach you take, you need a disk-imaging program.
> I use Powerquest's Drive Image but this is no longer supported and getting
> rather outdated. Others recommend Acronis. *There are also Linux options,
> though (like most things Linux) they are harder to use. *
>
> For a small rollout of identical computers I would forget sysprep. It's way
> too complex, plus it leaves you with the issue that users need to be re-setup
> post rollout. Instead, setup one computer and get everything as you want it,
> then image. On the imaged copies, run NewSID (from sysinternals) and then(if
> required) change the licence key and re-activate.
>
> For the actual imaging, HD to HD copying is by far the most efficient. I
> generally setup one or more 'imaging stations' which will boot from a DOSHD
> with the image, and then connect the HD to be imaged-to on the secondary
> port. This way, each imaging station can process perhaps five or ten HD'san
> hour. *
>
> "CJC" wrote:
> > Hi there,
>
> > I have been given the task of setting up a process to deploy XP onto
> > new PC’s when we buy them and have been looking on the net but I find
> > the mixed responses in the material quite cumbersome and confusing.

Thank you Anteaus and Shenan Stanley for your imput on this,

I am currently going through your links and deciding on the methods to
go for.

i know for sure I am using server 2008 with the deployment service but
am in process of deciding what to use for creating images.

Many thanks