How do I image Windows Home Server to a new hard drive?

By compuwysepc ·
Does anyone have a proven successful procedure to re-image a Windows Home Server to a new hard drive? I tried doing a disk to disk copy using Image Center, and it reported the duplication successful; however after being able to boot into Home Server successfully multiple file errors and 'backup service is not running' messages are displayed. I assume this is due to the manner in which Home Server adds/removes, and identifies connected drives. I have the original installation on a 160GB IDE drive and would like to move it to a 250GB SATA drive. After imaging the original, disconnected 160GB IDE drive registered as 'missing', and the 250GB shows as 'not added', despite being able to boot into it. I was able to reconnect the original drive and add the 250GB SATA drive, but that does not accomplish my goal, as I wanted the 160GB IDE drive replaced. Any ideas?
Note: I also have Paragon 8, Acronis True Image 8, and Clonezilla available for disk imaging or duplicating, but suspect that I will still encounter the same errors with those applications as well.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Call or chat with the people at Laplink Software.

by Ron K. In reply to How do I image Windows Ho ...

They have excellent phone and chat support. <br>
I've used PCMover Pro twice, successfully.<br>

Collapse -

I'm starting to think...

by NexS In reply to Call or chat with the peo ...

That you've got shares with Laplink

Collapse -

Here are a few things to remember when doing a clone or copy..

by Peconet Tietokoneet In reply to How do I image Windows Ho ...

1). Defrag. Make sure you do a defrag of the drive that you are copying from.

1a). Clean. Do a good clean up with Ccleaner:

2). Updates. Make sure you have all of the updates for the system.

3) Format. Do a low level format on the new drive to be sure there is nothing on it.

When you do a clone/copy of the drive, make sure you take everything off of the computer such as external drives etc.
When there are not any errors to the original drive, then use the cloning software to clone the drive or drives in question.
I have cloned many drives using Paragon software, but get the up to date version it works very well for what you need.

Hope this helps you out.

Collapse -

Thanks for the reminders

by compuwysepc In reply to Here are a few things to ...

Thanks for your suggestions, but the problem is not with being unfamiliar with cloning a hard drive, I have considerable experience cloning drives. My issues are specific to Windows Home Server. Because of the way Windows Home Server handles the removal or addition of drives, doing a standard disk clone results in the OS not being configured properly to recognize the new drive, and still expects to be able to access the old drive. Hence the 'not added' and 'missing' designations in the Server Storage window. When you add a new drive in Home Server it is formatted and added to the DATA partition to increase the storage capacity. It is not assigned a drive letter, it appears to be similar if not identical to mounting a new drive to an empty NTFS folder in XP. When you remove a drive from Home Server the data that is on it is dispersed across any remaining drives (hopefully without loss of data), the only exception is the SYS partition that is created during initial installation of the OS, I believe this partition remains unchanged regardless of whether you are adding or removing another drive. For exmple; when I added my 250GB SATA drive the DATA partition registered as 160GB size, but showed 292GB of Free Space, indicating that the remaining free space on the 160GB IDE drive and the available free space on the 250GB SATA drive were combined. By comparison the SYS partition showed no changes in capacity of free space sizes. So my dilemma is; Is there any way to remove the the old drive properly and add the new drive without Home Server trying to re-format the new drive after I just cloned the old one onto it?

Collapse -

Maybe this can help you...

by wellcraft19 In reply to Thanks for the reminders

Not sure, but it sounds like you are upgrading your system drive, and then this post ought to be of assistance:

Collapse -

You're correct, I am upgrading my system drive.

by compuwysepc In reply to Maybe this can help you.. ...

Your link sounds like it may be a solution, but I was hoping for something that didn't require reinstalling. Turning on duplication for all drives might solve shares issue, but still doesn't address system partition without reinstalling the OS and recreating the users.
Also since the system drive and the data drive are 2 partitions on the same physical drive, it isn't possible to just upgrade one without risking potential data loss on the other (or is it?).
The post on your link does mention the Drive Extender, which I suspect is 1 of 2 services that complicate the transfer. I believe the Drive Extender service and the Server Storage Mangement service are responsible for the drives are recognized and accessed by Home Server. It appears (and I admit that there is considerable conjecture and semi-educated guess work involved here) that drives configured in what behaves like some sort of hybrid cross between a Striped RAID and a JBOD. But the real problem seems to be that the actual physical hardware is somehow linked to the storage pool of Home Server, either by the serial number or drive parameters within the firmware of the drive itself.

Related Discussions

Related Forums