NNS ADix - How to...Create Microsoft Exchange Recipient Objects

	NNS ADix - How to...Create Microsoft Exchange Recipient Objects

This topic describes how to create Microsoft Exchange recipient objects with NNS ADix.

General

With NNS ADix you can create Microsoft Exchange recipients or update Exchange-related attributes on those recipients. A
recipient is any mail-enabled object in Active Directory to which Exchange can deliver or route messages.

Basically there are four types of recipients in Microsoft Exchange:

Mailboxes/Mailbox-Enabled Users: A mailbox that's assigned to an individual user in your Exchange organization
Mail Users: A mail-enabled Active Directory user that represents a user outside the Exchange organization
Mail Contacts: A mail-enabled Active Directory contact that contains information about people
or organizations that exist outside the Exchange organization
Distribution Groups: Mail-enabled Active Directory group objects that are primarily used for
distributing messages to multiple recipients

For more information about Exchange recipient types see ...:

Microsoft Technet - Understanding Recipients

There are different procedures for the various Exchange versions. The following topics are providing information
for Exchange 2000/2003, Exchange 2007 and Exchange 2010.

Mailboxes/Mailbox-Enabled Users

This topic describes how to create mailbox-enabled users with NNS ADix.

Note:
In order to create mailbox-enabled users, an Active Directory user object must be created. Please see
the following topic to get information about creating user objects with NNS ADix: NNS ADix - How to...Create User Objects

Exchange 2000/2003

The following table contains a list of mandatory attributes which are required to create Exchange Server 2000/2003
mailbox-enabled objects in Active Directory:

Attribute	Type	Description
mailNickname	single-valued	This attribute is the alias to the mailbox.
homeMTA homeMDB msExchHomeServerName	single-valued	One of the following attributes is mandatory for mailbox-enabled objects: homeMTA: This attribute is a distinguished name to the Message Transfer Agent (MTA) object where your mailbox resides. homeMDB: This attribute is a distinguished name to the private Messaging Database (MDB) where your mailbox resides. msExchHomeServerName: This attribute is the legacy distinguished name to the server where you have a mailbox (e.g. /o=org/ou=site/cn=configuration/cn=servers/cn=server).
msExchMailboxGuid	single-valued	This attribute contains the GUID for the mailbox to create. You can randomly generate GUIDs using the ADix Toolbox tool "ADix GUID Generator".

Note:
In Exchange 2000/2003 recipients are partially provisioned after their creation. The
Recipient Update Service (RUS) is responsible for setting the remaining attributes.

Example:

The following example creates a mailbox for an existing user named 'j.doe' on Exchange 2000/2003:

path;mailNickName;msExchMailboxGuid;homeMDB
LDAP://cn=j.doe,cn=users,dc=dom,dc=com;jdoe;j.doe;f4ba36ccbd8442cd8ff96bb6dda2daaa;CN=MBS,CN=SG1,CN=InformationStore,CN=EX01,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=DOM,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=dom,DC=com

Exchange 2007

The following table contains a list of mandatory attributes which are required to create Exchange Server 2007
mailbox-enabled objects in Active Directory:

Attribute	Type	Description
mailNickname	single-valued	This attribute is the alias to the mailbox.
homeMTA homeMDB msExchHomeServerName	single-valued	In order to create Exchange 2007 mailbox-enabled objects, ALL 3 attributes must be present: homeMTA: This attribute is a distinguished name to the Message Transfer Agent (MTA) object where your mailbox resides. homeMDB: This attribute is a distinguished name to the private Messaging Database (MDB) where your mailbox resides. msExchHomeServerName: This attribute is the legacy distinguished name to the server where you have a mailbox (e.g. /o=org/ou=site/cn=configuration/cn=servers/cn=server).
msExchMailboxGuid	single-valued	This attribute contains the GUID for the mailbox to create. You can randomly generate GUIDs using the ADix Toolbox tool "ADix GUID Generator".

Note:
    In Exchange 2007 there is no RUS which is setting the remaining Exchange attributes automatically.
   Therefore if you want to bulk import mailbox-enabled/mail-enabled Exchange 2007 user objects using NNS ADix,
    perform the following steps:
    1) Import the user objects using NNS ADix
    2) Execute the following Exchange Management Shell command: get-mailbox | set-mailbox –ApplyMandatoryProperties

Example:

The following example creates a mailbox for an existing user named 'j.doe' on Exchange 2007:

path;mailNickName;msExchMailboxGuid;homeMDB;homeMTA;msExchHomeServerName
LDAP://cn=j.doe,cn=users,dc=dom,dc=com;jdoe;j.doe;f4ba36ccbd8442cd8ff96bb6dda2daaa;CN=MBS,CN=SG1,CN=InformationStore,CN=EX01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=dom,DC=com;CN=Microsoft MTA,CN=EX01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=dom,DC=com;/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EX01

Exchange 2010

The following table contains a list of mandatory attributes which are required to create Exchange Server 2010
mailbox-enabled objects in Active Directory:

Attribute	Type	Description
mailNickname	single-valued	This attribute is the alias to the mailbox.
homeMDB msExchHomeServerName	single-valued	In order to create Exchange 2010 mailbox-enabled objects, ALL 2 attributes must be present: homeMDB: This attribute is a distinguished name to the private Messaging Database (MDB) where your mailbox resides. msExchHomeServerName: This attribute is the legacy distinguished name to the server where you have a mailbox (e.g. /o=org/ou=site/cn=configuration/cn=servers/cn=server).

