W2000 Server Transfer To New PC.

Discussion in 'NZ Computing' started by bigmouth, May 10, 2004.

  1. bigmouth

    bigmouth Guest

    While drunk on the weekend I apparently promised to help a friend who has an
    existing W2000 server, transfer the O/S to a new PC he will be getting.

    In the cold light of day and with the alcohol rapidly leaching out of my
    system, I need some help to prepare.

    I am thinking of putting the old Hard drive into the new PC and using the HD
    manufacturer's utility to copy the old to the new. I then was going to put
    the CD in and run a repair. At least I think that is what I thought.

    Any ideas?
    Is there a FAQ out there of some sort?
    I would try google but my head hurts (and I am lazy)

    Thank You.
    bigmouth, May 10, 2004
    #1
    1. Advertising

  2. bigmouth

    Rupert Guest

    You could put the new HDD into the old server - copy the entire disk across,
    move it to the new server and then use the W2K recovery console to install a
    new MBR etc. Once Windows starts up it will have a fit while coming to grips
    with all the new hardware but once that is done you should be fine.

    perhaps delete as much hardware in the device manager as you can though
    before you make the copy....

    "bigmouth" <> wrote in message
    news:LSAnc.2706$...
    > While drunk on the weekend I apparently promised to help a friend who has
    > an
    > existing W2000 server, transfer the O/S to a new PC he will be getting.
    >
    > In the cold light of day and with the alcohol rapidly leaching out of my
    > system, I need some help to prepare.
    >
    > I am thinking of putting the old Hard drive into the new PC and using the
    > HD
    > manufacturer's utility to copy the old to the new. I then was going to put
    > the CD in and run a repair. At least I think that is what I thought.
    >
    > Any ideas?
    > Is there a FAQ out there of some sort?
    > I would try google but my head hurts (and I am lazy)
    >
    > Thank You.
    >
    >
    Rupert, May 10, 2004
    #2
    1. Advertising

  3. Rupert
    > You could put the new HDD into the old server - copy the entire disk across,
    > move it to the new server and then use the W2K recovery console to install a
    > new MBR etc. Once Windows starts up it will have a fit while coming to grips
    > with all the new hardware but once that is done you should be fine.


    The biggest problem is the Hardware Abstraction Layer which is machine
    specific. This is part of Windows NT, 2000 and XP etc.

    There is a MS tool called Sysprep which can be used to facilitate the
    transfer of an image from a different machine, I'm not sure where you can
    get it from. I think it works by forcing Windows to rescan the hardware.
    Patrick Dunford, May 10, 2004
    #3
  4. bigmouth

    AD. Guest

    On Mon, 10 May 2004 18:14:04 +1200, Patrick Dunford wrote:

    > Rupert
    >> You could put the new HDD into the old server - copy the entire disk
    >> across, move it to the new server and then use the W2K recovery console
    >> to install a new MBR etc. Once Windows starts up it will have a fit
    >> while coming to grips with all the new hardware but once that is done
    >> you should be fine.

    >
    > The biggest problem is the Hardware Abstraction Layer which is machine
    > specific. This is part of Windows NT, 2000 and XP etc.


    That depends how you define machine specific.

    Last time I looked there were only a handful of different HALs ie ACPI vs
    APM, uniprocessor vs multiprocessor etc. That might've changed since
    XP/2003 came out but I doubt it.

    Two different uniprocessor ACPI machines (for example) would more than
    likely require the same HAL.

    There were the odd machines that came with vendor supplied HALs (eg some
    Compaq or SGI machines), but they were very rare back in the NT days and
    should be even rarer now after everyone realised what a PITA they were
    regarding service packs etc.

    Cheers
    Anton
    AD., May 10, 2004
    #4
  5. bigmouth

    EMB Guest

    In news:p,
    AD. <> expelled:
    >
    > Last time I looked there were only a handful of different HALs ie
    > ACPI vs APM, uniprocessor vs multiprocessor etc. That might've
    > changed since XP/2003 came out but I doubt it.
    >
    > Two different uniprocessor ACPI machines (for example) would more than
    > likely require the same HAL.
    >

    Bit more complex than that I think - the HAL is different between 2
    uniprocessor motherboards (both recent socket 462 but using different
    chipsets) I have here - I've tried and abandoned moving W2K between them.

    --
    EMB
    change two to number to reply
    EMB, May 10, 2004
    #5
  6. bigmouth

    Enkidu Guest

    On Mon, 10 May 2004 20:40:46 +1200, "AD." <> wrote:

    >On Mon, 10 May 2004 18:14:04 +1200, Patrick Dunford wrote:
    >
    >> Rupert
    >>> You could put the new HDD into the old server - copy the entire disk
    >>> across, move it to the new server and then use the W2K recovery console
    >>> to install a new MBR etc. Once Windows starts up it will have a fit
    >>> while coming to grips with all the new hardware but once that is done
    >>> you should be fine.

    >>
    >> The biggest problem is the Hardware Abstraction Layer which is machine
    >> specific. This is part of Windows NT, 2000 and XP etc.

    >
    >That depends how you define machine specific.
    >
    >Last time I looked there were only a handful of different HALs ie ACPI vs
    >APM, uniprocessor vs multiprocessor etc. That might've changed since
    >XP/2003 came out but I doubt it.
    >
    >Two different uniprocessor ACPI machines (for example) would more than
    >likely require the same HAL.
    >

    No, there are definitely a number of HALs for uniprocessor machines.

    Cheers,

    Cliff
    Enkidu, May 10, 2004
    #6
  7. bigmouth

    Enkidu Guest

    On Mon, 10 May 2004 13:26:00 +1200, "bigmouth" <> wrote:

    >While drunk on the weekend I apparently promised to help a friend who has an
    >existing W2000 server, transfer the O/S to a new PC he will be getting.
    >
    >In the cold light of day and with the alcohol rapidly leaching out of my
    >system, I need some help to prepare.
    >
    >I am thinking of putting the old Hard drive into the new PC and using the HD
    >manufacturer's utility to copy the old to the new. I then was going to put
    >the CD in and run a repair. At least I think that is what I thought.
    >
    >Any ideas?
    >Is there a FAQ out there of some sort?
    >I would try google but my head hurts (and I am lazy)
    >

    It may work, but I'd go for the reinstall. I've never fully trusted
    the repair thing and it has never completely fixed problems when I've
    used it.

    So what would you do? Shift and repair, and end up with a machine that
    isn't 100% or do a bright shiny rebuild, move only what's necessary,
    and leave all the accumulated dross behind?

    Cheers,

    Cliff
    Enkidu, May 10, 2004
    #7
  8. bigmouth

    steve Guest

    Enkidu wrote:

    > So what would you do? Shift and repair, and end up with a machine that
    > isn't 100% or do a bright shiny rebuild, move only what's necessary,
    > and leave all the accumulated dross behind?
    >
    > Cheers,
    >
    > Cliff


    With Linux, you can copy the existing system to a new disc over top of
    the barest of installs (just enough to boot).

    Windows is just too damn HARD and inflexible where this sort of thing is
    concerned.

    For a "business" or "enterprise" system, you'd think they would have
    this down to the point where you could just about do it automagically.

    Linux - bare install to new drive; boot from floppy or CD and copy the
    contents of the old hard drive over top of the basic install on the new
    hard drive....

    All done. Reboot.

    --
    ********************************************************************************
    "..... all experience hath shewn, that mankind are more disposed
    to suffer, while evils are sufferable, than to right themselves
    by abolishing the forms to which they are accustomed."
    - Thomas Jefferson
    steve, May 10, 2004
    #8
  9. bigmouth

    AD. Guest

    On Mon, 10 May 2004 20:59:35 +1200, EMB wrote:

    > In news:p, AD. <>
    > expelled:
    >>
    >> Last time I looked there were only a handful of different HALs ie ACPI
    >> vs APM, uniprocessor vs multiprocessor etc. That might've changed since
    >> XP/2003 came out but I doubt it.
    >>
    >> Two different uniprocessor ACPI machines (for example) would more than
    >> likely require the same HAL.
    >>

    > Bit more complex than that I think - the HAL is different between 2
    > uniprocessor motherboards (both recent socket 462 but using different
    > chipsets) I have here - I've tried and abandoned moving W2K between them.


    Are you sure it's actually the HAL itself that is causing the problem?

    I suspect people are confusing the HAL with the multitude of hardware
    specific drivers, registry settings, plug and play settings that get in
    the way when trying to move installs between machines.

    The HAL (eg hal.dll and maybe one or two other dlls) presents a consistent
    hardware interface between the kernel and the device drivers. It's purpose
    was to help make NT a much more portable OS.

    Now that I've bothered to have a look and count them, there are 8
    different HALs distributed with Windows 2000. 6 standard MS ones, and one
    each from Compaq and SGI.

    I admit that I'm not really sure these days whether or not many chipset /
    motherboard vendors produce their own specific ones, because I always use
    an MS one when installing Windows. But in the old NT days (it might be
    different now), people with vendor supplied HALs had to wait for their
    vendor to bring out service packs. That was the main reason it wasn't very
    popular.

    Cheers
    Anton
    AD., May 10, 2004
    #9
  10. bigmouth

    AD. Guest

    On Mon, 10 May 2004 23:10:05 +1200, Enkidu wrote:

    > On Mon, 10 May 2004 20:40:46 +1200, "AD." <> wrote:
    >>Last time I looked there were only a handful of different HALs ie ACPI vs
    >>APM, uniprocessor vs multiprocessor etc. That might've changed since
    >>XP/2003 came out but I doubt it.
    >>
    >>Two different uniprocessor ACPI machines (for example) would more than
    >>likely require the same HAL.
    >>

    > No, there are definitely a number of HALs for uniprocessor machines.


    I said 'more than likely'. There are 4 MS supplied uniprocessor supplied
    HALs in W2K, and only two are ACPI.

    Things are different of course if your hardware vendor supplied the HAL,
    but as far as I knew (things might've changed) only very specialised
    machines had them - eg the SGI virtual workstation that had a very
    different architecture than the average Intel machine of the time.]

    Cheers
    Anton
    AD., May 10, 2004
    #10
  11. bigmouth

    Howard Guest

    steve wrote:

    > Linux - bare install to new drive; boot from floppy or CD and copy the
    > contents of the old hard drive over top of the basic install on the
    > new hard drive....
    >
    > All done. Reboot.


    Steve,

    Would you even need to reboot? And if so, why?

    -H
    Howard, May 11, 2004
    #11
  12. bigmouth

    Edmond Lo Guest

    This are MS kb articles about doing just that.

    Do a seach on Technet or have a look at Q314082 (for XP or W2003) or look
    for similar.


    "bigmouth" <> wrote in message
    news:LSAnc.2706$...
    > While drunk on the weekend I apparently promised to help a friend who has

    an
    > existing W2000 server, transfer the O/S to a new PC he will be getting.
    >
    > In the cold light of day and with the alcohol rapidly leaching out of my
    > system, I need some help to prepare.
    >
    > I am thinking of putting the old Hard drive into the new PC and using the

    HD
    > manufacturer's utility to copy the old to the new. I then was going to put
    > the CD in and run a repair. At least I think that is what I thought.
    >
    > Any ideas?
    > Is there a FAQ out there of some sort?
    > I would try google but my head hurts (and I am lazy)
    >
    > Thank You.
    >
    >
    Edmond Lo, May 11, 2004
    #12
  13. bigmouth

    Enkidu Guest

    On Mon, 10 May 2004 23:33:41 +1200, steve <>
    wrote:

    >Enkidu wrote:
    >
    >> So what would you do? Shift and repair, and end up with a machine that
    >> isn't 100% or do a bright shiny rebuild, move only what's necessary,
    >> and leave all the accumulated dross behind?

    >
    >With Linux, you can copy the existing system to a new disc over top of
    >the barest of installs (just enough to boot).
    >

    We were talking about Windows and someone who needed help with
    Windows.

    Even with Linux there are good reasons for doing a rebuild rather than
    a system copy. It's called "leaving the accumulated crud behind".

    Cheers,

    Cliff
    Enkidu, May 11, 2004
    #13
  14. bigmouth

    -=rjh=- Guest

    bigmouth wrote:

    > While drunk on the weekend I apparently promised to help a friend who has
    > an existing W2000 server, transfer the O/S to a new PC he will be getting.
    >
    > In the cold light of day and with the alcohol rapidly leaching out of my
    > system, I need some help to prepare.
    >
    > I am thinking of putting the old Hard drive into the new PC and using the
    > HD manufacturer's utility to copy the old to the new. I then was going to
    > put the CD in and run a repair. At least I think that is what I thought.
    >
    > Any ideas?
    > Is there a FAQ out there of some sort?
    > I would try google but my head hurts (and I am lazy)
    >
    > Thank You.


    Check out

    http://www.windowsreinstall.com/install/other/motherboard/win2k.htm


    cheers
    -=rjh=-, May 12, 2004
    #14
  15. bigmouth

    Rob Guest

    "bigmouth" <> wrote in message news:<LSAnc.2706$>...
    > While drunk on the weekend I apparently promised to help a friend who has an
    > existing W2000 server, transfer the O/S to a new PC he will be getting.
    >
    > In the cold light of day and with the alcohol rapidly leaching out of my
    > system, I need some help to prepare.
    >
    > I am thinking of putting the old Hard drive into the new PC and using the HD
    > manufacturer's utility to copy the old to the new. I then was going to put
    > the CD in and run a repair. At least I think that is what I thought.
    >
    > Any ideas?
    > Is there a FAQ out there of some sort?
    > I would try google but my head hurts (and I am lazy)
    >
    > Thank You.


    Here's how I clone machines - YMMV:

    Put the new HDD in the OLD pc and use Ghost to mirror the old drive to
    the new one. Take out the old drive and hold onto it as a backup for
    now.

    Boot the OLD pc off the newly ghosted drive and then run sysprep
    /reseal to "clean" the Windows installation. At the end of sysprep
    the machine will shutdown.

    Whip the new HDD out and put it into the NEW pc.

    Boot the new PC. Windows will take longer to boot because it has to
    redetect all the hardware. It will then jump into mini-setup where
    you can enter the bits of info it needs (passwords, cd key etc.).

    Finally Windows will kick into life on the new hardware.



    I have used this method to move virtual machines from VMware GSX to
    Virtual Server but the theory still holds for physical machines.

    Sysprep info:
    http://www.acs.unimelb.edu.au/software/sysprep.html

    Using sysprep with Ghost:
    http://service4.symantec.com/SUPPORT/ghost.nsf/docid/2000081610075225?OpenDocument&ExpandSection=3,2
    Rob, May 13, 2004
    #15
  16. bigmouth

    Rob Guest

    Patrick Dunford <> wrote in message news:<>...
    > Rupert
    > > You could put the new HDD into the old server - copy the entire disk across,
    > > move it to the new server and then use the W2K recovery console to install a
    > > new MBR etc. Once Windows starts up it will have a fit while coming to grips
    > > with all the new hardware but once that is done you should be fine.

    >
    > The biggest problem is the Hardware Abstraction Layer which is machine
    > specific. This is part of Windows NT, 2000 and XP etc.
    >
    > There is a MS tool called Sysprep which can be used to facilitate the
    > transfer of an image from a different machine, I'm not sure where you can
    > get it from. I think it works by forcing Windows to rescan the hardware.


    Yeah it does and it works brilliantly. I've used it quite a bit to do
    this kind of thing.

    Sysprep can be found in \SUPPORT\TOOLS\DEPLOY.CAB on your Windows CD.
    Rob, May 13, 2004
    #16
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Zenner

    Re: Shared folder on W2000

    Zenner, Jul 17, 2003, in forum: MCSE
    Replies:
    0
    Views:
    395
    Zenner
    Jul 17, 2003
  2. fission
    Replies:
    6
    Views:
    429
    ImhoTech
    May 12, 2004
  3. Wil Jansen
    Replies:
    1
    Views:
    1,223
    Sparky Polastri
    Aug 17, 2004
  4. Wil Jansen
    Replies:
    0
    Views:
    388
    Wil Jansen
    Aug 25, 2004
  5. Henny Jansen

    mirroring and spanned volumes on W2000 server

    Henny Jansen, Oct 4, 2004, in forum: Computer Support
    Replies:
    1
    Views:
    431
Loading...

Share This Page