Strange issues with Out of Office

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:

New-ExchangeCertificate : Access is denied

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.

Enable Diagnostic logging on a UM Server

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.

Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1

Microsoft has released Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 last week. This API makes it possible to view the contents of stores. Since Exchange 2007 this MAPI is delivered apart. Via the link below you can download it.

Address rewriting in Exchange 2007

When you would like to use other addresses internal then external you may want to use the New-AddressRewriteEntry Powershell command to let Exchange do this for you.

Microsoft Exchange System Manager for Windows Vista 1.0

Microsoft has release version 1.0 of the Exchange System Manager for Windows Vista. With this tool you can manage your Exchange 2003 server from a Vista machine. There are a few restrictions in the software, belof a few of them:

Implement an Edge Transport server

In this tutorial we will have a look which steps are needed to implement an Edge Transport server in an Exchange 2007 environment.</p>

Installing the Edge Transport server is not very hard and configuring it is not a lot of work. We could start with the setup which will tell us which prerequisites are needed. If you would like to prevent this then download and install the following software before you start the setup:

The Active Directory Application Mode (ADAM) will let the Edge Transport server check the Active Dire tory if a user exists and if not block the e-mail.

During the setup we choose the option Custom Exchange Server Installation with this option we can choose that we only install the Edge Transport Server on this server. When we click on next we will get the following screen:

Here we only select the Edge Transport Server Role and click on the next button

Exchange will first run some tests: it will check if all necessary software is installed and the system meets the systemrequirements. As you can see this is not the case in my situation. I am trying to install the Edge Transport server on a 32-bit OS. This is not supported by Microsoft, in this case it doesn't matter because we run it in a test environment. If installing it in a production environment install it on a server with a 64-bit OS. When clicking on install we continue with the installation.

When the installation is finished we can start the Exchange Management Console, this will look like the screenshot below:

You can see that a few tabs are the same as on the Hub Transport Server. These tabs are empty at this moment but will be filled automatically during the configuration.

Because the Edge Transport Server and Hub Transport Server not know of eachother we first need to export the Edge Subscription and then import it on the Hub Transport Server. This can be done with the following command: New-EdgeSubscription by executing it with the correct parameters a XML file is created which can be imported on the Hub Transport Server.

The following command will create a file in the root of C.

Remove-Mailbox versus Disable-Mailbox

As you may now already you can do quiet a lot of things with Powershell in Exchange 2007. There are some risks, one of this commands is remove-mailbox. The name will let you think that you only remove the mailbox from a user but with this command the user is also removed.

Microsoft Exchange Server ActiveSync Web Administration Tool


id: 713 title: Which ports need to be opened between the Edge Transport server and the Hub Transport server date: 2008-08-17T21:57:46+00:00 author: Johan Veldhuis layout: post guid: permalink: /ports-open-between-edge-transport-server-and-hub-transport-server/ categories:

  • Exchange

    As you may know you can place an Edge Transport Server in your DMZ to communicate between the internet and the Hub Transport server, but which ports need to be opened for that ? Below a short overview: