McAfee for Marshal

Version: 6.0.4, Last Revision: December 07, 2009

McAfee for Marshal is a configuration and update tool that allows the McAfee anti-virus engine to be used with Marshal products.

These notes are additional to the Help or other documentation.

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

Important Notes About This Release
What's New
Upgrading McAfee for Marshal
Uninstalling McAfee for Marshal
Change History

Important Notes About This Release

This release supports ONLY the following versions and releases of Marshal Products:
- MailMarshal SMTP release 5.5.7.X or above (including 6.X, MailMarshal 2006)
- WebMarshal 3.5.3.x or above (including 3.7, WebMarshal 2006, WebMarshal 6.X)
- MailMarshal Exchange 5.2 and above. MailMarshal Exchange versions prior to 5.2 are no longer supported.
  - Note: This is a change from previous versions.
ALL Marshal product(s) installed on a server must be upgraded to supported releases BEFORE you upgrade McAfee for Marshal. The installer checks for supported versions.
Standalone updater: You can install the updater on a server where no Marshal products are installed. This feature could be useful if:
- You have multiple Marshal servers and you want to minimize Internet bandwidth used.
- Proxy or firewall issues make it difficult for the Marshal server to access the Internet..
To use this feature:
- Configure the standalone update server to access the DAT and Engine updates from the Internet.
- Configure all Marshal servers to update from the standalone update server.

What's New

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

Version 6.0

Supports installation on Windows Vista and Windows Server 2008 (32 and 64 bit versions)
Now uses incremental DAT updates from McAfee
Allows for automatic download and update of the McAfee Engine
Allows for standalone installation of the updater on a server where no Marshal product is installed
Allows DAT and Engine updates to be retrieved from a local URL by HTTP or FTP, as well as by UNC path or local file share

Version 5.200.x

Updated McAfee engine to version 5.200
Updated user interface and updater to common framework

Version 5.100.x

Updated McAfee engine to version 5.100
Rebranded product
Renamed from "Marshal Integrated McAfee Antivirus (MIMA)" to "McAfee for Marshal"
The default installation location for new installations is now %ProgramFiles%\Marshal\McAfee for Marshal.
If DAT files are more than 30 days old, the McAfee engine now returns a "signatures out of date" response. MailMarshal SMTP and WebMarshal will handle this response as specified in the rule conditions. By default all items will be blocked or quarantined.

To upgrade from earlier versions of McAfee for Marshal, ensure that no MailMarshal Configurator or WebMarshal Console instances are running, and then run the product installer. Version 6.0 supports upgrade from 5.100.x and above only. If MIMA or NIMA version 4.x is installed, you must uninstall it and then install McAfee for Marshal.

After upgrading, verify the HTTP proxy settings for the Engine update if required in your network. The upgrade process duplicates the existing proxy settings used for the DAT files updates. See the Engine Updates tab of the configuration tool.
This version of McAfee for Marshal does not support MailMarshal Exchange 5.0 or 5.1.X. You must upgrade MailMarshal Exchange to version 5.2 before you upgrade McAfee for Marshal.
On upgrade from version 5.100 or below, if the scheduled check was every 4 hours or less, the new scheduled check will be hourly.
This version of McAfee for Marshal places log files in the /logs subfolder of the installation folder. Earlier versions placed log files in the root of the installation folder. On upgrade, any existing log files are not automatically deleted.
Upgrading restarts the MailMarshal Engine and Controller services in some cases.

Uninstalling

To uninstall McAfee for Marshal:

Remove the McAfee for Marshal scanner from all MailMarshal and WebMarshal scanning rules.
Delete the McAfee for Marshal scanner from the list of scanners in each installed product.
Restart the Engine services for each product. If the server has not been restarted since McAfee for Marshal was installed, restart the MailMarshal Controller.
Close the MailMarshal Configurator and WebMarshal Console.
Use the Add/Remove Programs control panel to uninstall McAfee for Marshal.

Change History

The following additional items have been changed or updated in the specific build versions of McAfee for Marshal listed.

To check for any later information, please see Marshal Knowledge Base article Q12192.

6.0.4 December 07, 2009

VS-381	Upgrading to version 6.0.3 did not stop the MailMarshal engine when required to replace the MSMcAfee.dll file. Fixed.
VS-385	Update to the install logic was required due to change in the MailMarshal Exchange registry location.

6.0.3.8294 October 21, 2009

VS-367	The MailMarshal engine could stop unexpectedly if configuration was being reloaded under heavy email load. Fixed.
VS-375	Visual C++ redistributable versions included in the installer have been updated.

6.0.2.7263 April 22, 2009

VS-355	If directories were locked during update, the update was not completed and all unsuccessful update files were never deleted. Fixed.
VS-363	On e10000 note appliance updates, the installation did not complete correctly because MailMarshal services were not stopped. Fixed.

6.0.1.6519 December 12, 2008

VS-323	MailMarshal Exchange 5.2 is the minimum version supported. 5.1.1 is no longer supported.
VS-262	Files marked as "offline" were not scanned by the McAfee engine and an error could result. Fixed.
VS-280	The Registry and directory structure have changed from previous versions.
VS-284	A file deletion utility could delete too many items in some rare circumstances. Fixed.

5.200.0.4629 December 19, 2007

VS-119	Downloaded files were retained in a Windows temporary directory. Fixed.
VS-150	The name of the updater service is now "Marshal McAfee Updater." The existing name is not changed during upgrades.

5.100.0.2735 March 6, 2007

VS-120

Files of zero size contained in archives were not properly handled. Fixed.

5.100.0.2454 January 10, 2007

VS-91	Included MMMcAfee.DLL for MailMarshal Exchange installations.
VS-111	Removed limitation of not being able to install on a MailMarshal Array Manager only installation.

5.100.0.2371 December 12, 2006

VS-5	Updated to version 5.100.0.194 of MCSCAN32.DLL.
VS-79	The Updater component now retrieves files from a new location. Files are unpacked to a new location. Only the three most recent sets are kept. For more information, see Marshal Knowledge Base article Q11490.
VS-80	Updated to version 5.100.0.1 of MSMcAfee DLL used by Marshal products for virus scanning.
VS-81	The McAfee for Marshal installer installs the MSMcAfee DLL to any installed Marshal products on the server where it is installed. The installer cleans up old DAT files.

4.4.0.0 9 June 2005

Upgraded to version 4.4.0.0 of MCSCAN32.DLL.
- Changed product revision number to match McAfee scanner engine version number
- Provides support for updated .DAT file format
- Requires 4510 or later DATs

1.3.0.1 3 February 2004

Upgraded to version 4.3.2.0 of MCSCAN32.DLL.
- Support for Microsoft Office 2003 XML documents
- Improved support for RAR formats
- Updated support for latest .ZIP file formats
- Requires 4297 or later DATs

1.2.0.1 7 August 2003

Upgraded to version 4.2.6.0 of MCSCAN32.DLL.

(Earlier changes have been removed from this document.)