Sysprep

To deploy an image correctly, you have to run sysprep *before* teking the image and deploying it. In other words: the first thing that has to show on the new machine when it's booted for the first time is the sysprep wizard.
You can *not* deploy an image, boot it up to the cloned Windows, then run sysprep. This will result in an unsupported installation.
The Microsoft policy concerning disk duplication of Windows XP installations
http://support.microsoft.com/kb/314828

Thanks for your response.

Maybe I should have explained it a little better.

1) I have an sysprep.ini file saved from a previous image and domain.
2) I put the sysprep.ini file onto the C drive of a different model PC on a new domain, along with the other sysprep files
3) I amend the sysprep.ini file to coincide with the the new domain etc. I run then run sysprep mini-setup to reboot the PC.

Is this sufficient rather than having to go through the sysprep configuration wizard. Can I just amend the sysprep.ini file and then run mini-setup?

Hope this is a little clearer.

The configuration wizard is just that: a wizard to create the ini file in the first place. You can create the ini file manually, if you feel like it. There are two chm files in the deplyoment archive in which the different options are described.