MM&M UG UK

Can anybody point me at reference material that lists or details the mandatory attributes for an E5.5 mailbox.

My issue, I have Exchange 5.5, Active Directory and eDirectory, all of which are LDAP databases.

I am currently sync'ing AD with eDir using DirXML, and when I introduce Exchange attributes into AD using ADC, I need to understand the potential knock on effects.

Which attributes will be taken from E5.5 and alter or affect AD attributes that may then get replicated via DirXML into eDirectory.

Thanks.

---

"The isolated knowledge obtained by a group of specialists in a narrow field has in itself no value whatsoever" : Erwin Schrodinger

Well, it turns out there are only three "required" attributes in 5.5,

Delivery-Mechanism

Directory Name

Object-Class,

although 26 attributes have an existing value set by default for a new mailbox where just a first, last, display name and alias have been given on creation.

There are 167 attributes with no existing value set.

Fascinating....

---

"The isolated knowledge obtained by a group of specialists in a narrow field has in itself no value whatsoever" : Erwin Schrodinger

Hi Conroyd.

Thanks very much for keeping up the posting. As mentioned elsewhere in the forums I will soon have more time to do investigations and testing so hopefully I will be able to help out with answering some of these questions!

Cheers

Nathan

---

Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.

Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk

> I am currently sync'ing AD with eDir using DirXML, and when I introduce Exchange attributes into AD using ADC, I need to understand the potential knock on effects.

AD only has a couple of mandatory attributes: cn, instanceType, objectCategory, objectClass, objectSid, sAMAccountName.

As for what ADC synchronises, it's semi-configurable.  Out of the box, it's as follows:

Table 20.4 Object Class-Specific Mappings

Windows 2000 Attribute (LDAP Name) User Object	Exchange Attribute (LDAP Name) Mailbox Object
givenName	givenName
manager	manager
altRecipient	Alt-Recipient
publicDelegates	public-Delegates
mdbUseDefaults	mdb-use-defaults
mdbOverQuotaLimit	MDB-Over-Quota-Limit
mdbStorageQuota	MDB-Storage-Quota
submissionContLength	submission-cont-length
mDBOverHardQuotaLimit	DXA-task
protocolSettings	protocol-Settings
mapiRecipient	mapi-recipient
msExchHomeServerName	home-MDB
msExchHomeServerName	home-MTA
deliverAndRedirect	deliver-and-redirect
garbageCollPeriod	garbage-coll-period
securityProtocol	security-Protocol
deletedItemFlags	DXA-Flags
objectSID	Assoc-NT-Account
authOrig	Auth-Orig
unauthOrig	Unauth-Orig
dLMemSubmitPerms	DL-Mem-Submit-Perms
dLMemRejectPerms	DL-Mem-Reject-Perms
folderPathname	Folder-Pathname

 

Table 20.5 Object Class-Specific Mappings

Windows 2000 Attribute (LDAP Name) Contact Object	Exchange Attribute (LDAP Name) Custom Object
givenName	givenName
Manager	Manager
targetAddress	target-Address
protocolSettings	protocol-Settings
mapiRecipient	mapi-Recipient
AuthOrig	Auth-Orig
UnauthOrig	Unauth-Orig
dlMemSubmitPerms	dl-Mem-Submit-Perms
dlMemRejectPerms	dl-Mem-Reject-Perms

 

For more info., see: http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/deploy/dgbl_exc_hllt.mspx?mfr=true

 

Hi

This article details the attributes required and also which ones are mandatory.

http://www.microsoft.com/technet/prodtechnol/exchange/55/support/adsi.mspx

Cheers

Mark

Paul, Mark, thank you both for the information.

Declan

---

"The isolated knowledge obtained by a group of specialists in a narrow field has in itself no value whatsoever" : Erwin Schrodinger

Indeed thanks to both of you for signing up and getting involved.

Cheers

Nathan

---

Nathan Winters - MVP Exchange Server
MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.

Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk