-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've brought this topic up previously, but I thought I'd run it across you folks one more time to make sure I'm on the right track. We're preparing to upgrade a single NT4 domain to a 2003 AD domain, and I'll tentatively be using the following plan.
The current PDC (Serv01) is running NT4. Due to poor management by previous IT staff, it is also running Proxy Server 2, SQL Server 7, Exchange 5.5, and one critical third-party application. It also hosts multiple file shares. The domain consists of approximately 100 users and 80 workstations, so it is quite small. The current BDC (Serv02) is a clean box running NT4 TSE. I just built it a few weeks ago for this project. I intend to use this as a "cold spare" in case this project goes south. It is currently a BDC running backup on DNS and WINS and not much else. I have two new boxes, Serv03 and Serv04, that haven't been touched as of yet. 1) Remove Serv02 from network, store as cold spare. 2) Build Serv03 as NT4 box. Apply patches/SP's. 3) Promote Serv03 to PDC. Allow time for synchronization. Should Serv03 be running any specific services (DNS, WINS, etc.) at this point, before I upgrade it to Windows 2003? 4) Upgrade Serv03 to Server 2003. Give time to synchronize. Will I need to move any FSMO roles over, or will this be done automatically? Serv02 should be the only FSMO role-holder at the end of the migration, correct? 5) Install Server 2003 (clean) on Serv04. Promote to DC. At this point, the domain would sit in mixed mode for no less than two to three months while I beg management for money to buy new equipment and licenses to migrate things away from Serv01. Do you guys foresee any complications with this? 6) When apps have been migrated, trash Serv01 softly. Do you guys foresee any complications with my migration strategy? The most important IT asset of this organization is e-mail, so keeping the existing PDC (Serv01) safe is of paramount importance. Thanks! -James R. Rogers -----BEGIN PGP PUBLIC KEY BLOCK----- mQGiBD8Ejz8RBADyLgYvQ4o6OW2T1O6maExsMgNWw2IJdI47rtogW/vMzLQp/xGG QLZeY5ea9GB8S3DShOE0f1KXzhN4N0Q9y8UfohQgemFGl618I+LNqRzzX7nVXCI2 zVqX0Nok34A8LM/+Xyb/HFzT8HH1eWJjGNKKzOoBvOi9kS8zSbjT8eawLwCg/0uj l8ePD4XXF03JuLGAg475RfEEANhld9iLGXm0urGAQokOjp10rkhm1XyqtgVqtn6x j1BqPQS4nbeTgw+fzT7FrFbwenYBNPsb6ctoJNz2NgJZE4oTSHV/PyztZqBb8MF/ Yqcjc1pFlmiqn8TKBBINlrmnaKh7rFXVLMkJm31K+bf9RFH1UZ+1arf5P1sNMfoK 9kM6A/oCheoNFypeEgZKJflBtNLa8j6SxJ6XoMan90PJyrL9BeSCmN2bKTznBqnI +N/oSu0NguknnC/HMIHHWvmDvTIl/tlQKgWeTI/0/yASyM4gUTA944J4+sfjoEmj /Q0JzQGqBzvlUkHMhQWijT//VDuVRwE/DssPjZf6mbtXmXDb9LQqSmFtZXMgUi4g Um9nZXJzIDxSb2dlcnMtSkBCQ0lOZXR3b3Jrcy5OZXQ+iQBXBBARAgAXBQI/BI8/ BwsJCAcDAgoCGQEFGwMAAAAACgkQx7th0kPmEcXuxACfefK4gHIlYemREA7dmfWD 1hbAtI0AnjweHhnWApyN5tvHkMcAyX688P9VtFpKYW1lcyBSb2dlcnMgPC9vPUJD SSBPcmdhbml6YXRpb24vb3U9Rmlyc3QgQWRtaW5pc3RyYXRpdmUgR3JvdXAvY249 UmVjaXBpZW50cy9jbj1yb2dlcnMtaj6JAE4EEBECAA4FAj8Ej0MHCwkIBwMCCgAK CRDHu2HSQ+YRxVdhAJwLsi1R8AkmT0UhWFlqXH7wn72cswCdGYqQD3+fBPB99jZS /dIavPo0dUi5Ag0EPwSPQBAIAPZCV7cIfwgXcqK61qlC8wXo+VMROU+28W65Szgg 2gGnVqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ+AyDvWXpF9Sh01D49Vlf3HZSTz09jdvO meFXklnN/biudE/F/Ha8g8VHMGHOfMlm/xX5u/2RXscBqtNbno2gpXI61Brwv0YA WCvl9Ij9WE5J280gtJ3kkQc2azNsOA1FHQ98iLMcfFstjvbzySPAQ/ClWxiNjrtV jLhdONM0/XwXV0OjHRhs3jMhLLUq/zzhsSlAGBGNfISnCnLWhsQDGcgHKXrKlQzZ lp+r0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZJrqrol7DVekyCzsAAgIH/RAvgCO0kBdC LxaPL6VwWzXKPBG7pQrcRCT9G5tuY76mFTps+SlYvlJsctoob1mfMit/DnyGfVhV 1ckxalWQ+73Y8+UMG8HCBv81VBf5X0pKTOnB76YuT+9f0L90XT4KsPiAMREIAKOz hRNkjP17xQnw9i15BVCA/iCyuvQw1PP3M5Gjox/cDmTqgSdfxQqAaiP5kZmAbLeb 3Rk99lz4Z8crQQlcMtj1b3H7tOe0XcQNuIl/bCCOhdtyA77aKmZXm7ODKJmt58RJ nDrD8/kSu4haLg+ZNvy5fk8wuFMzNJfl72rRmrrNPJRyotYCpXzSkhhgPv2NrS2f sqGdOVYJyHeJAEwEGBECAAwFAj8Ej0AFGwwAAAAACgkQx7th0kPmEcW9NgCfayLO HTN5UAzARq7UjOtGNDwKCFoAoJlUxFti690k8p14gsVw9eDRPbPA =sbd1 -----END PGP PUBLIC KEY BLOCK-----
smime.p7s
Description: S/MIME cryptographic signature