Note:
    In Exchange 2010 there is no RUS which is setting the remaining Exchange attributes automatically.
   Therefore if you want to bulk import mailbox-enabled/mail-enabled Exchange 2010 user objects using NNS ADix,
    perform the following steps:
    1) Import the user objects using NNS ADix
    2) Execute the following Exchange Management Shell command: get-mailbox | update-recipient

Example:

The following example creates a mailbox for an existing user named 'j.doe' on Exchange 2010:

path;mailNickName;homeMDB;msExchHomeServerName
LDAP://cn=j.doe,cn=users,dc=dom,dc=com;jdoe;j.doe;CN=MBS,CN=SG1,CN=InformationStore,CN=EX01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=dom,DC=com;/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EX01

.top

Mail Users

This topic describes how to create mail users with NNS ADix.

Note:
In order to create mail users, an Active Directory user object must be created. Please see
the following topic to get information about creating user objects with NNS ADix: NNS ADix - How to...Create User Objects

Exchange 2000/2003

The following table contains a list of mandatory attributes which are required to create Exchange Server 2000/2003
mail user objects in Active Directory:

Attribute	Type	Description
mailNickname	single-valued	This attribute is the alias to the mail user.
targetAddress	single-valued	This attribute is the e-mail address to which you want to redirect the mail. This attribute is formatted like the proxyAddresses attribute, where there is a prefix that defines the address type (e.g. "SMTP:j.doe@dom.com".

Note:
In Exchange 2000/2003 recipients are partially provisioned after their creation. The
Recipient Update Service (RUS) is responsible for setting the remaining attributes.

Example:

The following example mail-enables an existing user named 'j.doe' on Exchange 2000/2003:

path;mailNickName;targetAddress
LDAP://cn=j.doe,cn=users,dc=dom,dc=com;jdoe;SMTP:j.doe@otherdom.com

Exchange 2007/2010

Use the same attributes as for Exchange 2000/2003.

Note:
    In Exchange 2007/2010 there is no RUS which is setting the remaining Exchange attributes automatically.
   Therefore if you want to bulk import mail-enabled Exchange 2007/2010 user objects using NNS ADix,
    perform the following steps:

    Exchange 2007:
    1) Import the user objects using NNS ADix
    2) Execute the following Exchange Management Shell command: get-mailuser | set-mailuser

    Exchange 2010:
    1) Import the user objects using NNS ADix
    2) Execute the following Exchange Management Shell command: get-mailuser | update-recipient

.top

Mail Contacts

This topic describes how to create mail contacts with NNS ADix.

Note:
In order to create mail contacts, an Active Directory contact object must be created. Please see
the following topic to get information about creating contact objects with NNS ADix: NNS ADix - How to...Create Contact Objects

Exchange 2000/2003

The following table contains a list of mandatory attributes which are required to create Exchange Server 2000/2003
mail contact objects in Active Directory:

Attribute	Type	Description
mailNickname	single-valued	This attribute is the alias to the contact.
targetAddress	single-valued	This attribute is the e-mail address to which you want to redirect the mail. This attribute is formatted like the proxyAddresses attribute, where there is a prefix that defines the address type (e.g. "SMTP:j.doe@dom.com".

Note:
In Exchange 2000/2003 recipients are partially provisioned after their creation. The
Recipient Update Service (RUS) is responsible for setting the remaining attributes.

Example:

The following example mail-enables an existing contact named 'j.doe' on Exchange 2000/2003:

path;mailNickName;targetAddress
LDAP://cn=j.doe,cn=users,dc=dom,dc=com;jdoe;SMTP:j.doe@otherdom.com

Exchange 2007/2010

Use the same attributes as for Exchange 2000/2003.

Note:
    In Exchange 2007/2010 there is no RUS which is setting the remaining Exchange attributes automatically.
   Therefore if you want to bulk import mail-enabled Exchange 2007/2010 contact objects using NNS ADix,
    perform the following steps:

    Exchange 2007:
    1) Import the contact objects using NNS ADix
    2) Execute the following Exchange Management Shell command: get-mailcontact | set-mailcontact

    Exchange 2010:
    1) Import the contact objects using NNS ADix
    2) Execute the following Exchange Management Shell command: get-mailcontact | update-recipient

.top

Distribution Groups

This topic describes how to create mail-enabled distribution groups with NNS ADix.

Note:
In order to create mail-enabled distribution groups, an Active Directory group object must be created. Please see
the following topic to get information about creating group objects with NNS ADix: NNS ADix - How to...Create Group Objects

Exchange 2000/2003

The following table contains a list of mandatory attributes which are required to create Exchange Server 2000/2003
mail-enabled distribution groups objects in Active Directory:

Attribute	Type	Description
mailNickname	single-valued	This attribute is the alias to the distribution group.

Note:
In Exchange 2000/2003 recipients are partially provisioned after their creation. The
Recipient Update Service (RUS) is responsible for setting the remaining attributes.

Example:

The following example mail-enables an existing group named 'group1' on Exchange 2000/2003:

path;mailNickName
LDAP://cn=group1,cn=groups,dc=dom,dc=com;group1

Exchange 2007/2010

Use the same attributes as for Exchange 2000/2003.

Note:
    In Exchange 2007/2010 there is no RUS which is setting the remaining Exchange attributes automatically.
   Therefore if you want to bulk import mail-enabled Exchange 2007/2010 distribution groups using NNS ADix,
    perform the following steps:

    Exchange 2007:
    1) Import the group objects using NNS ADix
    2) Execute the following Exchange Management Shell command: get-distributiongroup | set-distributiongroup

    Exchange 2010:
    1) Import the group objects using NNS ADix
    2) Execute the following Exchange Management Shell command: get-distributiongroup | update-recipient

.top