Urgent Exchange Vs AD

Question

Hi Experts,
In our company we have customized connector for AD and Exchange; Here is the how the exchange provision works; THis resourcce depends on AD; we always create user accounts in default mailbox. based on mailbox name we build and add all other related attributes to AD; mail , mail nickname , homemdb, legachyexchange, msexchhomeservername, proxyaddresses etc. when the person disable's we remove all those attributes in AD the mailbox of the user is in diconnected state; there is a job runs on exchange delete those disconnected mailboxes after 60days; if the user comes back we re-enable the accounts; if he comes back under manager different position number we create; new accounts; during that time I want to check exchange ; if the user has any previous mailboxes in disconneted state if yes I have to get that mailbox name and add related attributes to his AD account if not I have to provion the new exchange resource in constant store. that we have in lookup table.
how do I check if the person has previous mailbox or not? we delete all exchange related attributes when a person is disabled and moved 000 ou in AD.
if any code or API is available to check existing msexchmailboxguid or maibox FOR THAT USR

Answer 1

There are couple of scenario's
Scenario1: user exist's in OIM
user disabled in OIM
we delete the following exchange related attributes
Remove 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
When we enable we populate the following attributes in AD that automatically links the mailbox
msExchOmaAdminWirelessEnable     UD_EXCHMB_P_WIRELESSADMIN
mailNickname     UD_EXCHMB_P_MAILNICKNAME
mail     UD_EXCHMB_P_EMAIL
mDBUseDefaults     UD_EXCHMB_P_USEDEFQUOTA
mDBStorageQuota     UD_EXCHMB_P_QUOTAWARN
mDBOverQuotaLimit     UD_EXCHMB_P_QUOTANOSEND
mDBOverHardQuotaLimit     UD_EXCHMB_P_QUOTANOSENDREC
sAMAccountName     UD_EXCHMB_P_USERNAME
proxyAddresses,
hidefromaddresslist false
homeMDB
some times it is working fine some times it still creating the new mailbox. only thing is we wont store the following attributes in process form
msExchMailboxGuid,
msExchPoliciesIncluded
but we will store mailbox store name, AD object guid and the attributes I mensioned in enable process we store in process form.
Scenario 2: if the user does not exist in OIM
first time we are provisioning I want to check any disconnected mail box's existing for this user if yes I have to get those attributes into AD if no I will proviion with the default mailbox store that I have in OIM lookup.
Is there any API or code check priorer to provision the mailbox if any exisits?
all your help will be appreciated.
we are using connector version 9.0.4 echange and ad with customization
win2003 server