2000 to 2003 AD best practices

Home Forums Microsoft Networking and Management Services Active Directory 2000 to 2003 AD best practices

Viewing 1 post (of 1 total)
  • Author
  • Avatar

    Upgrading our 2000 sp4 AD environment to 2003 R2. Questions:

    1) I’m thinking building new machines from scratch to be the new DC’s is cleaner than upgrading the in place DC’s. Agreed? Any glaring drawbacks to this?

    2) Can I upgrade directly to R2? Microsofts “Common mistakes” document here: http://support.microsoft.com/kb/555040 says no, is this info outdated? :

    If you like to migrate to Windows 2003 R2 Domain, please consider the migration in two stages:
    a. Migration from NT/2000 Domain to Windows 2003 Domain
    b. Migration from Windows 2003 Domain to Windows 2003 R2 Domain.

    3) More microsoft advice, this time from http://support.microsoft.com/default.aspx?scid=kb;en-us;325379 :

    Early Microsoft documentation recommends that you isolate the schema operations master on a private network before you run adprep /forestprep. Real-world experience suggests that this step is not necessary and may cause a schema operations master to reject schema changes when it is restarted on a private network.

    Should I disregard this confusing step and just leave all connections active?

    Thanks in advance,

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.