All: It has been my practice for years that whenever I perform schema updates I 1) disable outbound replication on the schema master, 2) perform the schema update, 3) verify the rangeupper value for whatever I am updating, 4) re-enable outbound replication, 5) verify rangeupper on remaining domain controllers. I figure that this method helps to isolate the schema master from replicating a bad schema update to all other Domain Controller. The last thing that is written is the rangeupper version number if the update was successful. If the schema update were to go badly, I can seize the roll on another DC and shutdown the bad DC and rebuild. But if the bad schema update were to replicate to all other DC’s then I have a big problem.
There has been some discussion between me and my colleagues about disabling the outbound replication and that Microsoft advises to not do this. I have found this over at ASKDS blog site that make the statement to not disable but I am not sur eif this is the official stance of Microsoft or based upon experience. https://blogs.technet.microsoft.com/askds/2010/04/16/friday-mail-sack-i-live-again-edition/
I would like to get your opinion on the matter since there are several of you who ARE the BOOK and have debunked some incorrect MS statements in the past. I am looking for the correct answer and will admit if I am wrong on the matter. Brian Britt