RE: Steps to migrate a win2k domain to 2k3

Shannon,

The process is fairly straight-forward. Generally, the idea is to introduce
a 2003 DC to the environment (either by DCPROMO-ing aserver into the fold or
by doing an in-place upgrade of one of your W2kDC's). Now that your
environment is in Mixed mode, move your FSMO roles over and upgrade the other
DC's to 2003. Once completed, you can flip the switch and make it Native.
That's the general idea. Now, there are things like extending domainprep and
schemaprep and additional steps involved, which should be considered (see
links below). And YES, years of experience tells me that a test lab is
crucial to easing the pain of implementing ANY new system, so I highly
recommend a test lab for a dry run or two.
Now, here are the links:
Upgrade from AD 2000 to 2003:
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w2ktows03-2.mspx

AD planning:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/planning/default.mspx

-Allen Firouz

"Shannon Hemems" wrote:

> Hi there,
>
> This is probably a question that gets posted a fair amount, but here goes
> anyway.
>
> I've got a single site Win2k AD domain (native mode). 4 DC's,1 Exch2k3
> server (member server), and about 35 mixed Win2k & Win2k3 servers, running
> various server applications (e.g., Great Plains, Symantec AV Enterprise 8.0,
> Netbackup, IIS 5.0, SQL 2000, Perforce, etc.). We've also got a few Red Hat
> Linux 8.0 servers.
>
> We're running AD-integrated DNS, DHCP, RAS (pptp VPN), & DFS services.
>
> What's the best approach to migrating our domain & window services? I've
> seen some of the general articles, but having just gone through the Exchange
> migration, I found there were a lot of little side articles that I'd
> initially missed in my planning (I ended up following MS Exchange's step by
> step article, which was really helpful). Has anyone come across something
> similar, or have recommended articles to read?
>
> Many articles suggest building a test lab first to do a test migration that
> replicates your environment, but how in the world can anyone replicate their
> live domain, with all the various servers & apps? Do many people actually
> follow this step? If so, can it be done quickly (ie., a week) & cheaply?
>
> Thanks very much,
>
> Shannon
>
>
>
.

Relevant Pages

  • Re: Use Case Point Estimation
    ... As I understand from other articles this estimate includes: ... actual functional requirement, ... development environment. ... taken risk into account. ...
    (comp.object)
  • Different result sets on live and staging environment
    ... return of a different result set on our staging ... environment. ... articles displayed in the ... de vliegbasis Volkel vormt het 25-jarig jubileum van de F- ...
    (microsoft.public.inetserver.indexserver)
  • Different result sets on live and staging envirionment
    ... 2000/IIS5.0/IndexServer3.0) and live environment (Win ... Our staging environment displays the right ... All news articles or by selecting a specific period, ... live environment just 5 articles. ...
    (microsoft.public.inetserver.indexserver)
  • Re: Steps to migrate a win2k domain to 2k3
    ... the best starting place for my planning. ... years of experience tells me that a test lab is ... I found there were a lot of little side articles that I'd ...
    (microsoft.public.windows.server.active_directory)
  • Re: Creating a test Domain/Forest (need Help Please)
    ... you could create the DC in the test lab using dcpromo /adv. ... The upgrades to a DC using a backup of the production environment. ...
    (microsoft.public.windows.server.active_directory)