RE: Company physically relocating.. Win2k native w/Exch 2000 -> Win2k3

From: Feng Mao (fengmao_at_online.microsoft.com)
Date: 08/03/04


Date: Tue, 03 Aug 2004 06:47:16 GMT

Hi Bill,

Thank you for posting!

There is a KB article describes the necessary steps to upgrade Windows 2000
domain to Windows 2003 domain. As you have Exchange 2000 Server in Windows
2000 domain, please pay attection to the "Microsoft Exchange 2000 in
Windows 2000 forests" section.

How to upgrade Windows 2000 domain controllers to Windows Server 2003
http://support.microsoft.com/?kbid=325379

I hope that it helps.

Have a nice day!

Thanks & Regards,

Feng Mao [MSFT], MCSE
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: Company physically relocating.. Win2k native w/Exch 2000 ->
Win2k3
| thread-index: AcR4ohbr7PmH+wOVQv6mfYJmOfoUQw==
| X-WBNR-Posting-Host: 64.211.4.249
| From: "=?Utf-8?B?QmlsbHkgRA==?=" <Billy D@discussions.microsoft.com>
| Subject: Company physically relocating.. Win2k native w/Exch 2000 ->
Win2k3
| Date: Mon, 2 Aug 2004 08:05:03 -0700
| Lines: 28
| Message-ID: <E019493E-EFFE-4F1E-9636-7F9CC2E24DA1@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.migration:12685
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Hello All,
| Thanks ahead of time for responses. We are moving/relocating in a few
months and would like some suggestions on the best way to move/migrate our
servers at the same time with minimal headache (if that is possible) .. We
have the following:
|
| 1 DC - DHCP/WINS/ROOT AD/Schema/GC/Infra/RID/PDC
| 1 DC - GC
| 1 DNS
| 1 Exchange 2000 (Back-End)
| 1 Exchange 2000 (Front-End)
|
| We also have 4 remote offices running with a DC and Exchange server at
each site.
|
| We are physically moving to a new location and would like to plan the
best approach with minimal downtime. We'd like to upgrade alot of things
(hardware, OS, etc) but due to time contraints and manpower, we just need
minimal upgrade and do the rest later once we're settled. We have (2) new
servers ready for the upgrade to Win2k3.. eventually I would like to
replace our existing (2) DC's with these (2) new servers. Also note, we've
also done adprep/forestprep and we have no issues/use for the attributes
that were referenced under Exchange (iNetOrgPerson?)
|
| My thoughts are:
| 1. Install both new Win2k3 member then DCPROMO.
| 2. Transfer FSMO roles to one of the new servers.
| 3. Keep all (4) online.
| 4. For testing, move one of the new servers to the new site (new IP)..
treat it as a branch office? test updates, etc.
|
| After that I assume everything will fall in place? if it works then we
can move them over? During that transition period, we will keep our
existing IP structure.. for testing purposes we'll have a small subnet for
testing. Are there issues that I need to be aware of as far as IP/DNS ?
Should another internal DNS server be setup (Win2k3) for this as well at
the new site?
|
| Also thinking about doing Exchange 2003 upgrade, but may wait till move
is done when we're settled.
|
| Any other steps i may have missed, please advise.
|
| Again thanks for everyone's help.
|
| Bill
|



Relevant Pages

  • Re: NT to W2K3 Migration
    ... You cannot just promote a member server to AD. ... upgrade your PDC to windows 2000 or 2003, whichever flavor of AD you want to ... Upgrading from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: Native 2003 mode and NT4 workstations?
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • RE: Single Server Upgrade Exchange Question
    ... The Exchange Migration Wizard can migrate all user mailboxes. ... server and then import them to the destination server. ... Single Server Upgrade Exchange Question ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)

Loading