Ghosting OEM Machines - possible?

[sternfan2011]

Hi all,
I have used ghost before to image XP PCs over the network, but have yet to try either win7 or an OEM OS (xp was an enterprise license). My Qs:

• Is it legit to ghost OEM PCs? I have 60+ new PCs, with OEM win7. I was thinking that I could take one PC, set it up the software etc then push the image. I would then change the license key to the one on the box. Is this correct?
• If all the systems are the same, do I need to sysprep?
• I have heard horror stories of syspreping win7 - if I need to do a sysprep, does anyone have a good guide?

Any help/advice greatly appreciated,
Rob

 

[gregrocker]

This seems to work well: SysPrep to move HD to another computer

Imaging or cloning directlyl would need to be to the exact hardware since Win7 cannot be counted on to start on new hardware without SysPrepping or utilizing a feature like Acronis Universal Restore or a Paragon Adaptive Restore CD.

 

[Kari]

This seems to work well: SysPrep to move HD to another computer.

As much as I trust this method, it has served me well, I would not use it on corporate environment. I would rather choose the ImaxeX / WIM route (ImageX and WIM Image Format)

Kari

 

[sternfan2011]

Thanks for the prompt replies:

To be clear, all of the PCs are exactly the same - so no hardware issues.

In the past, I've done XP imaging by doing a sysprep, then pushing the image out with Ghost. But that was with an enterprise version of XP with a Volume License Key. In the end, all the PCs had the same key.

Where I'm having trouble is with the OEM key. If I sysprep one of the OEM boxes, and push out the image - I assume I am supposed to use the OEM key on the side of the box? Also, each of these already shows up as "activated" when I go into system properties. Will the ghosted PCs have trouble activating again?

I want to be sure before I start testing the images.

Thanks,
Rob

 

[gregrocker]

You can try an image on some of the boxes to see if it works. If you're prompted for reactivation insert the Key from COA sticker which came with machine if applicable.

Otherwise you can change out the Key at Computer>Properties proactively to reset the SID which should be different if not the hardware.

 

[sternfan2011]

I was looking at this article: http://www.sevenforums.com/tutorial...lation-transfer-new-computer.html#post1161038

Could it be the switching hardware that is causing the OEM activation issue?

Rob

 

[gregrocker]

Yes. You want the Product Key from each target machine entered at Computer>Properties activation link anyway. Otherwise it is using another machine's key and will be deactivated soon enough.

 

[theog]

This seems to work well: SysPrep to move HD to another computer.

As much as I trust this method, it has served me well, I would not use it on corporate environment. I would rather choose the ImaxeX / WIM route (ImageX and WIM Image Format)

Kari

+1

Is it legit to ghost OEM PCs? I have 60+ new PCs, with OEM Windows 7. I was thinking that I could take one PC, set it up the software etc then push the image. I would then change the license key to the one on the box. Is this correct?

No need to remove the factory OEM-SLP activation method Product Key,
if all the systems are the same.

If all the systems are the same, do I need to sysprep?

No need to use SYSPREP, if all the systems are the same.

   Information

We always assume you have made your Recovery Disks using the OEM manufacturer's Recovery Media Creator app the first day you had your new PC.
& made the Startup Repair CD.
startup repair disc-create
​

Did you make the OEM manufacturer's Recovery Disks?