Using the Mailbox Manager in Exchange 2000
One of the new features that was implemented in Exchange 2000 SP1 is the Mailbox Manager. With the Mailbox Manager an Exchange Administrator has the ability to control the content of a user’s mailboxes.
One of the new features that was implemented in Exchange 2000 SP1 is the Mailbox Manager. With the Mailbox Manager an Exchange Administrator has the ability to control the content of a user’s mailboxes.
It's bound to happen. Your boss is going to call you at the most inopportune moment ranting and raving about some super important email message that hasn't been delivered. It's times like this when you really want to know how to track messages sent in your organization. Thankfully, Microsoft has provided this ability for us.
In Mark Fugatt’s article “Forwarding Mail to an External Recipient,” he covered how to take mail destined for an internal mailbox and forward it to an outside email address such as a Hotmail or AOL account.
In my previous article I presented a script that iterated through all the OUs to export mail enabled users' mail addresses to a CSV file. Active Directory allows you, instead of going through each and evey the OUs, to perform directory wide searches by constructing an LDAP query. LDAP is a pretty complex and powerful query language. The more precise you want to get in your query, the more it gets difficult to control a query.
It is very common for some of your users to express an interest in having their mail delivered to a mailbox that is external to your organization. For example, the user is going to be working away from the office and would like their mail to be delivered to their Hotmail account. Another request might be to have their mail delivered to a different person altogether.
One of the big problems that Exchange Administrators have is controlling the size of user’s mailboxes. Well never fear help is at hand; with a few simple steps you can have a lot more control.
Part of the planning process for deploying Microsoft Exchange 2000 Server in your organization is determining how to administer it. With the introduction of Active Directory, you can separate the administration of servers from the administration of recipients. Understanding this separation is important in deciding how to administer Exchange. In addition, understanding the new administration models is necessary to administer servers and recipients effectively.
In Exchange 5.5 you had a GUI interface that let you easily import and export users in the Exchange Administrator utility. Active Directory essentially lets you do the same thing with two utilities: Ldifde and CSVDE. However, both utilities are not that easy to use. Basically you have to unappealing options: either you export the entire directory and start filtering through the many fields available there (and there are a lot!) or you deal with command line switches.
Most of the time your Exchange 2000 Server implementation probably runs fine with no problems at all. Unfortunately, problems can and do occur with any complicated system, and Exchange is no different. In the case of Exchange, however, you also have to take in account the email client software and it’s particulars. Since it’s safe to assume that most of your internal clients will be using Outlook as their email client, we can broaden our view of the Exchange implementation to include the Outlook client and its processes as well.