step 0: check for schema conflicts with Win2003 (e.g. Exchange 2000) and apply appropriate fixes to the Win2000 forest
ensure you perform step 6 on the Infrastructure Master of the respective domain
don't really need step 1-5 for child domain
 
you can perform step 9 prior to step 8 - then first upgrade a child domain DC if that makes you feel better...
 
general recommendation: after forestprep + domainprep are though, don't inplace upgrade the DCs - instead, install from scratch (i.e. add one new one then demote the other DC an reinstall etc.).  But we've done both and both work well (however, all in-place upgraded DCs were re-installed later on - no sweat with promote from media, when you first backup the system itself etc....)
 
you don't need extra help with your rollback plan - you've sort of taken care of it in step 1, 3, 4.  Additionally a very recent backup of at least one DC of each child domain would be good.
 
/Guido


From: Pelle, Joe [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 19. November 2003 19:46
To: [EMAIL PROTECTED]
Subject: [ActiveDir] see anything wrong?

Hello, everyone!

 

I want to run a scenario by you all and see if I am missing a step here or there… 

 

Scenario:

Security Root and Domain are Windows 2000 SP3

Both Security Root and Domain need to be Adprep/ForestPrep ADPrep/DomainPrep tomorrow

Both Security Root and Domain need to be upgraded to Windows Server 2003.

 

Plan:

1.                   Bring a new DC in the Security Root online today to get a fresh copy of the Schema and AD – Take new DC offline before upgrade

2.                   Adprep security root tomorrow for Friday upgrade

3.                   Take Schema master offline during adprep/forestprep

4.                   Put Schema master back online if no problems occur during adprep/forestprep

5.                   force replication of adprep/forestprep changes

6.                   adprep/domainprep security root

7.                   force replication of domainprep

8.                   Upgrade Security Root to Server 2003

9.                   repeat process for the Child domain

 

Any additions, thoughts, recommendations, real-life experiences you all could share with me would be very much appreciated. 

 

Also, if anyone has a good roll back plan in case of failure that would be good too ;)

Finally, we tested this in a lab with mediocre machines and the security root machine locks up after less than a minute once logged onto.

 

Thanks, again!

 

Joe Pelle

Systems Analyst

Information Technology

Valassis / IT

19975 Victor Parkway Livonia, MI 48152

Tel 734.591.7324  Fax 734.632.6151

[EMAIL PROTECTED]

http://www.valassis.com/

 

This message may have included proprietary or protected information.  This message and the information contained herein are not to be further communicated without my express written consent.

 

Reply via email to