RE: HELP: smooth migration from NT 4 to a new server on Windows 2003
From: Joe Wu [MSFT] (joewu_at_online.microsoft.com)
Date: 02/06/04
- Next message: Ma001: "ADMT migrating user issue"
- Previous message: Joe Wu [MSFT]: "Re: Can't install AD"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 06 Feb 2004 10:52:10 GMT
Hello Jack,
Thank you for your reply.
I think you can install Windows NT BDC on the new server that you want to
run Windows Server 2003 PDC. Apply the latest Service Pack SP6a and promote
it to PDC (the old PDC will be demoted to BDC automatically). Then please
upgrade the domain from the new PDC.
After the upgrade (if everything works well), you can then take the
offlined BDC online.
This is commonly used upgrade method as we can keep the current PDC intact
(if problem occurs, we can promote it to PDC again). In addition, upgrade
from a cleanly-installed system is easier to succeed.
Thanks for your time and cooperation and have a nice weekend!
Regards,
Joe Wu
Product Support Services
Microsoft Corporation
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.
--------------------
|Content-Class: urn:content-classes:message
|From: "Jack Ling" <fly2moon2@discussions.microsoft.com>
|Sender: "Jack Ling" <fly2moon2@discussions.microsoft.com>
|References: <92eb01c3ea27$200cf4d0$a401280a@phx.gbl>
<BEjoTMk6DHA.568@cpmsftngxa07.phx.gbl>
|Subject: RE: HELP: smooth migration from NT 4 to a new server on Windows
2003
|Date: Tue, 3 Feb 2004 19:08:28 -0800
|Lines: 209
|Message-ID: <9e7c01c3eacc$293bf8d0$a601280a@phx.gbl>
|MIME-Version: 1.0
|Content-Type: text/plain;
| charset="iso-8859-1"
|Content-Transfer-Encoding: 7bit
|X-Newsreader: Microsoft CDO for Windows 2000
|X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
|Thread-Index: AcPqzCk7pLe4mthlTsWAKc2s22hHPA==
|Newsgroups: microsoft.public.windows.server.migration
|Path: cpmsftngxa07.phx.gbl
|Xref: cpmsftngxa07.phx.gbl microsoft.public.windows.server.migration:7504
|NNTP-Posting-Host: tk2msftngxa14.phx.gbl 10.40.1.166
|X-Tomcat-NG: microsoft.public.windows.server.migration
|
|Hi Joe,
|
|Thanks a lot for your links to the references. I'll study
|in more details.
|
|As you suggested, Approach A seems easier. But to do an
|in-place upgrade of the old Windows NT server to Windows
|2003, I have to check whether there are limitations of
|the old hardware (whether can support W2K3). Besides, it
|has the additional cost of obtaining one more W2K3 server
|licence to this old server.
|
|I don't know whether this is the case for other
|companies? Don't know what is the general practice of
|most companies as they should have faced the same problem?
|
|* Refer to your recommended steps of Approach A, after
|all the changes are done for the PDC (to upgrade to
|W2K3), what happens to the BDC, which is still in Windows
|NT? When I bring it up online again, what would happen
|and should be done? Do I need to promto the BDC to W2K3
|as well?
|
|thanks,
|jackling.
|
|>-----Original Message-----
|>Hello Jackling,
|>
|>Thanks for your post.
|>
|>We cannot use Approach A if you want to run the Windows
|Server 2003 system
|>as a domain controller. Although we are able to join a
|Windows Server 2003
|>machine into a Windows NT domain as a member server, we
|cannot promote it
|>to be a domain controller.
|>
|>Actually, we have two possible solutions for this
|scenario:
|>
|>Solution 1: Perfome an In-place Upgrade:
|>
|>1. Perform full backups for the existing domain
|controllers. Put a BDC
|>offline for recovery purposes.
|>2. In-place upgrade the PDC to Windows Server 2003 and
|promote the domain.
|>3. Join the Windows Server 2003 to the upgraded domain.
|>4. Promote it to a relica domain controller.
|>5. Move all FSMO roles to the new DC.
|>6. Make it a GC.
|>
|>
|>Reference:
|>
|>Upgrading from Windows NT Server 4.0 to Windows Server
|2003
|>http://www.microsoft.com/windowsserver2003/evaluation/why
|upgrade/nt4/nt4tows
|>03-2.mspx
|>
|>Windows NT Server 4.0 Upgrade Guide
|>http://www.microsoft.com/windowsserver2003/partners/isvs/
|ntmigrate.mspx
|>
|>326209 HOW TO: Upgrade a Windows NT 4.0-Based PDC to a
|Windows Server 2003
|>http://support.microsoft.com/?id=326209
|>
|>816105 HOW TO: Create or Move a Global Catalog in
|Windows Server 2003
|>http://support.microsoft.com/?id=816105
|>
|>324801 HOW TO: View and Transfer FSMO Roles in Windows
|Server 2003
|>http://support.microsoft.com/?id=324801
|>
|>255504 Using Ntdsutil.exe to Seize or Transfer FSMO
|Roles to a Domain
|>Controller
|>http://support.microsoft.com/?id=255504
|>
|>Solution 2: Perform a Migration Upgrade
|>
|>Actually, this is your Approach B. This method is more
|complicated than the
|>first. If you do not want to change the domain name or
|restructure the
|>existing domain, I suggest that you use Solution 1.
|>
|>If you prefer Solution 2, we can use Active Directory
|Migration Tool (ADMT)
|>to move data between the two domain.
|>
|>Reference:
|>
|>325851 HOW TO: Set Up ADMT for a Windows NT 4.0-to-
|Windows Server 2003
|>Migration
|>http://support.microsoft.com/?id=325851
|>
|>Download details: Active Directory Migration Tool v.2.0
|>http://www.microsoft.com/downloads/details.aspx?
|familyid=788975b1-5849-4707-
|>9817-8c9773c25c6c&displaylang=en
|>
|>I hope the above information helps. Thanks!
|>
|>Regards,
|>Joe Wu
|>Product Support Services
|>Microsoft Corporation
|>
|>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.
|>
|>--------------------
|>|Content-Class: urn:content-classes:message
|>|From: "Jack Ling" <fly2moon2@discussions.microsoft.com>
|>|Sender: "Jack Ling"
|<fly2moon2@discussions.microsoft.com>
|>|Subject: HELP: smooth migration from NT 4 to a new
|server on Windows 2003
|>|Date: Mon, 2 Feb 2004 23:27:05 -0800
|>|Lines: 48
|>|Message-ID: <92eb01c3ea27$200cf4d0$a401280a@phx.gbl>
|>|MIME-Version: 1.0
|>|Content-Type: text/plain;
|>| charset="iso-8859-1"
|>|Content-Transfer-Encoding: 7bit
|>|X-Newsreader: Microsoft CDO for Windows 2000
|>|Thread-Index: AcPqJyAMRflh9IRNQtageiJ1UdrhGQ==
|>|X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
|>|Newsgroups: microsoft.public.windows.server.migration
|>|Path: cpmsftngxa07.phx.gbl
|>|Xref: cpmsftngxa07.phx.gbl
|microsoft.public.windows.server.migration:7477
|>|NNTP-Posting-Host: tk2msftngxa12.phx.gbl 10.40.1.164
|>|X-Tomcat-NG: microsoft.public.windows.server.migration
|>|
|>|Hi,
|>|
|>|Existing we have 1 Windows NT 4 server as PDC and 1
|>|Windows NT 4 server as BDC.
|>|
|>|Have newly acquired a new server with Windows 2003
|>|Standard server installed.
|>|
|>|Ultimately, the Windows 2003 server should take up the
|>|role for user logon authentication.
|>|
|>|Question: What's the recommended approach to integrate
|>|the Windows 2003 server to existing network?
|>|
|>|I've 2 possibilities in mind:
|>|
|>|Approach A - for minimum changes, should I (& can I)
|>|simply join the Windows 2003 server to the NT domain?
|And
|>|how do I do that?
|>|
|>|If that's done, does it mean that the Windows NT
|servers
|>|are still PDC and BDC and the Windows 2003 server is
|just
|>|a member server (and not even a BDC, or can it be
|treated
|>|as NT domain's PDC)?
|>|
|>|
|>|Approach B - Am I supposed to build a completely new
|>|Active Directory on the Windows 2003 server? How and
|can
|>|I export and import existing users from the NT domain
|to
|>|the Windows 2003 server?
|>|
|>|Over the client side (a mixture of Win95, 98, NT, 2000,
|>|XP machines), what do I need to do let them login to
|the
|>|newly created AD?
|>|
|>|
|>|I have 2 machines on Windows 2003 server, is it correct
|>|to say that the 2nd machine (which I will ask it to
|join
|>|the newly created AD) will act similar to a BDC (in NT
|>|domain's term), i.e. when the 1st machine goes off, the
|>|2nd machine still can authenticate users to login?
|>|
|>|
|>|thanks in advance,
|>|jackling
|>|
|>|
|>|
|>|
|>
|>.
|>
|
- Next message: Ma001: "ADMT migrating user issue"
- Previous message: Joe Wu [MSFT]: "Re: Can't install AD"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
