
Changes to Existing Class-Schema and Attribute-Schema Classes
For information about changes to the Active Directory schema, refer to the .ldf files. The .ldf files are located in the \amd64\Setup\Data\ folder on the Exchange 2007 installation DVD.
Modified Active Directory Schema Classes
All Active Directory schema class modifications support the setting of new attributes on existing objects. The addition of the delivContLength attribute to Site-Link objects supports a new feature that allows for the limiting of the size of messages that are sent between Active Directory sites. Only one change affects a non-Exchange object.
The following table lists the modifications to the Active Directory schema classes.
Active Directory schema class modifications
|
Class
|
Change
|
Attribute/Class
|
| ms-Exch-Mobile-Mailbox-Policy | add: mayContain | msExchMobileAdditionalFlags |
| ms-Exch-Mobile-Mailbox-Policy | add: mayContain | msExchMobileAllowBluetooth |
| ms-Exch-Mobile-Mailbox-Policy | add: mayContain | msExchMobileAllowSMIMEEncryptionAlgorithmNegotiation |
| ms-Exch-Mobile-Mailbox-Policy | add: mayContain | msExchMobileApprovedApplicationList |
| ms-Exch-Mobile-Mailbox-Policy | add: mayContain | msExchMobileMaxCalendarAgeFilter |
| ms-Exch-Mobile-Mailbox-Policy | add: mayContain | msExchMobileMaxEmailAgeFilter |
| ms-Exch-Mobile-Mailbox-Policy | add: mayContain | msExchMobileMaxEmailBodyTruncationSize |
| ms-Exch-Mobile-Mailbox-Policy | add: mayContain | msExchMobileMaxEmailHTMLBodyTruncationSize |
| ms-Exch-Mobile-Mailbox-Policy | add: mayContain | msExchMobileMinDevicePasswordComplexCharacters |
| ms-Exch-Mobile-Mailbox-Policy | add: mayContain | msExchMobileRequireEncryptionSMIMEAlgorithm |
| ms-Exch-Mobile-Mailbox-Policy | add: mayContain | msExchMobileRequireSignedSMIMEAlgorithm |
| ms-Exch-Mobile-Mailbox-Policy | add: mayContain | msExchMobileUnapprovedInROMApplicationList |
| ms-Exch-Organization-Container | add: mayContain | msExchForeignForestPublicFolderAdminUSGSid |
| ms-Exch-Storage-Group | add: mayContain | msExchStandbyCopyMachines |
| ms-Exch-Virtual-Directory | add: mayContain | msExchInternalNLBBypassHostName |
| Site-Link | add: mayContain | delivContLength |
Modified Active Directory Schema Attributes
The following table lists the modified Active Directory schema attributes.
Active Directory schema attribute modifications
|
Attribute
|
Change
|
Value
|
| ms-Exch-Schema-Version-Pt | replace: rangeUpper | 11116 |
| ms-Exch-Resource-Property-Schema | replace: OID | 1.2.840.113556.1.4.7000.102.50881 |
Exchange 2007 uses the ms-Exch-Schema-Version-Pt attribute to keep track of the Exchange schema version that is installed. This attribute is not actually set on any objects. The rangeUpper for the initial release of Exchange 2007 is 10637; the value for Exchange 2007 SP1 is 11116. This attribute is always modified with changes to the Exchange schema.
An object identifier (also known as OID) collision exists between an attribute that is used in the Defense Messaging System (DMS) version of Microsoft Exchange Server 2003 and the ms-Exch-Resource-Property-Schema attribute in the initial version of Exchange 2007. If you are installing Exchange 2007 SP1 in your forest, this collision will not affect you. If you have installed Exchange 2007 in your forest, the collision will be resolved automatically when you install Exchange 2007 SP1.
The ms-Exch-Resource-Property-Schema attribute is an optional attribute that can be set only on the Resource Schema object in the Global Settings for an Exchange 2007 organization. When you install Exchange 2007 SP1, Setup will detect whether Exchange 2007 has already been installed in the forest and whether this attribute already exists on the Resource Schema object. If the attribute exists, its value will be preserved and then set back on the Resource Schema object after the Active Directory schema is corrected.
The ms-Exch-Resource-Property-Schema attribute lets an administrator define custom properties for resource mailboxes. The custom properties can be one of two types: Rooms and Equipment. For example, an administrator can define Room/16 chairs and Room/8 chairs as custom properties. Resource owners can then select from the custom properties list to identify features of the room. You can use the set-ResourceConfig cmdlet in the Exchange Management Shell to set up the list of available custom properties. You can query defined resources by using the get-ResourceConfig cmdlet in the Exchange Management Shell. Note that loss of the property schema does not affect any properties that are already set on resource mailboxes; it only affects the list of properties that you can select from.
The object identifier for the ms-Exch-Resource-Property-Schema attribute in the initial release of Exchange 2007 is 1.2.840.113556.1.4.7000.102.50329. If it is necessary, Exchange 2007 SP1 Setup will import update_ResourcePropertySchema.ldf to deactivate the attribute and create a new attribute of the same name with a new object identifier of 1.2.840.113556.1.4.7000.102.50881. The new attribute will be functionally identical to the old one. If you have not installed Exchange 2007 in your forest, Exchange 2007 SP1 will create the attribute with the correct object identifier.
No changes have been made to the ADAM schema for the Exchange servers that are running the Edge Transport server role in this release, except for an increase in the ms-Exch-Schema-Version-Pt rangeUpper value to match the Active Directory version.
Exchange-Specific Schema Classes
Exchange 2007 SP1 schema classes and attributes contain no modifications.