M86 MailMarshal Exchange

Version: 7.0, Last Revision: June 28, 2011

These notes are additional to the MailMarshal Exchange User Guide and supersede information supplied in that Guide.

The information in this document is current as of the date of publication. To check for any later information, please see M86 Security Knowledge Base article Q13890.

Table of Contents

What's New
Upgrading MailMarshal Exchange
Uninstalling
Hardware and Software Requirements
Change History

What's New

For more information about additional minor features and bug fixes, see the change history.

Features New in 7.0

• Array Architecture: MailMarshal Exchange now uses the same array architecture as MailMarshal SMTP 6.X.
• MailMarshal SMTP features: MailMarshal Exchange has been updated with many rule elements and features found in MailMarshal SMTP 6.X.
• No spam filtering functions: MailMarshal Exchange does not provide SpamCensor or other anti-spam functionality. The "known threats zero day" category is available and automatically updated.
• New Reporting application: Reporting on MailMarshal Exchange activity is through Marshal Reporting Console (version 2.5 or above).

Upgrading MailMarshal Exchange

MailMarshal Exchange version 7.0 uses a different architecture to earlier versions of MailMarshal Exchange. Direct upgrade is not supported.

• To assist with migration, MailMarshal Exchange 7.0 can be installed on the same server as MailMarshal Exchange 5.3 or MailMarshal SMTP.
• MailMarshal Exchange 7.0 requires a new product key. You can request a key from the Configurator after installing the product.
• The MailMarshal Exchange 7.0 and 5.3 Agents CANNOT both be used to process messages on the same server.
• If the MailMarshal Exchange 7.0 Agent is enabled on an Exchange Server where MailMarshal Exchange 5.3 is running, the version 5.3 Agent will be uninstalled. You must not enable the 5.3 and 7.0 Agents at the same time, because significant problems with email processing would result.
• You can release messages quarantined by version 5.3, using the 5.3 Console.
• Best practice for the upgrade is to stop the Microsoft Exchange Transport service and allow queues to clear before enabling the MailMarshal Exchange 7.0 Agent.
• In some cases, when you uninstall version 5.3 after installing version 7.0, you must restart the system.
• If you wish to return to version 5.3, uninstall the 7.0 Agent before you install the 5.3 Agent.

Uninstalling

MailMarshal Exchange can be installed in a variety of scenarios. For full information on uninstalling MailMarshal Exchange from a production environment, see the MailMarshal Exchange User Guide.

To uninstall a trial installation on a single computer:

1. Stop and disable the MailMarshal Exchange Agent for all Exchange servers.
2. Close all instances of the MailMarshal Exchange Configurator and MailMarshal Exchange Console. Stop the websites of Web Components.
3. Use Add/Remove Programs from the Windows Control Panel to remove MailMarshal Exchange.
4. Use Add/Remove Programs from the Windows Control Panel to remove additional components you may have installed, such as Web Components.
5. If you have installed any components (such as the Configurator, Console, or Web Components) on other computers, uninstall them.
6. If you have installed SQL Express specifically to support MailMarshal Exchange and no other applications are using it, uninstall SQL Express.

Hardware and Software Requirements

Software

MailMarshal Exchange is supported in the following environments:

• Email processing nodes:
  • 64 bit OS only
  • Windows Server 2008 SP2, Windows Server 2008 R2, Windows Server 2003 SP2, SBS 2008 SP2
  • Exchange Server 2007 SP2 or SP3; Exchange Server 2010 SP1
  • Active Directory
  • Hub Transport Role
  • 8.3 file name creation must be enabled
• Array Manager:
  • Windows Server 2008 SP2, Windows Server 2008 R2, Windows Server 2003 SP2, SBS 2008 SP2
  • 64 bit OS preferred (required for single-server installation)
• Console and Configurator:
  • Windows Server 2008 SP2, Windows Server 2008 R2, Windows Server 2003 SP2, SBS 2008 SP2
  • Windows XP Professional SP3 (32 bits only)
  • Windows Vista SP2, Windows 7 RTM or SP1
  • 64 bit OS preferred
• Web Components:
  • Windows Server 2008 SP2, Windows Server 2008 R2, Windows Server 2003 SP2, SBS 2008 SP2
  • 64 bit OS preferred
  • .NET Framework 4
• SQL Server:
  • SQL Server 2005 SP3, SQL Server 2005 R2
  • SQL Server 2008 SP1, SQL Server 2008 R2

MailMarshal Exchange is a 32 bit application.

Note: You cannot install the MailMarshal Exchange Web components on Windows 2003 (IIS 6) together with Exchange 2007 Client Access Role (Outlook Web Access). Microsoft does not support side-by-side installation of 32 and 64 bit web applications to Windows 2003. If the MailMarshal Exchange website is required in this scenario, install it on another server.

Hardware

Hardware required is dependent on Microsoft Exchange Server. Follow Microsoft recommendations. Be aware that MailMarshal Exchange processing has a noticeable impact on email throughput.

You may require additional hard disk space depending on your archiving and quarantine retention policies. For default policies on a typical 1000 user server, M86 Security recommends you allow an additional 50 GB of free disk space for text logs, quarantine and archiving folders.

Installation recommendations

To help ensure smooth functioning of MailMarshal Exchange, M86 Security recommends the following:

• Install MailMarshal Exchange on all Hub Transport servers to ensure that all messages are scanned.
• For performance reasons, select a DLL integrated virus scanner. Do not use a command line scanner.
• For performance reasons, do not install other roles on the servers (particularly, do not install the Unified Messaging role)
• Although it is possible to add some Microsoft Edge Transport components to a Hub Transport server, M86 Security recommends you do not add these components.
• Do not change the user for the Exchange Transport Service.
• Do not manually adjust settings in the Exchange agents.config file, the transport agent priorities, or the default settings for the Replay directory.

Usage Notes

• To view the MailMarshal Exchange performance counters in Windows Server 2008 (64 bits), you must run the MMC in 32 bit mode. Use the following command line to start Performance Monitor:
  MMC /32 perfmon.msc

Change History       

Note: The information in this document is current as of the date of publication. To check for any later information, please see M86 Security Knowledge Base article Q13890.

7.0.2 (June 28, 2011)

7.0.1 (March 21, 2011)

• Initial release of new architecture.

© Copyright 2011 M86 Security. All rights reserved.

All text and figures included in this publication are the exclusive property of M86 Security. This document may not, in whole or in part, be copied, published or reproduced without prior written consent from M86 Security. Every effort has been made to ensure the accuracy of the content contained in this document. Such content is provided “as is” without warranty of any kind. M86 Security disclaims all warranties and conditions with regard to this content, including all expressed or implied warranties and conditions of merchantability, and fitness for a particular purpose. The company shall not under any circumstance be liable for any errors or damages of any kind (including but not limited to compensatory, special, indirect or consequential damages) in connection with the document’s contents. Any information in this document is subject to change without notice.

M86 Security, the M86 Security logo and M86-branded products are registered trademarks under license by M86 Security. All other product and company names mentioned herein are trademarks or registered trademarks of their respective companies. All rights reserved.