Cloning apps to handle SSDs?

[DeaconFrost]

I have a system that I'd like to clone to an SSD. The source disk is an HDD that is currently using two partitions. I'd like to just move the C partition to an SSD, but my only question is, what cloning apps would allow the SSD to be recognized properly, or would Windows 7 pick up the fact it is an SSD drive and adjust the OS accordingly, including enabling TRIM.

If it matters, the SATA controller is already set to AHCI, and the target drive is a Crucial C300.

Forgot to mention, I had been using Partition Wizard 7.0 (bootable iso) in the past, but never with an SSD.

 

[aem]

And the reason to get the OS onto the SSD is so you can boot it up to another machine?

I'm thinking you might need to make an iso of the image. But first maybe sysprep it?

 

[DeaconFrost]

No, it will be replacing the HDD as the boot disk. The HDD will then be used as storage. I think I'm actually leaning towards using the SSD in another system for now. I found Paragon software that would do it, but for $20, I'd just as soon as spend the two hours doing a clean install.

 

[ignatzatsonic]

I changed to an SSD about 6 months ago and considered making an image of my HDD and restoring it to the SSD. In the end, I did a fresh install---mostly because I could never convince myself that it might not eventually lead to a problem.

But I can't recall ever reading anything authoritative that led me to believe that ordinary third party imaging tools like Macrium, EaseUS, or Acronis would NOT work OK for the purpose.

Do you have any specific reason to believe they would not work?

Do you mean a true clone (real-time transfer from HDD to SSD without an intervening image) as opposed to making an image and then restoring it to the SSD?

I'd be interested in comments from anyone who has gone from HDD to SSD via clone or image.

 

[aem]

Kari's made a tut on doing a sysprep have you looked at that?. I would put the SSD into another machine and use it as a HDD just so you can clone it, rather than connecting it to the machine you wish to image.

 

[DeaconFrost]

There's no need to use Sysprep when it would be used in the same system that the OS is currently installed on. I also don't see why I would want to involve another computer to do a simple cloning operation. That's never been necessary before when going from HDD to HDD. I'm an I.T. Manager, so I'm very familiar with cloning and Sysprep. My questions are only revolving around the OS's autoconfig for an SSD drive.

 

[linnemeyerhere]

This program comes with some Crucial SSD's and it performs all the needed settings when transferring to the new SSD.
Highly recommended but you will need an adapter cable of some sort unless you order there kit.
EZ Gig IV Cloning Software with Data Select for Windows - Software - Products
I understand that the new Acronis will also handle this ISO as I'm sure other programs can as well but I can speak directly to the ease of the Apricorn......it's a cake walk !

 

[arkhi]

I didn't know complications exist between cloning an HHD to an SSD. I would have always assumed that you can simply image a drive to a .vhd and import said image to an SSD. I mean, wouldn't the OS recognize it immediately as an SSD anyway and apply the necessary operations for proper use?

 

[DeaconFrost]

That's the question. Based on the tutorial's listed here, I'm inclined to think no, unless you use something like Paragon that's specifically designed to do this. I'll probably end up trying it with Partition Wizard.

 

[linnemeyerhere]

arkhi,
I've heard sometimes luck can happen but the ideal way is either a clean install and data transfer or to use one of these latest generation imaging programs that take the SSD's particulars like trim and such into factor.

 

[arkhi]

Ohh. Cool, now I know that I should be cautious should I decide to get an SSD myself. Thank you

 

[pbcopter]

I used Acronis True Image to create an image of my original Hard drive (Windows 7) and then recovered the image to an new SSD. The correct alignment was preserved and Windows recognized it as an SSD and disabled Defrag as well as enabled trim, etc. The only thing I needed to do was disable indexing for the drive.

 

[gregrocker]

I'd lean toward the free quality premium Acronis cloning/imaging app which comes free with any WD or Seagate HD in the mix. Or one of the recommended freebies: Win7, Macrium, Paragon 11.

Here's the book on this: SSD - Install and transfer the Operating System

 

[aem]

