Remove Exchange Attributes vs. Delete Mailbox

Published Oct 13 2006 03:14 PM 36.6K Views

Over time, several people have inquired about the differences between the "Delete Mailbox" and "Remove Exchange Attributes" functionality in Exchange 2000/2003. Note: The Remove Exchange Attributes option only appears in the Exchange Tasks wizard within the Active Directory Users and Computers snap-in when the Advanced Features option is selected within the MMC console.

Seeing that I did not find much written about it, here is what I have learned.

This functionality was originally added in Exchange 2000 SP2. It was added to allow administrators the ability to forcibly remove Exchange attributes from a recipient object. This is useful in the following scenarios:

  • You use the ADC service and notice that some of your Exchange attributes are being incorrectly matched to the an Active Directory user object.
  • The mailbox for an Active Directory user points to an Exchange 200x server/database that no longer exists.
  • As part of the process to reconnect mailboxes after a disaster recovery operation.

Fundamentally, this is how it works:

  • If the object is a mailbox enabled user with a valid mailbox, then there is little difference between running these two options to delete the mailbox. Obviously, the "Delete Mailbox" option will be available only if there IS a mailbox (so a distribution list would have a "Remove email address" option instead).
  • The "Remove Exchange Attributes" option is available for ANY type of recipient object, mail enabled or not. This option is extremely useful when there is a need to "clear" the attributes in case that some of them were damaged or not valid for some reason. Let's say there is a mailbox enabled user that had some of his attributes changed by some process, and because of that, you cannot use the "Delete Mailbox" option. You can always run "Remove Exchange Attributes" to "clear out" the values so you can start fresh with mailbox enabling that user again.

Remove Exchange Attributes removes the following attributes as long as they actually exist as available attributes of that schema object:

  • adminDisplayName
  • altRecipient
  • authOrig
  • autoReplyMessage (ILS Settings)
  • deletedItemFlags
  • delivContLength
  • deliverAndRedirect
  • displayNamePrintable
  • dLMemDefault
  • dLMemRejectPerms
  • dLMemSubmitPerms
  • extensionAttribute1
  • extensionAttribute10
  • extensionAttribute11
  • extensionAttribute12
  • extensionAttribute13
  • extensionAttribute14
  • extensionAttribute15
  • extensionAttribute2
  • extensionAttribute3
  • extensionAttribute4
  • extensionAttribute5
  • extensionAttribute6
  • extensionAttribute7
  • extensionAttribute8
  • extensionAttribute9
  • folderPathname (Outlook Web Access Server)
  • garbageCollPeriod
  • homeMDB (Exchange Mailbox Store)
  • homeMTA
  • internetEncoding
  • legacyExchangeDN
  • mail (E-Mail Address)
  • mailNickname (Alias)
  • mAPIRecipient
  • mDBOverHardQuotaLimit
  • mDBOverQuotaLimit
  • mDBStorageQuota
  • mDBUseDefaults
  • msExchADCGlobalNames
  • msExchControllingZone
  • msExchExpansionServerName
  • msExchFBURL
  • msExchHideFromAddressLists
  • msExchHomeServerName (Exchange Home Server)
  • msExchMailboxGuid
  • msExchMailboxSecurityDescriptor
  • msExchPoliciesExcluded
  • msExchPoliciesIncluded
  • msExchRecipLimit
  • msExchResourceGUID
  • protocolSettings
  • proxyAddresses (Proxy Addresses)
  • publicDelegates
  • securityProtocol
  • showInAddressBook
  • submissionContLength
  • targetAddress
  • textEncodedORAddress
  • unauthOrig

In addition to removing the attributes above, the Delete Mailbox option also removes the mailbox information from the dsaccess cache. Note that this actually leaves the mailbox in place with the expectation that the mailbox cleanup task will take care of it at the appropriate time. So the mailbox is actually NOT deleted (purged) from the Information Store as part of this process. Although it will be purged by the mailbox cleanup task later, or as specified by the "Deletion settings" for mailboxes on the database's Limits tab in ESM.

