|
exchange
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Disaster Recovery Procedures from Exchange 2007 preparations.Having read MS White Paper: Preparing Active Directory for Exchange 2007, and other articles on preparing for exchange 2007 (PrepareLegacyExchangePermissions, PrepareSchema etc..), one article recommends isolating the DC from replicating schema changes to other DCs. My first question is can this be performed against ANY Domain controller, or must it be the FSMO role master. Secondly, if replication is temporarily disabled from the Domain controller against which the changes are made, in the event that a rollback is necessary, what procedures do I follow (specifically!) in order to bring the DC back to its previous state, without fear that these changes are spread throughout AD. Any help gratefully received. Cheers, John. Please post a reference to this recommendation so we can view it in context.
-- Show quoteEd Crowley MVP - Exchange "Protecting the world from PSTs and brick backups!" "jprstokato" <jprstok***@discussions.microsoft.com> wrote in message news:C29051A3-3711-40E0-84D2-13B7AACB8144@microsoft.com... > Hi, > > Having read MS White Paper: Preparing Active Directory for Exchange 2007, > and other articles on preparing for exchange 2007 > (PrepareLegacyExchangePermissions, PrepareSchema etc..), one article > recommends isolating the DC from replicating schema changes to other DCs. > My first question is can this be performed against ANY Domain controller, > or > must it be the FSMO role master. > Secondly, if replication is temporarily disabled from the Domain > controller > against which the changes are made, in the event that a rollback is > necessary, what procedures do I follow (specifically!) in order to bring > the > DC back to its previous state, without fear that these changes are spread > throughout AD. > > Any help gratefully received. > > Cheers, > > John.
http://technet.microsoft.com/en-us/library/bb288907.aspx
Show quote "Ed Crowley [MVP]" wrote:
> Please post a reference to this recommendation so we can view it in context. > -- > Ed Crowley > MVP - Exchange > "Protecting the world from PSTs and brick backups!" > > "jprstokato" <jprstok***@discussions.microsoft.com> wrote in message > news:C29051A3-3711-40E0-84D2-13B7AACB8144@microsoft.com... > > Hi, > > > > Having read MS White Paper: Preparing Active Directory for Exchange 2007, > > and other articles on preparing for exchange 2007 > > (PrepareLegacyExchangePermissions, PrepareSchema etc..), one article > > recommends isolating the DC from replicating schema changes to other DCs. > > My first question is can this be performed against ANY Domain controller, > > or > > must it be the FSMO role master. > > Secondly, if replication is temporarily disabled from the Domain > > controller > > against which the changes are made, in the event that a rollback is > > necessary, what procedures do I follow (specifically!) in order to bring > > the > > DC back to its previous state, without fear that these changes are spread > > throughout AD. > > > > Any help gratefully received. > > > > Cheers, > > > > John. > > > I do not see where that is recommended in that article, just that it is
possible. -- Show quoteEd Crowley MVP - Exchange "Protecting the world from PSTs and brick backups!" "jprstokato" <jprstok***@discussions.microsoft.com> wrote in message news:28CCFDA5-29F8-43B7-92BD-DE70A5BF1373@microsoft.com... > http://technet.microsoft.com/en-us/library/bb288907.aspx > > > "Ed Crowley [MVP]" wrote: > >> Please post a reference to this recommendation so we can view it in >> context. >> -- >> Ed Crowley >> MVP - Exchange >> "Protecting the world from PSTs and brick backups!" >> >> "jprstokato" <jprstok***@discussions.microsoft.com> wrote in message >> news:C29051A3-3711-40E0-84D2-13B7AACB8144@microsoft.com... >> > Hi, >> > >> > Having read MS White Paper: Preparing Active Directory for Exchange >> > 2007, >> > and other articles on preparing for exchange 2007 >> > (PrepareLegacyExchangePermissions, PrepareSchema etc..), one article >> > recommends isolating the DC from replicating schema changes to other >> > DCs. >> > My first question is can this be performed against ANY Domain >> > controller, >> > or >> > must it be the FSMO role master. >> > Secondly, if replication is temporarily disabled from the Domain >> > controller >> > against which the changes are made, in the event that a rollback is >> > necessary, what procedures do I follow (specifically!) in order to >> > bring >> > the >> > DC back to its previous state, without fear that these changes are >> > spread >> > throughout AD. >> > >> > Any help gratefully received. >> > >> > Cheers, >> > >> > John. >> >> >> To roll back, you simply "throw away" the DC. Wipe the disk and remove it
from the domain, rebuild Windows, promote it, and allow the old data to replicate to it. I don't think you would want the FSMO roles in this DC except for the schema master, which would be required. In the case of a rollback, you'd have to seize the schema master role onto another DC. -- Show quoteEd Crowley MVP - Exchange "Protecting the world from PSTs and brick backups!" "jprstokato" <jprstok***@discussions.microsoft.com> wrote in message news:C29051A3-3711-40E0-84D2-13B7AACB8144@microsoft.com... > Hi, > > Having read MS White Paper: Preparing Active Directory for Exchange 2007, > and other articles on preparing for exchange 2007 > (PrepareLegacyExchangePermissions, PrepareSchema etc..), one article > recommends isolating the DC from replicating schema changes to other DCs. > My first question is can this be performed against ANY Domain controller, > or > must it be the FSMO role master. > Secondly, if replication is temporarily disabled from the Domain > controller > against which the changes are made, in the event that a rollback is > necessary, what procedures do I follow (specifically!) in order to bring > the > DC back to its previous state, without fear that these changes are spread > throughout AD. > > Any help gratefully received. > > Cheers, > > John.  |
|||||||||||||||||||||||
Other interesting topics