Re: Migration of NT4 to Server 2003
- From: "Danny Sanders" <Danny.Sanders@xxxxxxxxxxxxxxxxx>
- Date: Wed, 25 May 2005 09:42:20 -0600
> Create a trust relationship with the existing NT domain, and use ADMT to
> migrate users, groups, computers. (including the existing NT4 BDC's)
>
> Let those changes settle in for a couple weeks.
To use ADMT the Win 2k3 domain must be in Win 2k native mode or later. Win
2k native mode does not provide for replication between AD DCs and NT 4.0
BDCs.
If your users change their passwords during those couple of weeks those
changes will not get replicated to the NT BDCs.
> Install W2K3 on new box and create new domain.
Think about installing NT 4.0 on it as a BDC while connected to your
existing network. Promote to PDC then upgrade to Win 2k3. You will then be
in mixed mode and your BDCs will continue to replicate with your AD DCs and
you can use the domain rename tool to rename the Win 2k3 domain.
> My assumption is that with both domains in place, I will gradually move
> any
> service accounts running under the old domain to the corresponding user on
> the new domain. I will also have to change the folder permissions on the
> file servers from the old domain to the new domain groups. This type of
> activity will continue to occur over time and after I think all references
> to the old domain have been removed, I can take down the BDCs.
There will be no need for this. Use this time to upgrade the rest of your
servers to Win 2k3.
Of course test first if you can.
hth
DDS W 2k MVP MCSE
<Kyle> wrote in message news:uDcEIcSYFHA.3572@xxxxxxxxxxxxxxxxxxxxxxx
> We're a small company of about 55 users moving from NT4\Exchange 5.5 to
> W2K3\Exchange2003. The servers are basically;
>
>
>
> NT4 BDC (SQL 7 Server)
>
> NT4 PDC (Backup\AntiVirus server)
>
> W2K Standalone (Exchange 5.5)
>
> W2K3 Standalone (file server)
>
>
>
> I have a new box to install W2K3 AD and Exchange 2003 on.
>
> The current NT4 domain is an upgrade from 3.51 domain, and the company has
> a
> new name are couple reasons for desiring fresh install and a new domain.
>
>
>
> The current thought is to
>
> Install NT4 on an old box, (P2-266) and promote to PDC. Take
> offline, use as fallback.
>
> Install W2K3 on new box and create new domain.
>
> Create a trust relationship with the existing NT domain, and use ADMT to
> migrate users, groups, computers. (including the existing NT4 BDC's)
>
> Let those changes settle in for a couple weeks.
>
> Install Exchange 2003 on the new AD server
>
> Move the 5.5 accounts to the Exchange 2003
>
> Rebuild the W2K system that held the 5.5 as a W2K3 AD Server
>
>
>
> When budget allows, I'll move Exchange 2003 to a W2K3 standalone.
>
>
>
> If things started getting flaky with the initial portion, the fallback
> would
> be to take the new W2K3 server offline, put the offline PDC back up, and
> possibly promote one of the existing BDCs.
>
>
>
> Are there any flaws in that scenario?
>
>
>
> My assumption is that with both domains in place, I will gradually move
> any
> service accounts running under the old domain to the corresponding user on
> the new domain. I will also have to change the folder permissions on the
> file servers from the old domain to the new domain groups. This type of
> activity will continue to occur over time and after I think all references
> to the old domain have been removed, I can take down the BDCs.
>
>
>
> Is this an accurate assessment?
>
>
>
> Thanks for your thoughts on this.
>
> Kyle
>
>
>
.
- References:
- Migration of NT4 to Server 2003
- From: Kyle
- Migration of NT4 to Server 2003
- Prev by Date: Concern regarding upgrading from 2k to 2k3
- Next by Date: Re: Concern regarding upgrading from 2k to 2k3
- Previous by thread: Migration of NT4 to Server 2003
- Next by thread: RE: Migration of NT4 to Server 2003
- Index(es):
Relevant Pages
|
Loading
