8 Appendix C: Product Behavior
The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.
Microsoft Exchange Server 2007
Microsoft Exchange Server 2010
Microsoft Exchange Server 2013
Microsoft Exchange Server 2016
Microsoft Exchange Server 2019
Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.
Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.
<1> Section 2.2.3.1: Exchange 2007, the initial release version of Exchange 2010, and Microsoft Exchange Server 2010 Service Pack 1 (SP1) do not include the DateTimePrecision element.
<2> Section 2.2.3.7: Exchange 2007 and Exchange 2010 do not use the ManagementRole element.
<3> Section 2.2.3.9: Exchange 2007 does not include the RequestServerVersion element. Microsoft Exchange Server 2007 Service Pack 1 (SP1) includes a fixed attribute with a value equal to Exchange2007_SP1. The initial release version of Exchange 2010 includes a fixed attribute with a value equal to Exchange2010. Exchange 2010 SP1 includes a fixed attribute with a value equal to Exchange2010_SP1. Microsoft Exchange Server 2010 Service Pack 2 (SP2) includes a fixed attribute with a value equal to Exchange2010_SP2.
<4> Section 2.2.4.4: Exchange 2007, Exchange 2010,and the initial release of Exchange 2013 do not support the ApplyConversationActionResponseMessageType complex type. This type was introduced in Microsoft Exchange Server 2013 Service Pack 1 (SP1) .
<5> Section 2.2.4.6: Exchange 2007, Exchange 2010, and Exchange 2013 do not support the ArrayofDistinguishedFolderIdType complex type.
<6> Section 2.2.4.8: Exchange 2007 and Exchange 2010 do not use the ArrayOfHighlightTermsType complex type.
<7> Section 2.2.4.10: Exchange 2007 does not return the items of type t:ItemType as a t:MessageType type. Exchange 2007 SP1 starts to return the items of type t:ItemType as a t:MessageType type.
<8> Section 2.2.4.10: Exchange 2007, Exchange 2010, and Exchange 2013 do not support the RoleMember element.
<9> Section 2.2.4.10: Exchange 2007, Exchange 2010, and Exchange 2013 do not support the Network element.
<10> Section 2.2.4.10: Exchange 2007, Exchange 2010, and Exchange 2013 do not support the Person element. Exchange 2016 and Exchange 2019 return Item element with type t:AbchPersonItemType instead of Person element.
<11> Section 2.2.4.10: Exchange 2007, Exchange 2010, and Exchange 2013 do not support the Booking element.
<12> Section 2.2.4.10: Exchange 2007, Exchange 2010, and Exchange 2013 do not support the XrmOrganization element.
<13> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the UpdateItemInRecoverableItemsResponseMessage element.
<14> Section 2.2.4.12: Exchange 2007 and the initial release version of Exchange 2010 do not include the EmptyFolderResponseMessage element.
<15> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the CreateFolderPathResponseMessage element.
<16> Section 2.2.4.12: Exchange 2007 and the initial release version of Exchange 2010 do not include the UploadItemsResponseMessage element.
<17> Section 2.2.4.12: Exchange 2007 and the initial release version of Exchange 2010 do not include the ExportItemsResponseMessage element.
<18> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the MarkAllItemsAsReadResponseMessage element.
<19> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetClientAccessTokenResponseMessage element.
<20> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetClientExtensionResponseMessage element.
<21> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the SetClientExtensionResponseMessage element.
<22> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetOMEConfigurationResponseMessage element.
<23> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the SetOMEConfigurationResponseMessage element.
<24> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the ArchiveItemResponseMessage element.
<25> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not include the GetStreamingEventsResponseMessage element.
<26> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetRemindersResponse and PerformReminderActionResponse element.
<27> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetRemindersResponse element.
<28> Section 2.2.4.12: Exchange 2007 and the initial release version of Exchange 2010 do not include the ApplyConversationActionResponseMessage element.
<29> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetSearchableMailboxesResponseMessage element.
<30> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the SearchMailboxesResponseMessage element.
<31> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetDiscoverySearchConfigurationResponseMessage element.
<32> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetHoldOnMailboxesResponseMessage element.
<33> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the SetHoldOnMailboxesResponseMessage element.
<34> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetNonIndexableItemStatisticsResponseMessage element.
<35> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetNonIndexableItemDetailsResponseMessage element.
<36> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the FindPeopleResponseMessage element.
<37> Section 2.2.4.12: Exchange 2007, the initial release version of Exchange 2010, and Exchange 2010 SP1 do not include the GetPasswordExpirationDateResponse element.
<38> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetPersonaResponseMessage element.
<39> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetConversationItemsResponseMessage element.
<40> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetUserRetentionPolicyTagsResponseMessage element.
<41> Section 2.2.4.12: Exchange 2007 and Exchange 2010 do not use the GetUserPhotoResponseMessage element.
<42> Section 2.2.4.12: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the UpdateMailboxAssociationResponseMessage complex type.
<43> Section 2.2.4.12: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not use the UpdateGroupMailboxResponseMessage complex type. This type was introduced in Exchange 2013 SP1.
<44> Section 2.2.4.12: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not use the PostModernGroupItemResponseMessage complex type. This type was introduced in Exchange 2013 SP1.
<45> Section 2.2.4.12: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not use the LikeItemResponseMessage complex type. This type was introduced in Exchange 2013 SP1.
<46> Section 2.2.4.19: Exchange 2007 and Exchange 2010 do not use the IsTruncated value.
<47> Section 2.2.4.20: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the BookingItemType complex type.
<48> Section 2.2.4.21: Exchange 2007 and Exchange 2010 do not use the ChangeHighlightsType complex type.
<49> Section 2.2.4.26: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support the DeleteItemResponseMessageType complex type. This type was introduced in Exchange 2013 SP1.
<50> Section 2.2.4.29: Exchange 2007 and Exchange 2010 do not include the ViewPrivateItems element.
<51> Section 2.2.4.31: Exchange 2007 does not return the MailboxType element in the GetItem operation.
<52> Section 2.2.4.38: Exchange 2007 and Exchange 2010 do not use the HighlightTermType complex type.
<53> Section 2.2.4.42: Exchange 2007 and Exchange 2010 return ErrorInvalidPropertyForOperation response code if IncludeMimeContent element is included in the SyncFolderItems operation request. Exchange 2013, Exchange 2016, and Exchange 2019 ignore. IncludeMimeContent element for SyncFolderItems operation.
<54> Section 2.2.4.42: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not use the UniqueBodyType element. This element was introduced in Exchange 2013 SP1.
<55> Section 2.2.4.42: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not use the NormalizedBodyType element. This element was introduced in Exchange 2013 SP1.
<56> Section 2.2.4.42: Exchange 2007 does not use the FilterHtmlContent element.
<57> Section 2.2.4.42: Exchange 2007 does not include the ConvertHtmlCodePageToUTF8 element.
<58> Section 2.2.4.42: Exchange 2007 and Exchange 2010 do not use the InlineImageUrlTemplate element.
<59> Section 2.2.4.42: Exchange 2007 and Exchange 2010 do not use the BlockExternalImages element.
<60> Section 2.2.4.42: Exchange 2007 and Exchange 2010 do not use the AddBlankTargetToLinks element.
<61> Section 2.2.4.42: Exchange 2007 and Exchange 2010 do not use the MaximumBodySize element.
<62> Section 2.2.4.44: Exchange 2007 and Exchange 2010 do not use the ManagementRoleType complex type.
<63> Section 2.2.4.46: Exchange 2007,Exchange 2010, and Exchange 2013 do not support the RoleMember element
<64> Section 2.2.4.46: Exchange 2007, Exchange 2010, and Exchange 2013 do not support the Network element.
<65> Section 2.2.4.46: Exchange 2007, Exchange 2010, and Exchange 2013 do not support the Person element.
<66> Section 2.2.4.46: Exchange 2007, Exchange 2010, and Exchange 2013 do not support the Booking element.
<67> Section 2.2.4.46: Exchange 2007, Exchange 2010, and Exchange 2013 do not support the XrmOrganization element.
<68> Section 2.2.4.47: ReferenceAttachment is not supported in Exchange 2013 and earlier.
<69> Section 2.2.4.49: Exchange 2007, Exchange 2010,and the initial release of Exchange 2013 do not support the NonEmptyArrayOfPredictedActionReasonType complex type. This type was introduced in Exchange 2013 SP1.
<70> Section 2.2.4.50: Exchange 2007 and Exchange 2010 do not use the NonEmptyArrayOfRoleType complex type.
<71> Section 2.2.4.51: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support the NormalizedBodyType complex type. This type was introduced in Exchange 2013 SP1.
<72> Section 2.2.4.56: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support the PrimarySmtpAddressType complex type. This type was introduced in Exchange 2013 SP1.
<73> Section 2.2.4.57: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support the PrincipalNameType complex type. This type was introduced in Exchange 2013 SP1.
<74> Section 2.2.4.68: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support the SIDType complex type. This type was introduced in Exchange 2013 SP1.
<75> Section 2.2.4.70: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support the SmtpAddressType complex type. This type was introduced in Exchange 2013 SP1.
<76> Section 2.2.4.72: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support the UniqueBodyType complex type. This type was introduced in Exchange 2013 SP1.
<77> Section 2.2.4.75: Exchange 2007 and Exchange 2010 do not include the FirstDayOfWeek element. The FirstDayOfWeek element was introduced in Exchange 2010 SP1.
<78> Section 2.2.5: Exchange 2007, Exchange 2010, and Exchange 2010 SP1 do not include the DateTimePrecisionType simple type. The DateTimePrecisionType simple type was introduced in Exchange 2010 SP2.
<79> Section 2.2.5: Exchange 2007 and the initial release version of Exchange 2010 do not include the following enumeration values: recoverableitemsroot, recoverableitemsdeletions, recoverableitemsversions, recoverableitemspurges, archiveroot, archivemsgfolderroot, archivedeleteditems, archiverecoverableitemsroot, archiverecoverableitemsdeletions, archiverecoverableitemsversions, and archiverecoverableitemspurges.
<80> Section 2.2.5: The initial release version of Exchange 2007 does not use the ExchangeVersionType simple type.
<81> Section 2.2.5: Exchange 2007 and Exchange 2010 do not use the IconIndexType simple type.
<82> Section 2.2.5: Exchange 2007 and Exchange 2010 do not use the PredictedMessageActionType simple type.
<83> Section 2.2.5: Exchange 2007 and the initial release version of Exchange 2010 do not include the following response codes: ErrorAccessModeSpecified, ErrorCannotEmptyFolder, ErrorClientDisconnected, ErrorInvalidLogonType, ErrorNoApplicableProxyCASServersAvailable, ErrorNoPublicFolderServerAvailable, ErrorProxyServiceDiscoveryFailed, ErrorSubscriptionUnsubscribed, ErrorOutlookRuleBlobExists, ErrorRulesOverQuota, ErrorInboxRulesValidationError, ErrorNewEventStreamConnectionOpened, ErrorMissedNotificationEvents, and ErrorApplyConversationActionFailed. Exchange 2010 SP1 does not include the ErrorAttachmentNestLevelLimitExceeded response code.
<84> Section 2.2.5: Exchange 2007 and the initial release version of Exchange 2010 do not include the following enumeration values: conversation:ConversationId, conversation:ConversationTopic, conversation:UniqueRecipients, conversation:GlobalUniqueRecipients, conversation:UniqueUnreadSenders, conversation:GlobalUniqueUnreadSenders, conversation:UniqueSenders, conversation:GlobalUniqueSenders, conversation:LastDeliveryTime, conversation:GlobalLastDeliveryTime, conversation:Categories, conversation:GlobalCategories, conversation:FlagStatus, conversation:GlobalFlagStatus, conversation:HasAttachments, conversation:GlobalHasAttachments, conversation:MessageCount, conversation:GlobalMessageCount, conversation:UnreadCount, conversation:GlobalUnreadCount, conversation:Size, conversation:GlobalSize, conversation:ItemClasses, conversation:GlobalItemClasses, conversation:Importance, conversation:GlobalImportance, conversation:ItemIds, and conversation:GlobalItemIds.
Exchange 2007, Exchange 2010, and Exchange 2010 SP1 do not include the following enumeration values: StoreEntryId, Alias, DirectoryId, DirectReports, ManagerMailbox, MSExchangeCertificate, Notes, PhoneticFullName, PhoneticFirstName, PhoneticLastName, Photo, and UserSMIMECertificate.
<85> Section 2.2.5.3: Exchange 2007, Exchange 2010, and Exchange 2010 SP1 do not include the DateTimePrecisionType simple type. The DateTimePrecisionType simple type was introduced in Exchange 2010 SP2.
<86> Section 2.2.5.7: In Exchange 2016 CU7 and Exchange 2019, for a contact item, a PersonalNotes element ([MS-OXWSCONT] section 2.2.4.3) will be returned when IdOnly is set in request.
<87> Section 2.2.5.10: Exchange 2007 and the initial release version of Exchange 2010 do not include the following enumeration values: recoverableitemsroot, recoverableitemsdeletions, recoverableitemsversions, recoverableitemspurges, archiveroot, archivemsgfolderroot, archivedeleteditems, archiverecoverableitemsroot, archiverecoverableitemsdeletions, archiverecoverableitemsversions, and archiverecoverableitemspurges.
<88> Section 2.2.5.10: Exchange 2007 ,Exchange 2010 and Exchange 2013 do not use the "recoverableitemsdiscoveryholds" value.
<89> Section 2.2.5.10: Exchange 2007 ,Exchange 2010 and Exchange 2013 do not use the "archiveinbox" value
<90> Section 2.2.5.10: Exchange 2007 ,Exchange 2010 and Exchange 2013 do not use the "archiverecoverableitemsdiscoveryholds" value.
<91> Section 2.2.5.10: Exchange 2007 and Exchange 2010 do not use the "syncissues" value.
<92> Section 2.2.5.10: Exchange 2007 and Exchange 2010 do not use the "localfailures" value.
<93> Section 2.2.5.10: Exchange 2007 and Exchange 2010 do not use the "serverfailures" value.
<94> Section 2.2.5.10: Exchange 2007 and Exchange 2010 do not use the "recipientcache" value.
<95> Section 2.2.5.10: Exchange 2007 and Exchange 2010 do not use the "quickcontacts" value.
<96> Section 2.2.5.10: Exchange 2007 and Exchange 2010 do not use the "conversationhistory" value.
<97> Section 2.2.5.10: Exchange 2007 and Exchange 2010 do not use the "adminauditlogs" value.
<98> Section 2.2.5.10: Exchange 2007 and Exchange 2010 do not use the "todosearch" value.
<99> Section 2.2.5.10: Exchange 2007 and Exchange 2010 do not use the "mycontacts" value.
<100> Section 2.2.5.10: Exchange 2007 and Exchange 2010 do not use the "directory" value.
<101> Section 2.2.5.10: Exchange 2007 and Exchange 2010 do not use the "peopleconnect" value.
<102> Section 2.2.5.10: Exchange 2007 ,Exchange 2010 and the initial release of Exchange 2013 do not use the "favorites" value. This value was introduced in Exchange 2013 SP1.
<103> Section 2.2.5.10: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the "mecontact" value.
<104> Section 2.2.5.10: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the "personmetadata" value.
<105> Section 2.2.5.11: Exchange 2007 and Exchange 2010 do not use the "Sharing" value.
<106> Section 2.2.5.14: The initial release version of Exchange 2007 does not support the ExchangeVersionType simple type.
<107> Section 2.2.5.14: Exchange 2007 includes only the target schema that is identified by the Exchange2007 enumeration value.
<108> Section 2.2.5.14: Exchange 2007 does not include the target schema that is identified by the Exchange2007_SP1 enumeration value.
<109> Section 2.2.5.14: Exchange 2007 and Exchange 2007 SP1 do not include the target schema that is identified by the Exchange2010 enumeration value.
<110> Section 2.2.5.14: Exchange 2007 and Exchange 2010 do not include the target schema that is identified by the Exchange2010_SP1 enumeration value.
<111> Section 2.2.5.14: Exchange 2007 and Exchange 2010 do not include the target schema that is identified by the Exchange2010_SP2 enumeration value.
<112> Section 2.2.5.14: Exchange 2007 and Exchange 2010 do not include the target schema that is identified by the Exchange2013 enumeration value.
<113> Section 2.2.5.14: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not include the target schema that is identified by the Exchange2013_SP1 enumeration value.
<114> Section 2.2.5.14: Exchange 2007, Exchange 2010, and Exchange 2013 do not include the target schema that is identified by the Exchange2015 enumeration value,
<115> Section 2.2.5.14: Exchange 2007, Exchange 2010, and Exchange 2013 do not include the target schema that is identified by the Exchange2016 enumeration value,
<116> Section 2.2.5.16: Exchange 2007 and Exchange 2010 do not use the IconIndexType simple type.
<117> Section 2.2.5.17: Exchange 2007 and Exchange 2010 do not use the WorkingElsewhere value.
<118> Section 2.2.5.18: Exchange 2007 does not use the Unknown value.
<119> Section 2.2.5.18: Exchange 2007 does not use the OneOff value.
<120> Section 2.2.5.18: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not use the GroupMailbox enumeration value. This value was introduced in Exchange 2013 SP1.
<121> Section 2.2.5.21: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support the PredictedActionReasonType simple type. This type was introduced in Exchange 2013 SP1.
<122> Section 2.2.5.22: Exchange 2007, Exchange 2010, Exchange 2016, and Exchange 2019 do not use the PredictedMessageActionType simple type. Exchange 2013 SP1 uses only the None value.
<123> Section 2.2.5.24: Exchange 2007 and the initial release version of Exchange 2010 do not include the following response codes: ErrorAccessModeSpecified, ErrorCannotEmptyFolder, ErrorClientDisconnected, ErrorInvalidLogonType, ErrorNoApplicableProxyCASServersAvailable, ErrorNoPublicFolderServerAvailable, ErrorProxyServiceDiscoveryFailed, ErrorSubscriptionUnsubscribed, ErrorOutlookRuleBlobExists, ErrorRulesOverQuota, ErrorInboxRulesValidationError, ErrorNewEventStreamConnectionOpened, ErrorMissedNotificationEvents, and ErrorApplyConversationActionFailed. Exchange 2010 SP1 does not include the ErrorAttachmentNestLevelLimitExceeded response code.
<124> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorArchiveFolderPathCreation error code.
<125> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorArchiveMailboxNotEnabled error code.
<126> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorArchiveMailboxServiceDiscoveryFailed error code.
<127> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorAvailabilityConfigNotFound error code.
<128> Section 2.2.5.24: Exchange 2007, Exchange 2010 and the initial release of Exchange 2013 do not use the ErrorCalendarInvalidDayForWeeklyRecurrence error code. This error code was introduced in Exchange 2013 SP1.
<129> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorCannotArchiveCalendarContactTaskFolderException error code.
<130> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorCannotArchiveItemsInPublicFolders error code.
<131> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorCannotArchiveItemsInArchiveMailbox error code.
<132> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorCannotGetSourceFolderPath error code.
<133> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorCannotGetExternalEcpUrl error code.
<134> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorCannotSpecifySearchFolderAsSourceFolder error code.
<135> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorChannelSubscriptionAlreadyExists error code.
<136> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorChannelSubscriptionNotFound error code.
<137> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorClientIntentInvalidStateDefinition error code.
<138> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorClientIntentNotFound error code.
<139> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorContentIndexingNotEnabled error code.
<140> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorDeleteUnifiedMessagingPromptFailed error code.
<141> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorExceededChannelSubscriptionCount error code.
<142> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorExtensionNotFound error code.
<143> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorImContactLimitReached error code.
<144> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorImGroupDisplayNameAlreadyExists error code.
<145> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorImGroupLimitReached error code.
<146> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInvalidChannelSubscriptionId error code.
<147> Section 2.2.5.24: IDs that are based on the Exchange 2007 server schema are not supported by Exchange 2007 SP1 or later.
<148> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorInvalidImContactId error code.
<149> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorInvalidImDistributionGroupSmtpAddress error code.
<150> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorInvalidImGroupId error code.
<151> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorInvalidItemForOperationArchiveItem error code.
<152> Section 2.2.5.24: Exchange 2007, Exchange 2010, and the initial release Exchange 2013 do no use the ErrorInvalidLikeRequest error code. This error code was introduced in Exchange 2013 SP1.
<153> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorInvalidRetentionTagTypeMismatch error code.
<154> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorInvalidRetentionTagInvisible error code.
<155> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorInvalidRetentionTagIdGuid error code.
<156> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorInvalidRetentionTagInheritance error code.
<157> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorMailboxHoldNotFound error code.
<158> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorMultiLegacyMailboxAccess error code.
<159> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorNewChannelConnectionOpened error code.
<160> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorPromptPublishingOperationFailed error code.
<161> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorPublicFolderMailboxDiscoveryFailed error code.
<162> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorPublicFolderOperationFailed error code.
<163> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorPublicFolderSyncException error code.
<164> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorTeamMailboxNotFound error code.
<165> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorTeamMailboxNotLinkedToSharePoint error code.
<166> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorTeamMailboxUrlValidationFailed error code.
<167> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorTeamMailboxNotAuthorizedOwner error code.
<168> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorTeamMailboxActiveToPendingDelete error code.
<169> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorTeamMailboxFailedSendingNotifications error code.
<170> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorTeamMailboxErrorUnknown error code.
<171> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorTooManyObjectsOpened error code.
<172> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorUnifiedMessagingReportDataNotFound error code.
<173> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorUnifiedMessagingPromptNotFound error code.
<174> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorUnableToRemoveImContact,FromGroup error code.
<175> Section 2.2.5.24: When an attempt is made to retrieve MIME content for an item other than a PostItemType, MessageType, or CalendarItemType object, in Exchange 2007, Exchange 2010, Exchange 2010 SP1 and Exchange 2010 SP2 ErrorUnsupportedMimeConversion will be returned. In Microsoft Exchange Server 2010 Service Pack 3 (SP3), Exchange 2013, Exchange 2016, and Exchange 2019 the operation succeeds and ErrorUnsupportedMimeConversion will not be returned.
<176> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorDuplicateLegacyDistinguishedName error code.
<177> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorInvalidClientAccessTokenRequest error code.
<178> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorNoSpeechDetected error code.
<179> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorUMServerUnavailable error code.
<180> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorRecipientNotFound error code.
<181> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorRecognizerNotInstalled error code.
<182> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorSpeechGrammarError error code.
<183> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorInvalidManagementRoleHeader error code.
<184> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorLocationServicesDisabled error code.
<185> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorLocationServicesRequestTimedOut error code.
<186> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorLocationServicesRequestFailed error code.
<187> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorLocationServicesInvalidRequest error code.
<188> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorWeatherServiceDisabled error code.
<189> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorMailboxScopeNotAllowedWithoutQueryString error code.
<190> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorArchiveMailboxSearchFailed error code.
<191> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorGetRemoteArchiveFolderFailed error code.
<192> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorFindRemoteArchiveFolderFailed error code.
<193> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorGetRemoteArchiveItemFailed error code.
<194> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorExportRemoteArchiveItemsFailed error code.
<195> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorInvalidPhotoSize error code.
<196> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorSearchQueryHasTooManyKeywords error code.
<197> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorSearchTooManyMailboxes error code.
<198> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorDiscoverySearchesDisabled error code.
<199> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorCalendarSeekToConditionNotSupported error code.
<200> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorCalendarIsGroupMailboxForAccept error code.
<201> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorCalendarIsGroupMailboxForDecline error code.
<202> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorCalendarIsGroupMailboxForTentative error code.
<203> Section 2.2.5.24: Exchange 2007 and Exchange 2010 do not use the ErrorCalendarIsGroupMailboxForSuppressReadReceipt error code.
<204> Section 2.2.5.24: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not use the ErrorOrganizationAccessBlocked error code. This error code was introduced in Exchange 2013 SP1.
<205> Section 2.2.5.24: Exchange 2007, Exchange 2010, and initial release of Exchange 2013 do not use the ErrorInvalidLicense error code. This error code was introduced in Exchange 2013 SP1.
<206> Section 2.2.5.24: Exchange 2007, Exchange 2010, and the initial release Exchange 2013 do not use the ErrorMessagePerFolderCountRecievedQuotaExceeded error code. This error code was introduced in Exchange 2013 SP1.
<207> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInvalidBulkActionType error code.
<208> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInvalidKeepNCount error code.
<209> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInvalidKeepNType error code.
<210> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorNoOAuthServerAvailableForRequest error code.
<211> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInstantSearchSessionExpired error code.
<212> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInstantSearchTimeout error code.
<213> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInstantSearchFailed error code.
<214> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorUnsupportedUserForExecuteSearch error code.
<215> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorMissingExchangePrincipal error code.
<216> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorUnexpectedUnifiedGroupsCount error code.
<217> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorParsingXMLResponse error code.
<218> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInvalidFederationOrganizationIdentifier error code
<219> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInvalidSweepRule error code.
<220> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInvalidSweepRuleOperationType error code.
<221> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorTargetDomainNotSupported error code.
<222> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInvalidInternetWebProxyOnLocalServer
<223> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorNoSenderRestrictionsSettingsFoundInRequest error code.
<224> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorDuplicateSenderRestrictionsInputFound error code.
<225> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorSenderRestrictionsUpdateFailed error code.
<226> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorMessageSubmissionBlocked error code.
<227> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorExceededMessageLimit error code.
<228> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorExceededMaxRecipientLimitBlock error code.
<229> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorAccountSuspend error code.
<230> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorExceededMaxRecipientLimit error code.
<231> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorMessageBlocked error code.
<232> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorAccountSuspendShowTierUpgrade error code.
<233> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorExceededMessageLimitShowTierUpgrade error code.
<234> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorExceededMaxRecipientLimitShowTierUpgrade error code.
<235> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInvalidLongitude error code.
<236> Section 2.2.5.24: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the ErrorInvalidLatitude error code.
<237> Section 2.2.5.26: Exchange 2007 and the initial release version of Exchange 2010 do not include the following enumeration values: conversation:ConversationId, conversation:ConversationTopic, conversation:UniqueRecipients, conversation:GlobalUniqueRecipients, conversation:UniqueUnreadSenders, conversation:GlobalUniqueUnreadSenders, conversation:UniqueSenders, conversation:GlobalUniqueSenders, conversation:LastDeliveryTime, conversation:GlobalLastDeliveryTime, conversation:Categories, conversation:GlobalCategories, conversation:FlagStatus, conversation:GlobalFlagStatus, conversation:HasAttachments, conversation:GlobalHasAttachments, conversation:MessageCount, conversation:GlobalMessageCount, conversation:UnreadCount, conversation:GlobalUnreadCount, conversation:Size, conversation:GlobalSize, conversation:ItemClasses, conversation:GlobalItemClasses, conversation:Importance, conversation:GlobalImportance, conversation:ItemIds, and conversation:GlobalItemIds.
Exchange 2007, Exchange 2010, and Exchange 2010 SP1 do not include the following enumeration values: item:StoreEntryId, contacts:Alias, contacts:DirectoryId, contacts:DirectReports, contacts:ManagerMailbox, contacts:MSExchangeCertificate, contacts:Notes, contacts:PhoneticFullName, contacts:PhoneticFirstName, contacts:PhoneticLastName, contacts:Photo, and contacts:UserSMIMECertificate.
<238> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the folder:DistinguishedFolderId value.
<239> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the folder:PolicyTag value.
<240> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the folder:ArchiveTag value.
<241> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the folder:ReplicaList value.
<242> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the ReminderNextTime value.
<243> Section 2.2.5.26: Exchange 2007 does not use the Item:UniqueBody value.
<244> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:flag value.
<245> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:InstanceKey value.
<246> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:NormalizedBody value.
<247> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:EntityExtractionResult value.
<248> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:PolicyTag value.
<249> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:ArchiveTag values.
<250> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:RetentionDate values.
<251> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:Preview value.
<252> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:NextPredictedAction value.
<253> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:GroupingAction value.
<254> Section 2.2.5.26: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not use the item:PredictedActionReasons value. It was introduced in Exchange 2013 SP1.
<255> Section 2.2.5.26: Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not use the item:IsClutter value. It was introduced in Exchange 2013 SP1.
<256> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:RightsManagementLicenseData value.
<257> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:BlockStatus value.
<258> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:TextBody value.
<259> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the item:IconIndex value.
<260> Section 2.2.5.26: Exchange 2007, Exchange 2010, Exchange 2013 do not use the item:MimeContentUTF8 value.
<261> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the item:Hashtags value.
<262> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the item:Mentions value.
<263> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the item:MentionedMe value.
<264> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the item:PendingSocialActivityTagIds value.
<265> Section 2.2.5.26: Exchange 2007, Exchange 2010 and the initial release of Exchange 2013 do not use the message:ApprovalRequestData value. This value was introduced in Exchange 2013 SP1.
<266> Section 2.2.5.26: Exchange 2007, Exchange 2010 and the initial release ofExchange 2013 do not use the message:VotingInformation value. This value was introduced in Exchange 2013 SP1.
<267> Section 2.2.5.26: Exchange 2007, Exchange 2010 and the initial release of Exchange 2013 do not use the message:ReminderMessageData value. This value was introduced in Exchange 2013 SP1.
<268> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the meeting:ProposedStart value.
<269> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the meeting:ProposedEnd value.
<270> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the meetingRequest:ChangeHighlights value.
<271> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the calendar:StartWallClock value.
<272> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the calendar:EndWallClock value.
<273> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the calendar:StartTimeZoneId value.
<274> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the calendar:EndTimeZoneId value.
<275> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the calendar:EnhancedLocation value.
<276> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the calendar:JoinOnlineMeetingUrl value.
<277> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the calendar:OnlineMeetingSettings value.
<278> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the calendar:IsOrganizer value.
<279> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the contacts:AbchEmailAddresses value.
<280> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the conversation:LastModifiedTime value.
<281> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the conversation:InstanceKey value.
<282> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the conversation:Preview value.
<283> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the conversation:IconIndex value.
<284> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the conversation:GlobalIconIndex value.
<285> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the conversation:DraftItemIds value.
<286> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the conversation:MentionedMe value.
<287> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the conversation:GlobalMentionedMe value.
<288> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:PersonaId value.
<289> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:PersonaType value.
<290> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:GivenName value.
<291> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:CompanyName value.
<292> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:SurName value.
<293> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:DisplayName value.
<294> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:EmailAddress value.
<295> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:FileAs value.
<296> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:HomeCity value.
<297> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:CreationTime value.
<298> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:RelevanceScore value.
<299> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the persona:RankingWeight value.
<300> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:WorkCity value.
<301> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:PersonaObjectStatus value.
<302> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:FileAsId value.
<303> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:DisplayNamePrefix value.
<304> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:YomiCompanyName value.
<305> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:YomiFirstName value.
<306> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:YomiFirstLast value.
<307> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Title value.
<308> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:EmailAddresses value.
<309> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:PhoneNumber value.
<310> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:ImAddress value.
<311> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:ImAddresses value.
<312> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:ImAddresses2 value.
<313> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:ImAddresses3 value.
<314> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:FolderIds value.
<315> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Attributions value.
<316> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:DisplayNames value.
<317> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Initials value.
<318> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:FileAses value.
<319> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:FileAsIds value.
<320> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:DisplayNamePrefixes value.
<321> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:GivenNames value.
<322> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:MiddleNames value.
<323> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Surnames value.
<324> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Generations value.
<325> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Nicknames value.
<326> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:YomiCompanyNames value.
<327> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:YomiFirstNames value.
<328> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:YomiLastNames value.
<329> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:BusinessPhoneNumbers value.
<330> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:BusinessPhoneNumbers2 value.
<331> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:HomePhones value.
<332> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:HomePhones2 value.
<333> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:MobilePhones value.
<334> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:MobilePhones2 value.
<335> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:AssistantPhoneNumbers value.
<336> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:CallbackPhones value.
<337> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:CarPhones value.
<338> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:HomeFaxes value.
<339> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:OrganizationMainPhones value.
<340> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:OtherFaxes value.
<341> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:OtherTelephones value.
<342> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:OtherPhones2 value.
<343> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Pagers value.
<344> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:RadioPhones value.
<345> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:TelexNumbers value.
<346> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:WorkFaxes value.
<347> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Emails1 value.
<348> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Emails2 value.
<349> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Emails3 value.
<350> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:BusinessHomePages value.
<351> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:School value.
<352> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:PersonalHomePages value.
<353> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:OfficeLocations value.
<354> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:BusinessAddresses value.
<355> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:HomeAddresses value.
<356> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:OtherAddresses value.
<357> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Titles value.
<358> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Departments value.
<359> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:CompanyNames value.
<360> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Managers value.
<361> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:AssistantNames value.
<362> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Professions value.
<363> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:SpouseNames value.
<364> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Hobbies value.
<365> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:WeddingAnniversaries value.
<366> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Birthdays value.
<367> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Children value.
<368> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Locations value.
<369> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:ExtendedProperties value.
<370> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:PostalAddress value.
<371> Section 2.2.5.26: Exchange 2007 and Exchange 2010 do not use the persona:Bodies value.
<372> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<373> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<374> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<375> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<376> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<377> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<378> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<379> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<380> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<381> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<382> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<383> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<384> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<385> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<386> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<387> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<388> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<389> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<390> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<391> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<392> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<393> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<394> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<395> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<396> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<397> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<398> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<399> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<400> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<401> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<402> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the SourceEntryId value
<403> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the DisplayName value
<404> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the AccountName value
<405> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<406> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<407> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<408> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<409> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<410> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<411> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<412> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<413> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<414> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<415> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<416> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<417> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<418> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<419> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<420> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<421> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<422> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.
<423> Section 2.2.5.26: Exchange 2007, Exchange 2010, and Exchange 2013 do not use the value.