What attributes are necessary for a contact to function?
What attributes are required for a contact to function in AD in a non-native 2007 environment? I'm trying to get around the legacyExchangeDN / X.500 issue before a migration of Notes users. Before the migration is to be performed, we want all users to accept email @companyA.com. An idea is to create contacts which would map the addresses @companyA.com to @companyB.com. All the outgoing mail from Lotus at company B will be re-written with @companyA. Before a user is migrated to companyA, a new mailbox will be created and the mail migration performed. Is it possible to nuke the legacyExchangeDN attributes from the contacts, and only retain the SMTP address, or will the messages fail from MAPI clients? (Or worse).
May 17th, 2010 11:51pm

Don't get too caught up about legacyExchangeDN. Your contact object can have a number of proxyAddresses associated with it, but the targetAddress attribute value is used by Exchange for routing purposes. In other words your contact can have both @companyA.com and @companyB.com proxyAddresses, but if the mailbox resides in CompanyA then that needs to be reflected in the targetAddress attribute value. Alexei
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2010 12:19am

Hi, Please understand that there are a minimum set of attributes that are required to make all Exchange components work properly for mail-enabled objects. For contacts, the least attributes are mailNickname, legacyExchangeDN, and displayName. To achieve your requirement, please try the method as below link: http://technet.microsoft.com/en-us/library/bb676395(EXCHG.80).aspx Thanks Allen
May 18th, 2010 8:33am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics