Re: NT Server to 2003 migration
From: mhorosky (mhorosky_at_comcast.net)
Date: 03/17/05
- Next message: Jason Tan: "Re: NT4 to 2003 with Dell2650"
- Previous message: Frances [MSFT]: "Re: Failed LDAP message"
- Messages sorted by: [ date ] [ thread ]
Date: 17 Mar 2005 03:02:44 -0800
I wanted to add that we are also planning a migration,
but i am confused on a couple of points. We have two
new server 2003's installed in an isolated network
(not connected to our production network, not promoted
to DC's yet). Do I promote one first, then connect it
to our production network, then run ADMT and setup the
trust, or do I connect it first, then promote it?
What would happen to my old PDC at that point?
I've also read where ADMT requires native mode, and
didn't quite understand, if that's the case, how it
will even see the old domain. I believe we will be
taking the "step 3" approach below. I have not yet
read the articles listed here, but will, as perhaps
they will help also.
Thank you for the courtesy of your reply.
Marin Marinov wrote:
> In article <258cb01c46091$d2042d30$a401280a@phx.gbl>,
> anonymous@discussions.microsoft.com says...
> > We are planning a migration from our current NT domain to
> > a 2003 domain with AD. The question that I have is
> > this. Our current NT PDC is named "Jack" and we have a
> > BDC named "Jill." We also have 4 2000 member servers in
> > this domain. We have 3 new servers with 2003 already on
> > them waiting to join the party. The problem that we are
> > working on is that we want to replace our "Jack" PDC with
> > one of the 2003 servers and in the process transfer all
> > the apps and data over to the new server. Here are the
> > questions.
> >
> > 1. Should we upgrade Jack to 2003 and transfer all the
> > data and apps over to a new server and be done with it?
> >
> > 2. Can we do step one and rename the new server
> > to "Jack" and change the IP address? (I don't think so)
> >
> > I know that we will have to do some demoting and
> > promoting along the way as well. Any feedback would be
> > appreciated.
> >
> > Thanks,
> > :-)
> > Michelle
> >
> Hi Michelle,
> The approach depends on whether Jack can support Win2K3 running on
it. I
> assume you want to preserve you domain intact (who doesn't ;)). There
> are 3 ways of doing it:
>
> 1) Upgrade Jack to Win2K3, promote the replacement Win2K3 server to
DC
> in the now Windows Server 2003 domain, transfer applications, and
> decommission old Jack. You can then rename the new DC to Jack again.
In
> this scenario there are several things to look for:
>
> * Transfer FSMO roles to the new server before you decomission Jack:
> HOW TO: View and Transfer FSMO Roles in Windows Server 2003
> http://support.microsoft.com/?id=324801
>
> HOW TO: View and Transfer FSMO Roles in the Graphical User Interface
> http://support.microsoft.com/?id=255690
>
> * Prevent Win2K3 DC overload from >= Win2K clients:
>
> How to Prevent Overloading on the First Domain Controller During
Domain
> Upgrade
>
http://support.microsoft.com/default.aspx?kbid=298713&product=winsvr2003
>
> I would suggest you take the time to read through (URLs wrap):
>
> HOW TO: Upgrade a Windows NT 4.0-Based PDC to a Windows Server 2003
> http://support.microsoft.com/?id=326209
>
> Windows NT Server 4.0 Upgrade Guide
>
http://www.microsoft.com/windowsserver2003/partners/isvs/ntmigrate.mspx
>
> Upgrading Windows NT 4.0 Domains to Windows Server 2003 Active
Directory
>
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/de
> ployguide/en-us/dssbe_upnt_overview.asp
>
> 2) Install Windows NT 4.0 on the new server as a BDC in the current
> domain, promote it to PDC, and upgrade the OS to Win2K3. You can do
this
> in a paralel environment,i.e. disconnect the BDC from the production
> network, connect to isolated LAN, promote to PDC and upgrade. This
way
> you don't influence the production environment but data can get out
of
> sync. Applications need to be reinstalled.
>
> 3) Peform an inter-forest migration - in this case you promote the
new
> Win2K3 server to a DC in a new domain and migrate existing security
> principals from the WinNT domain to this one using the Active
Directory
> Migration Tool (ADMT) v2.0 or a third-party tool. This is the most
> complex of the approaches, takes a lot of time for preparation and
> testing. You'll need to reinstall and configure all you applications.
> These links will give you more information on this approach:
>
> Migrating from Windows NT Server 4.0 to Windows Server 2003
>
http://www.microsoft.com/downloads/details.aspx?FamilyID=e92cf6a0-76f0-
> 4e25-8de0-19544062a6e6&displaylang=en
>
> Migrating Windows NT Server 4.0 Domains to Windows Server 2003 Active
> Directory
>
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4
> domtoad.mspx
>
> Restructuring Windows NT 4.0 Domains to an Active Directory Forest
>
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/de
> ployguide/en-us/dssbg_rent_overview.asp
> If you can go with 1) I suggest you do so - it will save you a lot of
> headaches.
>
> HOW TO: Set Up ADMT for a Windows NT 4.0-to-Windows Server 2003
> Migration
> http://support.microsoft.com/?id=325851
>
> Support WebCast: Domain Migration Using the Microsoft Active
Directory
> Migration Tool
>
http://support.microsoft.com/servicedesks/Webcasts/WC082301/wcblurb08230
> 1.asp
>
>
> If you can go with 1) it will save you a lot of headaches.
> I hope this shed some light on your migration, feel free to post
again
> if you have further concerns and we'll do our best to assist you ;)
>
> --
> Cheers,
> Marin Marinov
> MCT, MCSE 2003/2000/NT4.0,
> MCSE:Security 2003/2000, MCP+I
> -
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "True knowledge exists in knowing that you know nothing."
> Socrates
- Next message: Jason Tan: "Re: NT4 to 2003 with Dell2650"
- Previous message: Frances [MSFT]: "Re: Failed LDAP message"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
