No, the schema is replicated to ALL DCs in a forest. I generally VM the schema master after ensuring that it's also a GC (or I create a new GC and move the schema master role to it).
From: David Lum [mailto:david....@nwea.org] Sent: Monday, December 14, 2009 10:03 AM To: NT System Admin Issues Subject: RE: Extend Schema Thanks. My production environment has 2003 (not R2) Domain functional level and has Exchange 2007 in it. If I VM the production DC that should be enough, correct? Actually my setup is ROOT.PVT and I also have SUB.ROOT.PVT, and all my devices and systems are in SUB.ROOT.PVT, I need to VM a ROOT.PVT DC and a SUB.ROOT.PVT DC to make the test worthwhile, correct? Dave From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Monday, December 14, 2009 6:50 AM To: NT System Admin Issues Subject: RE: Extend Schema You have to do an authoritative forest restore. To put it simply, it's a non-trivial operation. Therefore: test in a lab and isolate the server where you are doing the schema updates until you are certain they succeeded. There are several times I can remember problems with schema updates: inetOrgPerson in Exchange 2003 vs. Windows 2003 (remember that Exchange 2003 could be installed on Windows 2000), Services For Unix UID attributes, etc. From: David Lum [mailto:david....@nwea.org] Sent: Monday, December 14, 2009 9:42 AM To: NT System Admin Issues Subject: Extend Schema One you extend an AD Schema, is there really any way to roll back? Has anyone ever heard of needing to do so? David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
