MCSE 70-294 Exam Prep Planning, Implementing, and Maintaining a Microsoft® Windows® Server™ 2003 Active Directory Infrastructure Don Poulton
800 East 96th Street • Indianapolis, Indiana 46240 USA
MCSE 70-294 Exam Prep: Planning, Implementing, and Maintaining a Microsoft® Windows® Server™ 2003 Active Directory Infrastructure Copyright ® 2007 by Que Publishing All rights reserved. No part of this book shall be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without written permission from the publisher. No patent liability is assumed with respect to the use of the information contained herein. Although every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions. Nor is any liability assumed for damages resulting from the use of the information contained herein. International Standard Book Number: 0-7897-3651-9 Printed in the United States of America First Printing: November 2006 09
08
07
06
4
3
2
1
Trademarks All terms mentioned in this book that are known to be trademarks or service marks have been appropriately capitalized. Que Publishing cannot attest to the accuracy of this information. Use of a term in this book should not be regarded as affecting the validity of any trademark or service mark.
Warning and Disclaimer Every effort has been made to make this book as complete and as accurate as possible, but no warranty or fitness is implied. The information provided is on an “as is” basis. The authors and the publisher shall have neither liability nor responsibility to any person or entity with respect to any loss or damages arising from the information contained in this book or from the use of the CD or programs accompanying it.
Bulk Sales Que Publishing offers excellent discounts on this book when ordered in quantity for bulk purchases or special sales. For more information, please contact U.S. Corporate and Government Sales 1-800-382-3419
[email protected] For sales outside of the U.S., please contact: International Sales
[email protected] Library of Congress Cataloging-in-Publication Data Poulton, Don. MCSE 70-294 exam prep : planning, implementing, and maintaining a Microsoft Windows server 2003 active directory infrastructure / Don Poulton. -- 2nd ed. p. cm. Earlier ed. under title: Windows Server 2003 active directory infrastructure, 2004. ISBN 0-7897-3651-9 (pbk.) 1. Electronic data processing personnel--Certification. 2. Microsoft software--Examinations-Study guides. 3. Directory services (Computer network technology)--Examinations--Study guides. 4. Microsoft Windows server. I. Poulton, Don Windows Server 2003 active directory infrastructure. II. Title. QA76.3.P68 2006 005.4'476--dc22 2006032881
PUBLISHER Paul Boger ACQUISITIONS EDITOR Betsy Brown DEVELOPMENT EDITOR Dayna Isley MANAGING EDITOR Patrick Kanouse PROJECT EDITOR Mandie Frank COPY EDITOR Mike Henry PROOFREADER Leslie Joseph TECHNICAL EDITOR Marc Savage PUBLISHING COORDINATOR Vanessa Evans INTERIOR DESIGNER Ann Jones COVER DESIGNER Gary Adair PAGE LAYOUT Molly Sharp
The Safari® Enabled icon on the cover of your favorite technology book means the book is available through Safari Bookshelf. When you buy this book, you get free access to the online edition for 45 days. Safari Bookshelf is an electronic reference library that lets you easily search thousands of technical books, find code samples, download chapters, and access technical information whenever and wherever you need it. To gain 45-day Safari Enabled access to this book:
. Go to http://www.quepublishing.com/safarienabled . Complete the brief registration form . Enter the coupon code U5KV-46ZJ-8SIV-N8JL-UKY1 If you have difficulty registering on Safari Bookshelf or accessing the online edition, please email
[email protected].
Contents at a Glance Introduction
xix
Microsoft ® 70-294 Exam Objectives
xxvii
Study and Exam Preparation Tips
xxix
Part I: Exam Preparation CHAPTER 1 Concepts of Windows Server 2003 Active Directory CHAPTER 2 Planning and Implementing an Active Directory Infrastructure
3 35
CHAPTER 3 Managing an Active Directory Infrastructure
115
CHAPTER 4 Maintaining an Active Directory Infrastructure
205
CHAPTER 5 Planning User, Computer, and Group Strategies
299
CHAPTER 6 Implementing User, Computer, and Group Strategies
367
CHAPTER 7 Planning and Implementing Group Policy
423
CHAPTER 8 Managing Group Policy
533
Part II: Final Review Fast Facts
609
Practice Exam
645
Practice Exam Answers
679
Part III: Appendixes APPENDIX A Accessing Your Free MeasureUp Practice Test
701
APPENDIX B MeasureUp’s Product Features
703
APPENDIX C Review Questions and Answers
707
Glossary
723
Index
737
Table of Contents Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Microsoft 70-294 Exam Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii Study and Exam Preparation Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix Learning Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx Study Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx Study Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx Pretesting Yourself . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii Exam Preparation Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii The MCSE Exam Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxii New Question Types: Simulation Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiv Putting It All Together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxv Final Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxviii Part I: Exam Preparation Chapter 1: Concepts of Windows Server 2003 Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 A Brief History of Directory Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 How Is Active Directory Built? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 X.500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Naming Standards of X.500 and LDAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 The Building Blocks of Active Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Namespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Global Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Partitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Directory Services Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
vi
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure
Logical Components of Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Forest. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Organizational Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Review of Active Directory Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Physical Components of Active Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Domain Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Global Catalog Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Flexible Operations Masters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Reviewing Active Directory’s Physical Components . . . . . . . . . . . . . . . . . . . . . . . 26 Some Advantages of Active Directory over Older Directory Services. . . . . . . . . 26 What Is New in Windows Server 2003 Active Directory? . . . . . . . . . . . . . . . . . . . . . . . 27 What Is New in Windows Server 2003 Release 2 Active Directory? . . . . . . . . . . . . . . 30 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Key Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Suggested Readings and Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Chapter 2: Planning and Implementing an Active Directory Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Planning the Active Directory Namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Subdividing the Active Directory Namespace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Administrative or Geographical Organization of Domains. . . . . . . . . . . . . . . . . . 40 Active Directory Namespace Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Building an Active Directory Forest. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Creating the Forest Root Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Active Directory Domain Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Creating Child Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Uninstalling Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Application Directory Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Upgrading Windows 2000 Domains and Forests . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Building an Active Directory Forest Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
vii
Contents
Windows Server 2003 Functional Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Domain Functional Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Forest Functional Levels and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Renaming Domains and Domain Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Functional Levels Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Sharing Active Directory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Global Catalog Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Universal Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Sharing Active Directory Information Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Placement of Flexible Operations Master Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Business Continuity of Operations Master Roles . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Operations Master Role Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Operations Masters Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Key Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Apply Your Knowledge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Answers to Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Suggested Readings and Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Chapter 3: Managing an Active Directory Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Active Directory Trust Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Trust Relationships Within an Active Directory Forest . . . . . . . . . . . . . . . . . . . 119 Interforest Trust Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Establishing Trust Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Managing Trust Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Active Directory Federation Services (ADFS). . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Understanding Trust Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Active Directory Forest and Domain Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Managing Schema Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Adding or Removing a UPN Suffix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Understanding the Directory Forest and Domain Structure . . . . . . . . . . . . . . . 155
viii
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure
Active Directory Site Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Creating Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Configuring Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Configuring Site Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Configuring Site Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Site Link Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Knowledge Consistency Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Configuring Connection Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Inter-Site Topology Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Preferred Bridgehead Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Configuring Replication Schedules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Configuring Site Link Costs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Apply Your Knowledge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Answers to Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Answers to Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Suggested Readings and Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Chapter 4: Maintaining an Active Directory Infrastructure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Managing and Monitoring Active Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Active Directory Support Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Active Directory Support Tools Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Monitoring Active Directory Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Monitoring FRS Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Restoring Active Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Backing Up Active Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Restoring Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Managing the Active Directory Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Restoring Active Directory Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
ix
Contents
Troubleshooting Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Diagnosing Issues Related to Active Directory Replication . . . . . . . . . . . . . . . . 267 Diagnosing Issues Related to Operations Master Role Failures. . . . . . . . . . . . . 272 Diagnosing Issues Related to the Active Directory Database . . . . . . . . . . . . . . . 276 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Apply Your Knowledge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Answers to Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Suggested Readings and Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Chapter 5: Planning User, Computer, and Group Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Security Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Functional Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Planning a Distribution Group Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Planning a Security Group Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 User and Group Creation Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Group Nesting Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 User Authentication Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Smart Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Domain Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Apply Your Knowledge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Answers to Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Answers to Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 Suggested Readings and Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
x
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure
Chapter 6: Implementing User, Computer, and Group Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Administrative Delegation Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Planning an OU Structure Based on Delegation Requirements . . . . . . . . . . . . 371 Planning a Security Group Hierarchy Based on Delegation Requirements . . . 378 Administrative Delegation Strategy Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 OU Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Administrative Requirements for an OU Structure . . . . . . . . . . . . . . . . . . . . . . . 385 Group Policy Requirements for an OU Structure . . . . . . . . . . . . . . . . . . . . . . . . 387 Implementing an OU Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Managing an OU Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Apply Your Knowledge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 Answers to Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 Answers to Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 Suggested Readings and Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 Chapter 7: Planning and Implementing Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 The Concept of Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 Components of Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 Group Policy Containers (GPCs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 Group Policy Templates (GPTs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 Planning the Application of Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 Group Policy Inheritance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 Using the Group Policy Management Console (GPMC) . . . . . . . . . . . . . . . . . . 431 Creating and Managing GPOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 Group Policy for Users and Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 Best Practices for Managing Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 Some Strategies for Planning a Set of GPOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 Group Policy Application Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
xi
Contents
Deploying the User and Computer Environment with Group Policy . . . . . . . . . . . . 462 Software Installation Using Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462 User and Computer Environment Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 Enrolling User and Computer Certificates with Group Policy . . . . . . . . . . . . . 475 Enrolling User and Computer Certificates with Group Policy Review . . . . . . 481 Configuring Security Settings with Group Policy . . . . . . . . . . . . . . . . . . . . . . . . 481 Redirecting Folders with Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Administrative Templates Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512 Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 Apply Your Knowledge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514 Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514 Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521 Answers to Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528 Answers to Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 Suggested Readings and Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 Chapter 8: Managing Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 Resultant Set of Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 RSoP Planning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537 RSoP Logging Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548 Gpresult . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 Other Tools for Troubleshooting Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Gpupdate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Gpotool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567 Advanced System Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567 RSoP and Gpresult Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569 Maintaining Software with Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570 Distributing Updates to Software Installed Using Group Policy. . . . . . . . . . . . 570 Configuring Automatic Updates for Network Clients Using Group Policy . . 577 RSoP and Software Installation Using Group Policy . . . . . . . . . . . . . . . . . . . . . 580 Group Policy Application Upgrade Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
xii
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure
Troubleshooting Group Policy Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581 Use of RSoP to Troubleshoot Group Policy Security Settings . . . . . . . . . . . . . 581 Use of Gpresult to Troubleshoot Group Policy Security Settings . . . . . . . . . . 584 Best Practices When Troubleshooting Group Policy Settings . . . . . . . . . . . . . . 585 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586 Key Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587 Apply Your Knowledge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587 Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588 Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596 Answers to Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601 Answers to Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603 Suggested Readings and Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606 Part II: Final Review Fast Facts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609 Planning and Implementing an Active Directory Infrastructure . . . . . . . . . . . . . . . . . 610 Plan a Strategy for Placing Global Catalog Servers . . . . . . . . . . . . . . . . . . . . . . . 610 Plan Flexible Operations Master Role Placement . . . . . . . . . . . . . . . . . . . . . . . . 611 Implement an Active Directory Service Forest and Domain Structure. . . . . . . 614 Implement an Active Directory Site Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . 617 Plan an Administrative Delegation Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618 Managing and Maintaining an Active Directory Infrastructure . . . . . . . . . . . . . . . . . . 619 Manage an Active Directory Forest and Domain Structure . . . . . . . . . . . . . . . . 620 Manage an Active Directory Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622 Monitor Active Directory Replication Failures. . . . . . . . . . . . . . . . . . . . . . . . . . . 623 Restore Active Directory Directory Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624 Troubleshoot Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626 Planning and Implementing User, Computer, and Group Strategies . . . . . . . . . . . . . 629 Plan a Security Group Strategy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629 Plan a User Authentication Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630 Plan an OU Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631 Implement an OU Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632 Planning and Implementing Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634 Plan a Group Policy Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634 Configure the User Environment Using Group Policy. . . . . . . . . . . . . . . . . . . . 636 Deploy a Computer Environment Using Group Policy . . . . . . . . . . . . . . . . . . . 639
xiii
Contents
Managing and Maintaining Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641 Troubleshoot Issues Related to Group Policy Application Deployment. . . . . . 641 Maintain Installed Software Using Group Policy. . . . . . . . . . . . . . . . . . . . . . . . . 642 Troubleshoot the Application of Group Policy Security Settings . . . . . . . . . . . 644 Practice Exam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645 Exam Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646 Practice Exam Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679 Part III: Appendixes Appendix A: Accessing Your Free MeasureUp Practice Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701 Appendix B: MeasureUp’s Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703 Multiple Testing Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703 Study Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703 Certification Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703 Custom Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703 Missed Question Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704 Non-Duplicate Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704 Question Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704 Random Questions and Order of Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704 Detailed Explanations of Correct and Incorrect Answers . . . . . . . . . . . . . . . . . . . . . . . 705 Attention to Exam Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705 Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705 Appendix C: Review Questions and Answers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707 Chapter 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707 Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707 Answers to Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708 Chapter 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709 Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709 Answers to Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
xiv
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure
Chapter 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711 Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711 Answers to Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712 Chapter 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713 Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713 Answers to Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714 Chapter 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715 Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715 Answers to Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715 Chapter 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716 Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716 Answers to Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716 Chapter 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717 Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717 Answers to Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718 Chapter 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719 Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719 Answers to Review Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
About the Author Don Poulton, MCSA, MCSE, A+, Network+, Security+, has been involved with computers since the days of 80-column punch cards. After a career of more than 20 years in environmental science, Don switched careers and trained as a Windows NT 4.0 MCSE. He has been involved in consulting with a couple of small training providers as a technical writer, during which time he wrote training and exam prep materials for Windows NT 4.0, Windows 2000, and Windows XP. In addition, he has worked on programming projects, both in his days as an environmental scientist, and more recently with Visual Basic to update an older statistical package used for multivariate analysis of sediment contaminants. When not working on computers, Don is an avid amateur photographer who has had his photos displayed in international competitions and published in magazines such as Michigan Natural Resources Magazine and National Geographic Traveler. Don also enjoys traveling and keeping fit. Don lives in Burlington, Ontario, with his wife, Terry.
About the Reviewer Marc Savage is a senior national technical advisor and technical trainer for Nexient. Combined with more than 11 years of experience in microcomputer training and systems development in the private, public, and nonprofit organization sectors his professional expertise is focused particularly on providing companies with a clear vision and direction in regards to Microsoft products. Marc currently holds the following certifications: MCT, MCSE, MCSA, CNE, A+, Network +, ITIL, and HDA. Over the past ten years Marc as worked on many titles at New Riders and Que Publishing. When not in front of his computer, Marc spends his time with his lovely wife Lynne and two daughters Isabelle and Carolyne. He can be reached at
[email protected].
Dedication To my terrific wife, Terry, who has stood by me and supported me throughout this project.
Acknowledgments I would like to thank all of the outstanding staff at Que Publishing, especially Carole McClendon and Betsy Brown, who worked with me throughout the project and whose copyediting improved the content and readability of the text. Thanks also to Kim Lindros, who put me in touch with Carole and Betsy at the start of this project. Lastly, thanks also go out to Marc Savage, the technical editor, who provided highly valuable constructive comments and suggestions for improving this book.
We Want to Hear from You! As the reader of this book, you are our most important critic and commentator. We value your opinion and want to know what we’re doing right, what we could do better, what areas you’d like to see us publish in, and any other words of wisdom you’re willing to pass our way. As Publisher for Que Publishing, I welcome your comments. You can email or write me directly to let me know what you did or didn’t like about this book—as well as what we can do to make our books better. Please note that I cannot help you with technical problems related to the topic of this book. We do have a User Services group, however, where I will forward specific technical questions related to the book. When you write, please be sure to include this book’s title and author as well as your name, email address, and phone number. I will carefully review your comments and share them with the author and editors who worked on the book. Email:
[email protected]
Mail:
Paul Boger Publisher Que Publishing 800 East 96th Street Indianapolis, IN 46240 USA
Reader Services Visit our website and register this book at www.examcram.com/register for convenient access to any updates, downloads, or errata that might be available for this book.
Introduction MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure is for network architects, system administrators, and other technical professionals who are pursuing the goal of becoming a Microsoft Certified System Engineer (MCSE). This book covers the Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure exam (70-294), which is a core exam for this certification. The exam is designed to measure your skill in managing and maintaining Active Directory in a Windows Server 2003 environment.
R2 This book covers all the objectives that Microsoft has established for exam 70-294. It has been updated to include coverage of the Service Pack 1 (SP1) and Release 2 (R2) upgrades of the Windows Server 2003 operating system. In the book, you will see special R2 icons by the new R2 material the 70-294 exam covers.
Who Should Read This Book This book is designed to cover all the objectives that Microsoft created for this exam, thereby helping you meet your certification goals by preparing you for Exam 70-294. It doesn’t offer end-to-end coverage of Active Directory in Windows Server 2003; rather, it helps you develop the specific core competencies that Microsoft says that administrators who support Active Directory in Windows Server 2003 will need to master. In a Windows Server 2003 network, the ability to install, support, and troubleshoot Active Directory is critical to the success of an administrator. As in Windows 2000, Active Directory is intimately integrated into Windows Server 2003, and you cannot have a domain structure without Active Directory. The exam touches on all the major components of Active Directory that are critical to a successful domain and forest implementation. Although volumes of information are available on the history, theory, and underlying applications, this book does not cover these portions of the services in detail. The purpose of this book is to provide an introduction to these services in general, provide an in-depth look at the Windows Server 2003 implementations of Active Directory, and prepare you to take the exam. One additional area that is new to this exam is the emphasis on security. In keeping with the Microsoft Trustworthy Computing initiatives, Microsoft is putting much greater emphasis than in the past on the security facets of all of its Windows Server 2003 exams. Because a great deal of related information exists that this book is not able to cover, each chapter in this book contains a section called “Suggested Readings and Resources” that points you
xx
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure
to sources that can fill in the blanks. Therefore, for example, although you might not be a Group Policy expert by the time you complete this book, you’ll know how to implement, configure, and troubleshoot Group Policy and its underlying concepts. You’ll also have a recommendation for some additional reading if you need to understand exactly what the makeup of Group Policy object (GPO) looks like. One of the most common questions with any of the Microsoft certification tests is, “Do I need to take a class to pass this test?” You can pass the exam by learning the material in this book, without taking a class. Of course, depending on your own personal study habits and learning style, you might benefit from studying this book and taking a class. However, one thing that is difficult for any book to provide is hands-on experience with the product. If you can set up an environment that enables you to perform the exercises outlined in this book (you’ll find hardware and software recommendations for this environment at the end of this introduction), you’re going to be in good shape. You’ll be in especially good shape if you have the opportunity to work with Windows Server 2003 in a production environment. Even if you are not planning to take the exam, you might find this book useful. The wide range of topics covered by the Microsoft exam objectives will certainly help you to accomplish the Active Directory management tasks at your job. Experienced MCSEs looking for a reference on the new features Microsoft included in Windows 2003 Server Active Directory in particular should appreciate the coverage of topics here. Microsoft assumes that the typical candidate for this exam will have a minimum of one year’s experience implementing and administering Active Directory in medium to very large network environments.
How This Book Helps You This book gives you a self-guided tour of all the areas of the product that are covered by the Planning, Implementing, and Maintaining a Windows 2003 Active Directory Infrastructure exam. The goal is to teach you the specific skills that you need to achieve your MCSE certification. You will also find helpful hints, tips, examples, exercises, and references to additional study materials. Specifically, this book is set up to help you in the following ways: . Organization—This book is organized around the individual objectives from
Microsoft’s preparation guide for the Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure exam. All objectives are covered in this book. They are not covered in the same order that you will find them on the official preparation guide (which you can download from http://www.microsoft.com/
xxi
Introduction
learning/exams/70-294.asp) but are reorganized for more logical teaching. I have also tried to make the information more accessible in several ways: . The full list of exam topics and objectives is included in this introduction. . After the introduction, you will encounter the “Study and Exam Prep Tips” sec-
tion. Read this section early on to help you develop study strategies. This section provides some general guidelines for preparing for a Microsoft certification exam. It also provides you with valuable exam-day tips and information. . Each chapter begins with a list of the objectives covered in that chapter. . Each chapter also begins with an outline that provides an overview of the material
and the page numbers where particular topics can be found. . The objectives are repeated where the material most directly relevant to it is cov-
ered (unless the whole chapter addresses a single objective). . Instructional features—This book is designed to provide you with multiple ways to
learn and reinforce the exam material. Following are some of the helpful methods: . Objective Explanations—As mentioned previously, each chapter begins with a list
of the objectives covered in the chapter. In addition, immediately following each objective is a more detailed explanation that puts the objective in the context of the product. . Study Strategies—Each chapter also offers a selected list of study strategies: exer-
cises to try or additional material to read that will help you learn and retain the material that you’ll find in the chapter. . Exam Alerts—Exam alerts appear in the margin to provide specific exam-related
advice. Such alerts might address material likely to be covered (or not covered) on the exam, ways to remember it, or particular exam quirks. . Review breaks and summaries—Crucial information is summarized at various
points in the book in lists or tables. Each chapter ends with a summary as well. . Key terms—A list of key terms from the chapter appears at the end of each chap-
ter. The glossary toward the end of the book defines each term. . Notes—Notes contain various kinds of useful information, such as tips on tech-
nology or administrative practices, historical background on terms and technologies, and side commentary on industry issues. . Warnings—When using sophisticated information technology, the potential for
mistakes always exists; catastrophes can even occur because of improper application of the technology. Warnings alert you to such potential problems.
xxii
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure . In the Field sidebars—These relatively extensive discussions cover material that
might not be directly relevant to the exam but is useful as reference material or in everyday practice. The Field sidebars also provide useful background or contextual information that is necessary for understanding the larger topic under consideration. . Exercises—Found at the end of the chapters in the “Apply Your Knowledge” sec-
tion and in the “Challenge Exercises” found throughout the chapters, exercises are performance-based opportunities for you to learn and assess your knowledge. . Step by Steps—These are hands-on tutorial instructions that walk you through
tasks and functions that are relevant to the exam objectives. . Extensive practice test options—The book provides numerous opportunities for you
to assess your knowledge and practice for the exam. The practice options include the following: . Exam Questions—These questions also appear in the “Apply Your Knowledge”
section. They reflect the kinds of multiple-choice questions that appear on the Microsoft exams. Use them to practice for the exam and to help you determine what you know and what you may need to review or study further. Answers and explanations are provided later in the section. . Practice exam—A practice exam is included in the “Final Review” section of the
book. The “Final Review” section and the practice exam are discussed later in this Introduction. . MeasureUp Practice Tests—MeasureUp provides further practice questions. For
a complete description of MeasureUp’s test engine, see Appendix B, “MeasureUp’s Product Features.” . Review questions—These open-ended questions appear in Appendix C. They
enable you to quickly assess your comprehension of what you read in each chapter. Appendix C includes answers to the review questions. . Final Review—This part of the book provides valuable tools for preparing for the exam. . Fast Facts—This condensed version of the information contained in the book is
extremely useful for last-minute review. . Practice Exam—A practice exam is included in this book. As much as possible,
questions on this practice exam are written in styles similar to those used on the actual exam. Use the practice exam to assess your readiness for the real thing. Use the extensive answer explanations to improve your retention and understanding of the material.
xxiii
Introduction
The book includes several other features, such as the “Suggested Readings and Resources” section at the end of each chapter that directs you to additional information that can aid you in your exam preparation and your real-life work. Valuable appendixes are provided as well, including a glossary and a description of what is on the CD-ROM. For more information about the exam or the certification process, contact Microsoft at 800-636-7544 or
[email protected] or visit www.microsoft.com/learning/.
Hardware and Software You Will Need As a self-paced study guide, this book is meant to help you understand concepts that you must refine through hands-on experience. To make the most of your studying, you need to have as much background on and experience with Windows Server 2003 as possible. The best way to do this is to combine studying with working on real networks, using the products on which you will be tested. This section describes the minimum computer requirements you need in order to enjoy a solid practice environment. The minimum computer requirements to ensure that you can study everything on which you’ll be tested are one or more workstations running Windows 2000 Professional or Windows XP Professional, and two or more servers running Windows Server 2003—all connected by a network. Many of the examples, exercises, and references in this book refer to Internet websites, so an Internet-connected network would be a benefit. Because this book looks at the core networking capabilities of the Windows Server 2003 family, the minimum requirements listed are specific to Windows Server 2003 Standard Edition, which has all the features covered by this exam and the lowest minimum hardware requirements. To get the full benefit of the exercises in this book, you need the following lab equipment: . Workstations—The workstation configuration should meet the following requirements: . Computer listed on the Microsoft Hardware Compatibility List (HCL) . Pentium 150MHz or better (Pentium processor 233MHz or better for
Windows XP) . 64MB RAM (128MB for Windows XP) . 2GB hard disk with a minimum of 650MB free space (1.5GB free space for
Windows XP) . 3.5-inch 1.44MB floppy drive . VGA video adapter (Super VGA adapter for Windows XP) . VGA monitor (Super VGA adapter for Windows XP)
xxiv
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure . Mouse or equivalent pointing device . CD-ROM drive . Network interface card (NIC) . Presence on an existing network or use of a hub to create a test network (Internet
connection beneficial for some exercises) . Microsoft Windows 2000 Professional or Windows XP Professional . Servers—The server(s) should meet the following requirements: . Two or three computers listed on the Microsoft HCL . Pentium 133MHz or better—Microsoft recommends a 550MHz processor . 256MB RAM (128MB is the minimum supported, but performance will suffer with
just 128MB) . 1GB free hard disk space . 3.5-inch 1.44MB floppy drive . VGA video adapter . VGA monitor . Mouse or equivalent pointing device . CD-ROM drive . NIC . Presence on an existing network or use of a hub to create a test network . Microsoft Windows Server 2003 Standard Edition (Enterprise Edition will also
work but is not needed) You should be able to use one computer in a dual-boot arrangement between Windows Server 2003 and Windows 2000 or XP Professional. A few exercises call for three machines running Windows Server 2003, but you should be able to do these exercises by configuring one machine as a dual-boot installation between two installations of Windows Server 2003. Two products that have proven invaluable to us in the writing field are VMWare (http://www.vmware.com) and Microsoft Virtual PC (http://www.microsoft.com/windows/ virtualpc/default.mspx). These products allow you to create and run multiple virtual client sessions on your PC. You can even run multiple domain controllers on a single PC; I created and tested the exercises in Chapter 3, “Managing an Active Directory Infrastructure,” using three
xxv
Introduction
virtual installations of Windows Server 2003 on a host machine running Windows XP Professional with 768 MB RAM, allocating 128 MB RAM to each virtual installation. Microsoft, of course, is highly motivated to spread the word about Windows Server 2003 to as many people as possible. You can download trial versions of Windows Server 2003 R2, along with other Microsoft products here: http://www.microsoft.com/windowsserver2003/ evaluation/trial/default.mspx. It is generally easiest to obtain access to the necessary computer hardware and software in a corporate business environment. It can be difficult, however, to allocate enough time within the busy workday to complete a self-study program. Most of your study time will likely occur after normal working hours, away from the everyday interruptions and pressures of your regular job.
This page intentionally left blank
Microsoft 70-294 Exam Objectives Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure Exam Number: 70-294 Associated Certifications: MCP, MCSE on Windows Server 2003 Length: 40–45 questions, including simulations
Exam Description The Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure exam is one of six core exams required of candidates pursuing the Microsoft Certified Systems Engineer (MCSE) on Windows Server 2003. The exam is designed to measure your skill in managing and maintaining Active Directory in a Windows Server 2003 environment. Each top-level exam objective is related to a job skill that the candidate is expected to have and demonstrate.
Exam Objectives Exam 70-294 consists of the following five objectives, each with several subobjectives.
Unit/Objective/Subobjective
Page
Planning and Implementing an Active Directory Infrastructure Plan a strategy for placing global catalog servers. 83 . Evaluate network traffic considerations when placing global catalog servers. 83 . Evaluate the need to enable universal group caching. 85 Plan flexible operations master role placement. 87 . Plan for business continuity of operations master roles. 87 . Identify operations master role dependencies. 95 Implement an Active Directory directory service forest and domain structure. 45 . Create the forest root domain. 45 . Create a child domain. 60 . Create and configure Application Data Partitions. 67 . Install and configure an Active Directory domain controller. 53 . Set an Active Directory forest and domain functional level based on requirements. 73 . Establish trust relationships. Types of trust relationships might include external trusts, shortcut trusts, and cross-forest trusts. 118
Unit/Objective/Subobjective
Page
Implement an Active Directory site topology. 152 . Configure site links. . Configure preferred bridgehead servers.
162 169
Plan an administrative delegation strategy.
370
. Plan an organizational unit (OU) structure based on delegation requirements. . Plan a security group hierarchy based on delegation requirements.
370 378
Managing and Maintaining an Active Directory Infrastructure Manage an Active Directory forest and domain structure. 132 . Manage trust relationships. . Manage schema modifications. Manage an Active Directory site. . Configure replication schedules. . Configure site link costs. . Configure site boundaries.
132 141 159 171 181 159
Continues on Following Page
Objective Matrix Continued
Unit/Objective/Subobjective
Page
Monitor Active Directory replication failures. Tools might include Replication Monitor, Event Viewer, and support tools. 208 . Monitor Active Directory replication. . Monitor File Replication Service (FRS) replication.
244
Restore Active Directory directory services.
257
208
. Perform an authoritative restore operation. 262 . Perform a nonauthoritative restore operation. 257 Troubleshoot Active Directory.
267
. Diagnose and resolve issues related to Active Directory replication. 267 . Diagnose and resolve issues related to operations master role failure. 272 . Diagnose and resolve issues related to the Active Directory database. 276
Planning and Implementing User, Computer, and Group Strategies Plan a security group strategy.
302
Plan a user authentication strategy.
318
. Plan a smart card authentication strategy. 318 . Create a password policy for domain users. 335 Plan an OU structure.
385
. Analyze the administrative requirements for an OU. 385 . Analyze the Group Policy requirements for an OU structure. 387 Implement an OU structure. . Create an OU. . Delegate permissions for an OU to a user or to a security group. . Move objects within an OU hierarchy.
391 391 396 400
Unit/Objective/Subobjective
Page
Planning and Implementing Group Policy Plan Group Policy strategy.
445
. Plan a strategy for configuring the user environment by using Group Policy. 445 . Plan a strategy for configuring the computer environment by using Group Policy. 445 Configure the user environment by using Group Policy. . Distribute software by using Group Policy. . Automatically enroll user certificates by using Group Policy. . Redirect folders by using Group Policy. . Configure user security settings by using Group Policy. Deploy a computer environment by using Group Policy.
462 462 475 496 481 462
. Distribute software by using Group Policy. 462 . Automatically enroll computer certificates by using Group Policy. 475 . Configure computer security settings by using Group Policy. 481
Managing and Maintaining Group Policy Troubleshoot issues related to Group Policy application deployment. Tools might include RSoP and the Gpresult command. 548 Maintain installed software by using Group Policy. 570 . Distribute updates to software distributed by Group Policy. . Configure automatic updates for network clients by using Group Policy.
570 577
Troubleshoot the application of Group Policy security settings. Tools might include RSoP and the Gpresult command. 581
Study and Exam Preparation Tips
This element of the book provides you with general guidelines for preparing for any certification exam, including Exam 70-294, “Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure.” It is organized into four sections. The first section addresses learning styles and how they affect preparation for the exam. The second section covers exam preparation activities and general study tips. This is followed by an extended look at the Microsoft certification exams, including a number of specific tips that apply to the various Microsoft exam formats and question types. Finally, changes in Microsoft’s testing policies and how they might affect you are discussed.
xxx
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure
Learning Styles To best understand the nature of preparation for the test, it is important to understand learning as a process. You are probably aware of how you best learn new material. You might find that outlining works best for you, or, as a visual learner, you might need to see things. You might need models or examples, or maybe you just like noodling around. Whatever your learning style, test preparation takes place over time. Obviously, you shouldn’t start studying for a certification exam the night before you take it; it is very important to understand that learning is a developmental process. Understanding learning as a process helps you focus on what you know and what you have yet to learn. Thinking about how you learn should help you recognize that learning takes place when you are able to match new information to old. You have some previous experience with computers and networking. Now you are preparing for this certification exam. Using this book, software, and supplementary materials will not just add incrementally to what you know; as you study, the organization of your knowledge actually restructures as you integrate new information into your existing knowledge base. This leads you to a more comprehensive understanding of the tasks and concepts outlined in the objectives and of computing in general. Again, this happens because of a repetitive process rather than a singular event. If you keep this model of learning in mind as you prepare for the exam, you will make better decisions concerning what to study and how much more studying you need to do.
Study Tips There are many ways to approach studying, just as there are many different types of material to study. However, the tips that follow should work well for the type of material covered on Microsoft certification exams.
Study Strategies Although individuals vary in the ways they learn information, some basic principles of learning apply to everyone. You should adopt some study strategies that take advantage of these principles. One of these principles is that learning can be broken into various depths. Recognition (of terms, for example) exemplifies a surface level of learning in which you rely on a prompt of some sort to elicit recall. Comprehension or understanding (of the concepts behind the terms, for example) represents a deeper level of learning than recognition. The ability to analyze a concept and apply your understanding of it in a new way represents further depth of learning. Your learning strategy should enable you to know the material at a level or two deeper than mere recognition. This will help you perform well on the exams. You will know the material
xxxi
Study and Exam Preparation Tips
so thoroughly that you can go beyond the recognition-level types of questions commonly used in fact-based multiple-choice testing. You will be able to apply your knowledge to solve new problems.
Macro and Micro Study Strategies One strategy that can lead to deep learning includes preparing an outline that covers all the objectives and subobjectives for the particular exam you are working on. You should delve a bit further into the material and include a level or two of detail beyond the stated objectives and subobjectives for the exam. Then you should expand the outline by coming up with a statement of definition or a summary for each point in the outline. An outline provides two approaches to studying. First, you can study the outline by focusing on the organization of the material. You can work your way through the points and subpoints of your outline, with the goal of learning how they relate to one another. For example, you should be sure that you understand how each of the main objective areas for Exam 70-294 is similar to and different from another. Then, you should do the same thing with the subobjectives; you should be sure that you know which subobjectives pertain to each objective area and how they relate to one another. Next, you can work through the outline, focusing on learning the details. You should memorize and understand terms and their definitions, facts, rules and tactics, advantages and disadvantages, and so on. In this pass through the outline, you should attempt to learn detail rather than the big picture (the organizational information that you worked on in the first pass through the outline). Research has shown that attempting to assimilate both types of information at the same time interferes with the overall learning process. If you separate your studying into these two approaches, you will perform better on the exam.
Active Study Strategies The process of writing down and defining objectives, subobjectives, terms, facts, and definitions promotes a more active learning strategy than merely reading the material does. In human information-processing terms, writing forces you to engage in more active encoding of the information. Simply reading over the information leads to more passive processing. You need to determine whether you can apply the information you have learned by attempting to create examples and scenarios on your own. You should think about how or where you could apply the concepts you are learning. Again, you should write down this information to process the facts and concepts in an active fashion. The hands-on nature of the exercises at the ends of the chapters provides further active learning opportunities that will reinforce concepts as well.
xxxii
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure
Common-Sense Strategies You should follow common-sense practices when studying: You should study when you are alert, reduce or eliminate distractions, and take breaks when you become fatigued.
Pretesting Yourself Pretesting allows you to assess how well you are learning. One of the most important aspects of learning is meta-learning. Meta-learning has to do with realizing when you know something well or when you need to study some more. In other words, you recognize how well or how poorly you have learned the material you are studying. For most people, this can be difficult to assess. Review questions, practice questions, and practice tests are useful in that they reveal objectively what you have learned and what you have not learned. You should use this information to guide review and further studying. Developmental learning takes place as you cycle through studying, assessing how well you have learned, reviewing, and assessing again until you feel you are ready to take the exam. You might have noticed the practice exam included in this book. You should use it as part of the learning process. The MeasureUp test simulation software also provides you with an excellent opportunity to assess your knowledge. You should set a goal for your pretesting. A reasonable goal would be to score consistently in the 90% range. See Appendix B, “MeasureUp’s Product Features,” for further explanation of the test simulation software.
Exam Preparation Tips After you have mastered the subject matter, the final preparatory step is to understand the presentation of the exam. Make no mistake: A Microsoft Certified Professional (MCP) exam will challenge both your knowledge and your test-taking skills. The following sections describe the basics of exam design, the exam formats, and hints targeted to each of the exam formats.
The MCSE Exam Format Every MCSE exam is released in one of two basic formats: fixed form and case study. What this book calls exam format is really little more than a combination of the overall exam structure and the presentation method for exam questions. Each exam format uses the same types of questions. These types or styles of questions include multiple-rating (or scenario-based) questions, traditional multiple-choice questions,
xxxiii
Study and Exam Preparation Tips
and simulation-based questions. It’s important to understand the types of questions you will be asked and the actions required to properly answer them. Understanding the exam formats is key to good preparation because the format determines the number of questions presented, the difficulty of those questions, and the amount of time allowed to complete the exam.
Fixed-Form The basic format for the MCSE exam is the traditional fixed-form exam. As its name implies, the fixed-form exam presents a fixed set of questions during the exam session and is the most likely form you will encounter for Exam 70-294. The individual questions are presented in random order during a test session. If you take the same exam more than once, you won’t necessarily see the same questions. The reason is that two or three final forms are typically assembled for every fixed-form exam Microsoft releases. They are usually labeled Forms A, B, and C. The final forms of a fixed-form exam are identical in terms of content coverage, number of questions, and allotted time, but the questions are different. You might notice, however, that some of the same questions appear on, or rather are shared among, different final forms. When multiple final forms of an exam share questions, the percentage of sharing is generally small. Many final forms share no questions, but some older exams might have a 10% to 15% duplication of exam questions on the final exam forms. Fixed-form exams also have a fixed time limit in which you must complete the exam. The MeasureUp practice exams provide fixed-form exams. The score you achieve on a fixed-form exam, which is always reported for MCSE exams on a scale of 0 to 1,000, is based on the number of questions you answer correctly. The exam’s passing score is the same for all final forms of a given fixed-form exam. The typical format for the fixed-form exam is as follows: . 50–60 questions. . 75–90 minute testing time . Question review is allowed, including the opportunity to change your answers
Case Study Exams The case study–based format for Microsoft exams first appeared with the advent of the 70-100 exam (the original “Solution architectures” exam). This format then appeared in the Windows 2000 Server MCSE Design exams, and has since been continued in the Windows Server 2003 Design exams (the 70-297 and 70-298 exams). The test-taker is presented with a series of testlets, which are independent sections in the exam that include a case study with 10 to 20 questions that apply to the case study. The case study is a long scenario-like description of an information
xxxiv
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure
technology situation, and includes information that you must extract and integrate with your understanding of Microsoft technology in order to answer the questions properly. A case study exam typically consists of three to five of these testlets. After you have completed each testlet, you move on to another testlet, with its case study and associated questions. You are typically allowed more time to complete a case study exam (as much as three hours) because of the intricacy of the scenarios presented. You cannot return to a previous testlet once you have moved on. While Microsoft currently employs the case study format for the Design exams only, exam formats are subject to change at any time without notice. Refer to the information provided at http://www.microsoft.com/learning/exams for up-to-date exam taking information.
New Question Types: Simulation Questions A variety of question types can appear on MCSE exams. Examples of multiple-choice questions and scenario-based questions appear throughout this book and the MeasureUp software. Simulation-based questions are new to the MCSE exam series. Simulation-based questions reproduce the look and feel of key Microsoft product features for testing purposes. The simulation software used in MCSE exams has been designed to look and act, as much as possible, just like the actual product. Consequently, answering simulation questions in a MCSE exam entails completing one or more tasks just as if you were using the product itself. The format of a typical Microsoft simulation question consists of a brief scenario or problem statement along with one or more tasks that you must complete to solve the problem. This advice sounds obvious, but your first step when you encounter a simulation is to read the question carefully. Do not go straight to the simulation application! You must assess the problem presented and identify the conditions that make up the problem scenario. Note on the scratch paper provided the tasks that must be performed or outcomes that must be achieved to answer the question and review any instructions on how to proceed. The next step is to launch the simulator by using the button provided. After clicking the Show Simulation button, you will see a feature of the product presented in a dialog box. The simulation application will partially cover the question text on many test center machines. Feel free to reposition the simulation or move between the question text screen and the simulation by using hotkeys, using point-and-click navigation, or even clicking the simulation launch button again. It is important to understand that your answer to the simulation question will not be recorded until you move on to the next exam question. This gives you the added ability to close and reopen the simulation application (using the launch button) on the same question without losing any partial answer you have made.
xxxv
Study and Exam Preparation Tips
The third step is to use the simulator as you would the actual product to solve the problem or perform the defined tasks. Again, the simulation software is designed to function, within reason, just as the product does. However, don’t expect the simulation to reproduce product behavior perfectly. Most importantly, do not allow yourself to become flustered if the simulation does not look or act exactly like the product. There are two final points that will help you tackle simulation questions. First, respond only to what is being asked in the question; do not solve problems that you are not asked to solve. Second, accept what is being asked of you. You might not entirely agree with conditions in the problem statement, the quality of the desired solution, or the sufficiency of defined tasks to solve the problem adequately. Always remember that you are being tested on your ability to solve the problem as it is presented. If you make any changes beyond those required by the question, the item will be scored as wrong on an MCSE exam.
Putting It All Together As you can see, Microsoft is making an effort to utilize question types that go beyond asking you simply to memorize facts. These question types force you to know how to accomplish tasks and understand concepts and relationships. You should study so that you can answer these types of questions rather than those that simply ask you to recall facts. Given all the different pieces of information presented so far, the following sections present a set of tips that will help you successfully tackle the exam.
More Pre-Exam Preparation Tips Generic exam-preparation advice is always useful. Tips include the following: . Become familiar with the product. Hands-on experience is one of the keys to success
on any MCP exam. . Review the current exam-preparation guide on the Microsoft Training & Certification
website. The documentation Microsoft makes available on the Web identifies the skills that every exam intends to test. Exam objectives occasionally change, so be abreast of the most recent developments. . Read all the material. Microsoft has been known to include on its exams material not
expressly specified in the objectives. This book includes additional information not reflected in the objectives in an effort to give you the best possible preparation for the examination—and for the real-world network experiences to come. . Memorize foundational technical detail, but remember that MCP exams are generally
heavier on problem solving and application of knowledge than on questions that require only rote memorization.
xxxvi
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure . Do the Step by Steps and complete the exercises in each chapter. They will help you
gain experience in using the specified methodology or approach. All Microsoft exams are task- and experience-based and require you to have experience actually performing the tasks on which you will be tested. . Use the review and exam questions to assess your knowledge. Don’t just read the chap-
ter content; use the questions to find out what you know and what you don’t. If you are struggling at all, study some more, review, and then assess your knowledge again. . Develop your own questions and examples for each topic listed in the exam objectives.
If you can develop and answer several questions for each topic, you should not find it difficult to pass the exam. . Find a study buddy. This might sound corny, but it works. You should find a coworker
or friend who is also preparing for the exam and use them to improve your knowledge. Quiz each other and assist each other with sections where you feel your knowledge is weak. . Take any of the available practice tests. We recommend the one included in this book
and the ones available through MeasureUp. As a supplement to the material bound with this book, try the free practice tests available on the Microsoft MCP website. . Look on the Microsoft MCSE website for samples and demonstration items. These
items tend to be particularly valuable for one significant reason: They help you become familiar with any new testing technologies before you encounter them on an MCSE exam.
During the Exam Session The following generic exam-taking advice that you’ve heard for years applies when you’re taking an MCP exam: . Take a deep breath and try to relax when you first sit down for your exam session. It
is very important that you control the pressure you might (naturally) feel when taking exams. . You will be provided scratch paper, usually in the form of one or two erasable plastic
sheets. Take a moment to write down any facts and technical detail that you have committed to short-term memory. . Carefully read all information and instruction screens. These displays have been put
together to give you information relevant to the exam you are taking. . Accept the nondisclosure agreement and preliminary survey as part of the examination
process. Complete them accurately and quickly move on.
xxxvii
Study and Exam Preparation Tips . Read the exam questions carefully. Reread each question to identify all relevant detail. . In fixed-form exams, tackle the questions in the order in which they are presented.
Skipping around won’t build your confidence; the clock is always counting down. . Don’t rush, but also don’t linger on difficult questions. The questions vary in degree of
difficulty. Don’t be flustered by a particularly difficult or wordy question. In addition to considering the basic preparation and test-taking advice presented so far, you also need to consider the challenges presented by the different exam designs, as described in the following sections.
Tips for Fixed-Form Exams Because a fixed-form exam is composed of a fixed, finite set of questions, you should add these tips to your strategy for taking a fixed-form exam: . Note the time allotted and the number of questions on the exam you are taking. Make
a rough calculation of how many minutes you can spend on each question, and use this figure to pace yourself through the exam. . Take advantage of the fact that you can return to and review skipped or previously
answered questions. Record the questions you can’t answer confidently on the scratch paper provided, noting the relative difficulty of each question. If a check box labeled Marked is available, select it; this assists you in returning to the question at the end of the exam because you will receive a summary list of all questions showing which ones you have marked. When you reach the end of the exam, return to the more difficult questions. . If you have session time remaining after you complete all the questions (and if you
aren’t too fatigued!), review your answers. Pay particular attention to questions that seem to have a lot of detail or that require graphics. . As for changing your answers, the general rule of thumb here is don’t! If you read the
question carefully and completely and you felt like you knew the right answer, you probably did. Don’t second-guess yourself. If, as you check your answers, one clearly stands out as incorrect, however, of course you should change it. But if you are at all unsure, go with your first impression.
Tips for Answering Simulation Questions Following are tips for answering the simulation questions: . Avoid changing any simulation settings that don’t pertain directly to the problem solu-
tion. Solve the problem you are being asked to solve and nothing more.
xxxviii
MCSE 70-294: Planning, Implementing, and Maintaining a Microsoft Windows Server 2003 Active Directory Infrastructure . Assume default settings when related information has not been provided. If something
has not been mentioned or defined, it is a noncritical detail that does not factor into the correct solution. . Be sure that your entries are syntactically correct, paying particular attention to your
spelling. Enter relevant information just as the product would require it. . Close all simulation application windows after completing the simulation tasks. The
testing system software is designed to trap errors that could result when using the simulation application, but trust yourself over the testing software. . If simulations are part of a fixed-form exam, you can return to skipped or previously
answered questions and change your answer. However, if you choose to change your answer to a simulation question or even attempt to review the settings you made in the simulation application, your previous response to that simulation question will be deleted.
Final Considerations Finally, a number of changes in the MCP program affect how frequently you can repeat an exam and what you will see when you do: . Microsoft has an exam retake policy. The rule is “two and two, and then one and two.”
That is, you can attempt any exam twice with no restrictions on the time between attempts. However, after the second attempt, you must wait two weeks before you can attempt that exam again. After that, you are required to wait two weeks between subsequent attempts. Plan to pass the exam in two attempts or plan to increase your time horizon for receiving the MCP credential. . New questions are always being seeded into the MCP exams. After gathering perform-
ance data on new questions, the examiners replace older questions on all exam forms. This means that the questions appearing on exams change regularly. These changes mean that the brute-force strategies for passing MCP exams have lost their viability. Therefore, if you don’t pass an exam on the first or second attempt, it is likely that the exam’s form could change significantly by the next time you take it. It could have a completely different set of questions or new question types. Microsoft’s intention is not to make the exams more difficult by introducing unwanted change, but to create and maintain valid measures of the technical skills and knowledge associated with the different MCP credentials. Preparing for an MCP exam has always involved not only
xxxix
Study and Exam Preparation Tips
studying the subject matter but also planning for the testing experience itself. With the continuing changes, this is now truer than ever.
NOTE Exam-taking Advice—Although this book is designed to prepare you to take and pass Exam 70-294, there are no guarantees. To really work with Windows Server 2003 Active Directory, you need a solid foundation in practical skills. This book and the Microsoft Certified Professional program are designed to ensure that you have that solid foundation. When taking the actual certification exam, make sure that you answer all the questions before your time limit expires. Do not spend too much time on any one question. Remember that unanswered questions are always scored as incorrect. If you are unsure about an answer, answer the question the best you can; then mark it for review when you have finished the rest of the questions. Be sure to read each question carefully and read all the answers before you make a selection. A question might have an answer that is close, but one of the other answers might, in fact, be a better answer. If you select an answer before reading all the choices, you might miss the best answer. Get a good night’s sleep before the exam. If you don’t know the exam information by the night before the exam, an all-night cram session will just make you tired when you are taking the exam. You need to be at your sharpest when you take this exam; don’t handicap yourself with sleep deprivation.
Remember, the primary objective of this book is not the exam; it is to ensure that you understand the material. After you understand the material, passing the exam should be simple. Knowledge is a pyramid; to build upward, you need a solid foundation. This book and the MCP programs are designed to ensure that you have that solid foundation. Good luck!
NOTE No Substitute for Experience The single best study tip that anyone can give you is to actually work with the product that you’re learning! Even if you could become a “paper MCSE” simply by reading books, you wouldn’t get the real-world skills that you need to be a success.
This page intentionally left blank
PART I
Exam Preparation Chapter 1 Concepts of Windows Server 2003 Active Directory Chapter 2 Planning and Implementing an Active Directory Infrastructure Chapter 3 Managing an Active Directory Infrastructure Chapter 4 Maintaining an Active Directory Infrastructure Chapter 5 Planning User, Computer, and Group Strategies Chapter 6 Implementing User, Computer, and Group Strategies Chapter 7 Planning and Implementing Group Policy Chapter 8 Managing Group Policy
This page intentionally left blank
1
CHAPTER ONE
Concepts of Windows Server 2003 Active Directory Active Directory version 2.0? For those of you who have worked only with Windows NT 4.0 servers and domains, Active Directory is an entirely new means of managing domains and enterprises. If you have some experience managing Novell NetWare servers, you will be familiar with many of the concepts of Active Directory. And for those of you who have worked with Active Directory in Windows 2000, you will find many new features that improve the way things are done and therefore ease the burden of administration. We begin this study guide by looking at what Active Directory is and explaining its features and concepts in a manner that sets the stage for the coming chapters. This chapter does not contain any formal Microsoft exam objectives, but you should become familiar with the terms discussed here. This information guides you as you study how to create your first Active Directory forest and domain and learn how to administer them on a day-to-day basis.
Outline Introduction
5
A Brief History of Directory Services
5
Physical Components of Active Directory
21
Sites
21
Domain Controllers
22
6
Global Catalog Servers
23
X.500
6
Flexible Operations Masters
24
LDAP
7
Schema Master
24
Naming Standards of X.500 and LDAP
8
Domain Naming Master
25
Distinguished Names
8
PDC Emulator
25
Relative Distinguished Names
9
Infrastructure Master
25
RID Master
26
How Is Active Directory Built?
User Principal Names
9
Globally Unique Identifiers
10
Security Identifiers
10
Active Directory Canonical Names
10
The Building Blocks of Active Directory 11 Namespaces
11
Objects
12
Containers
12
Schema
12
Global Catalog
13
Partitions
14
Directory Services Review
14
Logical Components of Active Directory 15 Domain
15
Tree
16
Forest
17
Organizational Units
17
Review of Active Directory Components 21
Reviewing Active Directory’s Physical Components
26
Some Advantages of Active Directory over Older Directory Services
26
What Is New in Windows Server 2003 Active Directory?
27
What Is New in Windows Server 2003 Release 2 Active Directory?
30
Chapter Summary
33
Key Terms Suggested Readings and Resources
33 34
Introduction Before we show you how to build and administer an Active Directory network, we need to show you the concepts on which Microsoft built Active Directory. We start by taking a brief look at what went before Active Directory to show the need for Microsoft to completely rebuild its directory service from the ground up. Those of you who have worked with Windows NT 4.0 will be familiar with its flat, self-limiting directory service that served its purposes well but limited companies with large networks and forced them to employ a series of domains to be able to build enterprise-sized networks. Beginning with Windows 2000, Microsoft introduced the new hierarchical directory service, Active Directory. We designed this chapter to acquaint those who have not used Windows 2000 Active Directory with the concepts and terms that Active Directory uses. This material is necessary for the proper understanding of topics in the chapters to come. Those of you who are experienced with Windows 2000 Active Directory and are upgrading your qualifications to Windows Server 2003 might want to skip most of this chapter. You should refer to the sections titled “What Is New in Windows Server 2003 Active Directory?” to acquaint yourself with the most important new features in this release. In addition, the section titled “What Is New in Windows Server 2003 Release 2 Active Directory?” introduces new features added with the Release 2 (R2) version of Windows Server 2003.
A Brief History of Directory Services In the days of Windows NT, Microsoft’s notion of directory services was rooted in the concepts developed in the era of Microsoft’s LAN Manager, a pre-Windows product. At this time, the concept of domains as logical groupings of computers was introduced. Each domain contained a single primary domain controller (PDC), which employed a database called the Security Accounts Manager (SAM) to hold objects such as user, group, and computer accounts. With his user account, a user could access any resource, such as a file, folder, or printer, for which he had permissions. Permissions for these objects were included with each object and made reference to the SAM to determine users’ group memberships and rights. Consequently, it was possible to think of a domain as a security boundary. The domain concept segmented the network world and allowed for access to information located within each group of computers, but it did not permit access to information located in a different group of computers. To access resources across the domain boundary, Microsoft introduced the concept of trusts. Simply stated, one domain could trust another domain that users in that domain were who they said they were, and could be permitted to use the trusting domain’s resources. In this way, the user could access resources in a trusted domain, again according to the permissions granted to that resource.
6
Chapter 1: Concepts of Windows Server 2003 Active Directory
As the size of an organization and the number of domains it contained grew, the trust relationships and amount of work needed to administer them grew rapidly. Likewise, the chances of problems increased. Microsoft recognized that something had to be done about this situation and looked to other established directory systems including the Novell Directory Services (NDS), which is built on the X.500 directory services specification and uses a hierarchical structure rather than the flat structure of the Windows NT directory service. In Windows Server 2003, Microsoft has added new features that improve its ease of use and management.
How Is Active Directory Built? Before studying the structure of Active Directory itself, we will take a little time to introduce the concepts of the X.500 and Lightweight Directory Access Protocol (LDAP) protocols, which are central to understanding Active Directory and its structure. Microsoft utilized the industry-standard LDAP interface as a basis for Active Directory so that third-party developers could more easily design add-on components capable of interacting with Active Directory and other LDAP-enabled databases. For more information on LDAP, refer to Request for Comments (RFC) 1777, which is available on the Internet.
X.500 X.500 was developed to help network users locate users elsewhere so that they could send email messages. It also provided information on applications that required access to resources elsewhere on the network, and on management systems that needed to know the name and location of objects on the network. First appearing in 1988, X.500 used an inverted tree concept to identify and describe all objects contained in a hierarchical database. In the inverted tree hierarchical structure, countries formed the top level (next to the root) and organizations and their organizational roots formed branches beneath these roots. The complete hierarchical X.500 system was known as the directory. X.500 used three types of information to locate resources: . Name services located specific names . Electronic address books identified addresses on the network . Directory services of centrally managed electronic address books helped users search
across networks The complete directory database, called the Directory Information Base (DIB), provides a total information-locating resource. Entries in the database are known as objects. Objects include items such as user accounts, files, and folders, as well as resources, such as printers.
7
How Is Active Directory Built?
The problem with X.500 was that it proved to be more complex than what most organizations needed. As originally created, X.500 was too open for the entire world to see. In addition, it was expensive and, in its original implementation, slower than other resource-locating methods.
LDAP LDAP is a protocol originally designed by the Internet Engineering Task Force (IETF) to work as a front-end client service to X.500–compatible directory services. Alternatively, it can function as a directory service on its own. LDAP is a subset of X.500 that operates on TCP/IP networks and, as compared to X.500, uses a lower level of system resources. LDAP is used as an Internet directory standard that is capable of providing open access to directory services over the Internet or a corporate intranet. Using a text-based query system, it allows users to quickly and easily query directories containing information such as usernames, email addresses, telephone numbers, and other user attributes. It has gone through several versions that are defined in RFCs for use as Internet standards. Active Directory supports versions 2 and 3 of LDAP. The most recent implementations of LDAP go beyond the X.500 standards in providing a solution needed to offer a global directory service. Included are such features as the support for extended character sets as used by various global languages and an easier referral mechanism to hand queries from one server to another. An extension mechanism is also provided to facilitate future development of the LDAP standard. LDAP uses the inverted tree concept originated by X.500 to identify and describe all objects contained in its database. Entries within LDAP’s inverted tree can include containers that hold other objects and leaf objects that represent entities such as people, computers, printers, and so on. Introduced with X.500 and further refined by LDAP is a series of definitions that have carried over into the Active Directory naming scheme. The hierarchical naming scheme is illustrated in Figure 1.1 and is explained in the next section.
Root
Country (C)
Organization (O)
Organizational Unit (OU)
Canada
U.S.A
Microsoft
Accounting
Australia
Quepublishing.com
Production
Management
Resources (users, computers, folders, printers, etc.)
The LDAP hierarchical naming scheme.
FIGURE 1.1
8
Chapter 1: Concepts of Windows Server 2003 Active Directory
Naming Standards of X.500 and LDAP Originating with X.500 and expanded on by LDAP is a series of naming standards that define the path to any object defined in the directory. Because Active Directory uses LDAP as the protocol of choice for accessing objects in the directory, you should know these naming paths and their components to understand the capabilities of Active Directory fully. The naming paths include the distinguished names and relative distinguished names. Additional identifiers you should be familiar with include the User Principal Names (UPNs) and Globally Unique Identifiers (GUIDs). We introduce these identifiers later in this chapter.
Distinguished Names A distinguished name (DN) defines the complete path from the top of the tree to the object and uniquely identifies each object in the LDAP inverted tree. The concept of distinguished names, which originated in the X.500 specifications, is a global one that was laid out with specific goals in mind. Those goals include the following: . To provide an unambiguous representation of the name of any resource . To provide a readily understood format for the majority of names . To achieve an attractive representation of information within several different layouts . To clearly represent the contents of the object being defined
To achieve these goals, a series of X.500-based delimiters was developed with standard abbreviation names, some of which were shown in Figure 1.1. These abbreviations comprise the complete definition of each DN. RFC 1779 gives the complete specification of distinguished names, including the complete syntax and full list of delimiters. The most common delimiters include . CN—Common name . OU—Organizational unit . DC—Domain component . O—Organization name . C—Country name
For any given object, the DN is a unique and unambiguous identification of the object and its location within the directory structure. In other words, two different objects can never have exactly the same DN. To specify a DN, include the name of the object itself, followed by the containers and the parent containers that hold the name in order. Note that a distinguished
9
How Is Active Directory Built?
name may contain more than one occurrence of a given delimiter. The following is an example of a distinguished name: CN=Tim Brown,OU=Inventory,DC=Quepublishing,DC=com
NOTE Displaying the DN Active Directory snap-in tools generally do not display the DN as shown in this example. We show this example to illustrate how LDAP recognizes the components of the DN. However, it is helpful to know the concept of the distinguished name and how objects fit together into the Active Directory hierarchy. You will see more of how these elements fit together as you progress through this training guide—for example, when you need to restore Active Directory objects. See Chapter 4, “Maintaining an Active Directory Infrastructure,” for more information.
Relative Distinguished Names The relative distinguished name (RDN) is the most granular part of the distinguished name, and it identifies a specific attribute of the object itself. For example, in the distinguished name given in the preceding section, the RDN is the first part: CN = Tim Brown. Within any given parent container, no two objects can have the same RDN; however, two objects within different containers can have the same RDN. An analogy could be the fact that more than one city with the same name can exist, as long as the cities are located in different states, such as Springfield, Illinois, and Springfield, Massachusetts. The DNs for these cities could be as follows: CN=Springfield,OU=IL,C=US and CN=Springfield,OU=MA,C=US The CN in these examples defines the exact city as opposed to a different city such as Chicago or Boston; therefore, the CN is also the RDN here.
User Principal Names In addition to the DN and RDN described in the preceding sections, Active Directory uses the concept of the User Principal Name (UPN), which is introduced here and is intimately related to these other names. The UPN is a user’s shortcut name that can be the same as a logon name or email address. For example, referring to the DN described earlier, the UPN could be
[email protected].
10
Chapter 1: Concepts of Windows Server 2003 Active Directory
Globally Unique Identifiers Every object stored in Active Directory also has a unique identifier called the Globally Unique Identifier, or GUID, which is a 128-bit hexadecimal number assigned when the object is created in Active Directory. The GUID is stored in an attribute called objectGUID, which exists for every object in Active Directory. Unlike the DN or RDN, this identifier never changes even if you move or rename the object. For example, an employee leaves the company and is replaced; you want the new employee to have the same rights and privileges as the old one, so you rename the user account. This account retains the GUID of the old account. However, if you were to delete an object and then later re-create another object with the same DN, the GUID would not be the same; this is the reason that if you have deleted an object, such as a user or group account, and then must re-create it, you must re-create all properties and attributes associated with the object.
Security Identifiers The security identifier (SID) is a value that uniquely identifies a security principal such as a user, group, service, or computer account within the Active Directory forest. (We introduce the concept of forests later in this chapter.) Every account is issued an SID when it is created. SIDs are used to identify security principals in Windows Server 2003 for access control purposes. No two objects in the forest can have the same SID. It contains two components: a domain portion, which is identical for all objects in the same domain, and a relative identifier (RID), which is unique for every object. A SID can change under certain circumstances, such as if a user is moved from one domain to another. As with the GUID, if you delete an object and later re-create an object with the same name, the SID would not be the same. Windows Server 2003 uses the SID, rather than the GUID, in determining object access, for reasons of backward compatibility. Windows NT 4.0 used the SID for this purpose, and these SIDs are maintained when a Windows NT domain is upgraded to Windows Server 2003.
Active Directory Canonical Names The canonical name is a version of the DN that Active Directory displays. It lists the RDNs from the root downward (that is, in reverse sequence to the DN) and does not use the RFC 1779 naming attribute descriptors. However, the canonical name does use the domain name system (DNS) domain name. For the DN given previously, the Active Directory canonical name would be as follows: Quepublishing.com/inventory/TimB
11
The Building Blocks of Active Directory
The Building Blocks of Active Directory Active Directory can support an almost unlimited scope of functions and capabilities in an enterprise network, from small-scale operations to a global-scale multidomain enterprise. Microsoft took the concepts of X.500 and LDAP, which we already discussed, and molded them with a series of new components to come up with Active Directory’s structure. To this end, Active Directory embraces the following concepts: . Namespace . Object . Container . Schema . Global catalog . Partition
We briefly introduce each of these concepts in the following sections.
Namespaces The concept of a namespace originated with early incarnations of the Internet. This term refers to a bounded area within which a name is resolved or translated into information that is encompassed by the name. For an analogy, you can think of a telephone directory as a type of namespace in which names are resolved to phone numbers; its area is bounded within the city, county, or other geographic area that is served by the directory. An example in the computer world is that of a hostname that represents an IP address. Microsoft took this concept and expanded on it until it encompassed any type of information that anyone might have a need to locate. Further, Microsoft made this concept dynamic so that when items were added, moved, or removed, the directory would reflect these actions. The result was Active Directory. Namespaces can be either flat or hierarchical. Flat namespaces have only one level at which they store information, such as the NetBIOS naming concepts used in Windows NT 4. Hierarchical namespaces, as the name suggests, use several levels of name definition, such as those found in an Internet name like www.sales.quepublishing.com. Here, com represents the top level, quepublishing represents a second-level domain, sales is a subdomain, and www is a web server name. As you are undoubtedly aware, DNS uses this type of namespace. The DNS naming scheme is used to create the structure of the Active Directory namespace, permitting interoperability with Internet technologies; therefore, the concept of namespaces is central to Active Directory. By integrating this concept with the system’s directory services,
12
Chapter 1: Concepts of Windows Server 2003 Active Directory
Active Directory facilitates the management of the multiple namespaces often found in the heterogeneous software and hardware environments of corporate networks. The two types of namespaces are contiguous and disjointed. They are defined as follows: . Contiguous—The name of the child objects in the hierarchy contains the name of the
parent object; for example, the relationship between domains within the same tree. . Disjointed—The name of a child object in the hierarchy does not contain the name
of the parent object; for example, the relationship between different trees in the same forest.
Objects An object is any specific item that can be cataloged in Active Directory. Examples of objects include users, computers, printers, folders, and files. These items are classified by a distinct set of characteristics, known as attributes. For example, a user can be characterized by a username, full name, telephone number, email address, and so on. Note that in general, objects in the same container have the same types of attributes but are characterized by different values of these attributes. The Active Directory schema defines the extent of attributes that can be specified for any object. The Active Directory service, in turn, classifies objects into classes. These classes are logical groupings of similar objects, such as users. Each class is a series of attributes that define the characteristics of the object.
Containers A container is an object designed to hold other objects within the directory. A folder could be considered a container because it holds the files and subfolders located beneath it. Like other objects, containers have their own attributes. Forests, trees, domains, and OUs are all different types of containers because they are all designed to contain other objects.
Schema The schema is a set of rules that define the classes of objects and their attributes that can be created in Active Directory. It defines what attributes can be held by objects of various types, which of the various classes can exist, and what object class can be a parent of the current object class. For example, the User class can contain user account objects and possess attributes such as password, group membership, home folder, and so on. You can mark attributes as indexed, which means that instances of the attribute are added to a searchable index and are more easily located by a user searching by the container in which the
13
The Building Blocks of Active Directory
attributes are located. This feature improves search time but increases the size (and replication time) of the Active Directory database. When you first install Active Directory on a server, a default schema is created; it contains definitions of commonly used objects and properties such as users, computers, and groups. This default schema also contains definitions of objects and properties needed for the functioning of Active Directory. The Active Directory schema is extensible; that is, you can define new types and attributes of directory objects, as well as new attributes for existing objects. In doing so, you can adapt the schema to a given type of business; for example, a wholesaler might want to add a warehouse object to the directory, including information specific to that business. Additions to the schema are implemented automatically and are stored within the Active Directory database. Applications can be built to extend the schema and can use such extensions immediately.
WARNING Schema Modification As we discuss in Chapter 3, “Managing an Active Directory Infrastructure,” modifying the schema is serious business. Improper modifications to the schema can harm or disable the domain controllers or even the entire network. For this reason, Microsoft has included a group called Schema Admins. Only members of this group have the right to modify the schema.
Global Catalog The global catalog is a central information database that can hold data describing objects throughout the Active Directory forest namespace. Active Directory builds up the global catalog by replicating information between all domain controllers in the forest. In this way, a comprehensive and complete database of all available objects is automatically built up. To extend the telephone directory analogy we referred to earlier in the chapter, you can think of the global catalog as a yellow pages directory that facilitates your locating a specific type of resource, such as a color printer on the seventeenth floor of your building. As well as providing a physical location that contains a subset of all information in each domain’s Active Directory database, the global catalog is a service that permits the resolution of many common queries that originate from anywhere in the forest. It holds and organizes the common attributes used in search operations, such as user and group names, filenames, and so on. All information pertaining to universal groups, including their membership, is found here. Usernames are stored in the UPN format; because of this, a user can log on to any computer in the forest by employing the UPN. By default, Active Directory stores the global catalog on the first domain controller in a new forest. It is possible to either move or copy the global catalog to another domain controller.
14
Chapter 1: Concepts of Windows Server 2003 Active Directory
Partitions Active Directory is divided into several partitions—not to be confused with disk partitions— that allow the enterprise-level network to be scaled to enormous proportions while remaining manageable. A schema partition and a configuration partition are stored on all domain controllers within an Active Directory forest, and application and domain partitions are common to domain controllers within a domain. The roles of these partitions are as follows: . Domain partition—This partition contains information about all objects such as
users, groups, computers, and organizational units in a domain. It is replicated to all domain controllers within the domain, and a subset of this information is replicated to global catalog servers in the forest. . Schema partition—This partition contains definitions of all objects and their attrib-
utes. Rules for creating and working with them are also located here. This partition is replicated to all domain controllers in the forest. . Configuration partition—This partition contains information about the structure of
Active Directory in the forest, including domains, sites, and services. It is replicated to all domain controllers in the forest. . Application directory partition—New to Windows Server 2003, this partition con-
tains application-specific data that needs to be replicated throughout specified portions of the forest. Also referred to as application partition, it can be replicated to a specific domain controller or to any set of domain controllers anywhere in the forest. In this way, it differs from the domain partition in which Active Directory replicates data to all domain controllers in that domain. It also contains DNS information for Active Directory–integrated DNS zones.
Directory Services Review Following is a summary of Active Directory and how it is built: . Microsoft designed and built Active Directory according to the concepts of the X.500
and LDAP networking protocols. . The distinguished name (DN) is a unique identifier that fully defines and locates any
object used in Active Directory. . The schema is a set of rules that define the classes of objects and their attributes in
Active Directory. . The global catalog is a central information database that holds data describing objects
throughout the Active Directory namespace.
15
Logical Components of Active Directory
Logical Components of Active Directory As already mentioned, Active Directory is a hierarchical database. This logical grouping of resources facilitates the locating of a resource by its name rather than by its physical location. Proceeding from the largest unit to the smallest one, the logical structure of Active Directory consists of forests, trees, domains, organizational units (OUs), and objects. Because a domain is the basic unit on which Active Directory is built, we introduce the domain first, followed by trees and forests (in which domains are located), and then organizational units, which are containers located within a domain.
Domain As already emphasized, the domain is the core building block of Active Directory. A domain is a logical grouping of computers and users that share a common database containing user accounts and other security information. In Windows NT 4.0, it was defined by a single PDC with its centralized SAM that holds information pertaining to all the users, groups, and computers in that domain. As in Windows 2000, the Active Directory database file (ntds.dit) defines the domain in Windows Server 2003. Each domain has its own ntds.dit file, which is stored on (and replicated among) all domain controllers by a process called multimaster replication. The domain controllers manage the configuration of domain security and store the directory services database. This arrangement permits central administration of domain account privileges, security, and network resources. Networked devices and users belonging to a domain validate with a domain controller at startup. All computers that refer to a specific set of domain controllers make up the domain. In addition, group accounts such as global groups and domain local groups are defined on a domainwide basis. In Windows NT 4.0 a domain was limited to about 40,000 objects (users, groups, or computers). Theoretically, a Windows Server 2003 domain could hold millions of objects. However, moderate- to large-size companies should consider the benefits that a multiple-domain structure offers. Some benefits of using multiple domains are as follows: . Domains can be considered security boundaries. In other words, domain administrators
can define access control lists (ACLs) that determine users’ access rights and permissions to objects within the domain at the domain level. Also, each administrator has the authority to set security policy only within his domain. . You can specify how resources in each domain can be accessed using Group Policy,
which can be configured on a domainwide basis. Group Policies have full control over all objects in the domain but do not have any authority over objects in other domains. . You can configure domains along geographical lines; for example, a multinational com-
pany may organize its network with a domain for every country. In this manner, the company can deal with legal and other country-specific issues.
16
Chapter 1: Concepts of Windows Server 2003 Active Directory . You can configure domains along business lines, such as a parent company with a series
of subsidiaries. This configuration simplifies reorganization should a subsidiary be sold or a new one acquired.
Tree A tree is a grouping of domains that share a contiguous namespace (see Figure 1.2). In other words, a tree contains a parent domain whose name is reflected in all child domains within that tree. For example, if the parent domain is quepublishing.com, additional domains in the same tree could have names such as products.quepublishing.com, accounts.quepublishing.com, or management.quepublishing.com. In addition, these child domains can also be parents of domains at a lower level—for example, Canada.products.quepublishing.com and USA.products.quepublishing.com. A domain called examcram.com would not belong to the same tree. Following the inverted tree concept originated by X.500, the tree is structured with the parent domain at the top and child domains beneath it. quepublishing.com
A tree consists of a group of domains that share a contiguous namespace, with the parent domain at the top.
FIGURE 1.2
accounts.quepublishing.com
products.quepublishing.com
management.quepublishing.com
WARNING Domain Hierarchy Although you could theoretically have any number of child domain levels, administration becomes difficult if there are more than a few levels. Try to avoid a domain hierarchy that is too complex.
By default, all domains in a tree link together with two-way, transitive trust relationships. You will learn more about trusts in Chapter 3.
17
Logical Components of Active Directory
Forest A forest is a grouping of domain trees that do not share a contiguous namespace (see Figure 1.3). For example, two trees whose parent domain names are quepublishing.com and examcram.com can be joined in a forest relationship, with each tree having its own namespace. Recalling the definition of namespace as a bounded area in which the directory can resolve names, the forest itself is also a namespace; in this case, it is a disjointed namespace. In other words, the two portions of the namespace do not share a name in common. By default, twoway transitive trust relationships exist between the parent domains in each tree throughout the forest. Again, these trust relationships do not need to be explicitly configured. In addition, all domains in the forest share a common schema, configuration, and global catalog.
quepublishing.com
accounts.quepublishing.com
products.quepublishing.com
examcram.com
FIGURE 1.3 A forest is a group of trees that form a disjointed namespace.
In a forest, one domain has to be the forest root domain. The forest root domain is always the first domain created when a new forest is created.
NOTE Creating a Forest You must first create the forest root; then you can create additional trees in the forest or additional domains in any tree in the forest. With the default Windows Server 2003 tools, you cannot join an existing domain to a tree or forest. Available third-party tools, however, can perform the tasks of pruning and grafting, as they are called. Alternatively, you can enable access between domains in different forests by creating a forest trust relationship. We discuss this trust relationship in Chapter 3.
Organizational Units An organizational unit is used to group objects within a domain into logical administrative groups (see Figure 1.4). It is a convenient grouping for holding objects that pertain to a given
18
Chapter 1: Concepts of Windows Server 2003 Active Directory
work unit, section, or department of an organization, such as the manufacturing department. A hierarchy of OUs is analogous to a hierarchy of folders on a disk; indeed, within the Active Directory Users and Computers Microsoft Management Console (MMC) snap-in, the various OUs are depicted as folder icons.
Accounts
Receivable
Products
Payable
Domestic
quepublishing.com
Export
FIGURE 1.4 You can create hierarchies of OUs within your domain structure.
Each OU can contain any type of noncontainer object such as users, groups, and computers. In addition, it can contain additional OUs within it. Therefore, you can build an OU hierarchy to any depth within the domain. You can also modify or remove a series of OUs. Within each OU, you can perform actions such as creating, moving, deleting, and modifying objects within the OU, as easily as the OUs themselves. Some uses of OUs are as follows: . Apply different sets of policies to users with different requirements. For example, you
might want to apply a different desktop to accountants than to engineers. You can do this by specifying Group Policy Objects (GPOs) that apply to the respective OUs. . Delegate control of certain user and/or computer accounts to a subset of assistant
administrators so that they can be responsible for accounts located within only a portion of the company and can perform activities such as resetting passwords and so on. . Separate various types of objects. For example, you can use one OU to hold just client
computers, another for member servers, another for domain controllers, and yet another for user and group accounts. In fact, Microsoft creates a default Domain Controllers OU when you install Active Directory.
19
Logical Components of Active Directory
Child Domains or Organizational Units? As you have probably noticed, it is possible to configure corporate divisions either as additional domains or as OUs within the domain. Organizations have different reasons for preferring one type of structure over another. International companies might want to create a single domain for each country in which they operate. This configuration provides flexibility in dealing with issues such as legal requirements, language, currency, and so on. Other companies might want to separate operational divisions—for example, manufacturing, sales, and administration. Considerations such as plans for future acquisitions or divestitures or the opening of new operating divisions can play a role in deciding what organizational model you should adopt. When planning a domain structure, you should ensure that corporate management plays a significant role in the planning process and that the top executives are informed of any decisions made at all stages of the planning process. We discuss the planning of domains and OUs further in Chapter 2, “Planning and Implementing an Active Directory Infrastructure.”
Challenge Designing an Active Directory Forest and Domain Structure In this chapter we have looked at the logical containers of Active Directory—forests, trees, domains, and OUs. We have shown how it is possible to design an Active Directory infrastructure in more than one way, compared to the simpler design structures that were available in Windows NT 4.0. To obtain the best use of these features, you need to plan the deployment of Active Directory in advance of its actual installation. It is not enough simply to go ahead and upgrade all your company’s Windows NT domains to Active Directory, as many companies have found out in the years since Windows 2000 was introduced. Consider a fictional, multinational company named Widgets.com, with business in North America, Europe, Australia, and Japan. The company manufactures widgets and distributes them to independent retailers by means of a system of wholesale distribution centers. Table 1.1 shows a few business details about this company.
TABLE 1.1 Widgets.com Business Operations Country United States
Operations Corporate administrative headquarters and business offices, located in Atlanta, GA Ten manufacturing facilities in eight states Twenty wholesale distribution centers (continues)
20
Chapter 1: Concepts of Windows Server 2003 Active Directory
TABLE 1.1 Continued Country Canada
Operations One manufacturing facility Three wholesale distribution centers
United Kingdom
European administrative headquarters Two manufacturing facilities Four wholesale distribution centers
France
One manufacturing facility, designed to handle the entire western European continent One wholesale distribution center
Germany
One wholesale distribution center
Italy
One wholesale distribution center
Japan
Asian administrative headquarters One manufacturing facility One wholesale distribution center
Australia
Australian administrative headquarters One manufacturing facility Two wholesale distribution centers
The company has hosted multiple Windows NT domains with at least one domain at each location at which it does some type of business. The result was a huge conglomeration of multiple domains and trust relationships, security lapses, and administrative headaches. Management saw the use of Active Directory as a way out of its problems. Review the company’s structure and build paper models of possible tree, domain, and OU structures that would fit this company’s structure. There is no single correct solution to this problem; several different outcomes are possible and might work equally well. Look at the following as a basic series of steps that you should follow: 1. Determine the number of domains required. 2. Determine whether to upgrade existing domains or deploy new domains. Remember that existing Windows NT domains cover only a single office, manufacturing facility, or distribution center. 3. Select the forest root domain. 4. Decide on a tree structure. Do you want a single tree encompassing the entire company or multiple trees representing continents or countries? 5. Decide on the domain structure and a logical sequence of domain names. Remember that you should try to minimize the number of domains deployed in the forest. You can employ OUs to subdivide your directory structure further in terms of administrative units.
21
Physical Components of Active Directory
Review of Active Directory Components Following is a review of Active Directory’s logical structure: . A domain is a logical grouping of computers and users that share a common database
containing user accounts and other security information. . A tree is a group of domains that share a contiguous namespace—in other words,
a parent domain with one or more child domains. . A forest is a group of domain trees that do not share a contiguous namespace. . An organizational unit (OU) is used to group objects within a domain into logical
administrative groups.
Physical Components of Active Directory These divisions of Active Directory are only logical ones; you can have several domains, even an entire forest, at one location, or alternatively, you can have a single domain spread out over several buildings or cities. Microsoft has provided a means to recognize and take into account the physical structure of the enterprise. This fact is important for various reasons, including the need to maintain the replication of the Active Directory database over slow wide area network (WAN) links that exist between physical sites and the need for users to be able to log on to a domain controller over a high-speed link.
Sites A site is a set of one or more IP subnets connected by a high-speed, always available local area network (LAN) link. Figure 1.5 shows an example with two sites, one located in Chicago and the other in New York. In other words, a site is contained within one building, or perhaps within several adjacent buildings in a campus setting. The boundary of the site is typically the boundary of the LAN. A subnet can be associated with only a single site. Sites contain only resource objects, such as computers. By contrast, it is assumed that different sites are connected by slower, WAN links that might be available only at certain times of the day or on demand. Using sites permits you to configure Active Directory replication to take advantage of the high-speed connection. It also enables users to connect to a domain controller using a reliable, high-speed connection.
22
Chapter 1: Concepts of Windows Server 2003 Active Directory
NOTE Site and Domain Topologies The site topology of a network is different from the domain topology. Consequently, you can have one domain across more than one site, and you can have one site that contains multiple domains. You can even have multiple domains, each with portions thereof, on the same multiple sites.
Chicago
New York
FIGURE 1.5 A site is a grouping of resources in one physical location and is distinct from any domain grouping.
Domain Controllers Domain controllers (DCs) are Windows Server 2003 computers on which Active Directory has been installed. Likewise, any server on which Active Directory is installed is automatically a domain controller. These servers authenticate users on the domain and replicate information to other domain controllers. All changes to domain configuration, such as adding user accounts, are performed at a domain controller. The DC stores a complete copy of all objects contained within the domain—along with the Active Directory schema and configuration—in the Active Directory database file, ntds.dit. Note that the DC stores domain partition information only for the domain to which it belongs, but it stores schema and configuration partition information for the entire Active Directory forest. Each DC can write to Active Directory. Every domain must have at least one DC. A domain may have more than one DC; having more than one DC provides the following benefits: . Fault tolerance—If one domain controller goes down, another one is available to
authenticate logon requests and locate resources through the directory. . Load balancing—All domain controllers within a site participate equally in domain
activities, thus spreading the load out over several servers. This configuration optimizes the speed at which requests are serviced.
23
Physical Components of Active Directory
You can promote a Windows Server 2003 computer to the role of DC by running the dcpromo.exe program, which you can start from the Run command or from the Configure Your Server Wizard (see Figure 1.6) or the new Manage Your Server program. We discuss the details of promoting a server in Chapter 2.
FIGURE 1.6 You can configure various roles, including that of domain controller, by using the Configure Your Server Wizard.
Global Catalog Servers When you install the first domain controller in a new domain, this domain controller is also a global catalog server by default. In other words, it stores a copy of the global catalog, and users can query it to locate resources within the forest. Active Directory replicates this information to other global catalog servers in the forest. You can also designate additional domain controllers in the domain as global catalog servers. Doing so spreads out the task of locating resources between servers, thus facilitating response to user queries. This capability is especially important for domains that span more than one site. You can also move the global catalog role from one domain controller to another, if necessary. The global catalog server performs the following directory roles: . Locates objects within the forest—When a user searches for objects such as people,
folders, or printers, the global catalog enables her to locate objects in other domains within the forest. Active Directory automatically directs any search for the entire directory to the global catalog server. . Authenticates users by their UPN—When a user logs on to a domain other than his
home domain using the UPN (for example,
[email protected] logging on to the products.quepublishing.com domain), the domain controller in the
24
Chapter 1: Concepts of Windows Server 2003 Active Directory products.quepublishing.com domain contacts the global catalog server to obtain
authentication information for this user. . Provides universal group membership information—A universal group can include
members from any domain in the forest, and its membership information, including permissions for resources assigned to it, is stored at the global catalog server. It supplies this information to a DC when a user who belongs to a universal group logs on. New to Windows Server 2003, a DC can then cache this information to facilitate future logons by the same user.
Flexible Operations Masters Although you can make most changes to Active Directory from any domain controller in the forest, you can perform certain functions only from specific locations. Microsoft has defined five specific roles, known as flexible single-master operations (FSMO) roles, which are assigned to specific domain controllers. The following two roles are located in only a single domain controller in the forest: . Schema master . Domain naming master
The other three roles are located on one domain controller in each domain: . PDC emulator . Infrastructure master . Relative identifier (RID) master
All five of these roles are located on the first domain controller installed in a new forest, and the three domain-specific roles are initially located on the first domain controller for each additional domain in the same forest. You can transfer these operations master roles to other domain controllers or seize their roles when a domain controller holding them becomes inoperable. Lack of availability of these operations masters affects the day-to-day management of Active Directory, as we discuss in the following sections.
Schema Master The schema master holds the only writable copy of the Active Directory schema and is the only location at which you can perform updates and modifications to the schema. If this role is unavailable, you cannot edit the schema until it is restored. We discuss the managing of schema modifications in Chapter 3.
25
Physical Components of Active Directory
Domain Naming Master The domain naming master plays a role in ensuring that names of newly created domains adhere to the proper naming conventions for new trees or child domains in existing trees, as described earlier in this chapter and illustrated in Figures 1.2 and 1.3. It also plays a role in removing domains from the forest. When you run dcpromo.exe on a server and select options to create a child domain or a new domain tree, the server contacts the domain naming master for this purpose. If this role is unavailable, you cannot create a new domain or remove an existing domain from the forest. We discuss creating child domains and new domain trees in Chapter 2.
PDC Emulator In a domain that contains Windows NT 4.0 backup domain controllers (BDCs) and is operating at the Windows 2000 mixed functional level, the PDC emulator propagates any changes to user properties, such as password changes to the BDCs. When a user logs on to a BDC from a down-level client computer, the BDC contacts the PDC emulator to ensure that modified credentials are available. If the user changes her password, the password change is handled by the PDC emulator, which replicates the changes to other domain controllers. This role is necessary because the NT 4.0 BDCs contain a read-only copy of the directory database. The PDC emulator also acts as a domain master browser for NetBIOS-based clients attempting to locate domain resources. If this role is unavailable, down-level clients cannot change their passwords. They also might be unable to log on if changes in their user account properties have taken place. In a mixed-mode domain with NT 4.0 BDCs, it would be impossible to make changes to any domain properties and have them propagate properly to the BDCs if the PDC emulator were unavailable. The PDC emulator in the forest root domain also operates as a time synchronization master and synchronizes the time on the various domain controllers. In its absence, the clocks on other domain controllers might lose their synchronization. This loss could cause problems in replication of the Active Directory database to other domain controllers.
Infrastructure Master The infrastructure master updates references from objects, such as membership in domain groups, in its domain to objects in other domains. When an administrator in any domain makes any changes to objects in his domain, the infrastructure master receives the changes from a global catalog server, updates this information in its database, and replicates the changes to the other domain controllers in its domain. This point is important because domain local groups can contain users and global or universal groups from other domains as well as the domain in which the group is located, and global groups can be made members of universal or domain local groups in other domains.
26
Chapter 1: Concepts of Windows Server 2003 Active Directory
WARNING Don’t Place the Infrastructure Master and Global Catalog Server on the Same Computer Because the infrastructure master must work with the global catalog server to keep group membership current, these two roles should be located on different servers from each other. Otherwise, the infrastructure master cannot locate any outdated data. For the infrastructure master to function properly, it should be located in the same site as a global catalog server.
RID Master The RID master assigns security identifiers (SIDs) to objects created in the domain. Every SID has two parts: a domain identifier that is common to all objects in the domain and a relative identifier (RID) that is unique to each object. In other words, no two objects in the same domain can have the same RID. The RID master hands out a pool of several hundred RIDs to every domain controller in the domain so that they can create new objects with unique identifiers. If this role is unavailable, other domain controllers cannot create new objects if they have no unused RIDs available.
Reviewing Active Directory’s Physical Components Following is a review of Active Directory’s physical structure: . A site is a set of one or more IP subnets connected by a high-speed LAN link. . A domain controller is a Windows Server 2003 computer on which Active Directory
has been installed. These servers authenticate users and replicate Active Directory data throughout the domain. . A global catalog server stores a copy of the global catalog and is used for communica-
tion between domains. . An operations master is a domain controller that performs one or more of five specific
roles that can be performed only from a single domain controller in the domain or forest.
Some Advantages of Active Directory over Older Directory Services Those of you who are just beginning to study Active Directory might wonder, “Why do we have to move from the comfort of the classic Windows NT directory service?” or “Why should we go to Active Directory?” The following are a few of the limitations of a Windows NT directory structure that Active Directory has improved on:
27
What Is New in Windows Server 2003 Active Directory? . Restricted size of the SAM—As already mentioned, the SAM is a flat database that
includes all user, group, and computer accounts. Because of its size limit, it cannot have more than about 40,000 objects representing approximately 25,000 user accounts. Many companies have required a multiple-domain model simply to circumvent this restriction. . Single point of failure—Because the PDC is the only computer with a read/write ver-
sion of the SAM, you cannot make any changes to domain containers should it become unavailable. . Poor operational performance—Because there is only a single PDC, the extent of
daily operations is limited to the capacity of this machine. This situation is more acute if the PDC is situated across a WAN link in another physical location. . Poor replication performance—If you have a large domain with many BDCs, the
PDC has to devote considerable effort in keeping the database replicated properly because of the hub-and-spoke replication topology (one PDC replicating directly to all BDCs). Active Directory sets up a replication topology that involves all domain controllers for a more efficient replication performance. . Limited management granularity—There is no capability for creating groups with
limited management capacity, except for groups such as Server Operators and Account Operators. In particular, you cannot delegate the administration of a portion of a domain to individuals or groups. Active Directory fixes this problem with its administrative delegation capability. . Nontransitive trust relationships—In Windows NT, you must configure all trust
relationships manually. In particular, trust relationships do not extend to more than two domains. (For example, if domain A trusts domain B and domain B trusts domain C, domain A does not trust domain C unless you configure an additional trust.) . Limited control of users’ desktops—In Windows NT, you can exert limited control
over what users can do on their desktops with System Policy. Active Directory presents Group Policy, which as you will see in Chapter 7, “Planning and Implementing Group Policy,” and Chapter 8, “Managing Group Policy,” provides a far greater capability of controlling desktops, applications, security, and much more.
What Is New in Windows Server 2003 Active Directory? Building on the initial version of Active Directory in Windows 2000, Microsoft has introduced a number of new features that enhance the manageability of Active Directory and increase its
28
Chapter 1: Concepts of Windows Server 2003 Active Directory
dependability. These new features thereby help to reduce the total cost of ownership of Active Directory. In the various chapters of this study guide, we discuss the enhancements of Windows Server 2003 alongside the older features. Here, we outline the more significant new features of Windows Server 2003 Active Directory. . Domain renaming—New to Windows Server 2003 is the ability to change the DNS
and/or NetBIOS names of any domain within the forest. Administrators can now make changes more easily in their Active Directory design—for example, when a company is sold or renamed. In a similar manner, you can also rename domain controllers. . Forest trusts—Administrators can configure trust relationships between different
Active Directory forests. This feature enables a user located in one forest to securely access resources in another forest. This capability can be useful when a new subsidiary company is acquired or when a company is hired under contract. . Schema modification—Microsoft has added new capabilities for redefining attributes
and class definitions in the Active Directory schema, including the deactivation of attributes that are no longer needed. . DNS enhancements—When you install the first domain controller, Windows creates
a more fully functional version of DNS, complete with the initial forward and reverse lookup zones. The debugging of problems related to improper DNS configuration is also simplified. . Enhancements to Group Policy—Microsoft has added new tools to facilitate the
management of Group Policy, as well as a considerable number of new policies that extend administrators’ ability to manage their domains. In particular, the new Resultant Set of Policy tool facilitates the task of resolving conflicts between multiple policies. The Group Policy Management Console is an optional add-on tool that simplifies Group Policy administration. . Application directory partition—This partition of Active Directory contains applica-
tion-specific data that needs to be replicated to specific domain controllers in the domain, and possibly to other domains in the forest. Certain types of applications create an application directory partition for ease of replication to other domain controllers. Its use can reduce replication traffic by replicating its data only to specific domain controllers. . New command-line tools—These new tools facilitate the administration of Active
Directory from the command line. This in turn enables administrators to schedule more tasks from the Task Scheduler, including tasks such as backups that are most conveniently run late at night when network use is minimal. You can even do some tasks remotely from the command line, such as remote administration of a server from your cell phone using only a wireless keyboard and the phone’s keypad.
29
What Is New in Windows Server 2003 Active Directory? . New wizards—Windows Server 2003 features new and improved wizards to facilitate
installation and management of Active Directory. They include the Manage Your Server application and enhancements to the Configure Your Server Wizard and the Active Directory Migration Tool version 2.0. . Active Directory Application Mode (ADAM)—Available as a separate component,
this new mode runs as a service and can be deployed on any member server as well as a domain controller. It addresses directory-related application deployment scenarios and is useful in fields such as e-commerce. ADAM also enables the functionality of directory-related applications beyond the domain or forest in which the application exists, or the use of such applications outside an Active Directory environment. . Improved ease of adding other domain controllers to an existing domain—You
can now use backup media to reduce the time required to add a new domain controller. This capability is especially useful in the case of a remote office. Rather than employing a lengthy replication of Active Directory partitions over a slow link, you can back up the domain controller’s system state to a CD, ship the CD to the remote office, and have staff at that office restore this data to the new DC. . Domain controller renaming—In Windows 2000, if you had to rename a domain
controller, it was necessary to demote the computer to a member server, rename it, and then promote it back to domain controller. Windows Server 2003 allows you to rename a domain controller without the need for demoting it. . New domain and forest functional levels—Because down-level domain controllers
do not support the new Windows Server 2003 functionality, Microsoft has introduced the following new domain functional levels: . Windows 2000 mixed—The default when you create a new domain, this func-
tional level allows support for domain controllers running Windows NT 4.0 and Windows 2000 in the same domain. It does not support new features introduced in either Windows 2000 or 2003, such as universal security groups and enhanced group nesting. . Windows 2000 native—This functional level allows support for Windows 2000
domain controllers but not Windows NT 4.0 domain controllers. It supports features of Windows 2000 Active Directory but not new Windows Server 2003 features such as those discussed in this section. . Windows Server 2003 interim—Used when upgrading a Windows NT 4.0
domain to Windows Server 2003, this functional level supports Windows NT 4.0 BDCs but does not support Windows 2000 domain controllers. . Windows 2003 native—This functional level supports all enhanced features of
Windows 2003 Active Directory but does not support domain controllers running older Windows versions.
30
Chapter 1: Concepts of Windows Server 2003 Active Directory
Microsoft has also introduced three forest functional levels: . Windows 2000 interim—The default when you first create a new forest, this
functional level allows support for domains operating in any of the domain functional levels. It does not support Windows Server 2003; rather, it supports only forestwide features such as domain renaming and enhanced schema modification. . Windows 2003 interim—Used when upgrading a Windows NT 4.0 enterprise
to a Windows 2003 forest, this functional level supports Windows NT 4.0 and Windows Server 2003 domain controllers, but not Windows 2000 domain controllers. . Windows 2003 native—This functional level supports only domains running
in the Windows 2003 native functional level and provides total support for all Windows Server 2003 Active Directory features. To facilitate the integration of Windows Server 2003 domain controllers into Windows 2000 domains, Microsoft has introduced a new command-line tool, Adprep. Located in the i386 folder of the installation CD-ROM, this tool, which prepares a Windows 2000 domain for upgrade, has two parameters: /forestprep and /domainprep. . /forestprep—Run this command on the schema master to prepare the forest for
upgrade. It extends the schema to receive the new Windows Server 2003 enhancements, including the addition of directory descriptors of certain objects. You should run this command before running the Adprep /domainprep tool on any of the domains. . /domainprep—Run this command on the infrastructure master of each domain to pre-
pare the Windows 2000 domain for upgrade to Windows Server 2003. It adjusts ACLs on Active Directory objects and on the Sysvol shared folder for proper access by Windows Server 2003 domain controllers.
What Is New in Windows Server 2003 Release 2 Active Directory? R2 Early in 2006, Microsoft introduced an interim upgrade to Windows Server 2003 known as Release 2, or R2. Built on the security improvements introduced in Service Pack 1 (SP1), R2 upgrades several important security and functionality features of Windows Server 2003, pending the release of the next Windows Server version, expected in late 2007.
31
What Is New in Windows Server 2003 Release 2 Active Directory?
Although Microsoft has not updated the 70-294 exam objectives to reflect the new components of R2, they might appear on exam questions related to the present objectives. Consequently, you should be familiar with these features. We introduce the following important Active Directory–related features here and describe these features in more detail at relevant locations in this study guide: . Security Configuration Wizard—Introduced with SP1, the Security Configuration
Wizard assists you in creating consistent security policies that can be applied to a series of servers. Policies created with the assistance of this wizard can be deployed using Group Policy to a site, domain, or OU. . Enhancements to ADAM—ADAM provides a storage location for directory-enabled
application data. Included is a setup wizard that enables you to create instances of ADAM along with associated application directory partitions. You can also create an ADAM administrator account in the configuration partition for administering the associated instance, and specify LDAP and Secure Socket Layer ports associated with this instance. Also included is an improved version of the LDAP editor tool (LDP) that includes the capability of accessing any LDAP server along with an ACL editor. ADAM also integrates with the low-level Active Directory Services Interfaces Editor (ADSI Edit) that enables you to view, edit, and delete Active Directory objects. See Chapter 2 for more information. . Active Directory Federation Services (ADFS)—ADFS provides a single sign-on
capability for authentication of users to multiple web-based applications. It facilitates the authentication of clients, suppliers, and partner company employees requiring access to web-based applications. ADFS securely shares credentials across enterprise borders, thereby eliminating the need to set up user accounts for these individuals. ADFS-based applications include a web agent that authenticates external users based on membership in groups created by the external organization for which you have specifically granted access. See Chapter 3 for more detail. . Services for UNIX—Provides password synchronization between Active Directory
servers and servers running UNIX Network Information Service, thereby enabling authentication across the two systems. . Improvements to Distributed File System (DFS)—DFS now includes two new
technologies that enable improved data (including Active Directory) replication across WANs. See Chapter 4 for more information: . DFS Namespaces—Enables you to present groups of folders located on different
servers as a virtual namespace tree. A new DFS Management snap-in facilitates management tasks and includes a wizard that simplifies the creation of new namespaces.
32
Chapter 1: Concepts of Windows Server 2003 Active Directory
EXAM ALERT Remember both terminologies The 70-294 exam might use the older FRS terminology. Understand that either term—FRS or DFS replication— might appear, and that they refer to the same feature.
. DFS Replication—Replaces Windows 2000 and
Windows Server 2003 File Replication Service (FRS), and provides improved multimaster replication across WANs. A new mechanism called remote differential compression (RDC) provides the capability of replicating only the changed portions of files, which can speed up Active Directory replication significantly.
. MMC version 3.0—Provides improved functionality for snap-ins written using .NET
APIs. An improved interface features an Actions pane that facilitates the performance of common tasks. Several new snap-ins, an improved Add/Remove Snap-in dialog box, and improved error-reporting capabilities have also been introduced. Automatically installed with Windows Server 2003 R2, you can also install MMC 3.0 on Windows XP Professional computers on which SP2 has been installed. MMC 3.0 will also be included in the upcoming Windows Vista release. For additional new features of R2, refer to What’s New in Windows Server 2003 R2 in the “Suggested Readings and Resources” section at the end of this chapter.
33
Chapter Summary
Chapter Summary In this chapter, we introduced you to the various concepts you should understand about Active Directory. We mentioned the shortcomings of the old Windows NT directory service and introduced the X.500 and LDAP building blocks on which Microsoft built Active Directory. We described the components of the Active Directory database, including the various objects and their attributes. Active Directory uses the LDAP distinguished name definitions, along with security identifiers (SIDs) and Globally Unique Identifiers (GUIDs) to identify every object uniquely. We introduced you to the series of Active Directory containers, including forests, trees, domains, and organizational units (OUs). We also introduced you to the schema and the global catalog, as well as the physical components of Active Directory, including sites and domain controllers. Specialized domain controllers (global catalog servers and the various operations masters) perform key operations that control the functionality of the domain and the forest. Finally, we summarized the most important new Windows Server 2003 Active Directory features that improve the functionality and ease the administration of domains and forests, as well as added features within R2.
Key Terms . Backup domain controller (BDC) . Container . Distinguished name (DN) . Domain . Domain controller . Domain name system (DNS) . Domain naming master . Flexible single-master operations (FSMO) . Forest . Functional level . Global catalog . Global catalog server . Globally Unique Identifier (GUID)
34
Chapter 1: Concepts of Windows Server 2003 Active Directory . Hierarchical . Infrastructure master . Lightweight Directory Access Protocol (LDAP) . Namespace . Object . Organizational unit (OU) . PDC emulator . Primary domain controller (PDC) . Relative distinguished name (RDN) . RID master . Schema . Schema master . Security identifier (SID) . Site . Tree . User Principal Name (UPN) . X.500
Suggested Readings and Resources 1. Microsoft Corporation. “Active Directory Collection.” http://technet2.microsoft.com/
WindowsServer/en/library/6f8a7c80-45fc-4916-80d9-16e6d46241f91033.mspx?mfr=true. 2. Microsoft Corporation. “What’s New in Windows Server 2003 R2.”
http://technet2.microsoft.com/WindowsServer/en/Library/f9d70026-ae8b-4969-87551ea1edc4e38e1033.mspx?mfr=true. 3. Microsoft Corporation. “Windows Server 2003 Active Directory.”
http://www.microsoft.com/windowsserver2003/technologies/directory/activedirectory/ default.mspx. 4. Microsoft Corporation. “Why Upgrade From Windows NT 4.0 to Windows Server
2003.” http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/ nt4townet.mspx.
2
CHAPTER TWO
Planning and Implementing an Active Directory Infrastructure Objectives This chapter covers the following Microsoft-specified objectives for the Planning and Implementing an Active Directory Infrastructure section of the Windows Server 2003 Active Directory Infrastructure exam:
Plan a strategy for placing global catalog servers . Evaluate network traffic considerations when placing global catalog servers. . Evaluate the need to enable universal group caching. . This objective is designed to ensure that you understand the importance of global catalog servers. To ensure that users can log on to Active Directory rapidly from any location, global catalog servers need to be available. In addition, universal group caching enables a user to log on without the need to contact a global catalog server after she has logged on previously to the same domain controller. You need to know the impact of global catalog servers on network traffic and how this traffic can be reduced by implementing universal group caching.
Plan flexible operations master role placement . Plan for business continuity of operations master roles. . Identify operations master role dependencies. . This objective evaluates your understanding of the importance of the operations master roles and what happens if one of them is not available. You need to understand what each operations master does and how to transfer these roles to other domain controllers.
Implement an Active Directory directory service forest and domain structure . Create the forest root domain. . Create a child domain. . Create and configure application data partitions. . Install and configure an Active Directory domain controller. . Set an Active Directory forest and a domain functional level based on requirements. . This objective ensures that you can create an Active Directory forest, including root and child domains, and raise its functional level to obtain the total benefits of an Active Directory implementation. You should keep in mind that installing Active Directory and installing a domain controller are one and the same. You should also understand the differences between installing child domains, installing additional trees in a forest, and installing additional domain controllers to an existing domain. You need to know when to raise your domain’s and forest’s functional level, and the benefits provided by doing so. In addition, you need to know how to create, manage, locate, and delete application directory partitions.
Outline Introduction Planning the Active Directory Namespace Subdividing the Active Directory Namespace Administrative or Geographical Organization of Domains
38
Domain Functional Levels
73
38
Forest Functional Levels and Requirements
74
39
Renaming Domains and Domain Controllers
77
Functional Levels Review
79
40
Use of Multiple Trees
41
Best Practices
41
Active Directory Namespace Review
Windows Server 2003 Functional Levels 73
43
Building an Active Directory Forest
43
Creating the Forest Root Domain
45
Sharing Active Directory Information Global Catalog Servers Evaluating Network Traffic Considerations When Placing Global Catalog Servers Universal Groups
81 82
83 84
53
Verifying Active Directory Installation
Evaluating the Need to Enable Universal Group Caching
85
53
Installing an Additional Domain Controller
Sharing Active Directory Information Review
87
55
Installing a Domain Controller from Backup Media
57
Active Directory Domain Controllers
87
67
Transferring Operations Master Roles
90
67
Using the Command Line to Transfer Operations Master Roles
93
Seizing Operations Master Roles
94
60
Uninstalling Active Directory
63
Application Directory Partitions
Creating Application Directory Partition Replicas
68
Application Directory Partition Reference Domains
69
Listing All Known Application Directory Partitions
69
Deleting Application Directory Partitions
70
Active Directory Application Mode (ADAM)
70
Upgrading Windows 2000 Domains and Forests Building an Active Directory Forest Summary
87
Business Continuity of Operations Master Roles
Creating Child Domains
Creating Application Directory Partitions
Placement of Flexible Operations Master Roles
Operations Master Role Dependencies
95
Operations Masters Review
98
Chapter Summary Key Terms Apply Your Knowledge
72 72
99 99 100
Exercises
100
Exam Questions
104
Answers to Exam Questions
110
Suggested Readings and Resources
113
Study Strategies This chapter covers how you set up Active Directory in various combinations of trees and domains. It also covers the management of global catalog servers and operations masters. You should understand how these components of Active Directory work together to keep your network functioning properly. In particular, you should pay attention to the following: . The different methods of installing domain controllers and how the installation procedure varies according to the logical creation point of each domain controller. . The benefits and requirements of the various domain and forest functional levels of Active Directory. . The functions of the global catalog servers and operations masters, and the problems that can occur if they are offline. You also need to know how to add global catalog servers and move operations master roles from one server to another.
38
Chapter 2: Planning and Implementing an Active Directory Infrastructure
Introduction In Chapter 1, “Concepts of Windows Server 2003 Active Directory,” we covered the basic building blocks of the logical Active Directory structure: forests, trees, domains, and organizational units (OUs). We also covered the concept of sites for distinguishing portions of the network separated physically by slow WAN links. The act of installing Active Directory on a server is conceptually very simple. You need only run the dcpromo.exe command and provide answers to the questions the wizard asks. Installing Active Directory is also simpler than installing a Windows NT 4.0 domain controller, for which you had to reinstall a server from scratch to promote a member server to domain controller or demote a domain controller to member server. The actual act of installing Active Directory, however, can be thought of as the tip of the iceberg. Before you install Active Directory, you need to plan how Active Directory will fit into your company’s corporate and geographical structure as well as your expectations for future growth and the potential for acquiring other companies. This chapter serves only as a basic introduction to the topic of planning.
Planning the Active Directory Namespace As we discussed in Chapter 1, the domain is the primary administrative unit within an Active Directory namespace. Windows Server 2003 uses the concept of domains to separate available resources among registered users. It is also the basic security unit, as you will see throughout this book, because many of the security requirements in Active Directory are focused at the domain level. Therefore, it is important to begin the process of planning any company’s Active Directory namespace from the viewpoint of the domain structure. All planning starts from the name of your company’s root domain. Recall in Chapter 1 that each tree has a root domain that is located at the top of the inverted tree structure. All subdomains contain this root domain name in their own domain name. In addition, the first domain in the entire forest is not only a root domain, but is also the forest root. Also, the top-level domain names used on the Internet and defined in the DNS hierarchy are included. The latter is not an absolute requirement if you are planning a domain that has no Internet representation whatsoever, but what company these days does not have a presence on the Internet? Therefore, it makes sense that your root domain can take the same name as your Internet domain name as registered with InterNIC (Internet Network Information Center). Consider a fictional company with an Internet domain name of company.biz. Although you can use this name as your Active Directory root domain name, it creates a risk of revealing your company’s Active Directory structure to the public Internet. Consequently, you might want to keep the internal name separate and use something like company.local for the Active Directory root domain name of the same fictional company.
39
Planning the Active Directory Namespace
Subdividing the Active Directory Namespace You can subdivide your namespace within Active Directory in two ways: . Separate domains . Organizational units (OUs)
In many instances, the use of separate domains or OUs would serve just as well as the other. In larger companies, the use of separate domains often arose from the limitations of the Security Accounts Manager (SAM) database in Windows NT. Because the Active Directory database can hold millions of objects, this limitation is seldom of importance in Active Directory design. For this reason, and because a single domain structure is the easiest type of structure to administer, this method is the best means of organizing your company’s namespace if possible. There is no specific need to create separate domains for administrative functions, geographical sites, or departments in the company. Logically, you can handle this function by setting up a system of OUs. An internal system of OUs provides the following additional advantages: . It can be administered either centrally or locally. The concept of delegation of control
in Active Directory facilitates the assignment of individuals as local administrators. . User authentication is simpler and faster within a single domain environment, regard-
less of where a user is located. . It is far simpler to modify when needed—for example, if your company is reorganized. . It is flexible and can include an internal hierarchy of departments, sections, work units,
and so on. There are, however, reasons for using separate domains for discrete divisions of your company: . This approach can facilitate decentralized administration of network resources. . In the case of multiple Internet domain names, the domain can be built to mirror the
Internet functionality. . Multiple domains representing different geographical locations might reduce the
amount of replication traffic across slow WAN links. . User account requirements that vary among departments or locations, such as pass-
word complexity, can be handled only by separate domains. . International legal and language needs might be handled more easily by using separate
domains. . Very massive organizations can be broken down into a domain structure.
40
Chapter 2: Planning and Implementing an Active Directory Infrastructure
Administrative or Geographical Organization of Domains You can organize a series of domains along either administrative or geographical means. For example, Figure 2.1 shows mycompany.com organized along three administrative divisions— Accounting, Products, and Advertising—all reporting to a Management group; contrasted with the company’s main offices located in San Francisco, Dallas, Toronto, and Atlanta.
Management
Accounting
Products
Advertising
Toronto
San Francisco Atlanta Dallas
FIGURE 2.1 Administrative and geographical divisions of mycompany.com.
You need to take into account conditions that favor either the administrative or geographical model. This can include the following factors: . Plans for future offices in additional cities . Projected growth of each of the company’s divisions . Potential for reorganization of the company along new departmental lines . Requirements for centralized or decentralized administration of the company . Needs for different security levels in either certain departments or certain offices . Current or future use of one or more Internet DNS namespaces
Such factors suggest the best domain organization for your company’s Active Directory namespace.
41
Planning the Active Directory Namespace
NOTE Plan Your Active Directory Deployment Carefully Due to the nature of Active Directory, the idea of domain planning is very different with Windows Server 2003 than it was with Windows NT 4.0. It is essential that you develop a tactical deployment plan before you begin. First, you must carefully evaluate the physical and administrative structure of the company. Then you will be in a position to decide on an administrative model and hence an appropriate domain structure. At the same time, be extremely careful and thorough in making your choice. It is far easier to create new OUs and move objects to them than to do the same with domains. Although you can rename a domain in Windows Server 2003 Active Directory, this process can be problematic and disruptive to proper network communication.
Use of Multiple Trees Within the Active Directory forest, you may have one or more trees. As outlined in Chapter 1, the main difference between trees and forests is that domains within a tree share a contiguous namespace, whereas domains located in different trees in the same forest have a disjointed namespace. Thus, quepublishing.com and examcram.com are root domains in two separate trees of the same forest. In almost all multiple domain enterprises, it makes sense to employ a single tree. The major exception occurs when two companies merge and want to maintain their separate identities. Their identities, and indeed their Internet namespaces, are best served by having more than one tree in the forest.
NOTE The Empty Forest Root Domain Another way of designing a multidomain forest is to employ an empty forest root domain, with a series of child domains representing administrative or geographical divisions of the company. The root domain contains only a small number of objects, and you can readily control membership in the Enterprise Admins and Schema Admins groups. The impact of business decisions such as the spin-off or renaming of subsidiary companies can be handled more readily. On the other hand, you must ensure that the forest root domain controllers are carefully secured and protected against disaster because their loss effectively destroys the entire forest structure.
Best Practices Planning the Active Directory domain structure is an act that has far-reaching implications. This process is something that cannot simply be decided by a few network administrators sitting down with a few diagrams of the network and company business structures. Rather, it must involve the company’s senior and middle management as well as business strategy specialists and representatives from remote offices. If you use internally developed applications,
42
Chapter 2: Planning and Implementing an Active Directory Infrastructure
representatives of the development team should be involved. The following several guidelines will help you make your Active Directory implementation proceed smoothly: . Know everything there is to know about the network—Although this guideline
might sound intuitive for senior administrators who have built the network from the ground up, those who have come on the scene more recently need to gather information about everything that must be accounted for in an Active Directory plan. . Employ a test lab—The lab should contain representative domain controllers, mem-
ber servers, and client computers. Set up a mini-version of your complete network and engage the assistance of a representative set of users to test all facets of the implementation thoroughly. . Prepare thorough documentation—This point can never be understated. Use tools
such as Microsoft Visio to prepare diagrams of different levels of company detail, from the major administrative units down to the smallest workgroups. Visio is a tool that is specifically designed for preparing administrative diagrams such as those required in this scenario. This exercise also helps in optimizing communication between technical individuals and top management. . Use an email distribution list to keep everyone informed—When all concerned
individuals have full access to the latest developments, unpleasant surprises are minimized. . Keep all employees informed—Although the regular workers might not understand
the details of what is happening, they should be informed of the summary points of any planned changes. They will then be much more able to cope with the changes. In addition, they could provide valuable feedback. . Ensure that all top managers know what’s happening—This point also can never
be understated. This helps prevent unpleasant surprises and the need to redo portions of the planning process. . Understand thoroughly the network’s TCP/IP infrastructure—Your under-
standing helps in designing the network and DNS configuration that is the foundation of the Active Directory infrastructure. It is especially true in developing the proper site structure, as will be discussed in Chapter 3, “Managing an Active Directory Infrastructure.” . Develop and adhere to an adequate security policy—Thoroughly review any secu-
rity policy that your company already has in place. Apply the policy’s constraints to the proper design of your company’s domain structure. Make any appropriate changes as you develop the Active Directory infrastructure.
43
Building an Active Directory Forest . Know the capabilities of your WAN links—If your network includes slow WAN
links, test and monitor the use of these links before and during the Active Directory implementation to ensure that you have the optimum configuration.
Active Directory Namespace Review Following are the key aspects involved in planning an Active Directory namespace from the viewpoint of the domain structure: . You can use either subdomains or OUs to subdivide your Active Directory namespace.
Although employing OUs in a large domain is simple, you might want to employ more than one domain for several reasons. . Two common means of organizing a series of domains are administrative and
geographical. . It is essential to plan the Active Directory structure thoroughly before starting any
kind of implementation. Keep everyone informed at all stages of the process.
Building an Active Directory Forest After you have created a comprehensive plan for your organization’s Active Directory structure, you are almost ready to install Active Directory. The first task that you must perform is to install the first domain controller for the forest root domain. You need to understand and realize several points before you actually start the process of installing Active Directory. First, the computer on which you install Active Directory must meet the following requirements: . Operating system—The computer must be running Windows Server 2003 Standard
Edition, Enterprise Edition, or Datacenter Edition. Note that a server running Windows Server 2003 Web Edition cannot be promoted to a domain controller. . Hard disk space—The computer must have a minimum of 200MB of disk space for
the Active Directory database, plus at least 50MB of disk space for the transaction log files, and additional space if it is a global catalog server. As the number of objects in Active Directory grows, the required disk space increases rapidly. The recommended minimum disk space is 1GB. It is wise to plan for this requirement in advance according to your network’s current and future anticipated size. . A disk volume formatted with the NTFS file system—Not only is having such a
volume recommended for file security, but it is also required for the SYSVOL folder. If this is not available, Active Directory installation cannot start.
44
Chapter 2: Planning and Implementing an Active Directory Infrastructure
NOTE Use of a Fault-Tolerant Disk Volume It is highly recommended that you use a fault-tolerant disk volume such as RAID-1 (disk mirroring) or RAID-5 (disk striping with parity) to hold the Active Directory database, log files, and SYSVOL folders. This enables the domain controller to continue functioning in the event of a disk failure until you are able to shut the server down to replace the failed disk. But remember that fault tolerance is no substitute for regular backups. We discuss backup and restore of domain controllers in Chapter 4, “Maintaining an Active Directory Infrastructure.”
. A DNS server—You must have available a DNS server that supports service (SRV)
resource records and the dynamic update protocol. This can be a Windows 2000, Windows Server 2003, or Berkeley Internet Name Domain (BIND) 4.9.7 or higher server. BIND versions 8.2.1 and higher provide complete Active Directory functionality. It need not be on the same server as the intended domain controller, but it should be if you want to integrate the DNS database with Active Directory. If an appropriate DNS server is not available, you will be prompted to install one during the Active Directory installation. . Administrative privileges—You must be using an account with the appropriate
administrative privileges for creating a domain on an existing Windows Server 2003 network. For creating the first domain controller, you must be logged on as a local administrator on the standalone server. To add a domain to a forest, you must be logged on as a member of the Enterprise Admins group, and to add a domain controller to an existing domain, you must be logged on as a member of the Domain Admins or Enterprise Admins group.
Active Directory and UNIX DNS Many companies have operated UNIX-based DNS servers in recent years. These servers have cooperated well with networks that run Windows NT, but with the advent of Active Directory in Windows 2000 and now Windows Server 2003, DNS has become elevated to a pivotal role. The popularity of UNIX-based DNS servers traces back to the beginnings of the Internet and the need for an automated naming service that could translate domain names to IP addresses and did not require continual manual updates, as the original system of HOSTS files did. The first DNS implementations were hosted on UNIX servers. They employed the Berkeley Internet Name Domain, which was developed at the University of California in Berkeley. A series of updates to BIND followed, each adding new features to DNS. BIND versions 4.9.7 and later allow SRV resource locator records, and versions 8.1.2 and later allow dynamic updating. As you have learned here, the Active Directory Installation Wizard installs DNS if a suitable DNS server is not available on the network. However, many companies have found that the wizard asks to install DNS despite the presence of a UNIX-based DNS server on the network. (continues)
45
Building an Active Directory Forest (continued)
What is the reason for this? It lies in the BIND version, as explained here, because Active Directory requires the ability to create SRV resource records. Although it is not required, the ability to support dynamic DNS is highly desirable. Therefore, you need to update the BIND version to 4.9.7 or later to be able to use the UNIX DNS server with Active Directory, and you should update to version 8.2.1 or later for full capabilities.
In addition, you should also be aware of the following changes that are made when you upgrade a server to a domain controller: . Local user and group accounts are deleted—Because all user and group account
information is stored in Active Directory, accounts contained within the standalone server’s SAM database are deleted. You must create domain user accounts that embody the privileges of the existing user accounts. The only exception is for the first domain controller in a domain; its local user accounts are migrated to the Users container in Active Directory. Before starting to install Active Directory, make sure that you have enumerated the existing accounts and their permissions so that you can re-create them later. . Permissions on resources are reset—Because the accounts no longer exist, neither
do the permissions granted to them. Therefore, all permissions revert to Everyone, Read, and will have to be reconfigured after new domain accounts have been created. . Encryption keys are lost—If you have encrypted data using the Encrypting File
System (EFS), you should decrypt these files before installing Active Directory, or at least export the cryptographic keys. These files will otherwise become unreadable. You can always re-encrypt the files later.
Creating the Forest Root Domain Objective:
Implement an Active Directory directory service forest and domain structure . Create the forest root domain
Microsoft has provided the Active Directory Installation Wizard with the capabilities of installing domain controllers under all conceivable scenarios. This wizard can perform the following tasks: . Create a new forest . Create a new domain tree . Create the first domain controller in a new domain
46
Chapter 2: Planning and Implementing an Active Directory Infrastructure . Create additional domain controllers for an existing domain . Install a DNS server if a suitable DNS server is not available . Create the Active Directory database and log files . Create the shared system volume, SYSVOL . Remove Active Directory services
The options presented by the Active Directory Installation Wizard depend on whether you are creating a new forest, a new tree in an existing forest, a new domain in an existing tree, or a new child domain. The additional options are covered in the “Installing an Additional Domain Controller,” “Creating Child Domains,” “Installing a Domain Controller from Backup Media,” and “Uninstalling Active Directory” sections of this chapter. Step by Step 2.1 outlines the procedure for creating the first domain controller in a new forest.
STEP BY STEP 2.1 Installing the First Domain Controller 1. Start the Active Directory Installation Wizard. You can do this by clicking Start, Run, typing dcpromo, and pressing the Enter key. You can also do this by clicking Start, Administrative Tools, Manage Your Server. This procedure displays the Manage Your Server dialog box, as shown in Figure 2.2.
Starting the Active Directory Installation Wizard from the Manage Your Server dialog box.
FIGURE 2.2
2. If you are using Manage Your Server, click Add or Remove a Role, and in the Configure Your Server Wizard page that appears, verify that you have performed the listed steps. Then click Next and perform the following steps:
47
Building an Active Directory Forest . The wizard tests your network settings and then displays a Server Role page. Select Domain Controller (Active Directory) and click Next. . On the Summary of Selections page, review the options and click Next to start the Active Directory Installation Wizard. 3. The Active Directory Installation Wizard displays a Welcome page. Click Next. 4. The Operating System Compatibility page, shown in Figure 2.3, informs you that improved Windows Server 2003 security settings affect how older versions of Windows communicate with the domain controller. Windows 95 and NT 4.0 Service Pack 3 and earlier cannot meet the new requirements and therefore cannot log on to a Windows Server 2003 domain controller. Click Next.
You are informed about security settings that prevent some older Windows clients or non-Windows systems from logging on to the Windows Server 2003 domain controller.
FIGURE 2.3
5. On the Domain Controller Type page, ensure that Domain Controller for a New Domain is selected and then click Next (see Figure 2.4).
FIGURE 2.4
Creating a new domain.
48
Chapter 2: Planning and Implementing an Active Directory Infrastructure 6. On the Create New Domain page, select Domain in a New Forest to create the first domain in a new forest and then click Next (see Figure 2.5).
FIGURE 2.5
Creating a new forest.
7. On the New Domain Name page, type the full DNS name of the new domain to be created (for example, quepublishing.com) in the text box provided and then click Next (see Figure 2.6).
Specifying the new domain name.
FIGURE 2.6
8. The NetBIOS Domain Name page should display the most qualified (first) part of the domain name (for example, QUEPUBLISHING), as shown in Figure 2.7. This name is used by down-level clients, such as Windows 98 or NT 4.0, to connect to the domain controller. Accept this or type a different name, and then click Next. This name must be unique to the entire Active Directory forest. You generally should accept this name unless you have a good reason to do otherwise.
49
Building an Active Directory Forest
Specifying the NetBIOS name of the domain.
FIGURE 2.7
9. The Database and Log Folders page, shown in Figure 2.8, displays the default locations of these folders. You might want to move one of these folders to a different physical drive for improved performance. Click Next when you are ready.
Specifying the locations of the database and log files.
FIGURE 2.8
10. The Shared System Volume page, shown in Figure 2.9, displays the default location of the SYSVOL folder. You might want to move this folder to a different drive for improved performance. It must be placed on an NTFS-formatted partition. Click Next when you are ready.
50
Chapter 2: Planning and Implementing an Active Directory Infrastructure
Specifying the location of the SYSVOL folder.
FIGURE 2.9
11. The wizard searches for a DNS installation and then displays the DNS Registration Diagnostics page. If it does not find an appropriate DNS server, the wizard offers to install DNS on the domain controller, as shown in Figure 2.10. You should accept this option and then click Next.
FIGURE 2.10 Specifying the installation of DNS on the new domain controller.
NOTE Using an Existing DNS Server If you are using an existing DNS server, you should ensure that the server you are promoting is configured with the address of the DNS server before you run dcpromo.
12. The Permissions page offers a selection between two permissions levels. If you are operating Windows NT 4.0 Remote Access Service (RAS) servers on the network, you need to select the weaker security level, which is represented by the Permissions Compatible with Pre-Windows 2000 Server Operating Systems option, so that they authenticate properly to the domain controller. Otherwise, leave the default
51
Building an Active Directory Forest option of Permissions Compatible Only with Windows 2000 or Windows Server 2003 Operating Systems selected, as shown in Figure 2.11. Then click Next.
FIGURE 2.11
Specifying security
permissions.
WARNING Security Risk Selecting the Pre-Windows 2000 Servers option presents a security risk. Selecting this option adds the Everyone group to the Pre-Windows 2000 Compatible Access group. As a result, everyone, whether authenticated or not, can read any property of any user or group account in the directory. The best option is to upgrade the RAS servers to Windows 2000 or Windows Server 2003.
13. The Directory Services Restore Mode Administrator Password page, shown in Figure 2.12, asks for the password used to start the domain controller in the Directory Services Restore Mode. Type and confirm a suitable password and then click Next.
FIGURE 2.12 Specifying the Directory Services Restore Mode Administrator password.
52
Chapter 2: Planning and Implementing an Active Directory Infrastructure
WARNING Use a Secure Password You should use a hard-to-guess password that includes a mix of upper- and lowercase letters, numerals, and punctuation characters. Be sure to write down this password and store it in a secured location, such as a locked drawer or cabinet where you keep backup tapes. The local Administrator account uses this password to log on to this computer when it is started in Directory Services Restore Mode. This is a special mode used for restore operations and for certain maintenance options, such as defragmenting the database file or moving it to another location. This account is the only local account that will exist after Active Directory installation is complete. See Chapter 4 for more details.
14. The Summary page displays a summary of the options you have configured. If any option is incorrect, click Back to correct it; click Next to install Active Directory. 15. The Active Directory Installation Wizard displays a progress page as it installs and configures DNS and Active Directory (see Figure 2.13). If it asks you for the Windows Server 2003 CD-ROM, insert it and click OK.
FIGURE 2.13
Installing Active Directory.
16. When installation of Active Directory is complete, the wizard displays a completion page. Click Finish. 17. You are told you must restart the computer to complete the Active Directory installation. Click Restart Now to restart the computer.
EXAM ALERT Placing the Database and Log Folders The purpose of placing the database and log folders on a separate drive from the SYSVOL folder is only to improve I/O performance. Such an act does not improve on security or fault tolerance, as an exam question might lead you to believe. Installing Active Directory You should be aware of the prerequisites that must be satisfied before you can install Active Directory. They include the differences between installing the first or additional domain controllers, new trees, and child domains. You might have to follow the proper installation steps in a simulation question on the exam. Remember that you need an NTFS partition to hold the SYSVOL folder, and remember that DNS must be available and support SRV resource records and (preferably) dynamic updates.
53
Building an Active Directory Forest
Active Directory Domain Controllers Objective:
Implement an Active Directory directory service forest and domain structure . Install and configure an Active Directory domain controller
After you have installed the first domain controller in your forest, you should perform the following additional tasks: . Verify the initial configuration of the first domain controller—Problems in Active
Directory installation usually show up as error messages during the installation process. However, occasional problems do not manifest themselves in this way; if not corrected, they could lead to more serious trouble at a later stage. . Verify the proper configuration of the DNS server—If the DNS server has not
been properly installed, many errors could occur at later stages, including the inability to contact the first domain controller when installing additional domain controllers or child domains. Users might also have difficulty logging on or accessing domain resources. . Install one or more additional domain controllers—To provide redundancy and
fault tolerance, you should install at least one additional domain controller. For a domain that spans large numbers of users and physical sites, additional domain controllers are necessary, including at least one at each additional site.
Verifying Active Directory Installation After you have installed Active Directory, you should take several steps to verify the installation. Step by Step 2.2 outlines several steps you should take to ensure the proper installation of Active Directory.
STEP BY STEP 2.2 Verifying Active Directory Installation 1. Click Start, Administrative Tools. As shown in Figure 2.14, Active Directory installation should include three default MMC snap-ins, which include the following: . Active Directory Domains and Trusts—Manages trust relationships with other forests and with Windows NT 4.0 domains . Active Directory Sites and Services—Manages Active Directory sites and replication . Active Directory Users and Computers—Manages users, groups, OUs, and computers in the domain, including Group Policy
54
Chapter 2: Planning and Implementing an Active Directory Infrastructure
FIGURE 2.14 Three snap-ins for managing Active Directory should appear at the top of the Administrative Tools folder.
2. Open Active Directory Users and Computers. Expand your domain name and ensure that the following containers are present: Computers, Users, and ForeignSecurityPrincipals. A Domain Controllers OU should also be present. 3. Select the Domain Controllers OU. An account with the name of the server should appear in the details pane, as shown in Figure 2.15.
FIGURE 2.15 A computer account for your new domain controller should appear in Active Directory Users and Computers.
55
Building an Active Directory Forest 4. The Administrative Tools folder should also contain a link to the DNS snap-in. Click this link to open the DNS snap-in. 5. Expand the server to reveal a link to Event Viewer as well as forward and reverse lookup zones, and then expand the forward lookup zone. You should see two folders for your domain name, one of them prefixed with _msdcs. Each contains several subfolders. 6. Look for SRV resource records in the _tcp and _udp nodes. If they are not present, wait a few minutes and refresh the display. If they are still not present, right-click the zone name and choose Properties. As Figure 2.16 shows, an Active Directory–integrated zone should exist, and the Dynamic Updates list should read Secure only. If not, change these values and then restart the Netlogon service to force the SRV resource records to be re-registered.
FIGURE 2.16 The zone Properties dialog box should indicate secure dynamic updates and an Active Directory–integrated zone.
7. After you have verified these records, close the DNS snap-in. 8. Click Start, My Computer, and navigate to the system root folder (usually C:\Windows). Verify that the NTDS (Active Directory database) and SYSVOL (shared system volume) folders are present. If you specified another location while running the Active Directory Installation Wizard, navigate to that location.
Installing an Additional Domain Controller Having installed and verified the first domain controller in the new forest, you should next install an additional domain controller in the same domain. You need a computer running any edition of Windows Server 2003 except the Web edition, and the server should first become a
56
Chapter 2: Planning and Implementing an Active Directory Infrastructure
member server in the domain in which it will be a domain controller. You also need to use an account with Domain Admins or Enterprise Admins membership. The procedure for installing the second domain controller is quite straightforward, as Step by Step 2.3 shows.
STEP BY STEP 2.3 Installing a Second Domain Controller 1. Click Start, Run, type dcpromo, and press Enter. You can also use the Manage Your Server Wizard, as described in Step by Step 2.1. 2. Click Next twice to bypass the Welcome page and the Operating System Compatibility page of the Active Directory Installation Wizard. 3. On the Domain Controller Type page, select Additional Domain Controller for an Existing Domain and then click Next. 4. The Network Credentials page asks for the username and password of an account with administrative privileges in the domain. If the computer is already configured as a member server in the domain, the domain name should appear, as shown in Figure 2.17; otherwise, type it in. Then click Next.
FIGURE 2.17 You need to supply credentials for an administrator account in the domain in which you are creating an additional domain controller.
5. The Additional Domain Controller page displays the name of the domain for which the server will become an additional domain controller, as shown in Figure 2.18. If this name is incorrect, type it or click Browse to locate the proper domain. Then click Next.
57
Building an Active Directory Forest
FIGURE 2.18 Specifying the domain in which you are making an additional domain controller.
6. Confirm or modify the locations of the Active Directory database and log files and then click Next. 7. Confirm or modify the location of the SYSVOL folder and then click Next. 8. Type and confirm the directory services restore mode administrator password and then click Next. 9. Review the information presented on the Summary page. If anything is incorrect, click Back. Otherwise, click Next to begin installing Active Directory. 10. When the completion page appears, click Finish and restart your computer as directed.
After you have completed installing each additional domain controller, you should verify the installation as described in Step by Step 2.2, except for the DNS step. DNS is not automatically installed on an additional domain controller. If you need DNS on the additional domain controller, you should use the Manage Your Server Wizard or Control Panel Add or Remove Programs to install it.
EXAM ALERT DNS Is Assumed to Exist You might see a tricky exam question that asks you to troubleshoot a DNS problem occurring during installation of another domain controller. Not only does dcpromo not install DNS when installing an additional domain controller, Active Directory does not even check that the DNS server is present and functioning. The system assumes that the presence of a DNS server was established when the first domain controller was installed.
Installing a Domain Controller from Backup Media The Active Directory Installation Wizard provides an Install from Media option that enables you to perform a domain controller installation using a system state backup from another
58
Chapter 2: Planning and Implementing an Active Directory Infrastructure
domain controller in the same domain as a source of Active Directory information. The Install from Media feature provides the following advantages: . Less time required to copy domain and global catalog information to the new domain
controller. . Less network traffic during domain controller promotion. . Less time required for recovery of a failed domain controller.
To install a new domain controller from media, first perform a system state backup of an existing domain controller in the same domain. Refer to Chapter 4, Step by Step 4.12, “Backing Up System State Data,” for instructions. You then restore this backup to the server you want to promote, and run the Active Directory Installation Wizard using the /adv option. Step by Step 2.4 shows you how:
STEP BY STEP 2.4 Installing a Domain Controller from Media 1. Log on to the server to be promoted as a member of the local Administrators group. 2. Click Start, Run, type ntbackup, and press Enter. 3. On the welcome page of the Backup or Restore Wizard, click Advanced Mode. 4. Select the Restore and Manage Media tab. 5. From the Tools menu, select Catalog a Backup File, type or browse to the location of the system state backup you have created, and then click OK. As shown in Figure 2.19, you can specify a network location.
FIGURE 2.19
be restored.
Locating the backup file to
59
Building an Active Directory Forest 6. The backup is added to the left pane of the backup window. Expand this entry to locate and select the system state backup. 7. From the Restore files to drop-down list, select Alternate location and then specify C:\Ntdsrestore in the Alternate location text box, as shown in Figure 2.20. Click Start Restore.
FIGURE 2.20 You will need to restore system state to an alternate location.
8. Click OK to accept the warning that not all system state data will be restored to the alternate location and then click OK again to perform the restore. 9. When the restore is completed, click Close and then close the Backup Utility dialog box. 10. Click Start, Run, type dcpromo /adv, and press Enter. 11. Click Next twice to bypass the Welcome page and the Operating System Compatibility page of the Active Directory Installation Wizard. 12. On the Domain Controller Type page, select Additional Domain Controller for an Existing Domain and then click Next. 13. On the Copying Domain Information page shown in Figure 2.21, select the location to which you restored the backup files. If necessary, click Browse to locate the backup files. Then click Next.
60
Chapter 2: Planning and Implementing an Active Directory Infrastructure
FIGURE 2.21 The Copying Domain Information page enables you to choose whether to copy information across the network or from restored backup files.
14. If the restored backup files were from a domain controller configured as a global catalog server, the Global Catalog page asks whether you want to configure the new domain controller as a global catalog. Click Yes or No as required and then click Next. 15. On the Network Credentials page, type the name and password of an account with domain administrative privileges and then click Next. 16. Follow steps 6 to 10 of Step by Step 2.3 to complete installation of the domain controller.
NOTE Use Dcpromo /adv to Create a Domain Controller at a Remote Site If you need to install a domain controller at a remote site connected to the rest of the network by a slow WAN link, using Dcpromo /adv reduces the time required to create the domain controller because it avoids the transfer of a large quantity of Active Directory data across the slow link.
Creating Child Domains Objective
Implement an Active Directory directory service forest and domain structure . Create a child domain
In building an Active Directory tree structure, you will encounter the need to create child domains in the same tree. The procedure, which is similar to that of creating a forest root domain, is outlined in Step by Step 2.5.
61
Building an Active Directory Forest
STEP BY STEP 2.5 Creating a Child Domain 1. Click Start, Run, type dcpromo, and press Enter. You can also use the Manage Your Server Wizard, as described in Step by Step 2.1. 2. Click Next twice to bypass the Welcome page and the Operating System Compatibility page of the Active Directory Installation Wizard. 3. On the Domain Controller Type page, ensure that Domain Controller for a New Domain is selected and then click Next. 4. On the Create New Domain page, select Child Domain in an Existing Domain Tree and then click Next. 5. On the Network Credentials page, type the name and password of an administrator account in the parent domain. If the domain name does not appear, type it and then click Next. 6. On the Child Domain Installation page, type the names of the parent and child domains in the text boxes provided and then click Next. These names are combined to produce the complete DNS name of the child domain, which is also displayed as shown in Figure 2.22.
FIGURE 2.22
Specifying the name of the
child domain.
7. The NetBIOS Domain Name page displays the NetBIOS name used by down-level Windows clients to connect to the new domain. This name must be unique within the entire forest. Accept this name or type a different name, and then click Next.
NOTE Remember That Each Domain Must Have a Unique NetBIOS Name If the NetBIOS Domain Name page displays the name of the parent domain, you must overtype this name with a unique name such as the first part of the child domain name you specified in step 6.
62
Chapter 2: Planning and Implementing an Active Directory Infrastructure 8. Confirm or modify the locations of the Active Directory database and log files and then click Next. 9. Confirm or modify the location of the SYSVOL folder and then click Next. 10. As shown in Figure 2.23, the DNS Registration Diagnostics page verifies the existence of a DNS server on the parent domain controller, if available. Otherwise, it informs you that you need to install DNS on this server, as shown previously in Figure 2.10. If so, accept the option to install DNS and then click Next.
WARNING Remember That Each Domain Must Have a Properly Functioning DNS Server If you select the I Will Correct the Problem Later by Configuring DNS Manually (Advanced) option in Figure 2.10, make very sure that you install, configure, and test DNS on the appropriate server immediately after completing the domain controller installation. Improper DNS configuration is the source of many problems with Active Directory.
FIGURE 2.23
Confirming the availability of
a DNS server.
11. The Permissions page offers a choice of default permissions, as explained previously and shown in Figure 2.11. Unless you have a specific need to do otherwise (such as using Windows NT 4.0 RAS servers), accept the default of Permissions Compatible Only with Windows 2000 or Windows Server 2003 Operating Systems, and then click Next. 12. Type and confirm a Directory Services Restore Mode Administrator password and then click Next. 13. Review the information on the Summary page. If necessary, click Back to make any needed corrections. Then click Next to install Active Directory. 14. When the Completing the Active Directory Installation Wizard page appears, click Finish and then restart the computer.
63
Building an Active Directory Forest
Again, you should verify proper installation of Active Directory and install at least one additional domain controller for your new child domain. Another similar option that you might encounter in building your Active Directory infrastructure is that of creating a new domain tree in the same forest. The procedure for doing so is similar to that of Step by Step 2.4, except that on the Create New Domain page (shown previously in Figure 2.5), you select the Domain Tree in an Existing Forest option.
The Test Lab Last year, a major auto parts manufacturer realized that its Windows NT 4.0 network was not handling its increasing business demands in an optimal fashion. Orders were delayed and customers were starting to turn to competitors. Knowing that Windows Server 2003 would soon appear on the horizon, the domain administrators formulated a plan and presented it to the company’s management, obtaining approval to upgrade the company’s domain controllers and member servers to the new operating system. One weekend, the administrators introduced two new domain controllers to the network and upgraded it to Windows Server 2003 domain functional level. They moved user and computer accounts onto the new servers and had everything ready for Monday morning, or so they thought. Monday came, no users could log on, no one could access anything on the network, orders had to be taken by hand, and frustration mounted. Quickly, the senior domain administrator re-installed a Windows NT 4.0 PDC and restored the domain database from a backup tape. Soon the network returned to a semblance of normalcy, but only after hours of delay and without any new improvements. Meeting the next day to discuss what went wrong, the different administrators had varying opinions. The realization was there, however, that they hadn’t tested the implementation properly. One of the administrators had suggested doing a test lab a few months before, but management had declined his idea. Now it came up again and management was more accepting. The company created a team consisting of several network administrators, a manager, and a few computer-savvy users. They built an Active Directory network in the test lab with servers and client computers that were representative of what the employees used, installed all the company’s applications, and tested everything thoroughly. As errors occurred, the team sought out the causes and implemented corrections. They found out that two important applications needed improvements to run in the Active Directory environment. After they had completed all this testing, they were in a far better position to implement Active Directory on their production network, and the next attempt succeeded smoothly, with only a few minor glitches that were quickly remedied.
Uninstalling Active Directory On some occasions you might want to uninstall Active Directory. Some of these situations include the need to upgrade to a more powerful server or to undo a serious configuration
64
Chapter 2: Planning and Implementing an Active Directory Infrastructure
problem. You can uninstall Active Directory by running dcpromo on a domain controller, should you need to demote it to a member server for any reason. Follow Step by Step 2.6 to demote a domain controller.
STEP BY STEP 2.6 Demoting a Domain Controller 1. Click Start, Run, type dcpromo, and press Enter. 2. Click Next to bypass the Welcome page of the Active Directory Installation Wizard. 3. The Remove Active Directory page, shown in Figure 2.24, informs you that removing Active Directory converts the domain controller to a member server. If the domain controller is the last domain controller in the domain, select the check box labeled This Server is the Last Domain Controller in the Domain. Then click Next.
FIGURE 2.24 The Remove Active Directory page summarizes what happens when you remove the last domain controller in the domain.
4. If the server holds the last replica of any application directory partitions, the Application Directory Partitions page informs you (see Figure 2.25). Click Next to enable the wizard to remove application partitions.
65
Building an Active Directory Forest
FIGURE 2.25 You are informed of the application directory partitions that will be deleted.
5. The Confirm Deletion page informs you that all application directory partitions will be deleted. Select the check box labeled Delete All Application Directory Partitions on This Domain Controller and then click Next. 6. The Administrator Password page asks for a password to be assigned to the new local administrator account. Type and confirm a suitable password and then click Next. 7. The Summary page presents a summary of actions you have performed (see Figure 2.26). Review the information presented and click Back if you need to make any changes. Click Next to begin the demotion.
FIGURE 2.26 The Summary page provides a summary of what will happen when you demote the server.
8. Active Directory charts the progress of domain controller demotion and displays a completion page when the process is done. Click Next and restart the computer.
66
Chapter 2: Planning and Implementing an Active Directory Infrastructure
Challenge You are a network administrator for a company named Example, Inc. Your company operates an Active Directory network with a single forest named example.com. Your user account is a member of the Enterprise Administrators group, your username is JohnD, and your password is Tr64Ys5. Example acquires another company named Samples. Samples does not have an Active Directory domain, but you must create a new domain, which will be named Samples.com. The new domain must share a common schema with the existing domain. Samples has their own IT staff, which will continue to manage their own resources and users. You need to create a domain for Samples that will fulfill these requirements. Try to work through this exercise on your own. If you have difficulty, refer to the steps that follow: 1. Log on to the server to be promoted as an administrator. 2. Click Start, Run, type dcpromo, and then press Enter. 3. Click Next to bypass the introductory page of the Active Directory Installation Wizard, and then click Next again to bypass the Operating System Compatibility page. 4. On the Domain Controller Type page, select Domain Controller for a New Domain and then click Next. 5. On the Create New Domain page, select Domain Tree in an Existing Forest and then click Next. 6. On the Network Credentials page, type JohnD as your username and Tr64Ys5 as your password. Click Next. 7. On the New Domain Tree page, type samples.com and then click Next. 8. On the NetBIOS Domain Name page, accept the default of SAMPLES and then click Next. 9. Click Next twice to accept the default locations for the database and log folders and the SYSVOL shared folder. 10. On the DNS Registration Diagnostics page, ensure that the option to install and configure DNS is selected and then click Next. 11. On the Permissions page, accept the default option and then click Next. 12. Type and confirm a restore mode password and then click Next. 13. On the Summary page, review the options and then click Next to begin Active Directory installation. 14. When informed that active Directory installation is complete, click Finish and then click Restart Now to restart the server.
67
Building an Active Directory Forest
Application Directory Partitions Objective
Implement an Active Directory directory service forest and domain structure . Create and configure application data partitions
An application directory partition (also simply called an application partition) is a new feature of Windows Server 2003 that contains application-specific data that needs to be replicated to only specific domain controllers in one or more domains of the Active Directory forest. DNS stores its Active Directory integrated zone data in an application directory partition. Services such as the Telephony Application Programming Interface (TAPI) can also store their data in an application partition. These programs and services usually create their own application directory partitions as required. By utilizing application directory partitions, Active Directory replicates their data to other domain controllers in the forest. A benefit of application directory partitions is that their data can be replicated to only specific domain controllers, as opposed to domain partitions, which are replicated to all domain controllers in the domain. Consequently, replication traffic is reduced. For example, DNS application directory partitions are replicated to only those domain controllers running DNS. The same application directory partition can replicate to domain controllers in more than one domain in the forest.
Creating Application Directory Partitions Developers can use the Active Directory Services Interface (ADSI) to create application directory partitions in which their programs can store data. This means of creating application directory partitions is beyond the scope of this study guide. Interested readers can find details on the Microsoft website. Here, we discuss the use of the ntdsutil command-line utility for creating and managing application directory partitions. This utility is used to perform Active Directory maintenance operations from the command line. We discuss additional uses of ntdsutil in Chapter 4. An application directory partition is identified by its LDAP distinguished name (DN). For example, you could create an application partition named app on the quepublishing.com domain by using the DN dc=app,dc=quepublishing,dc=com. Step by Step 2.7 outlines the procedure for using ntdsutil for creating an application directory partition.
68
Chapter 2: Planning and Implementing an Active Directory Infrastructure
STEP BY STEP 2.7 Creating an Application Directory Partition 1. Log on to a domain controller or member server as a member of the Domain Admins or Enterprise Admins group. 2. Open a command prompt and type ntdsutil. This command starts the ntdsutil command-line utility and displays an ntdsutil command prompt. 3. At this prompt, type domain management. 4. At the domain management prompt, type connection. 5. At the connection prompt, type connect to server <server>, where <server> is the name of the domain controller to which you want to connect. 6. Type quit to return to the domain management prompt. 7. At this prompt, type create nc
<domain_controller>, where is the DN of the application directory partition you want to create, and <domain_controller> is the name of the domain controller on which you want to create the partition. Type null to create the application directory partition on the current domain controller. 8. You receive a prompt informing you that the object was added to the directory, as shown in Figure 2.27. Type quit twice to exit the ntdsutil utility.
FIGURE 2.27
Creating an application directory partition.
Creating Application Directory Partition Replicas The previous procedure creates an application partition on the indicated domain controller only. To replicate the partition to other domain controllers in the domain or forest, you need to create an application directory partition replica. In this manner, you can control the set of domain controllers among which the partition is replicated.
69
Building an Active Directory Forest
The procedure for creating a replica is the same as that for creating the application directory partition, as outlined in Step by Step 2.7, except that at step 7, you need to type add nc replica <domain_controller>. The DN you specify should be the same as that of the partition you have created, and <domain_controller> is the name of the domain controller on which the replica is to be placed. Should you no longer require a replica on a given domain controller, you can follow this procedure, using the remove nc replica command in place of the add nc replica command.
Application Directory Partition Reference Domains The application directory partition reference domain is the parent domain of the application directory partition; in other words, it is the domain name as included in the partition’s DN. It is also known as the security descriptor reference domain. You can change an application directory partition’s reference domain by using the ntdsutil utility. Follow the procedure in Step by Step 2.7, and in step 7, type set nc reference domain , where is the DN of the desired reference domain.
Listing All Known Application Directory Partitions You can easily list the distinguished names of all known application directory partitions on a domain controller. Follow the procedure in Step by Step 2.7, and at step 7, type list. As shown in Figure 2.28, this procedure displays all application directory partitions contained on the domain controller to which you are connected.
FIGURE 2.28 Listing all application directory partitions on a given server.
To list the domain controllers holding replicas of a given application directory partition, follow the same procedure and type list nc replicas , where is the DN of the application directory partition of concern.
70
Chapter 2: Planning and Implementing an Active Directory Infrastructure
NOTE Listing Application Directory Partitions You do not need to have administrative credentials to list application directory partitions. You can perform this task from an ordinary user’s account.
Deleting Application Directory Partitions You can also use ntdsutil to delete application directory partitions that are no longer required. Use the procedure outlined in Step by Step 2.7, and at step 7, type delete nc <domain_controller>.
Active Directory Application Mode (ADAM) As introduced in Chapter 1, Active Directory Application Mode (ADAM) is a special mode of Active Directory that provides directory services for applications using standard application programming interfaces (APIs). Because ADAM runs as a user service and not a system service, you can start and stop ADAM instances as necessary. You can also add or remove instances without impacting the integrity of the Active Directory database. An example where ADAM is useful is in the management of a Web portal application that requires the hosting of users that require authentication without creating an Active Directory domain. You can host a Web portal that stores personalization information outside of Active Directory. Note that you can install ADAM on Windows XP Professional as well as Windows Server 2003.
R2 ADAM has been considerably enhanced in Windows Server 2003 R2 with new features such as the capability for creating users in the configuration partition that can act as ADAM administrators. A new Active Directory to ADAM Synchronizer tool enables the synchronization of Active Directory objects to an ADAM instance. A Schema Analyzer tool enables you to migrate the Active Directory schema to ADAM. You can install ADAM from the Windows Components Wizard in Control Panel Add or Remove Programs. After you have installed ADAM, an entry appears in the All Programs menu with links to the following components: . ADAM ADSI Edit—Opens the ADAM ADSI Edit snap-in, which enables you to
view, modify, create, or delete Active Directory objects. We briefly discuss ADAM ADSI Edit in Chapter 4. . ADAM Help—Provides a comprehensive help interface on all ADAM components,
including all management utilities. . ADAM Tools Command Prompt—Provides a command line from which you can
launch ADAM tools. Table 2.1 introduces the tools that you can launch from this command prompt.
71
Building an Active Directory Forest . Create an ADAM instance—Starts the Active Directory Application Mode Setup
Wizard, which enables you to create an ADAM instance or a replica of an existing instance. You can specify the LDAP and SSL ports that computers will use for accessing the instance, the LDAP distinguished name of an application directory partition, file locations associated with the ADAM instance, and any LDIF files to be imported into the application directory partition. You can also specify the service account used by ADAM as well as the user or group that will have administrative privileges over the ADAM instance.
TABLE 2.1 ADAM Command Line Tools Tool
Description
ADAM Csvde
Imports or exports data files from Active Directory in comma-separated value (CSV) format
ADAM Ldifde
Creates, modifies, or deletes Active Directory objects; extends the schema; exports data to other applications or services; or imports data into ADAM from other directory services
Adaminstall
Installs ADAM in unattended mode from a preconfigured setup file
Adamsync
Synchronizes Active Directory objects to an ADAM instance
Adamuninstall
Removes an ADAM instance
ADSchemaAnalyzer
Facilitates the migration of the Active Directory schema into an ADAM instance
Dsacls
Displays and modifies access control entries (ACEs) in the access control list (ACL) of ADAM objects
Dsdbutil
Provides advanced command-line tools for ADAM management
Dsdiag
Facilitates the analysis and troubleshooting of Active Directory or ADAM directory services
Dsmgmt
Provides additional ADAM management command-line utilities
Ldp
Provides a dialog box from which you can perform several management functions, including connecting to a specified LDAP server, adding objects to or deleting objects from Active Directory, modifying objects or their attributes, searching for attributes, running additional LDP utilities, and so on
Repadmin
Manages Active Directory and ADAM replication
We discuss several of these tools in more detail in later chapters of this study guide. For further information on using ADAM and its component tools, refer to the ADAM help files and to the Microsoft paper, “Introduction to Active Directory Application Mode,” included in the “Suggested Readings and Resources” section at the end of this chapter.
72
Chapter 2: Planning and Implementing an Active Directory Infrastructure
Upgrading Windows 2000 Domains and Forests Microsoft has made several hundred changes and additions to the Windows Server 2003 Active Directory schema. When you upgrade a Windows 2000 domain and forest to Windows Server 2003, you first need to incorporate these changes to the schema for the upgrade to take place properly. Microsoft has provided the Active Directory Preparation Tool (Adprep) for purposes of preparing the Windows 2000 domain and forest for upgrade to Windows Server 2003. Adprep, together with a series of LDIF files containing the schema upgrades, is found in the \I386 folder of the Windows Server 2003 CD-ROM. Step by Step 2.8 shows you how to pre-
pare a Windows 2000 forest for upgrading to Windows Server 2003.
STEP BY STEP 2.8 Preparing a Windows 2000 Forest for Upgrading to Windows Server 2003 1. At the schema master of the Windows 2000 forest, insert the Windows Server 2003 CD-ROM. 2. Click Start, Run, type d:\winnt32 /checkupgradeonly, where d: is the drive letter of the CD-ROM drive. Then click OK. This extracts Adprep to the Winnt\System32 folder and copies the LDIF files containing the schema upgrades. 3. Still at the schema master, click Start, Run, type Adprep /forestprep, and then click OK. This action performs the schema upgrade, and upgrades Active Directory permissions and modifies the display specifiers to support the added classes. 4. If the infrastructure master is on a different server, repeat steps 1 and 2 to extract the Adprep files to that server. 5. At the infrastructure master, click Start, Run, type Adprep /domainprep, and then click OK. This prepares the domain by adding support for new trust relationships plus a new container within the System container for tracking the updates. 6. If the Windows 2000 forest contains more than one domain, repeat steps 4 and 5 at the infrastructure master of every domain.
Building an Active Directory Forest Summary Following is a review of the facts you should know in regard to working with dcpromo and with application directory partitions: . You use the dcpromo program to create all types of Active Directory domain con-
trollers. This program also installs DNS and creates the Active Directory database and log folders and the SYSVOL folder. . The first domain controller to be created assumes the role of forest root domain
controller.
73
Windows Server 2003 Functional Levels . Remember the different options available in dcpromo for creating new trees, child
domains, and additional domain controllers for existing domains. . Running dcpromo on a domain controller demotes it to a member server. . An application directory partition stores application data on domain controllers. It
enables the storing of data on a subset of domain controllers in the domain or forest, and only the designated domain controllers replicate this partition. . ADAM is a special mode of Active Directory that provides directory services for appli-
cations. It provides a series of administrative tools that you can use to manage ADAM instances or Active Directory in general. . To upgrade a Windows 2000 forest to Windows Server 2003, you need to run Adprep /forestprep on the schema master and then run Adprep /domainprep on the infra-
structure master of each domain in the forest.
Windows Server 2003 Functional Levels Objective
Implement an Active Directory directory service forest and domain structure . Set an Active Directory forest and domain functional level based on requirements
When Microsoft introduced Active Directory in Windows 2000, it created two modes of operation to deal with the new features that legacy Windows NT servers were unable to deal with. They were known as mixed mode (which was created for backward compatibility purposes and supported only features available on Windows NT 4.0 domain controllers) and native mode (which supported all new Active Directory features, such as universal security groups and enhanced group nesting). Active Directory in Windows Server 2003 extends this concept further by introducing domain and forest functional levels. We briefly introduced these functional levels in Chapter 1, and we discuss them in more detail in the following sections.
Domain Functional Levels Windows Server 2003 Active Directory supports four domain functional levels: . Windows 2000 mixed—Similar to mixed mode in Windows 2000 Active Directory,
this functional level supports only features that are available with Windows NT 4.0 domain controllers. This is the default functional level at which a newly created Windows Server 2003 domain operates.
74
Chapter 2: Planning and Implementing an Active Directory Infrastructure . Windows 2000 native—Similar to native mode in Windows 2000 Active Directory,
this functional level supports only features that are available with Windows 2000 domain controllers. When you use this functional level, you cannot have any Windows NT 4.0 domain controllers on your domain. When you upgrade a Windows 2000 domain to Windows Server 2003, it initially operates at this functional level. . Windows Server 2003 interim—This functional level supports only Windows NT
4.0 and Windows Server 2003 domain controllers. It appears only when upgrading Windows NT 4.0 domain controllers to Windows Server 2003, supports the same functionality as Windows 2000 mixed functional level, and does not support Windows 2000 domain controllers. . Windows Server 2003—This functional level supports all features available with
Active Directory in Windows Server 2003. It supports only domain controllers running Windows Server 2003. The Windows 2000 mixed functional level does not allow the following features that are available in the Windows 2000 native functional level: . Universal security groups . Enhanced group nesting . Conversion of group types between security and distribution . SID history
The following additional features are available when you convert the functional level to Windows Server 2003: . Renaming of domain controllers . Update logon time stamp . Kerberos Key Distribution Center (KDC) version numbers . User password on InetOrgPerson object
Forest Functional Levels and Requirements Windows Server 2003 supports the following three forest functional levels: . Windows 2000—Supports domain controllers running any of Windows NT 4.0,
Windows 2000, or Windows Server 2003. . Windows Server 2003 interim—Supports domain controllers running Windows
NT 4.0 or Windows Server 2003. This level appears only when upgrading domain
75
Windows Server 2003 Functional Levels
controllers in Windows NT 4.0 domains to Windows Server 2003. It supports features from the Windows 2000 forest functional level plus group membership replication improvements and an improved Inter-Site Replication Topology Generator. . Windows Server 2003—Supports only domain controllers running Windows
Server 2003. The following new features of Active Directory in Windows Server 2003 are enabled only when the forest is operating at the Windows Server 2003 functional level: . Forest trusts . Domain renaming . Global catalog replication tuning . Defunct schema objects . Linked value replication . Improved replication algorithms . Dynamic auxiliary classes . InetOrgPerson object class change
The requirement for operating your Active Directory forest at any particular functional level is essentially the version of domain controllers you can have on the network. For domain functional levels, the requirements are as follows: . To operate at the Windows 2000 native functional level, you need to upgrade all
Windows NT 4.0 domain controllers to either Windows 2000 Server or Windows Server 2003. After you have upgraded to this functional level, you cannot introduce a Windows NT 4.0 domain controller. Note, however, that you can have Windows NT 4.0 member servers and client computers. . To operate at the Windows Server 2003 native functional level, you need to upgrade all
Windows NT 4.0 and Windows 2000 domain controllers to Windows Server 2003. After you have upgraded to this functional level, you cannot introduce any domain controllers that run either of these operating systems. Note, however, that you can have member servers and client computers running these operating systems.
EXAM ALERT Functional Levels You should understand the differences between domain and forest functional levels and the capabilities of the various functional levels. Know when upgrading domain functional levels is acceptable and understand the prerequisites for upgrading the forest functional level to Windows Server 2003.
76
Chapter 2: Planning and Implementing an Active Directory Infrastructure
To raise the forest functional level to Windows Server 2003, there is only one requirement: You must first raise the functional level of all domains in the forest to Windows Server 2003. In addition, you need to know that the upgrade to any of these domain or forest functional levels is one-way only; in other words, after you have upgraded the functional level, you cannot go back to a lower functional level. In addition, after you have raised the forest functional level to Windows Server 2003, you cannot introduce a new Windows NT or 2000 domain to the forest. Step by Step 2.9 shows you how to raise the domain functional level.
STEP BY STEP 2.9 Raising the Domain Functional Level 1. Click Start, Administrative Tools, Active Directory Domains and Trusts. 2. In the console tree, right-click your domain name and choose Raise Domain Functional Level. This selection displays the Raise Domain Functional Level dialog box, as shown in Figure 2.29.
FIGURE 2.29
Raising the domain functional
level.
3. Select the required functional level from the drop-down list and then click Raise. 4. You are warned that this operation affects the entire domain and cannot be reversed (see Figure 2.30). Click OK to raise the functional level.
FIGURE 2.30 You receive this warning when raising the domain functional level.
77
Windows Server 2003 Functional Levels 5. You receive a message informing you that the functional level was successfully raised and that it will now replicate to each domain controller in the domain. Click OK.
Step by Step 2.10 shows you how to raise the forest functional level.
STEP BY STEP 2.10 Raising the Forest Functional Level 1. Click Start, Administrative Tools, Active Directory Domains and Trusts. 2. At the top of the console tree, right-click Active Directory Domains and Trusts and select Raise Forest Functional Level. 3. In the Raise Forest Functional Level dialog box, select Raise (see Figure 2.31).
FIGURE 2.31
Raising the forest functional
level.
4. You are warned that this operation affects the entire forest and cannot be reversed. Click OK to raise the functional level. 5. You receive a message informing you that the functional level was successfully raised and that it will now replicate to each domain controller in the domain. Click OK.
Renaming Domains and Domain Controllers As discussed in Chapter 1, Active Directory in Windows Server 2003 provides the capability of renaming domains and domain controllers after the domain and forest functional levels have been raised to Windows Server 2003. Microsoft provides the rendom.exe utility for purposes of renaming domains. This tool is available as a free download from the Microsoft website; you download and run a file called
78
Chapter 2: Planning and Implementing an Active Directory Infrastructure domainrename.exe, which starts a setup wizard that installs the utility in the C:\Program Files\Microsoft Domain Rename Tools folder on your server. Running this tool consists of
running a series of commands from the command prompt, which are described in the “Step by Step Guide to Implementing Domain Rename,” which is referenced in the “Suggested Readings and Resources” section at the end of this chapter.
EXAM ALERT Domain Renaming You do not need to know the procedural details for renaming domains for the 70-294 exam. However, you should know that the rendom.exe tool is used for this purpose, and the domain and forest must be at the Windows Server 2003 functional level.
WARNING Understand the Implications of Domain Ranaming Renaming a domain is a serious operation that requires careful planning. Its complexity is directly related to the size of the domain, and it can break server applications such as Exchange and IIS. For example, domain renaming is not supported if Exchange 2000 is present. All domain controllers must be successfully updated or removed from the renamed domain. In addition, you must reboot all member computers twice after all domain controllers are updated.
To rename a domain controller, the forest and domain functional levels must be at the Windows Server 2003 level. The procedure is the same as with renaming other computers, as shown in Step by Step 2.11:
STEP BY STEP 2.11 Renaming a Domain Controller 1. Click Start, right-click My Computer, and choose Properties. 2. On the Computer Name tab of the System Properties dialog box, click Change. 3. Click OK to accept the warning that renaming the domain controller might cause it to become temporarily unavailable. 4. In the Computer Name Changes dialog box, type the new name and then click OK. 5. If requested, enter the name and password of an administrative account and then click OK. 6. Click OK twice and then click Yes to complete the renaming and restart the computer.
79
Windows Server 2003 Functional Levels
Functional Levels Review This section presents a detailed discussion of functional levels, which are described as follows: . Microsoft introduced the concept of functional levels to allow for backward compati-
bility with domain controllers running older Windows versions. . The Windows 2000 mixed domain functional level supports any of Windows NT 4.0,
Windows 2000, and Windows Server 2003 domain controllers. It allows only limited Active Directory functionality. . The Windows 2000 native domain functional level supports only Windows 2000 and
Windows Server 2003 domain controllers. It supports all the functionality of Windows 2000 Active Directory. . The Windows Server 2003 interim domain functional level appears only when upgrad-
ing Windows NT 4.0 domains and supports only Windows NT 4.0 and Windows Server 2003 domain controllers. . The Windows Server 2003 domain functional level supports only Windows Server
2003 domain controllers and allows complete Active Directory functionality. . The three forest functional levels are Windows 2000, Windows Server 2003 interim,
and Windows Server 2003. To upgrade to the Windows Server 2003 forest functional level, all domains must operate at the Windows Server 2003 domain functional level. . When you upgrade a domain or forest functional level, you cannot go back to the pre-
vious functional level. . You can use the rendom.exe command-line tool to rename a domain after raising the
functional level to Windows Server 2003. . Renaming a domain controller is similar to renaming other computers, providing that
the functional level has been raised to Windows Server 2003.
Challenge Upgrading Windows NT Domain Controllers and Functional Levels Many companies have been satisfied with their Windows NT 4.0 domains and have never upgraded them to Windows 2000. Now with the advent of Windows Server 2003 and Microsoft discontinuing its support for NT, you might encounter companies that are planning to upgrade their Windows NT domains directly to Windows Server 2003. (continues)
80
Chapter 2: Planning and Implementing an Active Directory Infrastructure (continued)
In this exercise, you are required to upgrade a Windows NT 4.0 primary domain controller (PDC) and backup domain controller (BDC) owned by a fictional company named Widgets to Windows Server 2003; then you need to raise the domain and forest functional levels. In a real-world situation, you should prepare an additional BDC and take it offline in case you encounter problems with the upgrade. This way, you can restore the domain to working condition by bringing the BDC back online and promoting it to a PDC. You will need two computers on which you have installed Windows NT 4.0 Server as PDC and BDC of a domain named widgets. Before you begin this exercise, you should have installed Service Pack 5 or 6a on these computers. If you have created separate disk partitions on your computers, you should be able to use the same computers on which you have installed Windows Server 2003 by installing Windows NT to a different partition. You should also be aware that this exercise will take two to three hours to complete, or possibly more, depending on the processor speed and RAM in your computers. First, you upgrade the PDC to Windows Server 2003, installing Active Directory in the process. Next, you upgrade the BDC. Finally, you upgrade the domain and forest functional levels. You should try working through this exercise on your own. If you are stuck, take a look at the following steps: 1. Insert the Windows Server 2003 CD-ROM in the drive of the PDC. 2. The Welcome to the Microsoft Windows Server 2003 Family screen appears. Click Install Windows Server 2003, Standard (or Enterprise) Edition. 3. On the Welcome to Windows Setup screen, ensure that the drop-down list reads Upgrade (Recommended) and then click Next. 4. Accept the license agreement and then click Next. 5. Type the product key and then click Next. 6. The Report System Compatibility screen shows any items that are not compatible with Windows Server 2003—in particular, Windows 95 and NT interoperability issues. Click Details to see more information about any selected item. When you are finished, click Next. 7. The computer reboots twice, and Windows Server 2003 installation proceeds. You have plenty of time for a long coffee break at this point. 8. The computer reboots a third time, the Administrator account is automatically logged on, and the Active Directory Installation Wizard starts. 9. Click Next to bypass the Welcome page and the Compatibility page. 10. Ensure that Domain in a New Forest is selected and then click Next. 11. On the Install or Configure DNS page, select No, Just Install and Configure DNS on This Computer and then click Next. 12. Type widgets.com as the full DNS name for the domain and then click Next. 13. The Forest Functional Level page asks you to choose the forest functional level. Choose Windows 2000 and then click Next. (continues)
81
Sharing Active Directory Information (continued)
14. Click Next to accept the default database and log file locations; click Next to accept the default SYSVOL location. 15. On the Permissions page, select Permissions Compatible Only with Windows 2000 or Windows Server 2003 Operating Systems and then click Next. 16. Type and confirm a Directory Services Restore password and then click Next. 17. On the Summary page, click Next to begin installing Active Directory. 18. When the completion page appears, click Finish and restart the computer. 19. Log on to the new domain controller with the administrator account and password used in Windows NT 4.0. 20. Repeat steps 1–7 at the BDC. After Windows Server 2003 installation is complete, the Active Directory Installation Wizard starts. 21. Click Next to bypass the Welcome page and the Compatibility page. 22. On the Additional Domain Controller or Member Server page, select Additional Domain Controller and then click Next. 23. If this computer is not configured for DNS name resolution, the Configure Domain Naming Service Client page appears. If you receive this page, right-click My Network Places, click Properties, and access the TCP/IP Properties dialog box for your network connection. Specify the IP address of the former PDC as the preferred DNS server and close this dialog box. Then click Next in the Active Directory Installation Wizard. 24. On the Network Credentials page, type the name and password of the domain administrator account used when upgrading the PDC. 25. Repeat steps 14–19 to complete the installation of Active Directory on this computer. 26. At the former PDC, open the Active Directory Users and Computers console, right-click the Widgets.com domain, and select Raise Domain Functional Level. Raise the domain functional level to Windows Server 2003. 27. After the domain functional level is raised, open the Active Directory Domains and Trusts console and raise the forest functional level to Windows Server 2003.
Sharing Active Directory Information For users to achieve the maximum benefit of Active Directory, they must be able to locate resources on the network, whether they are in the local domain, another domain in the forest, or a trusting forest. In Chapter 1, we introduced the concept of the global catalog. We also introduced several directory roles performed by the global catalog, including providing universal group information. In this chapter, we look further into the strategy of placing global catalog servers and universal group information and show you how you can configure these aspects of the directory.
82
Chapter 2: Planning and Implementing an Active Directory Infrastructure
Global Catalog Servers Recall that a global catalog server keeps a subset of information pertaining to objects located in its domain, as well as summary information pertaining to objects in other domains of its forest. In doing so, users can search the entire forest for resources that they might require. The global catalog server also contains information related to forestwide concerns, such as membership in universal groups. By default, the first domain controller in the forest is a global catalog server. You can add additional global catalog servers by following the procedure outlined in Step by Step 2.12.
STEP BY STEP 2.12 Designating an Additional Global Catalog Server 1. Click Start, Administrative Tools, Active Directory Sites and Services. 2. In the console tree, expand the site in which the required server is located. 3. Expand the Servers folder located therein and expand the folder for the desired server. 4. Right-click the NTDS Settings folder and choose Properties. 5. On the General tab of the NTDS Settings Properties dialog box, select the Global Catalog check box, as shown in Figure 2.32. Then click OK.
FIGURE 2.32
Configuring a domain controller to act as a global catalog server.
83
Sharing Active Directory Information
You can also remove the global catalog server role from a domain controller. Simply follow the procedure in Step by Step 2.12 and clear the Global Catalog check box.
Evaluating Network Traffic Considerations When Placing Global Catalog Servers Objective
Plan a strategy for placing global catalog servers . Evaluate network traffic considerations when placing global catalog servers
Recall that the function of a global catalog server is to assist users in locating resources anywhere on the network. In addition, it maintains information on universal group membership. If you have just a single domain in your forest, the global catalog server plays a minor role, and it is unlikely that you would need to designate additional global catalog servers. You need to be concerned with the following two opposing issues when deciding how many global catalog servers to deploy and where to deploy them: . As your forest increases in size, the size of the global catalog, and hence the amount of
replication traffic among global catalog servers, increases. The global catalog servers replicate with each other in a loop that is separate from other Active Directory replication. The more global catalog servers you deploy, the greater the amount of replication traffic generated. . On the other hand, with increasing forest size, the forest will have more users with
cross-domain queries. Consequently, the time required for users to reach resources in other domains will increase unless you add global catalog servers that users can easily reach. Adding such global catalog servers is especially important in multisite networks. When a user logs on to a given domain controller for the first time in a large enterprise, it is important for this domain controller to connect to a global catalog server to obtain information about any universal groups to which the user might belong. This information includes access permissions assigned to these groups. If the user is located in a branch office that does not have a global catalog server locally present, the domain controller must cross the slow link to the location in which the global catalog server resides. This results in slow logon performance, particularly when several users are logging on at the same time. Consider Figure 2.33, in which users in the head office and in Branch Office 1 have access to a global catalog (GC) server in their own sites; consequently, the logon and object search times are fast. However, users in Branch Office 2 must access a global catalog server in the head office across the slow intersite link. This can result in unacceptably slow logon and object search times, particularly if there is a lot of other intersite traffic. Furthermore, should the slow
84
Chapter 2: Planning and Implementing an Active Directory Infrastructure
link go down and the global catalog server become unavailable as a result, users would be unable to log on at all.
GC
GC
GC
Branch Office 1 Fast Logon and Access Times
Head Office
Branch Office 2 Slow Logon and Access Times
FIGURE 2.33 Logon and search times are much faster when a global catalog server is located onsite.
If sufficiently high bandwidth exists between two sites, locating a global catalog server at the remote site might not be necessary. You should monitor the growth in network traffic and check with users to see whether performance suffers. You should balance the need for additional global catalog servers against users’ need for additional disk space and Active Directory replication bandwidth. A new feature of Windows Server 2003 Active Directory, known as universal group caching, enables users to log on without access to a global catalog server, after they have logged on once to a given DC. We discuss this topic next.
Universal Groups We introduced the universal group in Chapter 1 as a group of users that can come from any domain in the forest. In the present discussion, it suffices to note that you can add users and groups from any domain in the forest to a universal group, and then either assign permissions directly to the group or add it to a domain local group, to which you assign the required permissions. It is important that universal group information be available in order to create a complete access ticket for any user as he logs on. As already mentioned, logon will fail if a global catalog server
85
Sharing Active Directory Information
is not available for any reason. However, as we have mentioned, you can use universal group caching to enable user logons without the need for accessing a global catalog server.
Evaluating the Need to Enable Universal Group Caching Objective
Plan a strategy for placing global catalog servers . Evaluate the need to enable universal group caching
Simply put, when you employ universal group caching, any domain controller that services a user’s logon will store any universal group information the first time that user logs on. In addition, the cache is periodically refreshed from the global catalog so that it reflects changes in universal group membership or permissions. When the user logs on again, the domain controller uses the cached information to ensure a fast, correct logon. Universal group caching is available at any domain or forest functional level that supports universal groups. It offers the following advantages: . You do not require a global catalog server at every site in your forest. . Logon times are faster because the domain controller no longer has to access a global
catalog server at every logon. . Bandwidth usage is reduced because the domain controllers do not need to replicate all
the objects found in the forest.
NOTE Ensure Optimum Replication of Universal Group Information Make sure that global catalog servers are no more than one replication hop away from all domain controllers in which universal group caching has been enabled. This way, you ensure optimum updating of universal group information in the universal group cache.
Balanced against the advantages of universal group caching is the possibility that a user can log on without updated information being available, should you make a change in universal group membership or permissions and the user logs on before the remote domain controller has updated its cache. This situation could be a potential security risk—for example, if you have denied access to a folder containing sensitive data to a universal group or a domain local group into which the universal group is nested. However, keep in mind that without universal group caching, no users can log on if the global catalog server is unavailable. Simply put, it becomes a question of convenience versus the possibility of incomplete security. Universal group caching is implanted at the site level with the Active Directory Sites and Services snap-in. Administer the following procedure, outlined in Step by Step 2.13.
86
Chapter 2: Planning and Implementing an Active Directory Infrastructure
STEP BY STEP 2.13 Enabling Universal Group Caching 1. Click Start, Administrative Tools, Active Directory Sites and Services. 2. In the console tree, expand the site in which the required server is located. 3. Select the required site name. If you have not configured any sites yet, this site will be named DefaultFirst-Site-Name. 4. In the details pane, right-click NTDS Settings and choose Properties. 5. In the Site Settings tab of the NTDS Site Settings Properties dialog box, select the check box labeled Enable Universal Group Membership Caching and then click OK (see Figure 2.34).
FIGURE 2.34
Enabling universal group caching.
EXAM ALERT Global Catalogs and Universal Group Caching You can use either of these options to facilitate logon at a remote site in a multidomain forest. If the exam question informs you that logons are slow and does not mention slow access to resources, the most likely answer is to enable universal group caching. If the exam question informs you that resource access across a WAN is slow, you need to configure a global catalog. Also remember that you do not need to enable both a global catalog and universal group caching at the same site.
87
Placement of Flexible Operations Master Roles
Sharing Active Directory Information Review Let’s review the following strategies for placing global catalog servers and universal group information and for configuring these aspects of the directory. . The global catalog server stores and replicates a subset of information on all domains
of the Active Directory forest. . Although the first domain controller in the forest is automatically a global catalog
server, you can designate additional domain controllers to be global catalog servers. . Having a global catalog server at each Active Directory site is helpful in expediting
user logons and locating resources. You need to balance this need with the amount of intersite replication traffic it creates. . You can enable universal group caching on any domain controller. This enables users
to log on without having to contact a global catalog server after they have logged on to the domain controller for the first time.
Placement of Flexible Operations Master Roles In Chapter 1, we introduced the five operations master roles and their functions. Initially, these roles are all located on the first domain controller installed in a new forest. This includes the two forestwide operations masters (domain naming master and schema master). The first domain controller in subsequent domains of the same forest holds the three domainwide operations master roles (PDC emulator, infrastructure master, and RID master). After you have installed additional domain controllers, you might have to move one or more of these roles. In this section, we discuss the need for moving some of these roles to other domain controllers.
Business Continuity of Operations Master Roles Objective
Plan flexible operations master role placement . Plan for business continuity of operations master roles
Although Active Directory has improved on the old Windows NT PDC/BDC model by creating all domain controllers as peers, some roles in Active Directory still can be performed only by a given domain controller. In a nutshell, this is the reason for the five operations master (or FSMO) roles.
88
Chapter 2: Planning and Implementing an Active Directory Infrastructure
NOTE Only Windows 2000 or 2003 Domain Controllers Can Hold an FSMO Role If your domain is operating at the Windows 2000 mixed functional level and contains one or more Windows NT 4.0 BDCs, these BDCs cannot hold any of the FSMO roles.
Moving one or more FSMO roles to different domain controllers has the obvious benefit of load balancing; in other words, the tasks associated with each role are distributed among different domain controllers. At the same time, you need to be aware of the need for availability of the FSMO servers and what can happen should any of the FSMO servers be unavailable for any reason. Some examples follow: . When you create a new child domain or an additional domain tree, the server you are
promoting to domain controller must contact the domain-naming master to ensure that the domain name you are providing is unique. If the domain naming master is unavailable, you cannot create a new child domain. However, business continuity still occurs in the absence of this FSMO—that is, until you need to create a new child domain. . Should you need to modify the schema, you must be able to connect to the schema
master. Modifications include installing software such as Exchange Server, which automatically creates several new schema definitions. Such an installation will fail if the schema master is unavailable. Again, business continuity still occurs in the absence of this server, until a need to modify the schema arises. . In a domain running at the Windows 2000 mixed functional level, you must be able to
connect to the PDC emulator to make user account modifications. Users changing their passwords must be able to connect to the PDC emulator. Although normal logons can proceed in the absence of the PDC emulator, any changes to user account properties will fail should this server be unavailable. Older Windows clients also look to this computer as the master browser for populating Network Neighborhood and for any system policies you have configured. . When operating at the Windows 2000 interim functional level, the PDC emulator is
responsible for recording password changes and replicating them to the BDCs. At any domain functional level, the PDC emulator still plays the important role of time server. It ensures that the clocks on all domain controllers remain synchronized. Should the PDC emulator be unavailable and the clocks on other domain controllers go out of sync, certain operations could fail or generate errors.
89
Placement of Flexible Operations Master Roles . When you are adding new users or groups, or modifying group membership on various
servers, these servers must all connect to the infrastructure master to ensure that different administrators are not performing conflicting changes. For example, if two administrators in two different cities create a user named JohnD at the same time, a problem would occur. In such a case, the infrastructure master will generate a uniqueness error. . The infrastructure master also tracks changes in group membership that can cross
domains. This capability is important because domain local groups can contain users and global groups in other domains, and global groups can be made members of domain local groups in other domains. In addition, these groups can be members of universal groups and vice versa. In the absence of the infrastructure master, these changes will fail. . When administrators create new user, group, or computer accounts in a domain
operating in the Windows 2000 native or Windows Server 2003 functional level, the domain controller on which the accounts are created must assign a security identifier (SID) to each account. This SID uniquely identifies the account to Active Directory, thereby differentiating it from other accounts in the domain. So that SIDs never become duplicated in the domain, an FSMO computer known as the RID master assigns a pool of 500 relative identifiers (the last portion of the SID) to each domain controller in the domain. The RID master sends a new pool to each domain controller when it has fewer than 50 remaining. In the absence of a RID master, domain controllers can continue to create accounts until the pool of identifiers on that server is exhausted, after which account creation will fail. It is evident from these examples that some operations masters must be more continuously available for business continuity than others. Problems arise most rapidly if the infrastructure master (and, in the Windows 2000 mixed functional level, the PDC emulator) is unavailable. All operations masters should be located on domain controllers that are accessible to as much of the network as possible over a fast link.
EXAM ALERT Operations Master Roles Know what each operations master does and the effect of its being offline. Know also how to recover from various types of operations master problems. You will be asked about troubleshooting the effects of operations masters being offline, and whether to transfer or seize operations master roles.
90
Chapter 2: Planning and Implementing an Active Directory Infrastructure
Transferring Operations Master Roles Following are several reasons that you might want to transfer an operations master role from one server to another: . Doing so enables you to provide load balancing, as already mentioned. The most fre-
quently shifted role is that of the PDC emulator. . You need to perform planned maintenance on or upgrade the computer holding one or
more FSMO roles. . Perhaps an FSMO role has been placed at a location that is behind a slow link and is
creating excessive WAN traffic after some type of shift in a company’s operations. . It is usually preferable to keep the servers hosting the FSMO roles near the administra-
tors who are responsible for them. . You need to ensure that the infrastructure master is not on the same domain controller
as the global catalog server in a multidomain environment. . In general, you should keep the domain naming master and the schema master on the
same server, and this server should be located close to another server on the same subnet that you can use as a backup. For these and other reasons, you might have to transfer an operations master role from one domain controller to another. You can do this from any domain controller in the domain. Step by Step 2.14 shows you how to transfer the three domain-level operations master roles.
STEP BY STEP 2.14 Transferring Operations Master Roles at the Domain Level 1. Log on to a domain controller as a member of the Domain Admins group. 2. Click Start, Administrative Tools, Active Directory Users and Computers. 3. In the console tree, right-click Active Directory Users and Computers and choose Connect to Domain Controller. 4. In the Connect to Domain Controller dialog box, shown in Figure 2.35, select the server to which you want to transfer the role(s) and click OK.
91
Placement of Flexible Operations Master Roles
FIGURE 2.35
Connecting to another domain controller.
5. Right-click your domain name and choose Operations Masters. 6. On the Operations Masters dialog box, shown in Figure 2.36, select the tab corresponding to the role to be changed. On that tab, click Change to transfer the role.
FIGURE 2.36 The Operations Masters dialog box enables you to transfer any of the three domain-based operations master roles.
7. A message box asks you to confirm the role transfer. Click Yes.
92
Chapter 2: Planning and Implementing an Active Directory Infrastructure 8. Repeat steps 6 and 7 for any additional roles to be transferred. 9. When you are finished, click Close to close the Operations Masters dialog box.
Transferring the forest-based operations master roles is slightly different from that of domainbased operations masters. Follow Step by Step 2.15 to transfer the domain naming master role.
STEP BY STEP 2.15 Transferring the Domain Naming Master Role 1. Log on to the domain controller to which you want to transfer the role as a member of the Enterprise Admins group. 2. Click Start, Administrative Tools, Active Directory Domains and Trusts.
NOTE You Can Also Transfer This Role When at Another Domain Controller Simply right-click Active Directory Domains and Trusts and select Connect to Domain Controller. Then browse to the proper domain and select the domain controller to which you want to transfer the role.
3. In the console tree, right-click Active Directory Domains and Trusts and select Operations Master. This displays the current holder of the domain naming master role. 4. In the Change Operations Master dialog box, shown in Figure 2.37, click Change.
FIGURE 2.37
The Change Operations Master dialog box.
5. You receive a confirmation message box. Click Yes to transfer the role. 6. You are informed that the operations master was successfully transferred. Click OK and then close the Change Operations Master dialog box.
93
Placement of Flexible Operations Master Roles
Transferring the schema master role is similar to that of the domain-naming master, except that you must be a member of the Schema Admins group, and you use the Active Directory Schema MMC to perform the transfer. This console is not present by default when Active Directory is installed. We discuss registering and installing this console in Chapter 3. After you have done so, follow the steps in Step by Step 2.15, substituting this console for the Active Directory Domains and Trusts console.
Using the Command Line to Transfer Operations Master Roles You can also transfer operations master roles from the command line, by employing the ntdsutil utility, as described in Step by Step 2.16.
STEP BY STEP 2.16 Using the Command Line to Transfer Operations Master Roles 1. Log on to a domain controller as a member of the appropriate group. 2. Open a command prompt and type ntdsutil. 3. At the ntdsutil command prompt, type roles. 4. At the FSMO maintenance command prompt, type connection. 5. At the server connections command prompt, type connect to server <domain_controller>, where <domain_controller> is the name of the server to which you want to connect. 6. At the server connections command prompt, type quit. 7. At the FSMO maintenance command prompt, type transfer , where is the role (PDC emulator, RID master, infrastructure master, domain naming master, or schema master) you want to transfer. 8. A message box asks you to confirm the role transfer (see Figure 2.38). Click Yes and then click OK in the confirmation dialog box that appears.
FIGURE 2.38 Changing an operations master role from the command line.
9. Repeat steps 7 and 8 to transfer additional roles as needed. 10. Type quit to exit the FSMO maintenance command prompt. 11. Type quit to exit the ntdsutil command prompt.
94
Chapter 2: Planning and Implementing an Active Directory Infrastructure
Seizing Operations Master Roles The procedures for transferring operations master roles work only if the domain controller currently holding the role is online. If this domain controller were to crash, you would need to seize the role.
WARNING Seize a Role Only If You Know You Cannot Restore the Current Operations Master to Operation Before you seize the missing role, make sure that the problem is not due to network connectivity or a temporary server problem. If you were to seize a role and later bring back the former holder of that role online, Active Directory would probably become corrupted. After seizing a role, you need to reformat the disk of the former role holder, reinstall Windows Server 2003, and promote it to domain controller.
To seize an operations master role, use the ntdsutil command as described in Step by Step 2.17.
STEP BY STEP 2.17 Seizing Operations Master Roles 1. Log on to a domain controller as a member of the appropriate group. 2. Open a command prompt and type ntdsutil. 3. At the ntdsutil command prompt, type roles. 4. At the FSMO maintenance command prompt, type connection. 5. At the server connections command prompt, type connect to server <domain_controller>, where <domain_controller> is the name of the server that is to receive the seized role. 6. At the server connections command prompt, type quit. 7. At the FSMO maintenance command prompt, type seize , where is the role (PDC emulator, RID master, infrastructure master, domain naming master, or schema master) you want to seize. 8. A confirmation message box asks you to confirm the role seizure, as shown in Figure 2.39. Click Yes to seize the role.
95
Placement of Flexible Operations Master Roles
FIGURE 2.39
Seizing an operations
master role.
9. ntdsutil first tries to connect to the server and confirm that it is not available. After it receives an error message, it seizes the role, displaying the output shown in Figure 2.40.
FIGURE 2.40 Completing the seizure of an operations master role.
10. Type quit twice and then exit the command prompt.
NOTE ntdsutil Will Not Seize the Role If the Server Holding the Role Is Online If ntdsutil finds that the server holding the role you are seizing is online, it transfers the role rather than seizes it.
Operations Master Role Dependencies Objective
Plan flexible operations master role placement . Identify operations master role dependencies
You should not place the infrastructure master on the same domain controller as a global catalog server unless you have configured all domain controllers as global catalog servers.
96
Chapter 2: Planning and Implementing an Active Directory Infrastructure
A dependency exists between the schema master and the global catalog. It is possible to list every schema attribute in the global catalog by selecting the Replicate This Attribute to the Global Catalog option, located on the Properties dialog box for the attribute. (We discuss the schema, its attributes, and their properties in Chapter 3.) Selecting this option adds information pertaining to that attribute to the global catalog, requiring a fast connection to the nearest global catalog server. This includes the installation of programs such as Exchange that add attributes to the schema. You should be aware that this option causes Windows 2000 global catalog servers to completely rebuild their global catalogs, resulting in a large amount of network traffic. Windows Server 2003 replicates only the changes in the global catalog produced by such a schema modification, thereby causing much less network traffic. If you have a mixture of Windows 2000 and 2003 on your global catalog servers, the various servers still act in this manner according to the particular operating system in use. This behavior is true regardless of the functional level at which the domains and forest are operating.
EXAM ALERT Placement of Operations Masters You should remember the following key points about operations master placements: First, on a network that has a large number of pre-Windows 2000 computers, place the PDC emulator at the site containing the largest number of these computers. Second, remember that the infrastructure master must not be located on the same server as a global catalog server unless all domain controllers are configured as global catalog servers or you are operating in a single domain model.
Challenge Operations Masters and Global Catalog Servers After you have created an Active Directory forest and domain structure and added a second domain controller to each domain, you should think about the placement of the various operations masters and global catalog servers. The object of this exercise is to understand the requirements for placing global catalog servers and operations masters in an Active Directory forest containing two domains: widgets.com and inventory.widgets.com. Each domain has two domain controllers: server01.widgets.com, server02.widgets.com, server11.inventory.widgets.com, and server12.inventory.widgets.com. To do this exercise completely, you need a test lab containing four computers on which you have installed Windows Server 2003 Standard or Enterprise Edition with the domains as specified here. If you don’t have this amount of hardware available, you can still do portions of the exercise and, at any rate, should follow through the required steps. You want to ensure that users in either domain can access resources anywhere in the forest, with fault-tolerant capabilities as permitted by the product’s limitations. (continues)
97
Placement of Flexible Operations Master Roles (continued)
You should try working through this problem on your own first. There could be more than one solution to the problem. If you are stuck or need guidance, follow these steps and look back at the Step by Step procedures for more detailed information. 1. Working from server01.widgets.com, open Active Directory Sites and Services. 2. In the console tree, expand the Default-First-Name-Site object, expand the Servers container, and expand the server02.widgets.com folder. 3. Right-click the NTDS Settings folder and choose Properties. 4. Select the Global Catalog check box and then click OK. 5. Repeat steps 1–4 at server11.inventory.widgets.com and designate server12.inventory.widgets.com as a global catalog server. 6. Back at server01.widgets.com, open Active Directory Users and Computers. 7. Right-click widgets.com and choose Connect to Domain Controller. 8. In the Connect to Domain Controller dialog box, select server02.widgets.com and click OK. 9. Right-click widgets.com and choose Operations Masters. 10. Select the PDC tab, click Change, and confirm the operation. 11. Repeat step 10, selecting either one of the other two tabs. 12. Close the Operations Masters dialog box. 13. In the console tree of Active Directory Users and Computers, right-click Active Directory Users and Computers and choose Connect to Domain. 14. Browse to inventory.widgets.com and then click OK. 15. Right-click Active Directory Users and Computers again and choose Connect to Domain Controller. 16. Repeat steps 8–12, specifying server12.inventory.widgets.com as the server to which you will move two operations master roles. Think about the answers to the following questions: If you were to have three domain controllers in each domain, what would you do differently in moving around operations master roles? Also, why didn’t we configure alternative locations for the schema master and domain naming master in the inventory.widgets.com domain?
98
Chapter 2: Planning and Implementing an Active Directory Infrastructure
Operations Masters Review Following is a review of the five operations masters: . Active Directory designates five operations masters, which perform roles that are suit-
able for single-master replication only. . Two of these operations masters are forestwide: the schema master and the domain
naming master. . The other three operations masters are domainwide: the infrastructure master, the
PDC emulator, and the RID master. . The infrastructure master should not be located on the same domain controller as a
global catalog server unless all domain controllers are configured as global catalog servers.
99
Chapter Summary
Chapter Summary This chapter guided you through the basics of planning and implementing Active Directory in Windows Server 2003 and provided you with practical experience in creating and configuring domains. You learned how to create the various domain controllers that are required for new and existing forests, trees, and domains using the Active Directory Installation Wizard (dcpromo). In addition, you learned the importance of domain and forest functional levels and how to raise these levels. You also learned how to prepare a Windows 2000 forest for upgrading to Windows Server 2003. Next you learned about global catalog servers and flexible operations master roles. You learned the importance of these roles and how to create additional global catalog servers and transfer or seize operations master roles. The next chapter will introduce you to the various types of Windows Server 2003 trust relationships, the schema, and UPN suffixes. It will also introduce you to creating, configuring, and managing sites in Active Directory.
Key Terms . Active Directory Application Mode (ADAM) . Application directory partition . BIND . Child domain . dcpromo . Domain functional levels . Domain partition . DNS . EFS . Forest functional levels . Global catalog servers . Interim functional levels
100
Chapter 2: Planning and Implementing an Active Directory Infrastructure . NetBIOS . NTFS . rendom . SRV resource records . SYSVOL . Universal group caching
Apply Your Knowledge The 70-294 exam tests your knowledge of the various situations that can be encountered when installing and configuring Active Directory. You need to be aware of the differences encountered when installing additional domain controllers, new domain trees, and new child domains. You also need to know how to create application directory partitions, configure global catalog servers, and manage operations masters. The exercises and exam questions presented here serve to reinforce these requirements. Note that you may encounter drag-and-drop or hot-spot questions on the exam. Due to the limitations of the printed page, we are unable to include questions of these types in the exam questions section. However, the explanations suggest the possibility of these question types where appropriate.
Exercises In Windows Server 2003, as in Windows 2000, a server must be running Active Directory to take on the role of domain controller, and vice versa. You promote a server to be a domain controller by running the Active Directory Installation Wizard. This practice differs from that of Windows NT 4, in which you had to re-install a server from scratch to be able to promote it from a member server to be either a primary or backup domain controller. To perform these exercises, you should have at least two computers on which you have installed Windows Server 2003 Standard Edition or Enterprise Edition as a standalone server, and have formatted the system root partitions with the NTFS file system. The exercises assume that the computers are named Server1 and Server2. You will be installing two domain controllers for an Active Directory domain named domain1.com.
101
Apply Your Knowledge
2.1 Installing a Forest Root Domain Controller This exercise demonstrates the procedure you can use to create a new domain named domain1.com. You can do this exercise on either of the two computers. Estimated Time: 20 minutes 1. Click Start, Run. Type dcpromo in the Run dialog box and then click OK. 2. The Active Directory Installation Wizard is started with a Welcome page. Click Next. 3. The Operating System Compatibility page informs you that improved Windows Server 2003 security settings affect how older versions of Windows communicate with the domain controller. Click Next. 4. On the Domain Controller Type page, ensure that the radio button labeled Domain Controller for a New Domain is selected and then click Next. 5. On the Create New Domain page, ensure that the radio button labeled Domain in a New Forest is selected and then click Next. 6. On the New Domain Name page, in the text box labeled Full DNS Name for New Domain, type the name of the new domain to be created—in this case domain1.com—and then click Next. 7. After a few seconds, the NetBIOS Domain page appears. Make sure that the most qualified (first) part of your domain name (for example, DOMAIN1) is displayed. Then click Next. 8. On the Database and Log Folders page, note the locations for these files and then click Next. 9. On the Shared System Volume page, note the location specified and then click Next. 10. On the DNS Registration Diagnostics page, select Install and Configure the DNS Server on This Computer, and Set This Computer to Use This DNS Server As Its Preferred DNS Server and then click Next. 11. On the Permissions page, select Permissions Compatible with Only Windows 2000 or Windows 2003 Server Operating Systems and then click Next. 12. On the Directory Services Restore Mode Administrative Password page, type a suitable password in the Password and Confirm Password text boxes and then click Next. 13. The Summary page provides a summary of the options you have entered. Ensure that these options are correct and then click Next. 14. When Active Directory installation is completed, the Completing the Active Directory Installation Wizard page appears. Click Finish. 15. You are told that you must restart the computer to complete the Active Directory installation. Click Restart Now to restart the computer.
102
Chapter 2: Planning and Implementing an Active Directory Infrastructure
2.2 Installing a Second Domain Controller In this exercise, you add a second domain controller to the domain1.com domain you just created. You should perform this exercise on the second computer running Windows Server 2003 Standard Edition or Enterprise Edition. The system root folder should also be formatted with NTFS. First, specify the IP address of the first domain controller as this computer’s preferred DNS server so that it can locate the domain controller by name. Estimated Time: 20 minutes 1. Log on to the second server as an administrator. 2. Click Start, Control Panel, and double-click Network Connections. 3. On the Network Connections dialog box, right-click your network connection and choose Properties. 4. On the Local Area Connection Properties dialog box, select Internet Protocol and click Properties. 5. If the IP address of the domain controller you just created in exercise 2.1 is not present, enter it in the Preferred DNS Server text box and then click OK. 6. Close the Local Area Connection Properties dialog box and the Network Connections dialog box. 7. Click Start, Run, type dcpromo, and then press Enter. 8. Click Next twice to bypass the Welcome page and the Operating System Compatibility page of the Active Directory Installation Wizard. 9. On the Domain Controller Type page, select Additional Domain Controller for the Same Domain, and then click Next. 10. On the Network Credentials page, type the username, password, and domain that you specified in exercise 2.1 and then click Next. 11. On the Additional Domain Controller page, if domain1.com is not listed in the Domain Name text box, type it and then click Next. 12. On the Database and Log Folders page, accept the default location and click Next. 13. On the Shared System Volume page, accept the default location and click Next. 14. On the Directory Services Restore Mode Administrative Password page, type a suitable password in the Password and Confirm Password text boxes and then click Next. 15. The Summary page provides a summary of the options you have entered. Ensure that these options are correct and then click Next. 16. When Active Directory installation is completed, the Completing the Active Directory Installation Wizard page is displayed. Click Finish and restart your computer.
103
Apply Your Knowledge
2.3
Creating an Application Directory Partition
In this exercise, you create an application directory partition named Apps on the Server1 server. You then create a replica of the partition on the Server2 server so that replication of the application directory partition can take place. Estimated Time: 5 minutes 1. Log on to Server1 as an administrator. 2. Open a command prompt and type ntdsutil. 3. At the ntdsutil prompt, type domain management. 4. At the domain management prompt, type connection. 5. At the connection prompt, type connect to server server1 and then type quit. 6. At the domain management prompt, type create nc dc=apps,dc=domain1,dc=com null. 7. At the domain management prompt, type connection. 8. At the connection prompt, type connect to server server2 and then type quit. 9. At the domain management prompt, type add nc replica dc=apps,dc=domain1,dc=com null. 10. Type quit twice and then exit the command prompt.
2.4
Upgrading Domain and Forest Functional Levels
In this exercise, you upgrade the functional levels of your new domain to receive the full capabilities provided in Windows Server 2003 Active Directory. You can complete this upgrade from either server. Estimated Time: 5 minutes 1. Log on as an administrator. 2. Click Start, Administrative Tools, Active Directory Users and Computers. 3. Right-click domain1.com and choose Raise Domain Functional Level. 4. In the Raise Domain Functional Level dialog box, select Windows Server 2003 from the drop-down list, click Raise, and then click OK twice. 5. Click Start, Administrative Tools, Active Directory Domains and Trusts. 6. Right-click Active Directory Domains and Trusts and choose Raise Forest Functional Level. 7. In the Raise Forest Functional Level dialog box, select Windows Server 2003, click Raise, and then click OK twice. 8. Close all open dialog boxes and MMC consoles.
104
Chapter 2: Planning and Implementing an Active Directory Infrastructure
Exam Questions 1. Nolan is a network administrator for a company that operates an Active Directory network consisting of two domains. The company has offices in Los Angeles and Tokyo, which are connected by a 128-kbps WAN link. Each office is represented by a separate Active Directory site, as well as its own domain. Nolan’s company stores resource location information in Active Directory so that users can perform searches to locate the appropriate resources using the Entire Directory option. However, users in the Tokyo office report that search times for resources are unacceptably slow. What can Nolan do to improve search times at the Tokyo office?
❍
A. Configure a global catalog server at the Tokyo office.
❍
B. Enable universal group caching at the Tokyo office.
❍
C. Configure a domain controller for the Los Angeles domain in the Tokyo office.
❍ D. Configure a domain controller for the Tokyo domain in the Los Angeles office. 2. Steve’s company has just merged with another large company and is converting its network organization over to a single domain model. Several OUs represent various departments, and several sites represent the cities where the company conducts business. The merged company has decided to consolidate its call center operations in St. Louis. These operations have previously been scattered around several cities in North America. Since the consolidation, Steve has received complaints of slow operation of certain administrative actions across the network. He realizes that one reason for this slowdown is that junior administrators have been adding user accounts for the merged organization in batches. After some investigation of the causes of this problem, he decides that poor placement of an operations master on the network is the cause of the problem. To solve this problem, Steve needs to move the operations master to a more powerful machine with better network connectivity in St. Louis. Which of the following operations masters should he move?
❍
A. Domain naming master
❍
B. Infrastructure master
❍
C. Schema master
❍ D. Relative Identifier (RID) master 3. Lynn is the network administrator for a company that operates an Active Directory domain in which all domain controllers run Windows 2000 Server. The company wants to upgrade the domain controllers to Windows Server 2003. Lynn’s user account is a member of the Domain Admins, Enterprise Admins, and Schema Admins groups in her company’s domain.
105
Apply Your Knowledge What actions does Lynn need to perform to upgrade the domain controllers to Windows Server 2003? To answer this question, select the two required actions from the list that follows in the sequence in which she must execute them.
❏
A. Run the Adprep /domainprep command at the infrastructure master.
❏
B. Run the Adprep /forestprep command at the infrastructure master.
❏
C. Run the Adprep /domainprep command at the PDC emulator.
❏ D. Run the Adprep /forestprep command at the schema master. ❏
E. Run the Adprep /domainprep command at the schema master.
❏
F. Run the Adprep /forestprep command at the domain naming master.
4. Your company is operating an Active Directory forest consisting of a single tree with an empty root domain and four child domains that represent operational divisions. You are responsible for maintaining the operations masters. In total, how many operations masters are present in this tree?
❍
A. One schema master, one domain naming master, one RID master, one PDC emulator, and one infrastructure master.
❍
B. Five schema masters, five domain naming masters, five RID masters, five PDC emulators, and five infrastructure masters.
❍
C. One schema master, one domain naming master, five RID masters, five PDC emulators, and five infrastructure masters.
❍ D. One schema master, one domain naming master, four RID masters, four PDC emulators, and four infrastructure masters. 5. The day after completing a three-week vacation, you come to the office and discover that users have complained that one of the domain controllers is not accepting logons. On checking Event Viewer, you notice several W32Time errors. You connect to the problematic domain controller and discover that its time is 15 minutes slow. Which of the following operations masters should you check for problems?
❍
A. Infrastructure master
❍
B. Schema master
❍
C. RID master
❍ D. PDC emulator 6. Andrew’s company operates a domain that was recently upgraded from Windows NT 4.0 to Windows Server 2003. Because the company budget allows for only two Windows Server 2003 domain controllers, it is still operating two Windows NT 4.0 servers as backup domain controllers. One Monday morning, users at several computers running Windows NT 4.0 Workstation complain
106
Chapter 2: Planning and Implementing an Active Directory Infrastructure that they were asked to change their passwords, but the password change was not accepted and they are unable to log on. Which of the following is the most likely reason for this problem?
❍
A. The infrastructure master is down.
❍
B. The PDC emulator is down.
❍
C. One of the Windows NT 4.0 backup domain controllers is down.
❍ D. Because the domain is running at the Windows 2000 mixed functional level, the users are unable to change their passwords. 7. You are the senior network administrator for examcram.com, which operates an Active Directory forest consisting of a root domain named examcram.com and two child domains named sales.examcram.com and accounting.examcram.com. All domains operate at the Windows 2000 native domain functional level. Domain controllers in the examcram.com domain run Windows Server 2003, and domain controllers in the two child domains run Windows 2000 Server. You need to rename all domain controllers in the examcram.com domain. Which actions should you perform?
❍
A. Raise the domain functional level of the forest root domain and each child domain to Windows Server 2003, and then raise the forest functional level of the forest root domain to Windows Server 2003.
❍
B. Raise the domain functional level of the forest root domain to Windows Server 2003, and then raise the forest functional level of the forest root domain to Windows Server 2003.
❍
C. Raise the domain functional level of the forest root domain and each child domain to Windows Server 2003, and then raise the forest functional level of all domains to Windows Server 2003.
❍ D. Raise the forest functional level of the forest root domain to Windows Server 2003, and then raise the domain functional level of the forest root domain and each child domain to Windows Server 2003.
❍
E. Raise the forest functional level of the forest root domain to Windows Server 2003, and then raise the domain functional level of the forest root domain to Windows Server 2003.
❍
F. Raise the forest functional level of all domains to Windows Server 2003, and then raise the domain functional level of the forest root domain and each child domain to Windows Server 2003.
8. Evelyn’s company consists of two divisions, one of which is located in New York and the other in London. A 512Kbps frame relay link connects the two locations. The company’s network is organized as a single domain. Administrators at each location control all aspects of their networks, including users, groups, and computers.
107
Apply Your Knowledge Managers in both divisions complain that sending data between them takes a long time. On checking the link, Evelyn discovers that it is running at 100% capacity. The company budget does not provide for upgrading to a faster link. Which of the following should Evelyn suggest as a means of reducing the load on the link?
❍
A. Create two OUs, one for each location.
❍
B. Create two sites, one for each location.
❍
C. Create two domains, one for each location.
❍ D. Create two forests, one for each location. 9. Debbie is the network administrator for a company that operates an Active Directory forest containing three domains and several sites that represent cities in which the company does business. The forest and all domains operate at the Windows Server 2003 functional level. As shown in the work area in Figure 2.41, two sites are located in Dallas and Houston. The Dallas site includes two domain controllers, Server1 and Server2, both configured as global catalog servers. The Houston site includes two domain controllers, Server3 and Server4, neither of which is configured as a global catalog server. The two sites are connected by a dedicated ISDN link. Users in the Houston site report that logon times are often unacceptably slow. Debbie needs to configure the network so that logon times are improved without generating excessive replication traffic. What should she do?
❍
A. Configure Server3 and Server4 as global catalog servers.
❍
B. Configure Server3 and Server4 with universal group membership caching.
❍
C. Configure the Dallas site with universal group membership caching.
❍ D. Configure the Houston site with universal group membership caching. Place configuration here.
Global Catalog Server Universal Group Membership Caching
Server1 Server2
ISDN
Place configuration here.
Server3 Server4
Dallas
Houston
Place configuration here.
Place configuration here.
FIGURE 2.41 Improve logon times without generating excessive replication traffic.
10. Heather is the IT manager of a community college whose administrative staff is planning the college’s new Windows Server 2003 domain infrastructure. Eight domain controllers will be located in various campus buildings. The college’s administrators and technical support staff are to be based in an annex to the computer sciences department that would include a powerful server acting as the forest root domain controller. This server would incorporate the roles of global catalog server,
108
Chapter 2: Planning and Implementing an Active Directory Infrastructure schema master, domain naming master, and infrastructure master. Servers in other buildings would take on the other operations master roles. After studying the proposal carefully, Heather asked the administrative staff to modify the operations master setup. Which of the following should the staff change?
❍
A. The infrastructure master computer does not need to be located close to the IT staff. A more sensible change would be to move this role elsewhere and have the PDC emulator located close to the support staff.
❍
B. The schema master and domain naming master roles cannot function properly if they are hosted by the same computer.
❍
C. The global catalog server and infrastructure master roles cannot function properly if they are hosted by the same computer.
❍ D. The college’s computer help center, which is staffed by students who work part-time shifts and is located in the student union building, needs frequent access to the infrastructure master. Locating this role there would make sense. 11. You are attempting to promote a server called SVR3 to a domain controller using the dcpromo tool. However, when you attempt to run this tool, you get an error message and the tool will not start. Which of the following conditions explains the reason you were unable to use the dcpromo tool?
❍
A. SVR3 is configured to receive an IP address from a DHCP server.
❍
B. SVR3 cannot find a DNS server that can handle SRV resource records.
❍
C. SVR3’s hard disk is configured with the FAT32 file system.
❍ D. SVR3 is unable to locate a certificate server on the network. 12. Susan has created an application directory partition, named DC1, on a domain controller in the company.com domain to store data from a custom accounting package and replicate it to domain controllers DC2 and DC3. DC3 is located in a child domain named production.company.com. What does she need to do to enable the partition to replicate to these domain controllers?
❍
A. Create new application directory partitions on both DC2 and DC3.
❍
B. Create application directory partition replicas on both DC2 and DC3.
❍
C. Specify production.company.com as the application directory partition reference domain.
❍ D. Use Active Directory Domains and Trusts to add production.company.com as a replication destination for the partition. 13. Marilyn is the systems administrator for her company, which runs a large Active Directory network that consists of several domains all contained within one tree structure. This company has operations in both North America and Europe. Marilyn works in the Boston head office, where the root
109
Apply Your Knowledge domain is established, including the domain controllers that hold the roles of domain naming master and schema master. One weekend, the domain naming master crashed, and the hardware techs discovered that it requires several new parts, including a new SCSI hard drive, and that the parts will take more than a week to be delivered and installed. However, Marilyn ur gently needs to create two new domains that will encompass the company’s newly expanded European operations. Without a functioning domain naming master, she is unable to create the new domains. She realizes that it is necessary to have another domain controller seize the role of domain naming master. Which of the following does Marilyn need to do to accomplish this task?
❍
A. Use the ntdsutil command-line utility.
❍
B. Use Active Directory Domains and Trusts.
❍
C. Use Active Directory Users and Computers.
❍ D. Reinstall another computer with Windows Server 2003. Use dcpromo.exe to promote it to a domain controller and specify that it is to be a domain naming master. 14. George’s company operates an Active Directory network with three domains. Because users require access to resources in all three domains, he has created several universal groups. One child domain has two sites connected by a 56K link. Each site has two domain controllers, one of which is a global catalog server at each site, and they are configured to replicate once each night. One day, the global catalog server at the smaller of the two sites crashed, and George had to order several hardware components to bring it back online. The next day, users at that site complained of excessively long logon times. The remaining domain controller does not have enough disk space to support hosting the global catalog. What should George do to expedite logon times until he can bring the failed domain controller up again?
❍
A. Configure more frequent replication with the other site in that domain.
❍
B. Change the scope of all the universal groups to global.
❍
C. Transfer the RID master role to the remaining domain controller at that site.
❍ D. Enable universal group caching on the remaining domain controller at that site. 15. Your company operates a network that contains three domains with eight sites, each representing different cities in which company offices are located. The domains represent separate business divisions. Some users require access to resources in other domains at other sites, and lately access has been slow at busy times of the day. You decide that there is a need for several additional global catalog servers in each domain. Which tool should you use to create these global catalog servers?
❍
A. The ntdsutil command-line tool.
❍
B. Active Directory Domains and Trusts.
❍
C. Active Directory Sites and Services.
❍ D. You cannot create more than one global catalog server per domain.
110
Chapter 2: Planning and Implementing an Active Directory Infrastructure
Answers to Exam Questions 1. A. Nolan should configure a global catalog server at the Tokyo office. It contains directory information about all objects in the forest, including the location of resources in each domain of the forest. Universal group caching stores information about universal group membership in the domain controller where it is implemented, but does not store information about resources in Active Directory, so answer B is wrong. Replicating the entire contents of each domain between domain controllers in the two sites across the WAN link would overload the link and is unnecessary for solving this problem, so answers C and D are wrong. See the section “Global Catalog Servers.” 2. D. The RID master assigns sequences of relative identifiers (RIDs) to every domain controller in the domain. If the RID master is overtaxed because of all operations including the assignment of RIDs, Steve should move this role to another more suitable domain controller. The infrastructure master updates references to objects in its domain that point to objects in another domain, so answer B is wrong. The PDC emulator acts as a primary domain controller when Windows NT or 9x clients must receive password changes or other user actions, so answer C is wrong. The domain-naming master ensures that domain names throughout the Active Directory forest are unique, so answer A is wrong. See the section “Placement of Flexible Operations Master Roles.” 3. D, A. To prepare the domain for upgrading to Windows Server 2003, Lynn must first run the Adprep /forestprep command at the schema master, and not the domain naming master or infrastructure master. She must then run the Adprep /domainprep command at the infrastructure master, and not at any other operations master. Therefore, answers B, C, E, and F are incorrect. You should note that in an “ordered list” or “build list and reorder” exam question, you must place the required items in the proper order for the answer to be scored correct. Therefore, specifying the answer to this question as “A, D” is incorrect. A question of this type would appear as a “drag and drop” question type on the exam. See the section “Upgrading Windows 2000 Domains and Forests.” 4. C. The schema master and domain naming master are forestwide roles, so only one of these roles exists in the forest, and answer B is wrong. The RID master, PDC emulator, and infrastructure master are domainwide roles, so each domain has one of these roles, for a total of five each and answer A is wrong. An empty root domain still has all five operations masters, so answer D is wrong. See the section “Placement of Flexible Operations Master Roles.” 5. D. The PDC emulator looks after the synchronizing of time on all domain controllers in the domain. If it is not functioning properly, time could drift and create this kind of problem. The infrastructure master is used to update object references in its domain that point to objects in another domain in the forest. The schema master keeps track of all changes to the schema. The RID master allocates sequences of relative identifiers (RIDs) to domain controllers for use when new objects are created in Active Directory. None of these other operations masters track time, so answers A, B, and C are wrong. See the section “Placement of Flexible Operations Master Roles.” 6. B. When a domain contains a mixture of Windows NT 4.0, Windows 2000, and Windows Server 2003 domain controllers, it operates in the Windows 2000 mixed functional level. Windows NT 4.0 client computers can be authenticated at any domain controller, but functions such as password changes can be accommodated only at the PDC emulator, which acts as a primary domain controller for these clients. The infrastructure master computer updates object references in its domain that point to
111
Apply Your Knowledge resources in another domain. Its absence might affect access to resources but not password changes, so answer A is wrong. Windows NT 4.0 BDCs can authenticate users but not change their passwords, so answer C is wrong. Although Windows 2000 mixed functional level does not allow improvements such as universal groups and enhanced group nesting, it does not affect users’ ability to change passwords, so answer D is wrong. See the section “Windows Server 2003 Functional Levels.” 7. A. You need to raise the forest functional level to Windows Server 2003 to be able to rename domain controllers. To raise the forest functional level to Windows Server 2003, you first need to raise the domain functional level of all domains to Windows Server 2003. You cannot raise the forest functional level to Windows Server 2003 until the domain functional level of all domains has been raised to Windows Server 2003, so answer B is incorrect. You must raise the domain functional level of all domains to Windows Server 2003 before you raise the forest functional level to Windows Server 2003, so answers D and E are incorrect. You need to perform the forest action on the root domain (examcram.com) only and not on the child domains, so answers C and F are incorrect. See the section “Renaming Domains and Domain Controllers.” 8. C. In this situation, in which business including network administration is essentially autonomous at the two locations, Evelyn should consider creating two domains, one for each location. This approach makes sense because domains are both a replication and a security boundary. Only the schema and configuration partitions, and possibly one or more application directory partitions, need to be replicated across the slow link. She cannot use OUs for reducing the amount of replication, so answer A is wrong. Use of sites is more desirable if administrators have to work more closely together, so answer B is wrong. She does not need to establish two forests, so answer D is wrong. See the section “Planning the Active Directory Namespace.” 9. D. Debbie needs to configure the Houston site for universal group membership caching. Logon times at the Houston site are slow because the domain controllers at this site need to contact the domain controllers at the Dallas site for universal group membership information. Universal group membership caching is enabled for a site from the NTDS Settings node of the Active Directory Sites and Services snap-in, and applies to all domain controllers in a site. Therefore, it is incorrect to suggest that universal group membership caching is enabled on a specific domain controller (Server3 or Server4), and answer B is incorrect. She needs to enable universal group caching at the site without global catalog servers; therefore, answer C is incorrect. The users in Houston are complaining only about slow logons and not about slow resource connections, so it is not necessary to configure Server3 or Server4 as a global catalog server; therefore answer A is incorrect. See the section “Evaluating the Need to Enable Universal Group Caching.” 10. C. Due to the way that the system determines references to external objects, the infrastructure master cannot be hosted on the same domain controller where the global catalog is located. For this reason, one of these roles should be hosted on another server. It is possible to administer the servers remotely, including the infrastructure master. Consequently, the location of this computer does not matter, so answer A is wrong. The domain naming master and schema master can operate on the same server without difficulties, so answer B is wrong. The students at the help center do not need access to the infrastructure master, so answer D is wrong. See the section “Placement of Flexible Operations Master Roles.”
112
Chapter 2: Planning and Implementing an Active Directory Infrastructure 11. C. An NTFS partition is required to support the SYSVOL folder, and dcpromo will give you an immediate error message should one not be present. The use of NTFS is always desirable anyway so that you can configure the proper security including permissions on the server. Although a domain controller having an automatically assigned IP address is not the best approach, this will not prevent dcpromo from running, so answer A is wrong. A DNS server that supports service (SRV) resource records and the dynamic update protocol must be available. However, dcpromo will offer to install one for you if it cannot locate one, so answer B is wrong. You do not need a certificate server to be able to run dcpromo, so answer D is wrong. See the section “Creating the Forest Root Domain.” 12. B. The application directory partition replica is used to create replicas of the application directory partitions on the domain controllers to which Susan wants the data replicated. The ntdsutil tool is used to create and configure application directory partitions. Creating additional application directory partitions creates separate partitions without any link to the partition she has already created, so answer A is wrong. Specifying a reference domain merely changes which domain is the parent domain of the application directory partition, so answer C is wrong. She cannot use Active Directory Domains and Trusts to configure application directory partitions, so answer D is wrong. See the section “Application Directory Partitions.” 13. A. To seize the role of domain naming master, Marilyn needs to use the ntdsutil command-line utility. It is appropriate to seize this role in this scenario because the hard disk of the old computer has failed and it will have to be reinstalled after parts have arrived. Consequently, to Active Directory it will be an entirely new computer, and the old computer will never be online again. Role seizure is appropriate under these circumstances. Using Active Directory Domains and Trusts, Marilyn can transfer the role of domain naming master to another computer but not seize this role, so answer B is wrong. Active Directory Users and Computers can transfer any of the three domainwide operations master roles but cannot seize any of these roles, so answer C is wrong. Marilyn cannot specify the role of domain naming master during the promotion of another computer to domain controller, so answer D is wrong. See the section “Placement of Flexible Operations Master Roles.” 14. D. Universal group caching enables any domain controller that services a user’s logon to store universal group information the first time the user logs on. It enables users to log on without the need to contact the global catalog server that is located across the slow link. More frequent replication does not help because this does not replicate universal group information to a domain controller that is not a global catalog server; therefore, answer A is wrong. Changing the scope of universal groups to global might enable faster logons, but it would allow access to resources in the same domain only, so answer B is wrong. The RID master has nothing to do with universal groups, so answer C is wrong. See the section “Evaluating the Need to Enable Universal Group Caching.” 15. C. You can designate additional global catalog servers by using the Active Directory Sites and Services tool and going to the Properties dialog box for the NTDS Setting object. The Active Directory Domains and Trusts and the ntdsutil tool cannot designate global catalog servers, so answers A and B are wrong. Although you can have only one of each operations master roles in each domain, you can have as many global catalog servers as you want, so answer D is wrong. See the section “Global Catalog Servers.”
113
Apply Your Knowledge
Suggested Readings and Resources 1. Boswell, W. 2000. “Deploying Windows Server 2003 Domains,” Chapter 9 of Inside
Windows Server 2003. Boston: Addison-Wesley. 2. Microsoft Corporation. “Active Directory Branch Office Planning Guide.”
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/ branchoffice/default.asp. 3. Microsoft Corporation. “Active Directory Collection.” http://technet2.microsoft.com/
WindowsServer/en/library/6f8a7c80-45fc-4916-80d9-16e6d46241f91033.mspx?mfr =true. 4. Microsoft Corporation. “Designing the Site Topology.” http://technet2.microsoft.com/
WindowsServer/en/Library/d9a82c36-8e7f-491a-81ec-532f73ea70e71033.mspx?mfr =true. 5. Microsoft Corporation. “Enabling Advanced Windows Server 2003 Active Directory
Features.” http://technet2.microsoft.com/WindowsServer/en/Library/a4072f1a-4a464d54-85ed-d469fd6547aa1033.mspx?mfr=true. 6. Microsoft Corporation. “Installing Windows Server 2003 R2.” http://
technet2.microsoft.com/WindowsServer/en/library/c68efa05-c31e-42c9-aed60391130ceac21033.mspx?mfr=true. 7. Microsoft Corporation. “Introduction to Active Directory Application Mode.” http://
download.microsoft.com/download/5/7/a/57a8d3ed-89f7-4878-b945-b68c447f288a/ Adam.DOC. 8. Microsoft Corporation. “Microsoft Windows Server 2003 Deployment Kit, Designing
and Deploying Directory and Security Services.” http://technet2.microsoft.com/ WindowsServer/en/Library/d2ff1315-1712-48e4-acdc-8cae1b593eb11033.mspx?mfr=true. 9. Microsoft Corporation. “Migrating Windows NT Server 4.0 Domains to Windows
Server 2003 Active Directory.” http://www.microsoft.com/windowsserver2003/ evaluation/whyupgrade/nt4/nt4domtoad.mspx. 10. Microsoft Corporation. “Step by Step Guide to Implementing Domain Rename.”
http://download.microsoft.com/download/c/f/c/cfcbff04-97ca-4fca-9e8c-3a9c90a2a2e2/ Domain-Rename-Procedure.doc.
This page intentionally left blank
3
CHAPTER 3
Managing an Active Directory Infrastructure Objectives This chapter covers the following Microsoft-specified objectives for the Planning and Implementing an Active Directory Infrastructure and Managing and Maintaining an Active Directory Infrastructure sections of the Windows Server 2003 Active Directory Infrastructure exam: Implement an Active Directory directory service forest and domain structure . Establish trust relationships. Types of trust relationships might include external trusts, shortcut trusts, and crossforest trusts. . Business requirements might dictate the need to use more than one forest in your enterprise. You need to understand how to create trust relationships with external forests and when to use external trusts or forest trusts. You should also understand when to use shortcut trusts within multiple-domain forests.
Manage an Active Directory forest and domain structure . Manage trust relationships . Manage schema modifications . Add or remove a UPN suffix . This objective is intended to make sure that you can manage several components of the Active Directory forest and domain structure. You should be aware of the different types of trust relationships you can configure within and between forests. You should also understand how to work with the Active Directory schema and how to use UPN suffixes to facilitate management and user logon in multiple-domain enterprises.
Implement an Active Directory site topology . Configure site links . Configure preferred bridgehead servers . This objective evaluates your knowledge of how Active Directory handles networks that are distributed among different physical locations separated by low-speed WAN links. You need to understand how to create and configure sites, site link bridges, and bridgehead servers, and how the Inter-site Topology Generator and Knowledge Consistency Checker operate.
Manage an Active Directory site . Configure replication schedules . Configure site link costs . Configure site boundaries . This objective is intended to make sure that you know how to manage several components of the links between Active Directory sites. You should understand the factors that affect intrasite and intersite replication and when to modify replication schedules and site link costs.
Outline Introduction
118
Active Directory Trust Relationships
118
Active Directory Site Topology
155
Creating Sites
156
Configuring Sites
157
Trust Relationships Within an Active Directory Forest
119
Interforest Trust Relationships
120
Configuring Site Boundaries
Establishing Trust Relationships
122
Configuring Site Links
162
Creating an External Trust
122
Site Link Bridges
163
Creating a Forest Trust
128
Knowledge Consistency Checker
165
Creating a Shortcut Trust
130
Configuring Connection Objects
166
132
Inter-Site Topology Generator
168
132
Preferred Bridgehead Servers
169
Managing Trust Relationships Validating Trust Relationships
Adding Domain Controllers
Changing the Authentication Scope 134
Specifying a Licensing Server
157 158 159
Configuring Replication Schedules
171
Configuring Name Suffix Routing
134
Removing a Crossforest Trust Relationship
What Does Active Directory Replicate?
171
137
Active Directory Federation Services (ADFS)
How Does Active Directory Replication Work?
172
138
Intrasite Replication
173
Understanding Trust Relationships
140
Intersite Replication
174
Active Directory Forest and Domain Structure
141
Configuring Site Link Costs
Managing Schema Modifications
141
Manually Forcing Replication
Installing the Schema Snap-In
142
Using the Schema Snap-In
145
Deactivating Schema Objects Adding or Removing a UPN Suffix Understanding the Directory Forest and Domain Structure
149 151 155
Chapter Summary Key Terms Apply Your Knowledge
179 181 183 184 185
Exercises
185
Exam Questions
192
Answers to Exercises
199
Answers to Exam Questions
199
Suggested Readings and Resources
203
Study Strategies This chapter builds on the foundations of the preceding chapter by covering the administration of forests and sites, as well as the Active Directory schema. As you work your way through the chapter, you should pay attention to the following: . Understand the different types of trust relationships available and when you should use them. In addition, you should know the differences between incoming and outgoing trust directions. . Understand the importance of schema modifications and the potential consequences of making such modifications. . Understand the ways you can create sites, site links, and site link bridges, and the importance of the Knowledge Consistency Checker and the Inter-Site Topology Generator. . Understand the way Active Directory replication works and its importance in keeping all domain controllers up to date. . Know the differences between intrasite and intersite replication and the way site topology affects replication.
118
Chapter 3: Managing an Active Directory Infrastructure
Introduction Now that you have created an Active Directory forest with a child domain and configured global catalog servers and operations masters, it is time to examine several issues related to multisided and multiforest Active Directory deployments. In this chapter, we cover several issues related to management of trust relationships among Active Directory forests, as well as schema modifications. We then turn our attention to creating, configuring, and managing sites, including replication and site links.
Active Directory Trust Relationships Objective
Implement an Active Directory directory service forest and domain structure . Establish trust relationships. Types of trust relationships might include external trusts, shortcut trusts, and cross-forest trusts.
Prospects of globalization and international commerce have increased the possibility of companies operating multiforest network enterprise structures. Before we look at the intricacies of interforest trusts, we briefly review trust relationships as they exist within a single forest. Before we look at the intricacies of Windows 2000 and interforest trusts, we will briefly review trust relationships as they existed within NT 4.0. Those of you who are upgrading from Windows NT 4.0 will be familiar with the trust relationships used to allow users in one domain to access resources in another domain. You could configure one domain to trust another one so that users in the second domain could access resources in the first one. Windows NT 4.0 did not create any trust relationships by itself; administrators in both the trusting and trusted domains had to configure every trust relationship. The domain where the resources are located is referred to as the trusting or resource domain, and the domain where the accounts are kept is referred to as the trusted or accounts domain. Some characteristics of trust relationships in Windows NT 4.0 follow: . In a one-way trust relationship, the trusting domain makes its resources available to
the trusted domain (see Figure 3.1). With the appropriate permissions, a user from the trusted domain can access resources on the trusting domain. However, users in the trusting domain are unable to access resources in the trusted domain, unless a two-way trust is set up.
119
Active Directory Trust Relationships
In a one-way trust relationship, the trusting domain holds the resources that users in the trusted domain need to access.
FIGURE 3.1
Trusting Domain
Trusted Domain
. A trust relationship exists between only two domains. Each trust relationship has just
one trusting domain and just one trusted domain. . A two-way trust relationship between domains is simply the existence of two one-way
trusts in opposite directions between the domains. . In Windows NT 4.0, trust relationships were not transitive; that is, if Domain A trusts
Domain B and Domain B trusts Domain C, these relationships do not mean that Domain A automatically trusts Domain C. To have such a relationship, a third trust relationship must be set up whereby Domain A trusts Domain C (see Figure 3.2). If Domain A trusts Domain B and Domain B trusts Domain C in a nontransitive trust, Domain A does not trust Domain C. In a transitive trust relationship, Domain A automatically trusts Domain C through Domain B when the other two trusts are created.
FIGURE 3.2 B
A
B
C Non-transitive
A
C Transitive
Trust Relationships Within an Active Directory Forest Active Directory in Windows 2000 introduced the concept of two-way transitive trusts that flow upward through the domain hierarchy toward the tree root domain and across root domains of different trees in the same forest. This includes parent-child trusts between parent and child domains of the same tree and tree root trusts between the root domains of different trees in the same forest. Because of this arrangement, administrators no longer need to configure trust relationships between domains in a single forest.
120
Chapter 3: Managing an Active Directory Infrastructure
NOTE Managing Trust Relationships You should be aware that only members of the Domain Admins group can manage trusts.
In addition, Windows Server 2003 provides for another trust relationship called a shortcut trust. It is an additional trust relationship between two domains in the same forest, which optimizes the authentication process when a large number of users need to access resources in a different domain in the same forest. This capability is especially useful if the normal authentication path needs to cross several domains. Consider Figure 3.3 as an example.
A.com
A.A.com
B.com
B.A.com
B.B.com
Shortcut trusts are useful if the authentication path to another domain in the forest has to cross several domain boundaries.
FIGURE 3.3
C.A.A.com
C.B.B.com
Suppose that users in the C.A.A.com domain need to log on to the C.B.B.com domain, which is located in the second tree of the same forest. The authentication path must cross five domain boundaries to reach the C.B.B.com domain. If an administrator establishes a shortcut trust between the C.A.A.com and C.B.B.com domains, the logon process speeds up considerably. This is also true for shorter possible authentication paths such as C.A.A.com to B.A.com or B.A.com to B.B.com. This also facilitates the use of Kerberos when accessing resources located in another domain.
Interforest Trust Relationships Whenever there is need for accessing resources in a different forest, administrators have to configure trust relationships manually. Windows 2000 offers the capability to configure oneway, nontransitive trusts with similar properties to those mentioned previously, between domains in different forests. You have to configure every trust relationship between each
121
Active Directory Trust Relationships
domain in the different forests explicitly. If you need a two-way trust relationship, you have to manually configure each half of the trust separately. Windows Server 2003 makes it easier to configure interforest trust relationships. In this section, we study these trust relationships. In a nutshell, for forests that are operating at the Windows Server 2003 forest functional level, you can configure trusts that enable two-way transitive trust relationships between all domains in the relevant forests. If the forest is operating at any other functional level, you still need to configure explicit trusts as in Windows 2000. Windows Server 2003 introduces the following types of interforest trusts: . External trusts—These one-way trusts are individual trust relationships set up
between two domains in different forests, as could be done in Windows 2000. The forests involved might be operating at any forest functional level. You can use this type of trust if you need to enable resource sharing only between specific domains in different forests. You can also use this type of trust relationship between an Active Directory domain and a Windows NT 4.0 domain. . Forest trusts—As already mentioned, these trusts include complete trust relationships
between all domains in the relevant forests, thereby enabling resource sharing among all domains in the forests. The trust relationship can be either one-way or two-way. Both forests must be operating at the Windows Server 2003 forest functional level. The use of forest trusts offers several benefits: . They simplify resource management between forests by reducing the number of
external trusts needed for resource sharing. . They provide a wider scope of UPN authentications, which can be used across the
trusting forests. . They provide increased administrative flexibility by enabling administrators to split
collaborative delegation efforts with administrators in other forests. . Directory replication is isolated within each forest. Forestwide configuration modifi-
cations such as adding new domains or modifying the schema affect only the forest to which they apply, and not trusting forests. . They provide greater trustworthiness of authorization data. Administrators can use
both the Kerberos and NTLM authentication protocols when authorization data is transferred between forests. . Realm trusts—These are one-way nontransitive trusts that you can set up between an
Active Directory domain and a Kerberos V5 realm such as found in UNIX and MIT implementations.
122
Chapter 3: Managing an Active Directory Infrastructure
Establishing Trust Relationships This section examines creating two types of trust relationships with external forests: external trusts and forest trusts. We then look at the shortcut trust, which is the only configurable type of trust relationship between two domains in the same forest. Before you begin to create trust relationships, you must be aware of several prerequisites: . You must be a member of the Enterprise Admins group or the Domain Admins group
in the forest root domain. New to Windows Server 2003, you can also be a member of the Incoming Forest Trust Builders group on the forest root domain. This group has the rights to create one-way, incoming forest trusts to the forest root domain. If you hold this level of membership in both forests, you can set up both sides of an interforest trust at the same time. . You must ensure that DNS is properly configured so that the forests can recognize
each other. You might have to configure conditional forwarding to enable DNS servers in one forest to forward queries to DNS servers in the other forest so that resources are properly located. . In the case of a forest trust, both forests must be operating at the Windows Server
2003 forest functional level. Windows Server 2003 provides the New Trust Wizard to simplify the creation of all types of trust relationships. The following sections show you how to create these trust relationships.
Creating an External Trust Follow Step by Step 3.1 to create an external trust with a domain in another forest or a Windows NT 4.0 domain.
EXAM ALERT Trust Creation Can Be Tricky! Know the variations of the procedures so that you can answer questions about the troubleshooting of problems related to interforest access as they relate to the options available when creating trusts. In particular, be aware of the differences between the incoming and outgoing trust directions.
STEP BY STEP 3.1 Creating an External Trust 1. Click Start, Administrative Tools, Active Directory Domains and Trusts to open the Active Directory Domains and Trusts snap-in.
123
Active Directory Trust Relationships 2. In the console tree, right-click your domain name and choose Properties to display the Properties dialog box for the domain. 3. Select the Trusts tab. This tab contains fields listing domains trusted by this domain and domains that trust this domain. Initially these fields are blank, as in Figure 3.4.
You can manage trusts from the Trusts tab of a domain’s Properties dialog box.
FIGURE 3.4
4. Click New Trust to start the New Trust Wizard, as shown in Figure 3.5.
You can create new trust relationships by using the New Trust Wizard.
FIGURE 3.5
5. Click Next, and on the Trust Name page, type the name of the domain with which you want to create a trust relationship (see Figure 3.6). Then click Next.
124
Chapter 3: Managing an Active Directory Infrastructure
On the Trust Name page, you can enter the DNS or NetBIOS name of the domain with which you want to create a trust.
FIGURE 3.6
6. The Trust Type page, shown in Figure 3.7, offers you a choice between an external trust and a forest trust. Select External Trust and then click Next.
You can select the trust type required from the Trust Type page.
FIGURE 3.7
NOTE Trust Types If the forest functional level is not set to Windows Server 2003, the forest trust option will not appear. You might receive an option to create a realm trust or an external trust with a Windows domain.
7. The Direction of Trust page, shown in Figure 3.8, offers you a choice of the following three types of trusts:
125
Active Directory Trust Relationships . Two-Way—Creates a two-way trust. This type of trust allows users in both domains to be authenticated in each other’s domain. . One-Way: Incoming—Creates a one-way trust in which users in your (trusted) domain can be authenticated in the other (trusting) domain. Users in the other domain cannot be authenticated in your domain. . One-Way: Outgoing—Creates a one-way trust that users in the other (trusted) domain can be authenticated in your (trusting) domain. Users in your domain cannot be authenticated in the other domain.
The Direction of Trust page offers you options for creating one-way or two-way trusts.
FIGURE 3.8
8. Select a choice according to your network requirements and then click Next. 9. The Sides of Trust page, shown in Figure 3.9, allows you to complete both sides of the trust if you have the appropriate permissions in both domains. If this is so, select Both This Domain and the Specified Domain. Otherwise, select This Domain Only and then click Next.
The Sides of Trust page enables you to complete both sides of the trust if you have the appropriate permissions.
FIGURE 3.9
126
Chapter 3: Managing an Active Directory Infrastructure 10. If you selected This Domain Only on the Sides of Trust page, the Trust Password page appears, asking for a password for the trust. You must specify the same password when creating the trust in the other domain. Type and confirm a password that conforms to password security guidelines, click Next, and then skip to step 13. Ensure that you remember this password. 11. If you selected Both This Domain and the Specified Domain on the Sides of Trust page, the Outgoing Trust Properties—Local Domain page, shown in Figure 3.10, offers the following two choices in the scope of authentication for users in the trusted domain: . Domain-Wide Authentication—This option authenticates users from the trusted domain for all resources in the local domain. Microsoft recommends this option only for trusts within the same organization. . Selective Authentication—This option does not create any default authentication. You must grant access to each server that users need to access. Microsoft recommends this option for trusts that involve separate organizations, such as contractor relationships.
FIGURE 3.10 The Outgoing Trust Authentication Level-Local Domain page provides two choices of authentication scope for users in the trusted domain.
12. Select the appropriate type of authentication and then click Next. 13. The Trust Selections Complete page displays a list of the options that you have configured (see Figure 3.11). Review these settings to ensure that you have made the correct selections. If any setting is incorrect, click Back and correct it. Then click Next.
127
Active Directory Trust Relationships
FIGURE 3.11 The Trust Selections Complete page displays a review of the trust settings you specified.
14. The Trust Creation Complete page informs you that the trust relationship was successfully created. Click Next to finish the process. 15. The Confirm Outgoing Trust page asks whether you want to confirm the outgoing trust (see Figure 3.12). If you have configured the trust from the other side, click Yes, Confirm the Outgoing Trust. Otherwise, click No, Do Not Confirm the Outgoing Trust. Then click Next.
FIGURE 3.12 The Confirm Outgoing Trust page provides a chance to confirm the other side of the trust.
16. The Confirm Incoming Trust page asks whether you want to confirm the incoming trust. Choices are the same as on the previous page. If you want to confirm this trust, enter a username and password for an administrator account in the other domain. 17. The Completing the New Trust Wizard page verifies the confirmation of the trust from the other side. Click Finish.
128
Chapter 3: Managing an Active Directory Infrastructure 18. You are returned to the Trusts tab of the domain’s Properties dialog box (see Figure 3.13). The name of the domain with which you configured the trust now appears in one or both of the fields according to the trust type you created. Click OK to close this dialog box.
After you have created the trust relationship, the Trusts tab of the domain’s Properties dialog box shows the name of the trusted domain together with the trust type and transitivity. FIGURE 3.13
Creating a Forest Trust Recall that this type of trust can be created only between two Active Directory forests that are both operating at the Windows Server 2003 forest functional level. Follow Step by Step 3.2 to create a forest trust.
STEP BY STEP 3.2 Creating a Forest Trust 1. Make sure that the forest functional level of both forests is set to Windows 2003. See Chapter 2, “Planning and Implementing an Active Directory Infrastructure,” for details. 2. Follow steps 1–5 of Step by Step 3.1 to access the Trust Name page of the New Trust Wizard. 3. Type the name of the forest root domain with which you want to create a trust and then click Next. 4. On the Trust Type page, select Forest Trust and then click Next. 5. On the Direction of Trust page, select the appropriate direction for the trust and then click Next.
129
Active Directory Trust Relationships 6. On the Sides of Trust page, specify whether you want to create the trust for this domain only or for both this domain and the specified domain, and then click Next. 7. If you are creating the trust for both forests, specify a username and password for the specified forest and then click Next. If you are creating the trust for this forest only, specify the trust password that the administrator in the other forest will need to specify to complete the creation of the trust for her forest. Then click Next. 8. The Outgoing Trust Authentication Level—Local Forest page, shown in Figure 3.14, provides two choices that are similar to those provided by the Outgoing Trust Authentication Level—Local Domain page. Make a choice and then click Next.
FIGURE 3.14 The Outgoing Trust Authentication Level—Local Forest page provides two choices of authentication scope for users in the trusted forest.
9. The Trust Selections Complete page displays a list of the options that you have configured (refer to Figure 3.11). Review these settings to ensure that you have made the correct selections. If any setting is incorrect, click Back and correct it. Then click Next. 10. The Trust Creation Complete page informs you that the trust relationship was successfully created. Click Next to finish the process. 11. The Confirm Outgoing Trust page asks whether you want to confirm the outgoing trust (refer to Figure 3.12). If you have configured the trust from the other side, click Yes, Confirm the Outgoing Trust. Otherwise, click No, Do Not Confirm the Outgoing Trust. Then click Next. 12. The Confirm Incoming Trust page asks whether you want to confirm the incoming trust. Choices are the same as on the previous page. If you want to confirm this trust, enter a username and password for an administrator account in the other forest. 13. The Completing the New Trust Wizard page verifies the confirmation of the trust from the other side. Click Finish. 14. You are returned to the Trusts tab of the domain’s Properties dialog box (refer to Figure 3.13). The
130
Chapter 3: Managing an Active Directory Infrastructure name of the domain with which you configured the trust now appears in one or both of the fields according to the trust type you created. Click OK to close this dialog box.
EXAM ALERT Know When You Should Create a Forest Trust Know that all domains involved must be at the Windows Server 2003 domain functional level, and that the forests must be at the Windows 2003 forest functional level. Also remember that a forest trust is the simplest way to connect forests when access to resources in multiple domains is required, and when Kerberos authentication across the forest boundary is needed.
EXAM ALERT If You Rename a Domain, Cross-Forest Trusts Are Invalidated If a question informs you that a domain has been renamed and users are unable to access resources in an external forest, the reason for this problem is that both external and forest trust relationships are invalidated by the rename process. You need to delete and re-create the trust relationships following the renaming process.
Creating a Shortcut Trust Recall that this type of trust can be created between child domains in the same forest to expedite crossdomain authentication or resource access. Follow Step by Step 3.3 to create a shortcut trust relationship.
STEP BY STEP 3.3 Creating a Shortcut Trust 1. In Active Directory Domains and Trusts, right-click your domain and choose Properties. 2. On the domain’s Properties dialog box, select the Trusts tab and click New Trust to start the New Trust Wizard. 3. Click Next, and on the Trust Name and Password page, type the DNS name or NetBIOS name of the domain with which you want to establish a shortcut trust and then click Next. 4. On the Direction of Trust page (refer to Figure 3.8), choose the appropriate option (two-way, one-way incoming, or one-way outgoing) and then click Next. 5. On the Sides of Trust page, specify whether you want to create the trust for this domain only or for both this domain and the specified domain, and then click Next.
131
Active Directory Trust Relationships 6. If you are creating the trust for both domains, specify a username and password for an administrator account in the specified domain. If you are creating the trust for this domain only, specify the trust password that the administrator in the other domain will need to specify to complete the creation of the trust for her domain. Then click Next. 7. The Trust Selections Complete page displays a summary of the settings you have entered (refer to Figure 3.11). Click Back if you need to make any changes to these settings. Then click Next to create the trust. 8. The Trust Creation Complete page informs you that the trust relationship was successfully created. Click Next to configure the trust. 9. The Confirm Outgoing Trust page asks whether you want to confirm the other side of the trust. If you have created both sides of the trust, click Yes. Otherwise, click No and then click Next. 10. The Confirm Incoming Trust page asks whether you want to confirm the incoming trust. Choices are the same as on the previous page. If you want to confirm this trust, enter a username and password for an administrator account in the other domain. 11. The Completing the New Trust Wizard page informs you that you have created the trust. Click Finish to return to the Trusts tab of the domain’s Properties dialog box (refer to Figure 3.13). The name of the domain with which you configured the trust now appears in one or both of the fields according to the trust type you created. Click OK to close this dialog box.
If you have created only one side of the trust, an administrator in the other domain must repeat this procedure to create the trust from her end. She will have to enter the trust password you specified in this procedure.
A Separate Research Forest A major aircraft manufacturer landed a contract with NASA to design one module of a prototype spacecraft for a manned Mars mission. Realizing that the research necessary to complete this project successfully required a high level of security, management asked the senior network administrator to set up a separate forest in the organization’s Windows Server 2003 Active Directory design. For the project to succeed, researchers needed access to certain data stored in the organization’s existing forest. Their user accounts would be in the new forest. Users in the existing forest did not need to access data in the research forest. The administrator had to choose a trust model that would enable the appropriate levels of access. With these needs in mind, the administrator decided to implement a one-way external trust relationship in which the existing forest trusted the research forest. It was then possible to place the researchers who needed access into a group that could be granted access to the appropriate resources in the existing forest. Because the trust relationship was one-way, no access in the opposite direction was possible. We take a further look at the use of groups to grant crossforest access in Chapter 6, “Implementing User, Computer, and Group Strategies.”
132
Chapter 3: Managing an Active Directory Infrastructure
Managing Trust Relationships Objective
Manage an Active Directory forest and domain structure . Manage trust relationships
After you have created a crossforest trust, the following limited set of configuration options is available from the trust’s Properties dialog box: . Validate Trust Relationships—This option enables you to verify that a trust has been
properly created and that the forests can communicate with each other. . Change the Authentication Scope—This option enables you to change the selection
of domainwide authentication or selective authentication that you made during creation of the trust, should you need to modify access control to the trusting forest’s resources. . Configure Name Suffix Routing—This option provides a mechanism that you can
use to specify how authentication requests are routed across Windows Server 2003 forests. It is available only when forest trusts are used.
Validating Trust Relationships To access the trust’s Properties dialog box and validate a trust relationship, follow Step by Step 3.4.
STEP BY STEP 3.4 Validating a Trust Relationship 1. In Active Directory Domains and Trusts, right-click your domain name and choose Properties. 2. On the Trusts tab of the domain’s Properties dialog box, select the name of the other domain or forest and click Properties. 3. This action displays the trust’s Properties dialog box, as shown in Figure 3.15.
133
Active Directory Trust Relationships
FIGURE 3.15 The General tab of the Properties dialog box of the other domain provides information on the trust’s properties.
4. To validate the trust relationship, click Validate. 5. If the trust is in place and active, you receive a confirmation message box, as shown in Figure 3.16. Otherwise, you receive an error message, such as the one in Figure 3.17.
FIGURE 3.16
This message box informs you that the trust is
valid.
FIGURE 3.17
If the trust cannot be validated, an error message such as this informs you of the problem.
134
Chapter 3: Managing an Active Directory Infrastructure
Changing the Authentication Scope Follow Step by Step 3.5 to change the authentication scope that you set when you create the trust.
STEP BY STEP 3.5 Changing the Authentication Scope of a Trust Relationship 1. Select the Authentication tab of the trust’s Properties dialog box, as shown in Figure 3.18. 2. Select either Domain-Wide Authentication or Selective Authentication (as already described in Step by Step 3.1) and then click OK.
FIGURE 3.18
The Authentication tab of a trust’s Properties dialog box allows you to change the trust’s authenti-
cation scope.
Configuring Name Suffix Routing When you initially create a forest trust, all unique name suffixes are routed by default. A unique name suffix is a name suffix within a forest, such as a User Principal Name (UPN) suffix, Service Principal Name (SPN) suffix, or domain name system (DNS) forest or tree name that is not subordinate to any other name suffix. For example, the DNS forest name quepublishing.com is a unique name suffix within the quepublishing.com forest. Consequently, name suffixes in one forest do not exist in another forest.
135
Active Directory Trust Relationships
Name suffix routing is a mechanism that can manage the routing of authentication requests across Windows Server 2003 forests connected by forest trust relationships. It enables name suffixes that do not exist in one forest to be used to route authentication requests to another forest. This includes child name suffixes. As a result, when you view name suffixes in the Name Suffix Routing tab of the domain’s Properties dialog box, as shown in Figure 3.19, they are prefixed by * to indicate that they refer to the parent domain and all child domains. If you add new child domains to either forest, they automatically inherit the name suffix routing properties of other domains in the forest. After you add a new name suffix and validate the trust, it appears on the Name Suffixes tab with a status (shown on the Routing column) of Disabled. The Status column indicates New for a newly created name suffix.
FIGURE 3.19 The Name Suffix Routing tab of a trust’s Properties dialog box allows you to enable or disable name suffix routing between forests.
You might have to disable name suffix routing to prevent certain authentication requests from flowing across the forest trust. You might also have to enable name suffix routing for additional name suffixes you have created or to exclude a child name suffix from routing. Follow Step by Step 3.6 to configure these name suffix routing options.
STEP BY STEP 3.6 Configuring Name Suffix Routing 1. On the Name Suffix Routing tab of the trust’s Properties dialog box, select the suffix whose routing status is to be changed and then click Enable or Disable as required. 2. The routing status in the Routing column changes. In the case of enabling a new name suffix routing, the New entry disappears from the Status column.
136
Chapter 3: Managing an Active Directory Infrastructure 3. To exclude a child name suffix from routing, select the parent suffix and click Edit to display the Edit domain name dialog box (see Figure 3.20).
FIGURE 3.20 You can exclude a name suffix that does not exist in the specified forest from routing by specifying it on the Edit domain name dialog box.
4. To exclude the name suffix, click Add. On the Add Excluded Name Suffix dialog box, type the name of the suffix and then click OK (see Figure 3.21).
FIGURE 3.21 The