New
#670
Oh! this one. Got it. Will try. I thought you were saying Repair Install.
I ended up restoring from Backup Image and running Startup Repair (as the restored image did not boot). Go it boot and running on X61T
And then after making a few System Restore snapshots on X61T, popped it in straight into T61 from X61T. (Very similar chipsets) - So, except for few drivers that had to be updated, its running well and good.
I might try SysPrep over next weekend with the additonal steps recommended by Kari and see if it can be a cleaner leaner machine with a fresh Hardware driver base.
Hey Kari, you must be exhausted from all these questions.
First, I'd like to start by thanking you for this awesome guide. I've got one hopefully simple/quick question. I'll be upgrading my motherboard and processor within the next few days. I've got Windows 7 Pro installed on my SSD, and the majority of my programs/games on a regular hard drive. Will the programs still refer to my P: drive for programs after sysrepping?
Thank you so much for this thread, and I'm sorry I had to contribute to the question-asking. :P
Kari,
Great thread :) I read it all but I may have missed an answer to a couple of questions that I have about Sysprep.
- I'm running Win 7 x64 Home Premium OEM version. My PC was built at a local store (Micro Center) and was originally configured for RAID 1 . I had problems with the array so a few months after the initial PC build, the store disabled the RAID config and re-installed Windows.
Since Windows was re-installed after the initial install, I'm guessing that Sysprep won't work for me. Does that sound right?
- Does Sysprep work with Windows OEM version, but possibly requiring a phone reactivation from MS?
It will work as far as I know it is a reinstall not an upgrade, say, from Home Premium to Ultimate. It works fine if your OS is a system Builder type of OEM.
If it is the first, initial installation of Windows or a reinstall is totally irrelevant. Sysprep works always when Windows is installed clean (Custom install instead of Upgrade install), regardless of if an OEM or Retail install media is used or how many times it is reinstalled. Microsoft does not support sysprepping Windows when it is in-place upgraded. There are three of these unsupported scenarios:
- An older Windows version is upgraded to a later version keeping installed software
- A Windows edition is upgraded to a superior edition of the same version keeping installed software
- Any Windows version edition and version is repair installed (repair install = in-place upgrade to same edition and version)
Sysprep works on any Retail and OEM version exactly the same way. A sysprepped Windows needs to be reactivated which in case of OEM version means it can usually be reactivated only when it stays on the same hardware. Moving a sysprepped OEM Windows image to another computer or same computer with new hardware components does usually not work, not even with phone activation.
Internet is full of success stories about users who have managed to reactivate an OEM Windows on different hardware; however, I do not want to create false expectations so I do not recommend transferring an OEM Windows. it might work, depending on the mood of the MS support tech who takes the call but it cannot be guaranteed.
Kari
Thanks for the info. I suspected that (OEM married to the MoBo/PC hardware) but I wanted to ask anyway.
I don't anticipate the need to try moving my OEM install to new hardware but if something happened to my MoBo, I might try it and see what happens.
I use Acronis (2011) for backups and it includes the "universal restore" option (restore to dissimilar hardware) but if I'm understanding the OEM issue, that wouldn't work.
Generally a factory OEM, such as Dell, HP, etc, can't be moved. System Builder OEMs can be but will take a call to MS to reactivate it.