Windows 2003 Ad

[pic]

Upgrading Exchange Server 5.5 to Exchange Server 2003 in a Medium-Sized Organization

Technical Article 3 of 4

In-Place Upgrade of Microsoft Windows and Active Directory

Updated: December 2004

Copyright
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft mustrespond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
Complying with allapplicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft mayhave patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2005 Microsoft Corporation. All rightsreserved.
Microsoft, Active Directory, ActiveSync, Outlook, Windows, Windows Mobile, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
Table of Contents

Introduction 1
In-Place DomainUpgrade Process 2
Windows Server 2003 Overview 2
Active Directory Overview 3
Discovery, Designing, and Prototyping Windows Server 2003
Active Directory 5
Step 1: Discovery Phase 5
Step 1.1: Verifying That an In-Place Domain Upgrade Is the Best Process 5
Step 1.2: Evaluating the Existing Environment 6
Step 1.3: Documenting the Current Environment 6
Step 2:Design Phase 8
Step 2.1: Windows Server 2003 Design 8
Step 2.2: Active Directory Design 9
Step 3: Prototype Phase 12
Step 3.1: Building the Lab 13
Step 3.2: Testing 13
Step 4: Resolve Potential Issues 17
Implementing Windows Server 2003 Active Directory 19
Step 5: Pre-Upgrade Task Completion Phase 19
Step 5.1: Relocate the LMRepl File ReplicationService 19
Step 5.2: Ensure Remote Access Service Compatibility 19
Step 5.3: Enable the Windows NT 4.0 Environment Change Freeze 20
Step 6: Implementation Phase 20
Step 6.1: Back Up All Domain Data 20
Step 6.2: Delegate the DNS Zone for the New Windows Server 2003 Domain 21
Step 6.3: Configure Protection Against Domain Controller Overload 22
Step 6.4:Upgrade the Operating System of the Windows NT 4.0 PDC 23
Step 6.5: Install Active Directory 23
Step 6.6: Configure the Site Topology 25
Step 6.7: Configure the Windows Time Service on the Forest Root
Domain Controller 26
Step 6.8: Enable Aging and Scavenging for DNS 26
Step 6.9: Verify DNS Server Recursive Name Resolution 27
Step 6.10: PerformPost-Upgrade Tests 28
Step 6.11: Modify Security Policies 29
Step 6.12: Use DNS Registration to Decrease the Workload on the
PDC Emulator 30
Step 6.13: Upgrade Additional Domain Controllers 31
Step 7: Post-Upgrade Phase 33
Step 7.1: Eliminate Anonymous Connections to Domain Controllers 33
Step 7.2: Raise Domain and Forest Functional Levels 33
Step 7.3:...