So long story short, these two tasks can be viewed as redundant at times, as long as everything is OK and goes as expected. However, in cases where you are troubleshooting a problem and need to "clear" the attributes of objects (that might not have a full set of attributes so the "Delete mailbox" or "Delete email address" tasks might not be available) the "Remove Exchange Attributes" task is your friend.

- Jason Dool

9 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-601248%22%20slang%3D%22en-US%22%3ERemove%20Exchange%20Attributes%20vs.%20Delete%20Mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-601248%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%20%3CP%3EOver%20time%2C%20several%20people%20have%20inquired%20about%20the%20differences%20between%20the%20%22Delete%20Mailbox%22%20and%20%22Remove%20Exchange%20Attributes%22%20functionality%20in%20Exchange%202000%2F2003.%20%3CB%3ENote%3A%20%3C%2FB%3EThe%20Remove%20Exchange%20Attributes%20option%20only%20appears%20in%20the%20Exchange%20Tasks%20wizard%20within%20the%20Active%20Directory%20Users%20and%20Computers%20snap-in%20when%20the%20Advanced%20Features%20option%20is%20selected%20within%20the%20MMC%20console.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2Fthemes%2Fexchange%2Fimages%2F429191_deletevsremove.jpg%22%20original-url%3D%22%2Fthemes%2Fexchange%2Fimages%2F429191_deletevsremove.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2Fthemes%2Fexchange%2Fimages%2F429191_deletevsremove.jpg%22%20original-url%3D%22%2Fthemes%2Fexchange%2Fimages%2F429191_deletevsremove.jpg%22%20%2F%3E%3C%2FA%3E%3C%2FP%3E%3CP%3ESeeing%20that%20I%20did%20not%20find%20much%20written%20about%20it%2C%20here%20is%20what%20I%20have%20learned.%3C%2FP%3E%3CP%3EThis%20functionality%20was%20originally%20added%20in%20Exchange%202000%20SP2.%20It%20was%20added%20to%20allow%20administrators%20the%20ability%20to%20forcibly%20remove%20Exchange%20attributes%20from%20a%20recipient%20object.%20This%20is%20useful%20in%20the%20following%20scenarios%3A%3C%2FP%3E%3CP%3E%3CUL%3E%20%3CLI%3EYou%20use%20the%20ADC%20service%20and%20notice%20that%20some%20of%20your%20Exchange%20attributes%20are%20being%20incorrectly%20matched%20to%20the%20an%20Active%20Directory%20user%20object.%3C%2FLI%3E%20%3CLI%3EThe%20mailbox%20for%20an%20Active%20Directory%20user%20points%20to%20an%20Exchange%20200x%20server%2Fdatabase%20that%20no%20longer%20exists.%3C%2FLI%3E%20%3CLI%3EAs%20part%20of%20the%20process%20to%20reconnect%20mailboxes%20after%20a%20disaster%20recovery%20operation.%3C%2FLI%3E%3C%2FUL%3E%20%3C%2FP%3E%3CP%3EFundamentally%2C%20this%20is%20how%20it%20works%3A%3CUL%3E%20%3CLI%3EIf%20the%20object%20is%20a%20mailbox%20enabled%20user%20with%20a%20valid%20mailbox%2C%20then%20there%20is%20little%20difference%20between%20running%20these%20two%20options%20to%20delete%20the%20mailbox.%20Obviously%2C%20the%20%22Delete%20Mailbox%22%20option%20will%20be%20available%20only%20if%20there%20IS%20a%20mailbox%20(so%20a%20distribution%20list%20would%20have%20a%20%22Remove%20email%20address%22%20option%20instead).%3C%2FLI%3E%20%3CLI%3EThe%20%22Remove%20Exchange%20Attributes%22%20option%20is%20available%20for%20ANY%20type%20of%20recipient%20object%2C%20mail%20enabled%20or%20not.%20This%20option%20is%20extremely%20useful%20when%20there%20is%20a%20need%20to%20%22clear%22%20the%20attributes%20in%20case%20that%20some%20of%20them%20were%20damaged%20or%20not%20valid%20for%20some%20reason.%20Let's%20say%20there%20is%20a%20mailbox%20enabled%20user%20that%20had%20some%20of%20his%20attributes%20changed%20by%20some%20process%2C%20and%20because%20of%20that%2C%20you%20cannot%20use%20the%20%22Delete%20Mailbox%22%20option.%20You%20can%20always%20run%20%22Remove%20Exchange%20Attributes%22%20to%20%22clear%20out%22%20the%20values%20so%20you%20can%20start%20fresh%20with%20mailbox%20enabling%20that%20user%20again.%3C%2FLI%3E%3C%2FUL%3E%20%3C%2FP%3E%3CP%3ERemove%20Exchange%20Attributes%20removes%20the%20following%20attributes%20as%20long%20as%20they%20actually%20exist%20as%20available%20attributes%20of%20that%20schema%20object%3A%3CUL%3E%20%3CLI%3EadminDisplayName%3C%2FLI%3E%20%3CLI%3EaltRecipient%3C%2FLI%3E%20%3CLI%3EauthOrig%3C%2FLI%3E%20%3CLI%3EautoReplyMessage%20(ILS%20Settings)%3C%2FLI%3E%20%3CLI%3EdeletedItemFlags%3C%2FLI%3E%20%3CLI%3EdelivContLength%3C%2FLI%3E%20%3CLI%3EdeliverAndRedirect%3C%2FLI%3E%20%3CLI%3EdisplayNamePrintable%3C%2FLI%3E%20%3CLI%3EdLMemDefault%3C%2FLI%3E%20%3CLI%3EdLMemRejectPerms%3C%2FLI%3E%20%3CLI%3EdLMemSubmitPerms%3C%2FLI%3E%20%3CLI%3EextensionAttribute1%3C%2FLI%3E%20%3CLI%3EextensionAttribute10%3C%2FLI%3E%20%3CLI%3EextensionAttribute11%3C%2FLI%3E%20%3CLI%3EextensionAttribute12%3C%2FLI%3E%20%3CLI%3EextensionAttribute13%3C%2FLI%3E%20%3CLI%3EextensionAttribute14%3C%2FLI%3E%20%3CLI%3EextensionAttribute15%3C%2FLI%3E%20%3CLI%3EextensionAttribute2%3C%2FLI%3E%20%3CLI%3EextensionAttribute3%3C%2FLI%3E%20%3CLI%3EextensionAttribute4%3C%2FLI%3E%20%3CLI%3EextensionAttribute5%3C%2FLI%3E%20%3CLI%3EextensionAttribute6%3C%2FLI%3E%20%3CLI%3EextensionAttribute7%3C%2FLI%3E%20%3CLI%3EextensionAttribute8%3C%2FLI%3E%20%3CLI%3EextensionAttribute9%3C%2FLI%3E%20%3CLI%3EfolderPathname%20(Outlook%20Web%20Access%20Server)%3C%2FLI%3E%20%3CLI%3EgarbageCollPeriod%3C%2FLI%3E%20%3CLI%3EhomeMDB%20(Exchange%20Mailbox%20Store)%3C%2FLI%3E%20%3CLI%3EhomeMTA%3C%2FLI%3E%20%3CLI%3EinternetEncoding%3C%2FLI%3E%20%3CLI%3ElegacyExchangeDN%3C%2FLI%3E%20%3CLI%3Email%20(E-Mail%20Address)%3C%2FLI%3E%20%3CLI%3EmailNickname%20(Alias)%3C%2FLI%3E%20%3CLI%3EmAPIRecipient%3C%2FLI%3E%20%3CLI%3EmDBOverHardQuotaLimit%3C%2FLI%3E%20%3CLI%3EmDBOverQuotaLimit%3C%2FLI%3E%20%3CLI%3EmDBStorageQuota%3C%2FLI%3E%20%3CLI%3EmDBUseDefaults%3C%2FLI%3E%20%3CLI%3EmsExchADCGlobalNames%3C%2FLI%3E%20%3CLI%3EmsExchControllingZone%3C%2FLI%3E%20%3CLI%3EmsExchExpansionServerName%3C%2FLI%3E%20%3CLI%3EmsExchFBURL%3C%2FLI%3E%20%3CLI%3EmsExchHideFromAddressLists%3C%2FLI%3E%20%3CLI%3EmsExchHomeServerName%20(Exchange%20Home%20Server)%3C%2FLI%3E%20%3CLI%3EmsExchMailboxGuid%3C%2FLI%3E%20%3CLI%3EmsExchMailboxSecurityDescriptor%3C%2FLI%3E%20%3CLI%3EmsExchPoliciesExcluded%3C%2FLI%3E%20%3CLI%3EmsExchPoliciesIncluded%3C%2FLI%3E%20%3CLI%3EmsExchRecipLimit%3C%2FLI%3E%20%3CLI%3EmsExchResourceGUID%3C%2FLI%3E%20%3CLI%3EprotocolSettings%3C%2FLI%3E%20%3CLI%3EproxyAddresses%20(Proxy%20Addresses)%3C%2FLI%3E%20%3CLI%3EpublicDelegates%3C%2FLI%3E%20%3CLI%3EsecurityProtocol%3C%2FLI%3E%20%3CLI%3EshowInAddressBook%3C%2FLI%3E%20%3CLI%3EsubmissionContLength%3C%2FLI%3E%20%3CLI%3EtargetAddress%3C%2FLI%3E%20%3CLI%3EtextEncodedORAddress%3C%2FLI%3E%20%3CLI%3EunauthOrig%3C%2FLI%3E%3C%2FUL%3E%20%3C%2FP%3E%3CP%3EIn%20addition%20to%20removing%20the%20attributes%20above%2C%20the%20Delete%20Mailbox%20option%20also%20removes%20the%20mailbox%20information%20from%20the%20dsaccess%20cache.%26nbsp%3BNote%20that%20this%20actually%20leaves%20the%20mailbox%20in%20place%20with%20the%20expectation%20that%20the%20mailbox%20cleanup%20task%20will%20take%20care%20of%20it%20at%20the%20appropriate%20time.%20So%20the%20mailbox%20is%20actually%20NOT%20deleted%20(purged)%20from%20the%20Information%20Store%20as%20part%20of%20this%20process.%20Although%20it%20will%20be%20purged%20by%20the%20mailbox%20cleanup%20task%20later%2C%20or%20as%20specified%20by%20the%20%22Deletion%20settings%22%20for%20mailboxes%20on%20the%20database's%20Limits%20tab%20in%20ESM.%3C%2FP%3E%3CP%3ESo%20long%20story%20short%2C%20these%20two%20tasks%20can%20be%20viewed%20as%20redundant%20at%20times%2C%20as%20long%20as%20everything%20is%20OK%20and%20goes%20as%20expected.%20However%2C%20in%20cases%20where%20you%20are%20troubleshooting%20a%20problem%20and%20need%20to%20%22clear%22%20the%20attributes%20of%20objects%20(that%20might%20not%20have%20a%20full%20set%20of%20attributes%20so%20the%20%22Delete%20mailbox%22%20or%20%22Delete%20email%20address%22%20tasks%20might%20not%20be%20available)%20the%20%22Remove%20Exchange%20Attributes%22%20task%20is%20your%20friend.%3C%2FP%3E%3CP%3E-%20Jason%20Dool%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Jul 01 2019 03:19 PM
Updated by: