Introduction to Microsoft Exchange 2003 – Types of Recipients
The classic Exchange 2003 recipient is a Windows 2003 user account with a mailbox. Microsoft refer to this as a mailbox enabled user. If you research Exchange 2003’s recipients, then you will discover a type of recipient for every occasion. For example, a Universal Distribution Group to send emails to a list of people or a Contact for you supplier.
Topics for Exchange 2003 Types of Mail Recipients
- Recipients in Exchange 2007
- Understanding the Recipient Types
- Mailbox-enable user
- Mail-enabled user
- Distribution Group
- Query-based Distribution Group
- Security-enabled group
- Mail-enabled Public Folder
- Creating Mail Enabled objects
There is no doubt, knowledge is power. If you truly understand the names and capabilities of email objects, then you will always choose the right recipient for the right job.
Mail-enabled user – Tricky recipient. An Active Directory account with an email address, but no mailbox in your Exchange Organization. I call this the contractor object. Their email is delivered, not to your exchange mailstore, but to their external account, e.g. hotmail or gmail.
Distribution Group – The old Exchange 5.5 DL (distribution list). Big organizations may favour the Universal Distribution groups, while companies with one domain prefer Global Distribution groups.
Query-based Distribution Groups – A great new idea in Exchange 2003. You must investigate these dynamic groups which are populated by LDAP queries. See how to manage these Query-based Distribution Groups groups here.
Security Enabled Group – Where ever possible, avoid this object and use Distribution Groups instead.
Here is my reasoning for shunning Security Enabled Groups for email recipients. Technically it takes longer to logon if users are members of lots of Security Groups – SIDS have to be checked and Universal group membership has to be verified.
However my main objection is because security groups are normally used for share permissions. I once saw an administrator add a user to a group that had access to the printer. What they forgot was that this was a mail-enabled group and the new user started receiving emails that were not meant for their eyes. (It was unpleasant because they were emails about that person’s redundancy.)
Import users from a spreadsheet, complete with their mailbox. Just provide a list of the users with the fields in the top row, and save as .csv file. Then launch this FREE utility, match your Exchange fields with AD’s attributes, click and import the users. Optionally, you can provide the name of the OU where the new mailboxes will be born.
- Bulk-import new users and mailboxes into Active Directory.
- Seek and zap unwanted user accounts.
- Find inactive computers.
Contacts – Easy recipient. These are your suppliers, customers with external email accounts. Contacts have no Active Directory account, just the email address of important people who your users regularly email. When you create a contact it appears in the Global Address List.
If there is a surprise with Contacts, it is that like User objects, Contacts have more tabs once you install Exchange, note the Exchange General and Exchange Advanced tabs.
Mail-enabled Public Folders – I think sending emails to public folders is a neat idea, however, it does not seem to have caught on at the sites that I have visited.
Start by launching Active Directory Users and Computers (Not the Exchange System Manager). Now I love OUs (Organizational Units). So I would create the new users, groups or contacts in a suitable OU rather than in the default users container.
If you get a choice of which server to create the mailbox, then choose a server physically close to the user. One company choose the server for the mailbox based on alphabetic order. This resulted in unnecessary traffic as the servers were in separate routing groups.
By default the mailbox name or alias = logon name. This makes sense and the user will soon get used to their alias. However if you have a strange rules for logon names, for example works number, then you can uncouple the alias = logon name and give the alias a more descriptive identifier.
The best feature of this new this new version of SolarWinds VM Monitor is that it checks Windows Hyper-V. Naturally, it still works with virtual machines on VMware ESX Servers. VM Monitor is a clever desktop tool that not only tests that your server is online, but also displays the CPU and memory utilization for each node.
It’s easy to install and to configure this virtual machine monitor, all you need the host server’s IP address or hostname and the logon info. Give this virtual machine monitor a try – it’s free.
Microsoft include an object class called InetOrgPerson in their Active Directory schema. It seems to me that InetOrgPerson has been on the fringes of Microsoft products since NT 4.0 days. Whereas object classes such as user and computer are tightly defined, InetOrgPerson is a general class suited to people objects that are migrating from other systems.
One use of the InetOrgPerson in Exchange 2003 is to create mobile (OMA) accounts for people who may be migrating from other LDAP systems. The situation is you do not wish to create a normal Active Directory user object. If you wish to provide this facility, then on the OMA client, tab ActiveSync, then Tools, Options and Server.
* Note InetOrgPerson can only be mail-enabled in Exchange 2003 Native mode
Summaryof Microsoft Exchange Server 2003 Recipients
Microsoft Exchange Server 2003 provides a rich variety of recipient objects, mailbox enabled, mail enabled and various distribution groups. Knowledge is power, so research the advantages and disadvantages of each recipient that has an email address. In particular take advantage of the new Query-based Distribution Groups in Exchange 2003.
If you like this page then please share it with your friends