In the following Step-by-Step video tutorial, you will see  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 this Screencast, we are configuring the maximum message size in OWA on an Exchange server 2007 running on Windows Server 2008.

Stay tuned on NetoMeter – subscribe to NetoMeter RSS.

Dean

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 video tutorial, we 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.

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.

Stay tuned on NetoMeter – subscribe to NetoMeter RSS.

Dean

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.

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.

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 the following Step-by-Step video tutorial, you will see how to configure Outlook Anywhere (RPC over HTTP) in Exchange Server 2007. We will also demonstrate how to configure Outlook 2007 and Outlook 2003 clients.

Stay tuned on NetoMeter – subscribe to NetoMeter RSS.

Dean