..., etc.

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== LDAP ======
===== All Exchange Mailboxes =====

The Exchange System Manager uses the "displayName" attribute, not common name, therefore, the displayName must be included in the initial lookup.  I think three fields is fine, CN, DN, displayName...

The base query to get all Exchange mailboxes is:
<code>
(&(&(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*))) ))))
</code>
=== Csvde ===

Csvde format for this query to retrieve CN's and displayNames:
<code>
csvde -f all_exchange.txt -r "(&(&(& (mailnickname=*) (|(&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*))) ))))" -l cn,displayName
</code>
Output of that query is simple to parse, and looks like:
<code>
DN,cn
"CN=102 Philosophy,OU=SIS,DC=ais,DC=columbia,DC=edu",102 Philosophy,102 Philosophy
</code>
===== Queries required =====

All users with exchange mailboxes
<code>csvde -f all_exchange.txt -r "(&(&(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*))) ))))" -l cn
</code>
Output: List of DNs,CNs.
Process: Output insert statements for DNs and CNs
Process: Output insert statements for OU

Manual export of CN with mailbox size from System Manager
Process: Output update statements with mailbox size where CN=CN.



===== Common Name =====

CN and DN are used universally throughout LDAP and Microsoft's AD infrastructure, including Exchange Server 2003 System Manager.  The DN is more specific, and should be used for the unique identifier of an object.  The CN is easier to parse, and can be used in a lot of cases.  

The simplest LDAP lookup for a Common Name looks like:
<code>
(cn=102 Philosophy)
</code>
Multiple CN's can be looked up via the OR operator, "!", as such:
<code>
(!(cn=102 Philosophy)(cn=Ben Hall))
</code>
..., etc.

User Tools

Site Tools

Page Tools
