Advanced Schema Copying/Repeating

  • 266 Views
  • Last Post 22 June 2016
a-ko posted this 21 June 2016

All, So I’m doing some schema stuff to be able to reproduce our production schema in development sandboxes as required. We currently use some of the Exchange Schema attributes for production use (rather than having created our own schema extensions), and I’d like to be able to quickly toss up sandboxes that include those object definitions without necessarily having to run the Exchange Setup every time in each of those domains. The goal here is to include a suite of scripts and LDF files which reproduce our production user domain on the fly, as needed. I am following along to https://technet.microsoft.com/en-us/magazine/2009.04.schema.aspx So I figured I’d take a snapshot of the existing schema (ldifde.exe -f export.ldf -d “CN=Schema,CN=Configuration,DC=whatever,DC=lol”) This gave me a large schema dump. So when editing the schema export, I’m noticing a lot of domain-specific information about the objects—which isn’t quite what I want. You can use the “-c” option to have it on-the-fly change the DN information, but what about the objectGUID, whencreated,whenchanged,uSNCreated? Does the import just drop those and re-create per domain? Note: Working Exchange in these domains isn’t necessary, though if that’s possible that’d be awesome J I just need a copy of the production schema to be able to toss around as needed. We’ve also got Skype, Sharepoint, etc….and we may at some point needed additional, custom extensions. Would anyone have any idea on recommendations? Example: Export from existing AD dn: CN=ms-Exch-Calendar-Repair-Log-File-Size-Limit,CN=Schema,CN=Configuration,DC=corp,DC=domain,DC=comchangetype: addobjectClass: topobjectClass: attributeSchemacn: ms-Exch-Calendar-Repair-Log-File-Size-LimitdistinguishedName:  CN=ms-Exch-Calendar-Repair-Log-File-Size-Limit,CN=Schema,CN=Configuration,DC=c orp,DC=domain,DC=cominstanceType: 4whenCreated: 20151125181722.0ZwhenChanged: 20151125181722.0ZuSNCreated: 18214attributeID: 1.2.840.113556.1.4.7000.102.51342attributeSyntax: 2.5.5.9isSingleValued: TRUEuSNChanged: 18214showInAdvancedViewOnly: TRUEadminDisplayName: ms-Exch-Calendar-Repair-Log-File-Size-LimitadminDescription: ms-Exch-Calendar-Repair-Log-File-Size-LimitoMSyntax: 2searchFlags: 0lDAPDisplayName: msExchCalendarRepairLogFileSizeLimitname: ms-Exch-Calendar-Repair-Log-File-Size-LimitobjectGUID:: Wi6aeoMXg020k/sjNl0pJg==schemaIDGUID:: 4Fp3cvGYfUajU2SfC/LA9g==isMemberOfPartialAttributeSet: FALSEobjectCategory:  CN=Attribute-Schema,CN=Schema,CN=Configuration,DC=corp,DC=domain,DC=comdSCorePropagationData: 16010101000000.0ZmsDS-IntId: -2016859933 Corresponding attribute entry in Exchange Schema Extensions with the 2013 CU12 Setup (setup\data\postexchange2003_schema53.ldf) dn: CN=ms-Exch-Calendar-Repair-Log-File-Size-Limit,<SchemaContainerDN>changetype: ntdsSchemaAddadminDescription: ms-Exch-Calendar-Repair-Log-File-Size-LimitadminDisplayName: ms-Exch-Calendar-Repair-Log-File-Size-LimitattributeID: 1.2.840.113556.1.4.7000.102.51342attributeSyntax: 2.5.5.9isMemberOfPartialAttributeSet: FALSEisSingleValued: TRUElDAPDisplayName: msExchCalendarRepairLogFileSizeLimitname: ms-Exch-Calendar-Repair-Log-File-Size-LimitoMSyntax: 2objectCategory: CN=Attribute-Schema,<SchemaContainerDN>objectClass: attributeSchemaschemaIdGuid:: 4Fp3cvGYfUajU2SfC/LA9g==searchFlags: 0

Order By: Standard | Newest | Votes
michael1 posted this 22 June 2016

You can copy the schema files from an Exchange installation ISO/ZIP and apply them yourself.

 

The attributes you mention are created as part of the schema creation/application itself.

 

