NT 4.0 - 2003 Migration - ADMT vs in place upgrade
- From: "Megan" <megan_grubb@xxxxxxxxx>
- Date: Tue, 30 May 2006 09:50:25 -0400
I'm planning a migration from NT 4.0 Enterprise to 2003 Enterprise. I have
an exchange 5.5 server, which I plan on migrating to a 2003 server (new
hardware, fresh OS install). I plan on doing an in-place upgrade of the
domain, but am still torn between doing that or using ADMT to migrate the
domain. The less I have to play with the client machines, the better. From
a security and reliability stand point, which is better? The following is
just a quick overview of what I'm planning to do.
I currently have the following in my domain:
PCD 1 - NT 4.0 SP6a. Does nothing but serve as a PDC.
BDC 1 - NT 4.0 SP5. RAS, shared printers, file server, WINS.
BDC 2 - NT 4.0 SP6a. Goldmine and quotewerks. Runs several batch files
which serve as license servers.
BDC 3 - NT 4.0 5.0 SP5. Exchange 5.5 SP4. File server. Also runs one
batch file which serves as a license server.
BDC 4 - NT 4.0 SP5. File server. Panapro license server.
Member Server 1 - NT 4.0 SP6a. Blackberry server. (This can easily be
redone after the upgrade)
Standalone Server 1 - Windows 2000 Advanced Server. OWA. (This can easily
be redone after the upgrade as it's rarely used)
Standalone Server 2 - Windows 2000 Server - Nightly Exmerge to PST files.
WSUS. Managed Symantec Anti-virus.
I plan to do the upgrade the following way:
1. Create an extra BDC with SP6a, replicate all domain information.
Disconnect it.
2. Update Rdisks for all NT DCs.
3. Do a few things with the Exchange server (exmerge...manual copy of public
folders...run pfadmin.exe...print out of all mailbox resources...etc.)
4. In place upgrade of PDC 1 to 2003 Enterprise. Install AD and DNS. This
will remain as the PDC emulator.
5. Create a reverse DNS lookup zone on PDC 1.
6. Ensure domain is still functional....otherwise take 2003 server offline
and promote BDC created in step one to a PDC.
7. New exchange server (new hardware) - Install 2003 Enterprise, run DC
promo to install AD.
8. Install Exchange 2003 with latest service pack.
9. Migrate all mailboxes, public folders, etc. from the old Exchange server
to the new one. <--- Not sure the best way to do this. I'd like to keep
the same server name, but don't think it's possible. I know I'll have to
change each client PC. There's a tool to do this, but I can't think of the
name of it right now.
10. New install of 2003 Enterprise and run as a DNS server.
11. Ensure domain is functional and slowly upgrade each NT server to 2003.
Is this the best way to go about doing this? I'm not too concerned about
RAS, OWA, or the blackberry server. Those should be pretty easy to get up
and running again. We still have a dozen or so 98 machines, so I'd like to
leave the domain in mixed mode for a while. Our currently Exchange 5.5
server is not very reliable and I don't trust it one bit, so I would like to
avoid installing the AD Connector. I've tested up to step 6 in a mock
network, and things seem fine so far. I was especially surprised that it
handled the underscore we have in out NetBIOS domain name (very foolish, I
know, but I never set this up).
Can anyone spot anything I'm overlooking? Any other ideas on what I could
do?
.
- Follow-Ups:
- RE: NT 4.0 - 2003 Migration - ADMT vs in place upgrade
- From: Vincent Xu [MSFT]
- RE: NT 4.0 - 2003 Migration - ADMT vs in place upgrade
- Prev by Date: RE: Broken Trust leading to access issues
- Next by Date: Re: Inplace Upgrade Nt 4.0
- Previous by thread: RE: Prepare W2K Server for migration to another drive?
- Next by thread: RE: NT 4.0 - 2003 Migration - ADMT vs in place upgrade
- Index(es):
Relevant Pages
|
