locked
Imaging System Drive RRS feed

  • Question

  • File under "beating dead horse."

    BUT...

    The data on the forum is a bit confliciting. Some say it works, some say it doesnt.

    I want to replace my system drive. When I built my WHS I used an old PC (I was young and dumb and...) its a 3 year old 120GB Samsung which has had a couple near misses with chkdsk errors already.

    My thought was to ghost the drive - OUTSIDE OF THE SERVER - in a non-running config. I would copy the c: partition as-is at 20GB (along with the MBR) and then copy over the d: partition.

    According to at least one thread this works. It seems that most imaging problems have been with people trying to do "live" images on their running WHS.

    Questions:

    1. Anybody tried it this way? Did it work or does WHS leave have some other trick for identifying the system drvie that doesnt get copied?
    2. Has anybody fried their WHS when doing it THIS WAY.
    3. Assuming it does work: Can I resize the D: partition as part of the same process (at least one post said yes)
    4. If I get talked out of this and decide to install the clean drive and do a reinstall, does anyone know of a clean way to get all of my user/add-in/customizations documented somewhere so I have a nice checklist of what I'll be spending all night working on? I's like to get that together before the main drive goes belly up on me.


    Thanks in Advance!
    Tuesday, September 16, 2008 2:23 AM

Answers

  • mprachar said:

    File under "beating dead horse."

    BUT...

    The data on the forum is a bit confliciting. Some say it works, some say it doesnt.

    I want to replace my system drive. When I built my WHS I used an old PC (I was young and dumb and...) its a 3 year old 120GB Samsung which has had a couple near misses with chkdsk errors already.

    My thought was to ghost the drive - OUTSIDE OF THE SERVER - in a non-running config. I would copy the c: partition as-is at 20GB (along with the MBR) and then copy over the d: partition.

    According to at least one thread this works. It seems that most imaging problems have been with people trying to do "live" images on their running WHS.

    First, to clarify:  Doing what you suggest is unsupported.  (And, FWIW, I wouldn't recommend it either.  I would have a real issue with trusting a drive that had been set up in a way that is untested and unsupported by MS.)

    mprachar said:

    Questions:

    1. Anybody tried it this way?

    I personally haven't, but as you said, other people have tried it and I believe some people got it to work.

    mprachar said:

    Did it work or does WHS leave have some other trick for identifying the system drvie that doesnt get copied?

    No.  It's a standard NTFS drive.

    mprachar said:

    2. Has anybody fried their WHS when doing it THIS WAY.

    I don't recall ever seeing anyone say that, but I wouldn't swear that it's never happened.

    mprachar said:

    3. Assuming it does work: Can I resize the D: partition as part of the same process (at least one post said yes)

    In theory, yes.  However, this is precisely the reason why I wouldn't do what you suggest.

    mprachar said:

    4. If I get talked out of this and decide to install the clean drive and do a reinstall, does anyone know of a clean way to get all of my user/add-in/customizations documented somewhere so I have a nice checklist of what I'll be spending all night working on? I's like to get that together before the main drive goes belly up on me.

    The users and add-ins are listed in the Console, so you could just write those down on a piece of paper.  As for customizations (I guess you mean apps you've installed from the desktop), you can find those in Add/Remove Programs.

    mprachar said:

    Thanks in Advance!



    Tuesday, September 16, 2008 2:48 AM
    Moderator