To successfully complete the migration process, you must update the schema on the Source Server if it is running either Windows SBS 2003 or Windows Server 2003.
Note: This is general best practice guidance for implementing schema extensions, not the testing of their functionality.
(Please be sure you isolate your recovery environment when you test forest recovery).
Please refer to the errata for this document, which may include some normative corrections.
As with any change to the Active Directory infrastructure, the two primary concerns around implementing a schema extension are: 1. However, having personally helped customers with dozens of schema updates, I can honestly say that staying within best practices isn’t that hard, and definitely makes implementation less risky and less stressful.
Have you tested it, so you can be reasonably sure it will behave as expected when implemented in production? The reason this question gets so sticky is that customers either don’t have a test environment, or they don’t have a test environment that reasonably reflects the production environment.
This means that, if you have SP1 or higher running on your DC’s, then you don’t need to run adprep /domainprep.
Before starting any schema update, it is important to Check date and time of last successfull replication.
This document is also available in these non-normative formats: XML and XHTML with visible change markup. Copyright © 2004 XML Schema Part 0: Primer is a non-normative document intended to provide an easily readable description of the XML Schema facilities, and is oriented towards quickly understanding how to create schemas using the XML Schema language.
XML Schema Part 1: Structures and XML Schema Part 2: Datatypes provide the complete normative description of the XML Schema language.
#demandglobalchange // https:// Updating from 2003 to 2003 R2 & implementing Exchange are 2 common administrative tasks which both require a schema update.