Re: Hardware upgrade
From: DavidA (d_l_adamson_at_hotmail.com)
Date: 03/07/04
- Next message: Leonard Severt [MSFT]: "Re: Recovery Console /Format /reinstall windows 2000"
- Previous message: Ruth: "Upgrade"
- In reply to: DavidA: "Re: Hardware upgrade"
- Messages sorted by: [ date ] [ thread ]
Date: 7 Mar 2004 13:49:22 -0800
I'd like to thank the people who responded, and also others who have
responded to similar questions elsewhere. In the end, I seem to have
made things work. Here is what I did:
1) Full back up, including system state.
2) Installed new RAID controller & 4 disks. (Had trouble formatting
it - I had to remove the disk on the IDE channel and boot from W2000
CD and get that to format it - then reconnect the IDE disk and that
gave me the RAID array as a formatted drive D)
3) Took another backup (forgot to do system state and forgot to
exclude the previous backup file so it was a large backup file!)
4) Copied the backup files to the RAID array - these were the only
files on it.
5) Made an Emergency Recovery Disk
6) Transferred the RAID array to the new PC.
7)Booted from setup CD and tried to do a repair using only the ERD and
the backup file on the disk. This seemed to nearly work, but not
quite.
8) Went to plan B. Did a new install on the RAID array in the new PC
without re-formatting the disk (so the backup files were preserved).
9) Did a full restore, including system state (fromt he backup BEFORE
the RAID driver had been installed). This successfully turned the new
PC into the "same" as the old one EXCEPT for the unfortunate fact that
the network card was different (I think I could have avoided this
problem by temporarily using the network card from the old server!)
10) Discovered that the static IP address I had previously used for
the server (and which I didn't want to change) was still assigned to a
phantom network card which was the one that belonged in the old
server.
11) Tried to fix this by moving the network card from the old server
to the new - this didn't work - the card appeared as a new instance of
the same type and the phantom was still there.
12) Searched through the registry for entries of "Netgear" - the old
card was a Netgear one and the new one was "D-Link". Deleted all the
registry entries that I could (I wasn't allowed to delete some). This
was risky, but I still had Plan C in reserve because the old server
was still fully functional and I could have made the new one a
secondary domain controller and done the dcpromo stuff.
13) Re-started and tried to set the IP addres to the one I wanted.
This worked, and from then on, my new PC "looks" to the rest of the
network, just like the old one.
d_l_adamson@hotmail.com (DavidA) wrote in message news:<cb20310c.0403051503.bbb49fc@posting.google.com>...
> It is a domain controller, so I would have to do the more complex
> operation described below. I am not at all expert on the operations
> you are talking about - can you give me pointers to more information
> on the process please?
>
> Thanks,
> DavidA
>
> >
> > If your Server is a domain controller, then you can NOT
> > run SYSPREP. I suggest to install a clean Windows 2000
> > on the new hardware, add it to the domain, make it another
> > domain controller of your existent domain (like this you
> > get a mirror copy of your Active directory database into
> > the second DC), move the shared folders and all objects
> > into the second DC. Move the infrastructure master, RID
> > master, PDC emulator, operation master, and Global Catalog
> > to the second DC, remove the first DC from the network by
> > taking it offline.
- Next message: Leonard Severt [MSFT]: "Re: Recovery Console /Format /reinstall windows 2000"
- Previous message: Ruth: "Upgrade"
- In reply to: DavidA: "Re: Hardware upgrade"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
