MEG 7.0 Patch 2 (7.0.2) Now Available

[jsonger]

McAfee Email Gateway (MEG) 7.0 Patch 2 (7.0.2) is now available. This release includes new features, fixes, and enhancements including:

• Adds the ability to import certain settings from MEG 6.7.2 with Hotfix 8 to MEG 7.
• Secure Web Delivery enhanced to support Pull Messages in the Blade and Cluster environments

To download MEG 7.0 Patch 2, go to the McAfee downloads site at: http://www.mcafee.com/us/downloads/downloads.aspx.  

For a full list of changes, see the Release Notes in PD24053:
https://kc.mcafee.com/corporate/index?page=content&id=PD24053.

For additional resources to assist with the migration from McAfee Email Gateway 6.7.2 HF8, see:

PD23757 - Email Gateway 6.7.2 to 7.0.2 Migration Guide:
https://kc.mcafee.com/corporate/index?page=content&id=PD23757

KB76333 - Resources for migrating from Email Gateway (Iron Mail) 6.7.2 to MEG 7:
https://kc.mcafee.com/corporate/index?page=content&id=KB76333

KB76333 includes links to articles on the following topics:

• Console UI mapping
• Exporting and importing TLS certificates
• How to create Content Analysis or Envelope Analysis rules
• How to configure Data Loss Prevention
• SMTPI/O conversion
• Virtual Hosts conversion
• Policy-based encryption

For Technical Support issues, contact your Support Account Manager (SAM), or go to https://mysupport.mcafee.com.

Message was edited by: jsonger on 11/14/12 1:14:17 PM CST

[Regis]

Howdy J,

Is a delta between this RTW release of p2 and the RTS release available?   Curious if the issues in the Administration tab under IE were addressed and whether periodic head scratchers in certain Detailed Report searches timing out might be among them.

It remains a very good idea to make sure you have a current configuration backup for each of your boxes, and having the p1 ISO uploaded into the Rescue image part of the appliance (I used McAfee-MEG-7.0-2151.119.iso )  in case you have to fall back.    I was probably a special egg, but if anyone else runs into a "Kernel panic - not syncing: VFS: Unable to mount root fson unknown-block(0,0)"  on the post-p2 reboot (when coming from a hotfixed p1 build on a 5000 appliance),  or into "cannot detect hardware platform"  issues, rescuing back to p1, re-applying p2, and importing the config backup that was taken at p1 works a treat and isn't as time consuming as you'd think.