Re: NT Domain Rename and Upgrade to Serer 2003
- From: "Polly" <Polly@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 9 May 2005 01:44:02 -0700
Hi Dean
Many thanks for your positive response here.
Could I please just run one more thing by you. In our Server 2003 Forest we
are going to have a root domain (this will be an 'empty domain that will be
used for securing the forest) and a child domain When I introduce the root
my thoughts are, introduce a newly built 2003 server as the Root DC, then
promote the nt4 pdc to be the child dc.
My thoughts are regarding schema extension, will the promotion of the NT4
PDC take into account these or will the schema extension such for Storage
Central etc need to be done on the root before adding the child domain.
Any advice would be gratefully appreciated.
Polly
Can you
Polly
"Dean Wells [MVP]" wrote:
> Assuming you mean an in-place upgrade, the domain related issues
> concerning SIDs are removed when performing an in-place upgrade vs. a
> migration. If the upgrade process involves only one source NT4 domain
> and one target 2003 domain, I would recommend the upgrade approach over
> migration since it does not require sIDHistory nor re-ACLing. Other
> than the steps you've provided not mentioning the upgrade itself, they
> appear well thought out.
>
> There are a number of additional tasks that I perform for the sake of my
> own comfort following the upgrade of the NT4 PDC that assist in ensuring
> the physically upgraded DC causes no unpredictable problems at a later
> time, in short -
>
> 1. Install a fresh 2003 server
> 2. DCpromo it as a replica DC against the newly upgraded NT4 PDC (now a
> 2K3 DC)
> 3. Gracefully transfer responsibility for all 5 FSMOs, the GC and DNS to
> the fresh 2K3 DC
> 4. Replicate, verify the 2 DCs are consistent
> 5. Gracefully DCpromo down the upgraded NT4 DC
>
> HTH
>
> --
> Dean Wells [MVP / Directory Services]
> MSEtechnology
> [[ Please respond to the Newsgroup only regarding posts ]]
> R e m o v e t h e m a s k t o s e n d e m a i l
>
> Polly wrote:
> > Hi
> >
> > I have a few questions I hope you can help with.
> >
> > I am involved in a project to re-name an NT Domain then use an
> > in-house upgrade to Server 2003. My prefered method would have been
> > build a new 2003 Forest with the new required domain name then user
> > the ADMT tool to migrate the users and resources.
> >
> > However, an alternative solution has been sold to the customer that
> > being, re-name the NT Domain. Once the NT4 domain has been renamed
> > then peform an inhouse upgrade.
> >
> > My concern is issues around the SID when re-naming the NT4 domain.
> > The solution will be as follows:
> >
> > . Build a new BDC - allow replication
> > . Remove the new BDC from existing Domain
> > . Rename to new domain name BDC
> > . Promote to new domain name PDC
> > . Reconnect to Network
> > . Add another BDC
> > . Establish trusts
> > . Set up security permissions
> > . Move 10 client machines into new domain
> > . Trial Logons
> > . Resecure DATA at all sites
> > . Move remaining clients into new domain
> > . Move Member servers to new domain
> > . Tidy up
> >
> > Can anyone advise if there will be any SID issues when we connect the
> > users, clients and resoruces to this new domain?
> >
> > Polly
>
>
>
.
- Follow-Ups:
- Re: NT Domain Rename and Upgrade to Serer 2003
- From: Dean Wells [MVP]
- Re: NT Domain Rename and Upgrade to Serer 2003
- References:
- NT Domain Rename and Upgrade to Serer 2003
- From: Polly
- Re: NT Domain Rename and Upgrade to Serer 2003
- From: Dean Wells [MVP]
- NT Domain Rename and Upgrade to Serer 2003
- Prev by Date: Domain Users in ADAM group
- Next by Date: Global Policy to disable FDD & USB not working
- Previous by thread: Re: NT Domain Rename and Upgrade to Serer 2003
- Next by thread: Re: NT Domain Rename and Upgrade to Serer 2003
- Index(es):
Relevant Pages
|