RE: Real simple NT to Server 2003 replacement
- From: v-amanwa@xxxxxxxxxxxxxxxxxxxx (Amanda Wang [MSFT])
- Date: Tue, 17 May 2005 06:42:04 GMT
Hello,
Thanks for your post.
The method you mentioned in your post is just as creating a new Windows 2k3
domain. Can I assume that you need to keep the original domain name in
your new Windows 2k3 domain? Actually, if you use this method, you need to
rejoin these workstations to 2003 domain and the copy their profiles again.
Therefore, it is not determined whether you use the same domain as the
original domain name or not.
We recommend you use upgrade path to accomplish the goal. The detailed
recommended upgrade steps are as the following:
As a kind reminder, please backup the whole system before you take any
action. Also, it is best if you perform the upgrade process during a
non-business time such as the weekend. :)
Performing a upgrade
======================
1.Install NT 4.0 BDC on the new box.
2.Promote the BDC to the PDC, which demotes the PDC to a BDC.
3.Do a full backup of the former PDC and remove it from the
network.
4.Upgrade the new PDC to Windows Server 2003.
If you want to expand the boot partition, please refer to the
following KB:
325857 How To Expand the Boot Partition During a Windows Server
2003 Upgrade
http://support.microsoft.com/?id=325857
5.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.
How to Verify an Active Directory Installation
http://support.microsoft.com/default.aspx?scid=kb;en-us;298143
6.Run for a test period.
7.If desired you can do a clean installation of Windows Server 2003
on the new machine that you want to use to be a PDC, and bring it online as
an Active Directory domain controller.
8.Transfer all Flexible Single-Master Operation (FSMO) roles to the
new Windows Server 2003 domain controller.
9.Verify all directory information has replicated.
Verify successful replication to a domain controller
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Opera
tions/00e7f86b-ccd3-4cb8-9a01-bf747241b500.mspx
10.Demote the first domain controller to a member server, and
remove from the domain.
I suggest you check the following KB articles to migrate to Win2k3 from NT4:
Migrating Windows NT Server 4.0 Domains to Windows Server 2003 Active
Directory
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4domt
oad.mspx
Upgrading from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tows
03-2.mspx
HTH!
Thanks & Regards
Amanda Wang [MSFT]
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.
=====================================================================
--------------------
>From: "Bud" <bc1@xxxxxxxxxx>
>Subject: Real simple NT to Server 2003 replacement
>Date: Mon, 16 May 2005 17:18:37 -0700
>Lines: 16
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <OnFF#XnWFHA.1384@xxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.migration
>NNTP-Posting-Host: 207-170-255-77.asisna.com 207.170.255.77
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10204
>X-Tomcat-NG: microsoft.public.windows.server.migration
>
>I have a real simple network composed of 1 NT 4.0 server and 150 clients.
>The NT server is used for DHCP, file serving, and a web proxy. I would
like
>to setup our new 2003 server by copying the files. Then take the server
>offline install Active Directory with the same domain name and DHCP,
>manually entering the users (about 25), the 3 groups, and permissions.
>Demote the NT server to just be our proxy server (I don't know if that is
>even possible, but if it isn't, we would let every station have direct
>access to the net), turn off all the workstations, and hook server 2003
back
>up to the network.
>
>Will this work? Where are the flaws and what should I watch out for?
>
>Thanks,
>Bud
>
>
>
.
- Follow-Ups:
- References:
- Prev by Date: RE: Proxy Server 2.0 issues after server migration into 2003 AD domain
- Next by Date: Re: Cannot browse the network after migration
- Previous by thread: Re: Real simple NT to Server 2003 replacement
- Next by thread: Re: Real simple NT to Server 2003 replacement
- Index(es):
Relevant Pages
|
Loading
