RE: upgrading/migrating 2000 domain to 2003
- From: "sketchy" <sketchy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 6 May 2005 22:04:01 -0700
Jason,
Thank you for the informative response to this user's question. I have a
very similar scenario and had a question very similar to this. Two antique
Win2k domain controllers that fortunately don't do much beyond that
(performing primary and secondary DNS, and some DHCP, but thats it. My Win2k
Member servers do all of the work; Exchange, SQL, etc.). I just bought two
brand new servers (that will have Win2k3 on them) to finally replace these
two machines worthy of the Smithsonian, but unlike this other user, I want to
"retire" these two machines after I make the switch. So I'm assuming that I
can follow the guidelines you have layed out for this other user, after the
point of demoting the servers, and simply shut them down? Correct?
For simplicity, I have decided to avoid any type of trickery about trying to
swap out one server identity for the other (more common on member servers).
Can you confirm that this is probably best to avoid when it comes to domain
controllers?
--
Sketchy
"Jason Tan (MSFT)" wrote:
>
> Hi Gaute,
>
> Thanks for posting!
>
> ---I wonder, is it possible to install a third machine with windows
> 2003,make it a member of the existing windows 2000 domain, perform a
> promotion and point the FSMO-roles to this server and then upgrade the rest
> of the AD-controllers?
>
> Right, your plan is the exact method which we recommend to perform. This is
> not in place upgrade. I would like to provide you with the below
> information for your reference:
>
> Performing a "not in place" upgrade:
> ============================================
>
> 1. Run Adprep /forestprep, Adprep /domainprep on win2k DC.
>
> 2. Install win2k3 on your new machine and join it to the win2k domain.
>
> 3. Promote win2k3 to be an additional DC. This process will replicate
> user/computer accounts from 2k to 2k3.
>
> 4. Install AD-integrated DNS on 2k3, this process will auto replicate DNS
> from 2k to 2k3.
>
> 5. Move Global Catalog to the new server.
>
> 6. Switch FSMO Roles to the new server.
>
> 7. Add DHCP role to the new server.
>
> Please refer to the following KB:
>
> 130642 How to Move a DHCP Database to Another Windows Server
> http://support.microsoft.com/?id=130642
>
> 8. Run for a test period and make sure everything is OK.
>
> 9. Demote the win2k DC and make a clean install of win2k3. Promote it to be
> an additional DC.
>
> The additional DC in a domain can offer fault tolerance and ensure the
> single DC is not overloaded.
>
> The following are some helpful documents for upgrading from Windows 2000 to
> Windows Server 2003:
>
> 325379 How to Upgrade Windows 2000 Domain Controllers to Windows Server 2003
> http://support.microsoft.com/?id=325379
>
> Upgrading from Windows 2000 Server to Windows Server 2003
> http://www.microsoft.com/windowsserver2003/upgrading/w2k/default.mspx
>
> Upgrading from Windows 2000 Server to Windows Server 2003
> http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w2kto
> ws03-2.mspx
>
> If there is anything that is unclear, please feel free to let me know.
>
> Thanks & Regards,
>
> Jason Tan
>
> 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.
>
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
.
- Follow-Ups:
- RE: upgrading/migrating 2000 domain to 2003
- From: Jason Tan (MSFT)
- RE: upgrading/migrating 2000 domain to 2003
- Prev by Date: nt4 current users
- Next by Date: NT4 upgrade, password policies
- Previous by thread: nt4 current users
- Next by thread: RE: upgrading/migrating 2000 domain to 2003
- Index(es):
Relevant Pages
|
