McAfee VirusScan Enterprise 5100 Engine Released
As posted on the McAfee engine-beta mailing list:
All,
I apologise with the delay of this message but we
have experienced some issues posting the various Engine packages, which are still in the process of being
resolved, but I'm pleased to announce that the 5.1.00 AV Engine has
concluded its beta cycle.
The Windows version of the 5.1.00 Engine has been
released in an Engine-only SuperDAT. In approximately 4 weeks time it will be
incorporated into the normal SuperDAT and placed
on the FTP site and the default McAfee MAA repositories.
The 5.1.00 Windows and Unix command line scanners
are available via the main McAfee download.
The 5.1.00 version of the Netware Engine is still
undergoing testing and will be released in the
mid August timeframe. The main
McAfee Beta site reflects this by having a
hyperlink to the Release Candidate version
of this Engine and the Beta forum will remain open for discussion until this
Engine has been fully released.
Could you please ensure that you remove all Beta
and Release Candidate versions of the
engine prior to upgrading to the official release code. In order to do this
please review the guidelines below.
Regards,
Darren
McAfee Engine Beta Team
Overview:
The following text aims to provide
scenarios and highlight potential pitfalls for upgrading from the 4.4.00 or pre
RTW 5.1.00 Engines.
Problem:
How to deploy the 5.1.00 Engine
update effectively.
Note that it is expected that the 5.1.00 Engine
will be rolled into the main update site & all update packages approximately
4 weeks after the release of the Engine Only SuperDat package.
Solution:
On the release of the 5.1.00
Engine only SuperDat package the following changes will also occur:
An ePO 3.x deployable 5.1.00 Engine-only package
will be released. This is so that the 5.1.00 Engine can be added to the ePO 3.x
repository, or to a stand-alone MAA installation.
Update Scenarios:
1. Not using ePO, Not using local MAA, Not Using
CommonUpdater Site.
Update the engine locally using the Engine-only
SuperDat package.
This will require a force (/F) option if you're
running a pre RTW 5.1.00 Engine and it will also require a minimum of 4777 Anti-Virus definition (DAT) files too.
2. Not using ePO, Not using local MAA, Using
the CommonUpdater Site.
Update the engine locally using the Engine-only
SuperDat package (as in 1. above).
3. Not using ePO, Using local MAA.
Download
and check-in the Engine-Only ePO package into your MAA installation and follow
the product user guide as normal.
4. Using ePO 3.x
ePO 3.x has an integrated
MAA repository with additional functionality compared to stand-alone MAA.
Download and check-in the Engine-only ePO package to roll out to your client
machines.
Note: ePO 3.x has the option of checking these
packages into one of three branches - Current, Previous & Evaluation. This
means there are more options for deploying the
5.1.00 Engine.
If the Engine is checked-in to the current branch
and providing the ePO agents have default "update" settings, the 5.1.00 Engine
will be updated on all client
machines.
If you do not want to rollout to all client
machines immediately, please check the package in to the evaluation branch and
change the ePO agent "update" settings so the
relevant update option (SuperDAT or Engine) is using the evaluation
branch.
Once satisfied with the 5.1.00 Engine, check the
package into current and reset default agent "update" settings to
current.
Make sure you have configured an Agent Update task
when changing agent settings.