Maybe you have seen a mail queue with a lot of mails to strange domains. After further investigation most times you will find out that it will be NDR’s. When you zoom in to the messages you can recognize them because they have the following properties:
I found a nice question on the MSExchange forum which I thought it may be interesting. It may happen that during an import there goes something wrong with the calender, how can you clear all items from the calender ? The answer is via the Powershell with the following command:
E-mail address policies are always nice to play with, but when you don’t use them often you sometimes forget the variables which you can provide to build an e-mail address. I made a short list of available variables:
In Exchange 2003 you could use the Cleanup database to check the mailboxdatabase for mailboxes who were not assigned to users anymore. In Exchange 2007 you can do this via the Exchange Management Shell. The command that you need to use for this is clean-mailboxdatabase. This command will scan the Active Directory for mailboxes who are not assigned to users anymore but are not marked as this in the AD. When the status is not correct it will update the status directly.
Exchange 2007 contains a few nice tools. One of them is the queue viewer_,_ with this tool you can get an overview of all mails who are still in the queue of Exchange 2007. You can do this also via the Powershell command get-queue, with this command all mail queues are displayed with the ammount of messages in it.
Normally the Out of Office functionality isn’t really hard and you won’t have a lot of issues with it. But when you have issues they can be quite complicated. For example, if Out of Office is enabled but it doesn’t send the message to the sender. There are a few things you should check in this case. The problem is most times caused by the rule entry in the users mailbox. To clean this up you should start Outlook with the /cleanrules option. When this doesn’t solve the issue you will have to do some Exchange “hacking”, this can be done with two tools:
As you may already now you can use the New-ExchangeCertificate Powershell to add a new certificate to a few services of Exchange or create a certificate request. During a visit on the MsExchange forum I found a post of somebody who had issues with this. Despite the credentials he used to login he got the message Access is denied.
If you are troubleshooting an issue some logging is really usefull. On the UM server diagnostic logging is enabled by default on the lowest level. In case you need to have more logging you should manually change it to a higher level.