used ssd + new build

[kingscurate]

Hi Gents,
Purchased a ssd drive few months back, now planning a new build. I want to use the old ssd for the new build as im currently using it. IT has my OS and programs stored no docs/files etc .
I will purchase a new windows 7 code, as im using oem.
Whats the best way to go about this, do i do a sys prep install and then input the new win 7 code, do i secure clean the ssd and then do a new install?
I looked at the tutorials on this, but dont really answer my Q.
The other thing is some apps are specific to my current setup, im assuming i would have to deactivate and uninstall before i carry on?? And then reinstall on my new setup.
Any guidance welcomed

 

[kingscurate]

Anyone?

 

[gregrocker]

It's best to Clean Reinstall.

If you want to try moving your current install, then SysPrep to move HD to another computer.

Insert the new Product Key after you start it up, once you're sure the hardware is working correctly.

 

[kingscurate]

So i treat the ssd the same as a hdd, and do either one of sysprep or clean install.

 

[gregrocker]

Yes. If it has any problems we can advise you on alignment.

 

[whs]

I would suggest to Secure Erase the SSD before you make a clean install. That will speed it up and set it back to out of the box condition.

How to securely erase an SSD drive | How To - CNET

Then I would define a single active primary aligned partition on the SSD (using command prompt of your installation disc). That way you avoid a lot of problems in the future because you get no independent system partition. The bootmgr will be on C.

I know Greg will not agree. But unless you use bitlocker (only available in Ultimate), this extra partition is nothing but a pain - e.g. for imaging.

 

[gregrocker]

Actually Wolfgang, I can take 100mb or leave it. The troubleshooting steps I most often post include wiping and defining a C partition as well. My only point in the past is not to risk removing it since it's not worth the bother, or even a second thought.

 

[whs]

Greg, many people run into trouble when they image. Either they forget to image it because it is hidden or they do not restore it when they e.g. replaced the HDD. It's just an unnecessary pain in the neck.

 

[gregrocker]

OK, I'm beginning to get why so many here are dead set against it. Thanks.

I haven't gotten to help in the Backup forum for several years now, since SysVol creation on 100mb was a prob with imaging - was that resolved by an Update or SP1? . I used to make it there after I got through Install, General and Performance. But I rarely get to Performance any more.

 

[whs]

There is no problem with imaging the 100MB partition, but many people just forget about it.

If you use the Windows 7 native imaging, it is automatically being dragged along. But since Windows 7 native imaging is not very swift, most people use OEM products that don't do that - mostly Macrium, Paragon and lately Aomei Backupper.