nm-admin

We have already demonstrated how to configure Standard Journaling in Exchange Server 2007. It is enabled per-Mailbox Database and affects all mailboxes residing on that database.

Exchange Server 2007 offers a more advanced form of Journaling – Premium Journaling. It is available both in Exchange Server Standard and Enterprise editions, and you need Enterprise CALs for the journaled mailboxes when using premium journaling. Premium Journaling (or the so called per-Recipient journalling) allows you a far more granular approach when selecting the scope of the journaling process. You can target an Internal scope, External scope, Global scope, and Specific Journal Recipients, as you will see in the demonstration bellow.

We will show you also how to lock down the journaling mailbox to avoid spoofing messages being sent to it, how to set its storage quota, and how to check/enable the Journaling Agent on the Hub Transport Server.

In the following Step-by-Step Screencast, we are using a default installation of an Exchange Server 2007 SP1, and we will configure Premium Journaling for all messages sent to/from the members of a distribution group. You can get the list of all Exchange Management Shell commands used in the demo from here.

Exchange journaling allows you to create a copy of e-mails in your Exchange organization (journal e-mails), and send them to a dedicated (journal) mailbox on an Exchange Server. This process is often required for the purposes of regulatory compliance, data retention, etc.
Exchange Server 2007 supports envelope journaling – as you can see in our demo, the original message is wrapped in a journaling envelope. This allows you to see the sender, and all recipients, including BCC recipients, and recipients in distribution lists.

In addition, you can choose between two types of journaling in Exchange Server 2007:
– Standard journaling (the so called Per-Mailbox Journaling). You can enable it per mailbox database and all messages sent to/from addresses on that database are journaled. As you can see in the Screencast bellow, the destination (journal) mailbox should reside on a database which is not being journaled.
-Premium journaling. It can target an Internal scope, External scope, Global scope, and Specific Journal Recepients, and we will demonstrate it in a separate screencast.

Standard and Premium journaling are available both in Exchange Server 2007 Standard and Exchange Server 2007 Enterprise edition. If you are planning to implement Premium Journaling on Exchange Server 2007 Standard edition, you need Exchange Enterprise CALs (Client Access Licenses) for the mailboxes which you are planning to journal.

Journaling is often configured together with message archiving. Archiving is the process of storing the already journalled e-mails in a separate environment. We will demonstrate some of the popular archiving solutions in a series of screencasts too.

In the following Step-by-Step Screencast, we will demonstrate how to configure Standard (per-Mailbox) Journaling to a trusted (locked down) mailbox in Exchange Server 2007 SP1.

We have already demonstrated How to Configure Message Size Limits in Exchange Server 2007 SP1. In this screencast, we will demonstrate how to configure the maximum message size limit in Outlook Web Access (OWA) by modifying the maxRequestLength parameter in web.config file.
If the maximum message size that can be sent from a mailbox exceeds the maxRequestLength, you may get the following errors in OWA:

– The attachment you are trying to upload exceeds the maximum size limit for attachments allowed by your organization. For more information, contact technical support for your organization.
– The files … were not attached because they exceed the maximum size limit of … (MB) for attachments.
– This message could not be sent because it exceeds the maximum size allowed.

In addition, if your Exchange 2007 server is running on a Windows Server 2008, you have to configure Outlook Web Access to allow content that is equal to the size of the maximum message size. Failing to do this will result in the following errors, when you use OWA to send a large attachment :

– Server Error 404 – File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
– Server Error in Application DEFAULT WEB SITE/OWA. HTTP Error 404.13 – Not Found. The request filtering module is configured to deny request that exceeds the request content length.

In our demo, we are configuring the maximum message size in OWA on an Exchange server 2007 running on Windows Server 2008.You can get the list of the commands used in the demo

from here
.

Setting and managing the message size limits which are applied to the individual messages traversing your organization is an important part of the successful implementation of Exchange Server 2007 infrastructure.

In the following Step-by-Step Screencast, we will demonstrate the different scopes of message size limits which you can configure in Exchange Server 2007 SP1. There are several important improvements which SP1 added regarding the message size limits implementation. One of them is the option to manage Message size limits through the GUI – the Exchange Management Console. All our examples are demonstrated both by using the Exchange Management Console and the Exchange Management Shell.

In addition, it was a common situation to have conflicting Organizational and Global limits in Exchange 2007 RTM. In Exchange Server 2007 SP1 this problem has been resolved. As you can see in the Screencast, changes that you make to the organizational limits are automatically copied over to the Global limits.

We also demonstrate how to apply message limits to the inbound and outbound messages on the Send and Receive connectors.

There are special users who must send or receive messages that are larger than the specified allowed size. We demonstrate such scenarios both by configuring User limits and by creating Transport rules.

We also pay special attention to the Order of precedence for Message Size limits. You can download the text file with the different scenarios for Order of Precedence for Message Size limits from here. For your convenience, we provide the list of all Exchange Management Shell commands used in the demo here.

Outlook Anywhere is one of the very popular features in Exchange Server 2007. It allows Outlook 2007 and Outlook 2003 clients to connect to Exchange Server over the Internet by using RPC (Remote Procedure Calls) over HTTP. Actually, Outlook Anywhere used to be known as RPC over HTTP in Exchange Server 2003 and we have already demonstrated some of the most common scenarios:
– How to Configure RPC over HTTPS in Exchange Server 2003, running on a Domain Controller
– How to Configure RPC over HTTPS in Exchange Server 2003, SP1 or higher. Exchange and Domain Controller/Global Catalog running on separate servers

The main benefits from Outlook Anywhere are :
– Remote access to Exchange Server over the Internet
– You can use the same URL that you use for Outlook Web Access (and Microsoft Exchange ActiveSync)
– You can use the same SSL certificate implemented for Outlook Web Access and Exchange ActiveSync
– Unauthenticated requests from Outlook cannot access Exchange Server
– No need for VPN (Virtual Private Network) to access Exchange Server across the Internet

In addition, the RPC over HTTP implementation in Exchange Server 2007 – Outlook Anywhere, allows a much easier and fully automated client configuration, in case you are using Outlook 2007. As you can see in the demonstration bellow, all that is required is, to provide your e-mail address, username, and password. Outlook 2003 clients should be configured manually and we demonstrate this too.

It is important to note, that the easiest scenario is when you are using a Multiple Domain (UCC) SSL certificate on your Exchange Server (installing UCC in Exchange 2007 is demonstrated here) and we start with it. The scenarios, when you are using a Single Name SSL Certificate (How to Install a Single Name GoDaddy SSL Certificate in Exchange Server 2007) and Self Signed SSL certificate require additional steps and will be demonstrated in separate Screencasts.

In our demo, we are using a Single Exchange Server 2007 installed on a Windows Server 2008.

There are cases when you need to allow unauthenticated relaying for specific hosts or network devices in Exchange Server 2007. Typical examples are software packages (like accounting software) or network printers, scanners etc.
Exchange Server 2007 allows authenticated relaying, so if your device or application can authenticate, then this is the recommended approach.
On the other hand, if you don’t have a choice due to software or hardware limitations, your other option is allowing anonymous relay on Exchange Server 2007. As you do not want to turn the Exchange server into an open relay, you have to configure a new connector and restrict anonymous relay based on the source of incoming messages.

In the following Screencast, we will demonstrate how to allow anonymous relay on a receive connector for a specific IP address – a host which is running an accounting application.