RE: 3 MUD Migration Strategy thoughts please
From: Rebecca Chen [MSFT] (v-rebc_at_online.microsoft.com)
Date: 10/22/04
- Next message: David: "RE: Migration to Server 2003 / Exchange 2003"
- Previous message: rtootle: "RE: AD Migration Error migrating Workstation from NT 4.0 domain"
- In reply to: Mike: "3 MUD Migration Strategy thoughts please"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 22 Oct 2004 11:22:53 GMT
Hi Mike,
The plan seems good. :)
It seems your enterprise is pretty large. I suggest you consider the whole
structure of the AD, such as how to design the forest, domain's
relationship etc. below is some links for your reference:
Active Directory Operations Overview
http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/ac
tivedirectory/maintain/opsguide/part1/adogd00.mspx
Deployment Planning Guide
http://www.microsoft.com/windows2000/techinfo/reskit/dpg/default.asp
Once you have decided to implement an in-place upgrade process will go like
this:
- Install NT 4.0 BDC on the new hardware
- Promote a Windows NT 4.0 BDC to the PDC, which demotes the PDC to
a BDC.
- Do a full backup of the former PDC and remove it from the network.
- Upgrade the new PDC to Windows Server 2003.
- Use the Windows Server 2003 Active Directory wizard to turn on the
Active Directory service. The Active Directory service imports the existing
user accounts, groups, and other settings from the PDC.
- Run your new Windows Server 2003 domain controller with Active
Directory for a test period.
- If desired you can do a clean installation of Windows Server 2003
on the former PDC, and bring it online as an Active Directory domain
controller.
- Transfer all Flexible Single-Master Operation (FSMO) roles to the
new Windows Server 2003 domain controller.
- Verify all directory information has replicated.
- Demote the first domain controller to a member server, and remove
from the domain.
Then, you can install Exchange server and transfer mailbox etc. For
Exchange part, I suggest you post all Exchange-related question to the
microsoft.public.exchange.setup since the Exchange guy will provide more
valuable suggestions.
Why Upgrade from Windows NT 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4town
et.mspx
Upgrading from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tows
03-2.mspx
Any update, let us get in touch!
Best regards,
Hi Mike,
The plan seems good. :)
It seems your enterprise is pretty large. I suggest you consider the whole
structure of the AD, such as how to design the forest, domain's
relationship etc. below is some links for your reference:
Active Directory Operations Overview
http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/ac
tivedirectory/maintain/opsguide/part1/adogd00.mspx
Deployment Planning Guide
http://www.microsoft.com/windows2000/techinfo/reskit/dpg/default.asp
Once you have decided to implement an in-place upgrade process will go like
this:
- Install NT 4.0 BDC on the new hardware
- Promote a Windows NT 4.0 BDC to the PDC, which demotes the PDC to
a BDC.
- Do a full backup of the former PDC and remove it from the network.
- Upgrade the new PDC to Windows Server 2003.
- Use the Windows Server 2003 Active Directory wizard to turn on the
Active Directory service. The Active Directory service imports the existing
user accounts, groups, and other settings from the PDC.
- Run your new Windows Server 2003 domain controller with Active
Directory for a test period.
- If desired you can do a clean installation of Windows Server 2003
on the former PDC, and bring it online as an Active Directory domain
controller.
- Transfer all Flexible Single-Master Operation (FSMO) roles to the
new Windows Server 2003 domain controller.
- Verify all directory information has replicated.
- Demote the first domain controller to a member server, and remove
from the domain.
Then, you can install Exchange server and transfer mailbox etc. For
Exchange part, I suggest you post all Exchange-related question to the
microsoft.public.exchange.setup since the Exchange guy will provide more
valuable suggestions.
Why Upgrade from Windows NT 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4town
et.mspx
Upgrading from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tows
03-2.mspx
Any update, let us get in touch!
Rebecca Chen
MCSE2000 MCDBA CCNA
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: 3 MUD Migration Strategy thoughts please
>thread-index: AcS3YbkIDcPMkhIMSs+KGCrXzqzslA==
>X-WBNR-Posting-Host: 195.173.57.160
>From: "=?Utf-8?B?TWlrZQ==?=" <Mike@discussions.microsoft.com>
>Subject: 3 MUD Migration Strategy thoughts please
>Date: Thu, 21 Oct 2004 04:33:01 -0700
>Lines: 26
>Message-ID: <B3D78724-2761-4B99-BE69-1DBA754D2662@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: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.migration:14647
>X-Tomcat-NG: microsoft.public.windows.server.migration
>
>Folks,
>
>I'm going back on forth trying to decide on a migration path from NT 4 to
>2003..
>
>We are a 2200 user organisation with 3 NT4 MUD's one of which is the
'main'
>focused account domain. - I was thinking of implementing a couple of new
>BDC's on new hardware into the 'main' account domain, promoting one to be
the
>PDC and then upgrading that to AD in conjunction with the other new BDC.
>
>I see upgrading as a big plus as we won't have to worry as much about
>SIDhistory and ADMT.
>
>Once the new (upgraded) AD domain is in place I plan to install Exchange
>2003 (native mode straight away) into the domain and migrate mailboxes
>across..
>
>I will then subsequently ADMT users and resource from the other domains
into
>the new upgraded AD domain..
>
>Any thoughts? Good or Bad?
>
>We want to minsise the impace to users etc and make things as smooth as
>possible!
>
>M
>
- Next message: David: "RE: Migration to Server 2003 / Exchange 2003"
- Previous message: rtootle: "RE: AD Migration Error migrating Workstation from NT 4.0 domain"
- In reply to: Mike: "3 MUD Migration Strategy thoughts please"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