show

mcasey posted this 21 June 2016

Have you looked at Schema Analyzer? https://technet.microsoft.com/en-us/magazine/2009.04.schema.aspx On Jun 21, 2016 5:10 PM, "Mike Cramer" <mike.cramer@xxxxxxxxxxxxxxxx> wrote:
All, So I’m doing some schema stuff to be able to reproduce our production schema in development sandboxes as required. We currently use some of the Exchange Schema attributes for production use (rather than having created our own schema extensions), and I’d like to be able to quickly toss up sandboxes that include those object definitions without necessarily having to run the Exchange Setup every time in each of those domains. The goal here is to include a suite of scripts and LDF files which reproduce our production user domain on the fly, as needed. I am following along to https://technet.microsoft.com/en-us/magazine/2009.04.schema.aspx So I figured I’d take a snapshot of the existing schema (ldifde.exe -f export.ldf -d “CN=Schema,CN=Configuration,DC=whatever,DC=lol”) This gave me a large schema dump. So when editing the schema export, I’m noticing a lot of domain-specific information about the objects—which isn’t quite what I want. You can use the “-c” option to have it on-the-fly change the DN information, but what about the objectGUID, whencreated,whenchanged,uSNCreated? Does the import just drop those and re-create per domain? Note: Working Exchange in these domains isn’t necessary, though if that’s possible that’d be awesome J I just need a copy of the production schema to be able to toss around as needed. We’ve also got Skype, Sharepoint, etc….and we may at some point needed additional, custom extensions. Would anyone have any idea on recommendations? Example: Export from existing AD dn: CN=ms-Exch-Calendar-Repair-Log-File-Size-Limit,CN=Schema,CN=Configuration,DC=corp,DC=domain,DC=comchangetype: addobjectClass: topobjectClass: attributeSchemacn: ms-Exch-Calendar-Repair-Log-File-Size-LimitdistinguishedName:  CN=ms-Exch-Calendar-Repair-Log-File-Size-Limit,CN=Schema,CN=Configuration,DC=c orp,DC=domain,DC=cominstanceType: 4whenCreated: 20151125181722.0ZwhenChanged: 20151125181722.0ZuSNCreated: 18214attributeID: 1.2.840.113556.1.4.7000.102.51342attributeSyntax: 2.5.5.9isSingleValued: TRUEuSNChanged: 18214showInAdvancedViewOnly: TRUEadminDisplayName: ms-Exch-Calendar-Repair-Log-File-Size-LimitadminDescription: ms-Exch-Calendar-Repair-Log-File-Size-LimitoMSyntax: 2searchFlags: 0lDAPDisplayName: msExchCalendarRepairLogFileSizeLimitname: ms-Exch-Calendar-Repair-Log-File-Size-LimitobjectGUID:: Wi6aeoMXg020k/sjNl0pJg==schemaIDGUID:: 4Fp3cvGYfUajU2SfC/LA9g==isMemberOfPartialAttributeSet: FALSEobjectCategory:  CN=Attribute-Schema,CN=Schema,CN=Configuration,DC=corp,DC=domain,DC=comdSCorePropagationData: 16010101000000.0ZmsDS-IntId: -2016859933 Corresponding attribute entry in Exchange Schema Extensions with the 2013 CU12 Setup (setup\data\postexchange2003_schema53.ldf) dn: CN=ms-Exch-Calendar-Repair-Log-File-Size-Limit,<SchemaContainerDN>changetype: ntdsSchemaAddadminDescription: ms-Exch-Calendar-Repair-Log-File-Size-LimitadminDisplayName: ms-Exch-Calendar-Repair-Log-File-Size-LimitattributeID: 1.2.840.113556.1.4.7000.102.51342attributeSyntax: 2.5.5.9isMemberOfPartialAttributeSet: FALSEisSingleValued: TRUElDAPDisplayName: msExchCalendarRepairLogFileSizeLimitname: ms-Exch-Calendar-Repair-Log-File-Size-LimitoMSyntax: 2objectCategory: CN=Attribute-Schema,<SchemaContainerDN>objectClass: attributeSchemaschemaIdGuid:: 4Fp3cvGYfUajU2SfC/LA9g==searchFlags: 0

Close