For starters look at: MS-KBQ314649_W2K3 ADPREP Command Causes Mangled Attributes in W2K Forests That Contain E2K Servers MS-KBQ325379_How to Upgrade Windows 2000 Domain Controllers to Windows Server 2003 MS-KBQ555040_Common Mistakes When Upgrade Windows 2000 Domain To Windows 2003 MS-KBQ324392_Enhancements to Adprep.exe in Windows Server 2003 Service Pack 1 and in hotfix 324392 Also see: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/bc5ebbdb-a8d7-4761-b38a-e207baa73419.mspx) http://www.petri.co.il/windows_2003_adprep.htm MS-KBQ555038_How to enable Windows 98-ME-NT clients to logon to Windows 2003 based Domains MS-KBQ887426_Incorrect Schema extension for OS X prevents ForestPrep from completing in Windows 2000 MS-KBQ555262_Common Mistakes When Upgrading Exchange 5.5-2000 To a Exchange 2003 MS-KBQ822942_Considerations When You Upgrade to Exchange Server 2003 (1) well that depends if you are doing an in-place upgrade of the server or "transfering" functionality to a new server version. If you will an in-place upgrade of the servers you need to upgrade Exchange first to 2003 and then WIndows to 2003. If you are introducing new hardware for the newer versions you can do it simultaneously. (2) I hate in-place upgrades so I always try to avoid them as crap always remains. If you have new hardware introduce the new freshly installed servers. If you don't have new HW, well there is only one option (besides using the swing method at a time) and that is doing an in-place upgrade (3) see 2 (4) gothas/not to forget * Make sure you move the RUS from E2K to E2K3 before increasing the FFL to W2K3 (reason: LVR, as E2K might not see changes) (I think it is also mentioned in one of the KB articles) * READ the KB articles well. They contain tons of info on how to do it the right way! * Don't forget other services like DHCP, WINS, DNS (as in configured IP addresses of the W2K servers that should be changed to the W2K3) * Introduce the new servers (DC with DHCP, WINS, DNS if applicable) change TCP/IP settings of all servers in the network to the new servers. Stop and disable services to see if you have forgotten something and after a while shutdown and remove servers Good luck! Cheers, Jorge
________________________________ From: [EMAIL PROTECTED] on behalf of Stevo Sent: Mon 10/24/2005 10:56 PM To: ActiveDir@mail.activedir.org Subject: [ActiveDir] Windows 2000 / Exchange 2000 Upgrade to 2003 Experts, I have a small domain with 3 Windows 2000 DCs and 2 Exchange 2000 mail servers (across 2 sites). I'm planning on upgrading both the domain and Exchange to 2003 and would like some recommendations from people who have actually done this (successfully would be preferred). The questions I have include the following: 1) What is the best order to perform this upgrade? Exchange first or Domain first? 2) Would it be better to perform an upgrade of the existing controllers, or bring new 2003 DCs online? 3) Same for Exchange - should I upgrade the Exchange server, or should I bring a new 2003 Exchange server online concurrently and then migrate accounts over to the new server? 4) What are the gotchas?!! I am planning on replacing the hardware of all DCs and Exchange servers, so any advice around best practices would be appreciated. Thanks Stevo List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
