Security Software

Hi Experts,

Exchange is not linking to old mail box when we re-enable instead it is creating the new mailbox user is lossing all his old emails; we are doing the following

IDM current implementation steps at our company:
During the separation IDM performs the following operations on Exchange:
1.) Sets the msExchHideFromAddressLists = True
2.) Removes the following Exchange Attributes

dLMemRejectPerms none
delivContentLength none
deliverAndRedirect none
deliveryMechanism none
delivExtContTypes none
dLMemDefault none
dLMemSubmitPerms none
dnQualifier none
enabledProtocols none
forwardingAddress none
folderPathname none
formData none
heuristics none
importedFrom none
mDBStorageQuota none
internetEncoding none
textEncodedORAddress none
unauthOrig none
unmergedAtts none
replicationSensitivity none
msExchPoliciesExcluded none
replicationSignature none
securityProtocol none
submissionContLength none
targetAddress none
replicatedObjectVersion none
publicDelegates none
protocolSettings none
pOPContentFormat none
pOPCharacterSet none
msExchUserAccountControl none
msExchUseOAB none
msExchADCGlobalNames none
msExchALObjectVersion none
msExchControllingZone none
msExchCustomProxyAddress none
msExchExpansionServerName none
msExchFBURL none
msExchHideFromAddressLists none
msExchInconsistentState none
msExchMailboxGuid none
msExchMailboxSecurityDescriptor none
msExchMailboxUrl none
msExchMasterAccountSid none
msExchOmaAdminExtendedSettings none
msExchOmaAdminWirelessEnable none
msExchPfRootUrl none
msExchPoliciesIncluded none
msExchPolicyEnabled none
msExchPolicyOptionList none
msExchPreviousAccountSid none
msExchProxyCustomProxy none
msExchRecipLimit none
msExchResourceGUID none
msExchUnmergedAttsPt none
language none
languageCode none
extensionData none
expirationTime none
displayNamePrintable none
mail none
mailNickname none
homeMDB none
homeMTA none
msExchHomeServerName none
mDBUseDefaults none
mDBStorageLimit none
mDBOverQuotaLimit none
mDBOverHardQuotaLimit none
proxyAddresses none
showInAddressBook none
mAPIRecipient none
legacyExchangeDN none
garbageCollPeriod none
adminDisplayName none
altRecipient none
authOrig none
autoReply none
autoReplyMessage none
deletedItemsFlags none


During the re-hire or re-enable IDM performs the following operations;

3.) Sets the msExchHideFromAddressLists = False
4.) msExchOmaAdminWirelessEnable UD_EXCHMB_P_WIRELESSADMIN
5.) mailNickname UD_EXCHMB_P_MAILNICKNAME
6.) mail UD_EXCHMB_P_EMAIL
7.) mDBUseDefaults UD_EXCHMB_P_USEDEFQUOTA
8.) mDBStorageQuota UD_EXCHMB_P_QUOTAWARN
9.) mDBOverQuotaLimit UD_EXCHMB_P_QUOTANOSEND
10.) mDBOverHardQuotaLimit UD_EXCHMB_P_QUOTANOSENDREC
11.) sAMAccountName UD_EXCHMB_P_USERNAME
12.) proxyAddresses
13.) homeMDB UD_EXCHMB_P_EXCHSTORE

The Exchange related fields that are stored in IDM are as follows;
UD_EXCHMB_P_WIRELESSADMIN Wireless Admin
UD_EXCHMB_P_USERNAME Username
UD_EXCHMB_P_USERGUID User GUID
UD_EXCHMB_P_USEDEFQUOTA Use Default Quota
UD_EXCHMB_P_QUOTAWARN Quota Warning Level (KB)
UD_EXCHMB_P_QUOTANOSENDREC Quota Prohibit Send & Receive (KB)
UD_EXCHMB_P_QUOTANOSEND Quota Prohibit Send (KB)
UD_EXCHMB_P_PASSWORD Password
UD_EXCHMB_P_ORGNUMBER Organization Number
UD_EXCHMB_P_ORGNAME Organization Name
UD_EXCHMB_P_MAILNICKNAME Mail Nickname
UD_EXCHMB_P_EXCHSTORE Exchange Store
UD_EXCHMB_P_EMAIL Primary Email Address
UD_EXCHMB_P_DOMAIN User Domain


it is creating the new mailbox instead of linking the old mailbox any idea do I need to push any other attribute in AD
When I searched on Microsoft I found the following
General Information
For a mailbox-enabled user, two attributes must be present. The first is the mailNickname attribute, and the second is one of the following attributes:
• msExchHomeServerName
• homeMDB
• homeMTA
If any one of these attributes is present, and the user has a mailNickname attribute, the user is considered a mailbox-enabled user.
In this case, the Recipient Update Service attempts to populate some of the following attributes if they are not present:
• msExchHomeServerName
• homeMDB
• homeMTA
• legacyExchangeDN
• displayName
• msExchMailboxGuid
These attributes are populated in the following order:
1. If the msExchHomeServerName attribute is not present, it is created based on the homeMDB or homeMTA attribute, depending on which one is present. If the msExchHomeServerName attribute cannot be created, the process stops.
2. After the msExchHomeServerName attribute is set, the homeMDB and homeMTA attributes are populated if either one is missing. If you have multiple mailbox stores or message transfer agents (MTAs) on your server, the Recipient Update Service picks the first one that it finds when it does an Active Directory search. Therefore, this selection can be considered a random choice.
3. To create the legacyExchangeDN and displayName attributes, the Recipient Update Service follows the same steps that are used for a mail-enabled recipient.
4. Finally, if the msExchMailboxGuid attribute is not present, the Recipient Update Service creates the msExchMailboxGuid attribute by generating a GUID.