There's no need to use Sysprep when it would be used in the same system that the OS is currently installed on. I also don't see why I would want to involve another computer to do a simple cloning operation. That's never been necessary before when going from HDD to HDD. I'm an I.T. Manager, so I'm very familiar with cloning and Sysprep. My questions are only revolving around the OS's autoconfig for an SSD drive.

You sysprep to make it ready to be captured and dumped. Doesn't matter where you dump the image it's about preparing an image, capturing it onto a media and then dumping it onto another machine or in this case your SSD. But i know this is not what you are after, right?

You scenario is this.

HDD0 - The OS you want to capture.
HDD1 - The SSD you want to dump the image of HDD0 onto.

HDD0 and HDD1 are on the same machine.

If this is not correct where is the SSD?

I'd lean toward the free quality premium Acronis cloning/imaging app which comes free with any WD or Seagate HD in the mix. Or one of the recommended freebies: Win7, Macrium, Paragon 11.

Here's the book on this: SSD - Install and transfer the Operating System

"The OS transfer

This is done with an image. There are a variety of free imaging programs (e.g., the free editions of Macrium, Paragon, Acronis, etc.) that are suitable for the task. You can also use the Windows7 imaging, which has the advantage that it deals with the 100MB active boot partition automatically. Disadvantage is that you never know exactly what it does.

You image your partitions to an external disk (you may have to assign a drive letter to the 100MB partition so that the imaging program can identify it) and then pull the images back in to the SSD (using the bootable recovery program of the imaging program).
"

This is basically capturing an image, dumping it onto another media, then puting it back to the SSD. Sounds like what i would do with North Ghost and Bart PE (excluding the technicality of removing SSIDs etc).

 

[DeaconFrost]

You sysprep to make it ready to be captured and dumped. Doesn't matter where you dump the image it's about preparing an image, capturing it onto a media and then dumping it onto another machine or in this case your SSD. But i know this is not what you are after, right?

That is my scenario listed, but Sysprep is not needed when there are no hardware or licensing changes. I'm also not creating an image at all. I'm cloning from one drive to the other. I'm not asking about or questioning the process....I'm asking about the software used to clone, and how, or if, it can configure Windows 7 properly.

 

[preiius]

Everyone recommends starting from scratch. Reinstalling windows and applications take minutes, they say, but they usually left out what a pain it is to configure them.

As ignatzatsonic said, no one has said with authority that cloning from hdd to ssd doesn't work if the imaging tools is compatible with win7 and supports alignment, such as true image 2011.

Once you moved to a ssd, and if win7 hasn't already recognized it is now running on a ssd, try refreshing WEI to tell windows to reconfigure itself on what hardware it is running on, i.e. enable trim, disable defrag, proper alignment, etc.

 

[DeaconFrost]

That was going to be my plan. Starting from scratch is no big deal, as I am down to under 2 hours for that entire process. I was asking out of curiosity, mainly. This is on a work system, so I was looking for the quickest solution.

 

[gregrocker]

Try cloning or imaging it over to see how performance pans out. If it doesn't then do the clean install.

Have been surprised at user satisfaction with transferring to HD>SSD using imaging. Wolfgang's tutorial receives much deserved praise as it allows tuning the image to SSD.

 

[aem]

You sysprep to make it ready to be captured and dumped. Doesn't matter where you dump the image it's about preparing an image, capturing it onto a media and then dumping it onto another machine or in this case your SSD. But i know this is not what you are after, right?

I'm asking about the software used to clone, and how, or if, it can configure Windows 7 properly.

Yes i know but you already know a couple of software that clones HDDs. And i have given oen also Ghost. But which will work for Windows 7 is something of a trial and error. If you are worried about SIDs, Windows Keys, MAC address, Computername (or anyone of of those). Sysprep with imagex i recon.

 

[essenbe]

The real question is not the clone itself but whether the alignment will be correct. I have used the acronis clone feature several times. It works most of the time but I have had it mess up the alignment too. It is not foolproof. The clone is foolproof but it is the alignment that does not always remain correct. Paragon migrate will do it every time exactly correct. I have transfered an OS with it to a new raw drive. It came out perfect and aligned exactly right. No prep needed.