Running sysprep AFTER I install a HDD into a new PC without the old PC?

[riahc3]

Is it possible to run sysprep on a HDD that I install into a NEW PC without having access anymore to the old one? I know you have to run sysprep on the old PC while the HDD is plugged in and running system and then you sysprep it with generalize but is it possible to do this afterwards? Maybe you don't have the source/original PC....

Thank you

 

[SimMike2]

You could always install it and let Windows 7 find all the drivers and stuff, which will probably take a few reboots, and after this is done, before reactivating, do sysprep at this point and reboot. I find Windows 7 is pretty good at major hardware changes, you will probably just need to reactivate. OEM copies will be the most trouble for reactivating.

 

[riahc3]

You could always install it and let Windows 7 find all the drivers and stuff, which will probably take a few reboots, and after this is done, before reactivating, do sysprep at this point and reboot. I find Windows 7 is pretty good at major hardware changes, you will probably just need to reactivate. OEM copies will be the most trouble for reactivating.

It BSOD when it says "Starting Windows". I cant even get into Windows. That's why

 

[ViRGE]

My understanding is that the system has to be up and running first to run SysPrep. So in your case I do not believe it would be possible.

 

[JackMDS]

I think there is a way to salvage it.

Get a Bootable Acronis True Image Premium and backup the HD to an external drive (or another network computer).

Then reinstall the backup using the True Image Capacity to install to any hardware.

 

[Bubbaleone]

Sysprep is a deployment tool for preparing a disk image to install Windows operating systems onto new hardware (there are specific limitations). Sysprep is always run on the technician computer first. It prepares the computer for disk imaging, or delivery to a customer, by configuring the computer to create a new computer security identifier (SID) when the computer is restarted. In addition, the Sysprep tool cleans up user-specific and computer-specific settings and data that must not be copied to a destination computer.

In the future, you may find TechNet's Sysprep Technical Reference is worth spending some time studying. It also won't hurt you to familiarize yourself with Microsoft's Unsupported Sysprep Scenarios.

.

 

[ViRGE]

I think there is a way to salvage it.

Get a Bootable Acronis True Image Premium and backup the HD to an external drive (or another network computer).

Then reinstall the backup using the True Image Capacity to install to any hardware.

Humm, that's actually rather clever. It's not free, but that would do the trick. Good thinking, Jack.

 

[riahc3]

I think there is a way to salvage it.

Get a Bootable Acronis True Image Premium and backup the HD to an external drive (or another network computer).

Then reinstall the backup using the True Image Capacity to install to any hardware.

I have Acronis True Image Premium but what is True Image Capacity? Is it separate product or is it included?

 

[ViRGE]

I have Acronis True Image Premium but what is True Image Capacity? Is it separate product or is it included?

Universal Restore is what you're looking for: https://kb.acronis.com/content/2149

 

[riahc3]

Tried Universal Restore but nothing.

My steps just in case:

1: Got the Clonezilla generated image and put it back in a VM
2: Ran Universal Restore on it
3: Tried to boot it but same thing.

 

[KillerBee]

Sysprep is a deployment tool for preparing a disk image to install Windows operating systems onto new hardware (there are specific limitations). Sysprep is always run on the technician computer first. It prepares the computer for disk imaging, or delivery to a customer, by configuring the computer to create a new computer security identifier (SID) when the computer is restarted. In addition, the Sysprep tool cleans up user-specific and computer-specific settings and data that must not be copied to a destination computer.

In the future, you may find TechNet's Sysprep Technical Reference is worth spending some time studying. It also won't hurt you to familiarize yourself with Microsoft's Unsupported Sysprep Scenarios.

.

Sure that's the official MS way Bubbaleone

but just wondering what you use yourself for imaging/deployment
do you use any 3rd party tools or just MS stuff like WAIK,MDS,WDS,SCCM

 

[WinOutreach2]

If you really want to get it running, you can attach the hard disk with the operating system in question to a virtual machine and it should boot. It is unlikely that a virtual machine would have any conflicting hardware to interfere with the boot process and you should at least be able to get into Windows. From there, you can run Sysprep and prepare it for disparate hardware. You may also want to remove and conflicting driver packages at that point, specifically incompatible storage controllers or graphics card drivers. You may also need to change the storage controller mode as is explained in this Intel Communities thread.

Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet

 

[jae]

Install the new hdd, boot to WinPE, place your unattended file and scripts, run sysprep.

What are you trying to accomplish or why are you trying to accomplish using this way??

 

[takeru]

What are you trying to accomplish or why are you trying to accomplish using this way??

actually i'm curious about this as well. it's been well over a month. if this was a production environment the user would have been given a newly imaged system a long time ago. if this is personal, are you trying to move your drive + oem windows system to a new computer? what version of windows 7 is this?