Reverting to snapshot tends to nuke the time stamps. Nuking timestamps tosses you into host isolation mode. Host isolation mode is bad, time consuming and painful.
We have a full lab (with a restored AD environment) where we do testing and once it's in production, we open a ticket with MS is something goes wrong. The only time something goes wrong is when our AD team forgets, snapshots a DC and then reverts it. On Fri, Jun 8, 2012 at 12:32 PM, David Lum <[email protected]> wrote: > In this day and age of VM’s, what would be the simplest way to test and > possibly roll back a schema extension? Would this work?**** > > ** ** > > **1. **Power down all DC’s**** > > **2. **Snapshot schema master**** > > **3. **Power up schema master**** > > **4. **Extend schema **** > > **5. **Smoke test **** > > **a. **If there are failures revert to snapshot**** > > **b. **If all checks out OK power up remaining DC’s**** > > *David Lum* > Systems Engineer // NWEATM > Office 503.548.5229 //* *Cell (voice/text) 503.267.9764**** > > ** ** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
