Cloning a System using Sysprep

[b4u]

Hi,

I have 4 computers, exactly the same hardware parts. I want to install the basic software on one machine, then clone the system to the other 3 computers (and save the image for future "reset").

So I've picked one computer, and installed the following base software:
- Windows XP Pro + SP2
- All hardware drivers
- Office 2003 Basic Edition + SP2
- Activated Windows and Office so I could install all the WebUpdates available

So now I have a computer ready to clone.

I was thinking about using Sysprep to prepare the software to cloning, then make an image using Norton Ghost 10.

I was thinking about doing the following steps:

A) Install Norton Ghost 10 (since I can't make an image without installing it, I think);

B) Run the Sysprep tool;

C) Execute Ghost and create the image.



But I have some questions regarding this procedure:

1# I've read the following Link from Microsoft where they explain how to do the job, but they state the following:

7. Run Sysprep.exe. (...)

8. If the computer is ACPI?compliant, the computer will shut down by itself. If not, a dialog box appears stating that it is safe to shut down the computer.

9. Take out the system drive and follow the steps for duplicating the system on other computers. You must have special equipment or software for duplicating hard disks.

So after running Sysprep, the system will shutdown, then I'll have a problem ... I cannot power it on because it will run the system and ask for all information, then it's too late for making an image ... am I better off removing the drive and cloning it using another system with Ghost in it?

2# Will the Sysprep, under an activated windows, prepare it for re-asking the installation key and re-activation of windows?

3# The link above state:

3. (Optional) Install and customize applications, such as Microsoft Office, Internet Explorer favorite items, and so on.

Am I to assume Sysprep will automatically detect Office 2003 Installation and prepare it for cloning too? (Asking for key and installation on first run)




Thanks for any help and opinion 🙂

 

[Jiggz]

Dude, if all systems are identical, you'd be better off installing a hardrive as a slave with the system you are cloning. Then moving it back to the system it came from. This will only work if all system are 100% identical but it's still a violation of the EULA. Another easier way is to use an external hdd. The configured hdd you want to clone will be the ext hdd and the system you are cloning to is configured to boot from the ext hdd. Again, it all about M$ EULA you're concern about.

 

[b4u]

Originally posted by: Jiggz
Dude, if all systems are identical, you'd be better off installing a hardrive as a slave with the system you are cloning. Then moving it back to the system it came from. This will only work if all system are 100% identical but it's still a violation of the EULA. Another easier way is to use an external hdd. The configured hdd you want to clone will be the ext hdd and the system you are cloning to is configured to boot from the ext hdd. Again, it all about M$ EULA you're concern about.

How can it be a violation of the EULA if Microsoft describes the steps to do it, and even a tool like Sysprep? In my case, I have 4 licences of both Windows and Office, so I've paid for the software ... I just want an easy way of cloning and reset system in the future with minimum intervention.

 

[b4u]

* bump and more info *

I have 4 brand new computers, all with exactly the same hardware
brand/models. I also have 4 Windows XP Pro OEM licenses and 4 Office 2003
Basic Edition OEM licenses, a pair for each computer, so they are legit.

Now I've installed Windows XP Pro and Office 2003 Basic on one machine, and
I want to clone the disk to the other 3 machine hard drives.

I've used sysprep to prepare the system for cloning, and after restart,
windows shows a mini setup screen sequence to setup the system.

The problem I have is with Office 2003 Basic Edition installation ... it
doesn't ask for any info regarding key/activation.

I mean, I've activated windows and office so I could run webupdates and
install all security/enhancements available. Windows re-asks for key, and
I'll have to reactivate it, so I can setup the 4 different keys in each
computer, and they will be legit. Now with office, it doesn't ask again for
the key, so I'll endup with 4 computers with the same office key ... and
probably with the same activation ...

How can I make office to reset key and activation? Any Sysprep tool specific
for office?

Thanks

 

[mikeyes]

Like Jiggz said don't use sysprep.

The only reason to use sysprep is to prepare an image for multiple different hardware profiles. If you have 4 computers with the same hardware, get windows and all your software setup on computer 1. Then use ghost to make an image of that hard drive and use that image on the other 3 computers. Or put the hard drives into computer 1 as a slave and image from drive to drive.

Another function of sysprep is to generate a unique SID on each computer. To take care of this run a small program called newSID on each computer that receives an image. Link (its freeware). This will generate a random SID for the other 3 computers. After that your done.

Technically speaking you should use VLA copies of windows and office if you want to image. In the Microsoft world there is no way to legally image with OEM based software. Thats supposed to be one advantage of paying for VLA or open license based software Those copies do not need activation as they are designed for imaging environments. Just hang on to your licenses and if anyone ever asks just show that you have purchased enough licenses to cover your physical computers.

 

[Smilin]

Yes, DO use sysprep. It is the MS recommended (and supported!) method for preparing images. There is more to sysprep than just changing your SID.

They key used for each XP pro box can be provided at minisetup time so it's a non-issue.

Normally what you are doing is done with VL keys so re-using an office key isn't an issue. There may be one or more better ways to do this but here is one way:

895456 How to change the product key for Office XP, for Office 2003, and for 2007 Office programs and suites
http://support.microsoft.com/default.aspx?scid=kb;EN-US;895456

Just use cmdlines.txt or other unattened method to add this if you wish. If it's only 4 machines you could also do this by hand after the fact. The important thing is not to activate before taking the image.

 

[b4u]

Originally posted by: Smilin
Yes, DO use sysprep. It is the MS recommended (and supported!) method for preparing images. There is more to sysprep than just changing your SID.

They key used for each XP pro box can be provided at minisetup time so it's a non-issue.

Normally what you are doing is done with VL keys so re-using an office key isn't an issue. There may be one or more better ways to do this but here is one way:

895456 How to change the product key for Office XP, for Office 2003, and for 2007 Office programs and suites
http://support.microsoft.com/default.aspx?scid=kb;EN-US;895456

Just use cmdlines.txt or other unattened method to add this if you wish. If it's only 4 machines you could also do this by hand after the fact. The important thing is not to activate before taking the image.

My intention is to do what it's described on the link you provided, then run sysprep to prepare the machine. Then use a program to take the image to a file.

Now about the "The important thing is not to activate before taking the image.", I want to take the image of a system with all the updates available until now, and for that I need to activate the product. I believe that re-inserting a key for windows and office will trigger the "activation" thing. Am I right?

 

[Smilin]

For Office I'm unsure so I would suggest not activating until it's rolled out. I'm a platforms guy so my knowledge on office activation is thin. I could be wrong.


For the OS it doesn't matter if it's activated or not when the sysprep/image are done. Mini-setup will prompt you for a key then activation can be done, as usual, within 30 days after mini-setup completes.