McAfee VirusScan Enterprise antivirus software Implementation Guide
تبلیغات
تبلیغات
VirusScan
®
Enterprise
Updating
version 7.1.0
Implementation Guide
Revision 1.0
COPYRIGHT
© 2003 Networks Associates Technology, Inc. All Rights Reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form or by any means without the written permission of Networks Associates Technology, Inc., or its suppliers or affiliate companies. To obtain this permission, write to the attention of the
Network Associates legal department at: 5000 Headquarters Drive, Plano, Texas 75024, or call +1-972-963-8000.
TRADEMARK ATTRIBUTIONS
Active Firewall, Active Security, Active Security (in Katakana), ActiveHelp, ActiveShield, AntiVirus Anyware and design, Appera, AVERT, Bomb
Shelter, Certified Network Expert, Clean-Up, CleanUp Wizard, ClickNet, CNX, CNX Certification Certified Network Expert and design, Covert,
Design (stylized N), Disk Minder, Distributed Sniffer System, Distributed Sniffer System (in Katakana), Dr Solomon’s, Dr Solomon’s label, E and
Design, Entercept, Enterprise SecureCast, Enterprise SecureCast (in Katakana), ePolicy Orchestrator, Event Orchestrator (in Katakana), EZ SetUp,
First Aid, ForceField, GMT, GroupShield, GroupShield (in Katakana), Guard Dog, HelpDesk, HelpDesk IQ, HomeGuard, Hunter, Impermia,
InfiniStream, Intrusion Prevention Through Innovation, IntruShield, IntruVert Networks, LANGuru, LANGuru (in Katakana), M and design,
Magic Solutions, Magic Solutions (in Katakana), Magic University, MagicSpy, MagicTree, McAfee, McAfee (in Katakana), McAfee and design,
McAfee.com, MultiMedia Cloaking, NA Network Associates, Net Tools, Net Tools (in Katakana), NetAsyst, NetCrypto, NetOctopus, NetScan,
NetShield, NetStalker, Network Associates, Network Performance Orchestrator, Network Policy Orchestrator, NetXray, NotesGuard, nPO, Nuts
& Bolts, Oil Change, PC Medic, PCNotary, PortalShield, Powered by SpamAssassin, PrimeSupport, Recoverkey, Recoverkey – International,
Registry Wizard, Remote Desktop, ReportMagic, RingFence, Router PM, Safe & Sound, SalesMagic, SecureCast, SecureSelect, Service Level
Manager, ServiceMagic, SmartDesk, Sniffer, Sniffer (in Hangul), SpamKiller, SpamAssassin, Stalker, SupportMagic, ThreatScan, TIS, TMEG,
Total Network Security, Total Network Visibility, Total Network Visibility (in Katakana), Total Service Desk, Total Virus Defense, Trusted Mail,
UnInstaller, VIDS, Virex, Virus Forum, ViruScan, VirusScan, WebScan, WebShield, WebShield (in Katakana), WebSniffer, WebStalker, WebWall,
What's The State Of Your IDS?, Who’s Watching Your Network, WinGauge, Your E-Business Defender, ZAC 2000, Zip Manager are registered trademarks or trademarks of Network Associates, Inc. and/or its affiliates in the US and/or other countries. Sniffer
®
brand products are made only by Network Associates, Inc. All other registered and unregistered trademarks in this document are the sole property of their respective owners.
LICENSE INFORMATION
License Agreement
NOTICE TO ALL USERS: CAREFULLY READ THE APPROPRIATE LEGAL AGREEMENT CORRESPONDING TO THE LICENSE YOU PURCHASED,
WHICH SETS FORTH THE GENERAL TERMS AND CONDITIONS FOR THE USE OF THE LICENSED SOFTWARE. IF YOU DO NOT KNOW WHICH
TYPE OF LICENSE YOU HAVE ACQUIRED, PLEASE CONSULT THE SALES AND OTHER RELATED LICENSE GRANT OR PURCHASE ORDER
DOCUMENTS THAT ACCOMPANIES YOUR SOFTWARE PACKAGING OR THAT YOU HAVE RECEIVED SEPARATELY AS PART OF THE PURCHASE
(AS A BOOKLET, A FILE ON THE PRODUCT CD, OR A FILE AVAILABLE ON THE WEB SITE FROM WHICH YOU DOWNLOADED THE SOFTWARE
PACKAGE). IF YOU DO NOT AGREE TO ALL OF THE TERMS SET FORTH IN THE AGREEMENT, DO NOT INSTALL THE SOFTWARE. IF APPLICABLE,
YOU MAY RETURN THE PRODUCT TO NETWORK ASSOCIATES OR THE PLACE OF PURCHASE FOR A FULL REFUND.
Attributions
This product includes or may include:
Software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( http://www.openssl.org/ ).
Cryptographic software written by Eric A. Young ( [email protected]
) and software written by Tim J. Hudson ( [email protected]
).
Some software programs that are licensed (or sublicensed) to the user under the GNU General Public License (GPL) or other similar Free Software licenses which, among other rights, permit the user to copy, modify and redistribute certain programs, or portions thereof, and have access to the source code. The GPL requires that for any software covered under the GPL which is distributed to someone in an executable binary format, that the source code also be made available to those users. For any such software covered under the GPL, the source code is made available on this CD. If any Free
Software licenses require that Network Associates provide rights to use, copy or modify a software program that are broader than the rights granted in this agreement, then such rights shall take precedence over the rights and restrictions herein.
Software originally written by Henry Spencer, Copyright 1992, 1993, 1994, 1997 Henry Spencer.
Software originally written by Robert Nordier, Copyright
©
1996-7 Robert Nordier. All rights reserved.
Software written by Douglas W. Sauder.
Software developed by the Apache Software Foundation ( http://www.apache.org/ ).
International Components for Unicode (“ICU”) Copyright
©
1995-2002 International Business Machines Corporation and others. All rights reserved.
Software developed by CrystalClear Software, Inc., Copyright
©
2000 CrystalClear Software, Inc.
FEAD
®
Optimizer
®
technology, Copyright Netopsystems AG, Berlin, Germany.
Issued SEPTEMBER 2003 / VirusScan
®
Enterprise software version 7.1.0
D
OCUMENT
B
UILD
003-EN
Contents
3 Updating Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4 Managing the AutoUpdate Repository List . . . . . . . . . . . . . . . . . 29
Implementation Guide iii
Contents
5 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
iv VirusScan
®
Enterprise software version 7.1.0
Preface
This guide describes the McAfee
®
VirusScan
®
Enterprise updating process, and provides the following information:
Overview of the update directory structure. See
.
Overview of the update process using McAfee AutoUpdate. See
.
Information about specifying repositories for both existing and new customers. See
.
Performing updates using different scenarios. These scenarios include using
VirusScan Enterprise, McAfee AutoUpdate Architect
™
, and McAfee
Installation Designer
™
independently, or in a mixed environment. See
Managing the repository list using the VirusScan Enterprise, McAfee
Installation Designer, and McAfee AutoUpdate Architect. See
Troubleshooting information that applies to updating with VirusScan
.
Roadmap for getting additional information.
Audience
This information is intended primarily for two audiences:
Network administrators who are responsible for their company’s anti-virus and security program.
Users who are responsible for updating virus definition (
DAT
) files on their workstation, or configuring the software’s detection options.
Implementation Guide 5
Preface
Conventions
This guide Help file uses the following conventions:
Bold
Courier
Italic
<
TERM
>
NOTE
WARNING
All words from the user interface, including options, menus, buttons, and dialog box names.
Example
Type the
User name
and
Password
of the desired account.
Text that represents something the user types exactly; for example, a command at the system prompt.
Example
To enable the agent, run this command line on the client computer:
FRMINST.EXE /INSTALL=AGENT
/SITEINFO=C:\TEMP\SITELIST.XML
For emphasis or when introducing a new term; for names of product manuals and topics (headings) within the manuals.
Example
Refer to the VirusScan Enterprise Product Guide for more information.
Angle brackets enclose a generic term.
Example
In the console tree under
ePolicy Orchestrator
, right-click
<
SERVER
>.
Supplemental information; for example, an alternate method of executing the same command.
Important advice to protect a user, computer system, enterprise, software installation, or data.
6 VirusScan
®
Enterprise software version 7.1.0
Getting information
Getting information
Installation Guide *†
Product Guide *
Help §
System requirements and instructions for installing and starting the software.
VirusScan Enterprise 7.1.0 Installation Guide
Product introduction and features, detailed instructions for configuring the software, information on deployment, recurring tasks, and operating procedures.
VirusScan Enterprise 7.1.0 Product Guide
McAfee Installation Designer Product Guide
McAfee AutoUpdate Architect Product Guide
High-level and detailed information on configuring and using the software.
What’s This? field-level help.
Configuration Guide *
For use with ePolicy Orchestrator
™
. Procedures for configuring, deploying, and managing your McAfee Security product through ePolicy Orchestrator management software.
Implementation Guide *
Supplemental information for product features, tools, and components.
Release Notes ‡
ReadMe. Product information, resolved issues, any known issues, and last-minute additions or changes to the product or its documentation.
Contacts ‡
Contact information for McAfee Security and Network Associates services and resources: technical support, customer service, AVERT (Anti-Virus Emergency
Response Team), beta program, and training. This file also includes phone numbers, street addresses, web addresses, and fax numbers for Network
Associates offices in the United States and around the world.
*
An Adobe Acrobat .PDF file on the product CD or the McAfee Security download site.
†
A printed manual that accompanies the product CD. Note: Some language manuals may be available only as a .PDF file.
‡
Text files included with the software application and on the product CD.
§
Help accessed from the software application: Help menu and/or Help button for page-level help; right-click option for What’s
This? help.
Implementation Guide 7
Preface
Contacting McAfee Security & Network Associates
Technical Support
Home Page
KnowledgeBase Search http://www.networkassociates.com/us/support/ https://knowledgemap.nai.com/phpclient/homepage.aspx
PrimeSupport Service Portal
*
http://mysupport.nai.com
McAfee Security Beta Program
http://www.networkassociates.com/us/downloads/beta/
Security Headquarters — AVERT (Anti-Virus Emergency Response Team)
Home Page http://www.networkassociates.com/us/security/home.asp
Virus Information Library
Submit a Sample —
AVERT WebImmune
AVERT DAT Notification
Service
Download Site
http://vil.nai.com
https://www.webimmune.net/default.asp
http://www.networkassociates.com/us/downloads/updates/
Home Page http://www.networkassociates.com/us/downloads/
DAT File and Engine Updates http://www.networkassociates.com/us/downloads/updates/
Product Upgrades
Training
*
ftp://ftp.nai.com/pub/antivirus/datfiles/4.x
https://secure.nai.com/us/forms/downloads/upgrades/login.asp
McAfee Security University http://www.networkassociates.com/us/services/education/mcafee/unive rsity.htm
Network Associates Customer Service
http://www.nai.com/us/index.asp
http://www.networkassociates.com/us/products/mcafee_security_home
.htm
US, Canada, and Latin America toll-free:
Phone
+1-888-VIRUS NO
or
+1-888-847-8766
Monday – Friday, 8 a.m. – 8 p.m., Central Time
For additional information on contacting Network Associates and McAfee Security— including toll-free numbers for other geographic areas — see the Contact file that accompanies this product release.
*
Logon credentials required.
8 VirusScan
®
Enterprise software version 7.1.0
Introduction
1
The VirusScan Enterprise software depends on information in the virus definition
(
DAT
) files to identify viruses. Without updated files, the product software might not detect new viruses or respond to them effectively.
With VirusScan Enterprise you can download updates for both
DAT
files and scanning engines from the Network Associates repository. VirusScan 4.5.x and
NetShield
®
4.5 allowed updating via
FTP
,
UNC
share, or local path. The VirusScan
Enterprise software adds
HTTP
to the list.
You can use VirusScan Enterprise, McAfee Installation Designer, or the McAfee
AutoUpdate Architect utility to configure and manage various aspects of updating. For example, to download a HotFix, a Service Pack, an
EXTRA
.
DAT
, a
Super
DAT
package, or a .
CAB
file, use the McAfee AutoUpdate Architect utility to check these packages into the AutoUpdate repository.
The information in this document is based on the assumption that you have installed the VirusScan Enterprise software. For information about installing the software, see the VirusScan Enterprise Installation Guide.
The following topics are covered in this section:
.
Implementation Guide 9
Introduction
Updating tasks and tools
The VirusScan Enterprise software provides two methods for performing updates:
The AutoUpdate task is used to perform scheduled or immediate updates.
The VirusScan Enterprise software provides a default update task that is scheduled to update every Friday at 5:00 p.m., with one-hour randomization. You can rename and reconfigure this default update task. You can also create additional update tasks to meet your updating requirements. See the VirusScan Enterprise 7.1.0 Product Guide for more information creating and configuring update tasks.
The AutoUpdate task can be used in several ways to perform updating. See
on page 21 for more information.
The Rollback
DAT
s tool is used to roll back the
DAT
files to the last backed up version.
You can use this tool to roll back the
DAT
files to the last backed up version, if you find that the current
DAT
files are corrupt or incompatible for some reason. Once the rollback occurs, you cannot go back to the previous version again. The next time an update is performed, the
DAT
version in the registry is compared with the
DAT
files in the update repository. If the new
DAT
files are the same as the ones flagged in the registry, no update occurs. See the VirusScan
Enterprise Product Guide for more information about rolling back the
DAT
files.
10 VirusScan
®
Enterprise software version 7.1.0
AutoUpdate overview
When you perform an AutoUpdate task, these activities occur:
AutoUpdate overview
Figure 1-1. AutoUpdate task overview
Implementation Guide 11
Introduction
Update directory structure
The VirusScan Enterprise software relies on a directory structure to update itself.
This directory structure also supports VirusScan 4.5.x and NetShield 4.5 for updating, as long as the entire directory structure is replicated in the same locations that VirusScan 4.5.1 used for updating. You can use the mirror task to replicate a directory structure. For more information about mirror tasks, see the
VirusScan Enterprise Product Guide.
The following shows the directory structure in the repository after using a mirror task to replicate the Network Associates repository.
Figure 1-2. Update directory structure in the repository
For more information about the repository directory structure, see
Enterprise to replicate the update structure
.
12 VirusScan
®
Enterprise software version 7.1.0
Repositories
2
A repository, or download site, is a location from which you retrieve updates. The repository list,
SITELIST
.
XML
, contains one or more repositories. The number of repositories that you need depends on your updating requirements. This section describes how existing and new customers can specify repositories.
The VirusScan Enterprise software comes pre-configured with two repositories: ftp://ftp.nai.com/CommonUpdater http://update.nai.com/Products/CommonUpdater
NOTE
The
FTP
repository is the default site. If you plan to use the
FTP repository to perform updates, you are automatically configured to do so after the VirusScan Enterprise installation process completes.
You can use either of these sites to download the latest updates if you are using
VirusScan Enterprise 7.1.0 exclusively, or if you are using VirusScan Enterprise
7.1.0 in a mixed environment with VirusScan 4.5.1 or NetShield 4.5.
See Editing the AutoUpdate repository list in the VirusScan Enterprise Product Guide for more information about configuring repositories.
You can specify repositories depending on your updating needs as follows:
Implementation Guide 13
Repositories
Existing customers
If you are installing the VirusScan Enterprise 7.1.0 software over a previous version of VirusScan, NetShield, or VirusScan Enterprise, you can select the
preserve settings
option during installation.
NOTE
When you select the
preserve settings
option, all settings are preserved with one exception. If you had your previous version of VirusScan or NetShield set to update via an
FTP repository, and you select the
preserve settings
option during the installation process, the
FTP
repository location is automatically updated to the new Network Associates
FTP repository location that is being used with VirusScan
Enterprise.
FTP repository
The default Network Associates
FTP
repository is located at: ftp://ftp.nai.com/CommonUpdater
NOTE
The Network Associates
FTP
repository is the default download site. If you plan to continue to use the
FTP repository to perform updates, you are automatically configured to do so after the VirusScan Enterprise installation process completes.
UNIX FTP servers as updating or replication servers
Using
UNIX FTP
servers as updating or replication servers applies to VirusScan
Enterprise and McAfee AutoUpdate Architect.
UNIX FTP
servers are supported with the following restriction:
Our updating schema is not aware of relative user paths for the updating and replication accounts. This affects the update path that you configure in
VirusScan Enterprise and the replication strategy that you design and manage with McAfee AutoUpdate Architect.
If two separate accounts (such as an anonymous user and an authenticated user) are being used to access the same repository, then the path from the root (/) of the file system to the repository must be the same for both
FTP
users.
14 VirusScan
®
Enterprise software version 7.1.0
Existing customers
This means that if you execute the chroot command on one user, you must execute
chroot on the other, making sure to use either the same location or symbolic links to that location. Therefore, if anonymous defines the root as /var/ftp, then the replicator account’s home directory should be /var/ftp; and the
FTP
server should be configured to execute the chroot replicator to its home directory.
NOTE
Setting symbolic links is beyond the scope of this document; refer to your
UNIX
documentation.
UNC share or local path
If you are using a
UNC
share or a local path to perform updates, and plan to continue doing so, choose from these options:
Preserve settings —
Use the Setup utility to install the VirusScan Enterprise software, and select the
preserve settings
option during the installation process.
Pre-configuration option —
Use McAfee Installation Designer to modify the
VirusScan Enterprise installation (.
MSI
) file before installing the VirusScan
Enterprise software. See the McAfee Installation Designer Product Guide for details.
Post installation option —
Use McAfee Installation Designer to save your current settings to a .
CAB
file, then install the VirusScan Enterprise software.
After the installation completes, place the .
CAB
file in the MID folder located in the VirusScan Enterprise installation directory. See the McAfee Installation
Designer Product Guide for details.
HTTP repository
The default Network Associates
HTTP
repository is located at: http://update.nai.com/Products/CommonUpdater
VirusScan 4.5.x and NetShield 4.5 did not allow updating via an
HTTP
repository.
See
on page 18 for information about specifying an
HTTP repository.
Implementation Guide 15
Repositories
New customers
If you are installing the VirusScan Enterprise software for the first time, you have the following options for specifying repositories:
FTP repository
The default Network Associates
FTP
repository is located at: ftp://ftp.nai.com/CommonUpdater
NOTE
The Network Associates
FTP
repository is the default download site. If you plan to use the
FTP
repository to perform updates, you are automatically configured to do so after the
VirusScan Enterprise installation process completes.
UNIX FTP servers as updating or replication servers
Using
UNIX FTP
servers as updating or replication servers applies to VirusScan
Enterprise and McAfee AutoUpdate Architect.
UNIX FTP
servers are supported with the following restriction:
Our updating schema is not aware of relative user paths for the updating and replication accounts. This affects the update path that you configure in
VirusScan Enterprise and the replication strategy that you design and manage with McAfee AutoUpdate Architect.
If two separate accounts (such as an anonymous user and an authenticated user) are being used to access the same repository, then the path from the root (/) of the file system to the repository must be the same for both
FTP
users.
This means that if you execute the chroot command on one user, you must execute
chroot on the other, making sure to use either the same location or symbolic links to that location. Therefore, if anonymous defines the root as /var/ftp, then the replicator accounts home directory should be /var/ftp; and the
FTP
server should be configured to chroot replicator to its home directory.
NOTE
Setting symbolic links is beyond the scope of this document; refer to your
UNIX
documentation.
16 VirusScan
®
Enterprise software version 7.1.0
New customers
UNC share or local path
If you plan to perform updates using a
UNC
share or a local path, you must install the VirusScan Enterprise software, then configure the
UNC
share or the local path in the AutoUpdate repository list. See Editing the AutoUpdate repository list in the
VirusScan Enterprise Product Guide for details.
After you have installed the VirusScan Enterprise software and configured the
UNC
share, you have these configuration options for future installations of
VirusScan Enterprise:
Pre-configuration option —
Use McAfee Installation Designer to modify the
VirusScan Enterprise installation (.
MSI
) file with the
UNC
settings, then use this file to ensure all future VirusScan Enterprise installations use those
UNC settings. See the McAfee Installation Designer Product Guide for details.
Post installation option —
Use McAfee Installation Designer to create a .
CAB file that specifies the
UNC
settings. Use the .
CAB
file for all future VirusScan
Enterprise installations that are to be configured with the
UNC
settings. See the
McAfee Installation Designer Product Guide for details.
NOTE
We strongly recommend that you test any configuration process before using it for deployment.
Implementation Guide 17
Repositories
HTTP repository
The default Network Associates
HTTP
repository is located at: http://update.nai.com/Products/CommonUpdater
If you plan to perform updates using an
HTTP
repository, you must install the
VirusScan Enterprise software, then configure the
HTTP
repository in the
AutoUpdate repository list. See Editing the AutoUpdate repository list in the
VirusScan Enterprise Product Guide for details.
After you have installed the VirusScan Enterprise software and configured the
HTTP
repository, you have these configuration options for future installations of
VirusScan Enterprise:
Pre-configuration option —
Use McAfee Installation Designer to modify the
VirusScan Enterprise installation (.
MSI
) file with the
HTTP
settings, then use this file to ensure all future VirusScan Enterprise installations use those
HTTP settings. See the McAfee Installation Designer Product Guide for details.
Post installation option —
Use McAfee Installation Designer to create a .
CAB file that specifies the
HTTP
settings. Use the .
CAB
file for all future VirusScan
Enterprise installations that are to be configured with the
HTTP
settings. See the
McAfee Installation Designer Product Guide for details.
NOTE
We strongly recommend that you test any configuration process before using it for deployment.
18 VirusScan
®
Enterprise software version 7.1.0
New customers
HTTP with proxy environments
VirusScan Enterprise 7.1.0 uses the proxy settings for the locally installed version of Internet Explorer 4.0 or higher, to authenticate to the proxy server. If you configure VirusScan Enterprise to use the
HTTP
repository, it is important to consider the following situations when you are designing your update strategy:
Multiple authentications with proxy and firewalls
— VirusScan Enterprise cannot update if your environment needs to authenticate to more than one device, such as to a proxy server and a firewall. The update may appear to take longer than expected, and time out with the following error:
Cannot Authenticate to Proxy server error or Access denied - You are not
permitted to see this page error.
Content-scanning firewalls —
Some content-scanning firewall programs include an option to scan incoming traffic for non-business related material.
Network Associates has implemented security checks to monitor whether our download files have been modified in any way and are valid. Most content-scanning firewalls that were tested do not modify our packages during download. If the content-scanning firewall does modify the Network
Associates packages, you may see an Unable to open files error, or other errors depending on what was changed about our files. If possible, you should configure the content-scanning firewall program so that it does not scan the
Network Associates download site.
Implementation Guide 19
Repositories
20 VirusScan
®
Enterprise software version 7.1.0
Updating Scenarios
3
You can use several updating methods, depending on your environment and updating needs.
Refer to the following update scenarios for information about updating in your environment:
Updating from the Network Associates repository
Multiple sites updating from the Network Associates repository
Multiple sites updating internally with a staged deployment
Implementation Guide 21
Updating Scenarios
Updating from the Network Associates repository
Use this scenario for updating
DAT
and engine files from the Network Associates repository.
NOTE
To download HotFix, Service Pack,
EXTRA
.
DAT
, Super
DAT package, or .
CAB
files, see
Using McAfee AutoUpdate Architect
Figure 3-1. Updating from the Network Associates repository
Pre-configuration options
— Use McAfee Installation Designer to customize the VirusScan Enterprise installation (.
MSI
) file. If you do so, the new defaults take effect when you install theVirusScan Enterprise software to other computers.
See the McAfee Installation Designer Product Guide for details.
22 VirusScan
®
Enterprise software version 7.1.0
Updating from the Network Associates repository
FTP repository —
The Network Associates
FTP
repository is the default download site.
NOTE
If you are currently using the default VirusScan 4.5.1
FTP repository, or plan to use the
FTP
repository to perform updates after installing VirusScan Enterprise, you are automatically configured to do so after the installation process completes. No changes are required to the VirusScan
Enterprise installation (.
MSI
) file.
The default Network Associates
FTP
repository is located at: ftp://ftp.nai.com/CommonUpdater
Preserve settings
— If you are installing VirusScan Enterprise over a previous version of VirusScan or NetShield, and wish to preserve settings, select the
preserve settings
option during installation.
NOTE
If you are currently using the default VirusScan 4.5.1
FTP repository, VirusScan Enterprise automatically updates to the new default
FTP
repository, even if you choose to
preserve settings
.
HTTP repository or internal UNC share
— Use McAfee Installation Designer to configure these repositories before or after installing VirusScan Enterprise.
See the McAfee Installation Designer Product Guide for details.
The default Network Associates
HTTP
repository is located at: http://update.nai.com/Products/CommonUpdater
Implementation Guide 23
Updating Scenarios
Multiple sites updating from the Network
Associates repository
Use this scenario to update multiple sites with the
DAT
and engine files from the
Network Associates repository.
NOTE
To download HotFix, Service Pack,
EXTRA
.
DAT
, Super
DAT package, or .
CAB
files, see
Using McAfee AutoUpdate Architect
Figure 3-2. Multiple sites updating from the Network Associates repository
Pre-configuration options
— Use McAfee Installation Designer to customize the VirusScan Enterprise installation (.
MSI
) file. If you do so, the new defaults take effect when you install theVirusScan Enterprise software to other computers.
See the McAfee Installation Designer Product Guide for details.
24 VirusScan
®
Enterprise software version 7.1.0
Multiple sites updating from the Network Associates repository
FTP repository —
The Network Associates
FTP
repository is the default download site.
NOTE
If you are currently using the default VirusScan 4.5.1
FTP repository, or plan to use the
FTP
repository to perform updates after installing VirusScan Enterprise, you are automatically configured to do so after the installation process completes. No changes are required to the VirusScan
Enterprise installation (.
MSI
) file.
The default Network Associates
FTP
repository is located at: ftp://ftp.nai.com/CommonUpdater
Preserve settings
— If you are installing VirusScan Enterprise over a previous version of VirusScan or NetShield, and wish to preserve settings, select the
preserve settings
option during installation.
NOTE
If you are currently using the default VirusScan 4.5.1
FTP repository, VirusScan Enterprise automatically updates to the new default
FTP
repository, even if you choose to
preserve settings
.
HTTP Network Associates repository or internal UNC share
— Use McAfee
Installation Designer to configure these repositories before or after installing
VirusScan Enterprise.
See the McAfee Installation Designer Product Guide for details.
The default Network Associates
HTTP
repository is located at: http://update.nai.com/Products/CommonUpdater
Implementation Guide 25
Updating Scenarios
HTTP authentication
— Site 1 uses authentication and the other two sites do not. There are several ways to plan for this configuration:
Use ePolicy Orchestrator
™
or McAfee AutoUpdate Architect to manage this site configuration.
See the ePolicy Orchestrator Product Guide or the McAfee AutoUpdate
Architect Product Guide for details.
Use McAfee Installation Designer to create two .
CAB
files that contain the required site-specific update information. Copy these .
CAB
files to the MID folder located in the VirusScan Enterprise installation directory. VirusScan
Enterprise retrieves the site settings from the .
CAB
files and uses it for updating.
You can also use McAfee Installation Designer to create workstation-specific or server-specific .
CAB
files.
See the McAfee Installation Designer Product Guide for details.
Use McAfee Installation Designer to create two installation filess; one for each site that contains the required site-specific updating information. As each package deploys, it configures the local computer to use the site-specific update information, such as proxy user name and password, or proxy
IP
address.
See the McAfee Installation Designer Product Guide for details.
26 VirusScan
®
Enterprise software version 7.1.0
Multiple sites updating internally with a staged deployment
Multiple sites updating internally with a staged deployment
Use this scenario to test deployment before replicating the update files to the internal servers:
Figure 3-3. Multiple sites updating internally with a staged deployment
In this scenario, a staged deployment site has been created for a limited number of users to test the
DAT
files, before deploying them to the remainder of the company. A main repository is configured to retrieve updates from the Network Associates
FTP
or
HTTP
repository.
Implementation Guide 27
Updating Scenarios
You can create the main repository using either of these options:
Use the VirusScan Enterprise mirror task to replicate the Network Associates repository to the main repository. See the VirusScan Enterprise Product Guide for details about using the mirror task.
Use the McAfee AutoUpdate Architect pull task. See the McAfee AutoUpdate
Architect Product Guide for details about using the pull task.
Once the update structure is in place, test clients and servers that are configured to update from this main repository will do so when their next scheduled update runs.
NOTE
McAfee AutoUpdate Architect can check Service Packs,
HotFixes,
EXTRA
.
DAT s, Super
DAT
packages, and .
CAB
file packages into this update structure. Once these packages are checked in, the VirusScan Enterprise update task pulls these packages down and installs them during scheduled updates.
After the testing cycle is complete, the structure can be replicated to the internal servers for the remainder of the company. You can use the command line or common scripting utilities to manage replication. McAfee AutoUpdate Architect can manage and automate these replication tasks from the Network Associate repository to the main repository, as well as from the main repository to the internal update servers. The internal servers can be
FTP
,
HTTP
, or
UNC
shares.
28 VirusScan
®
Enterprise software version 7.1.0
Managing the AutoUpdate
Repository List
4
The AutoUpdate repository list contains the repositories used to perform update tasks. You can have as many repositories as you need to meet your updating requirements. You can use the AutoUpdate repository list to download the following:
DAT
file updates
Scanning engine upgrades
EXTRA
.
DAT
file
Super
DAT
package
HotFix
Service Pack
.
CAB
file
You can use VirusScan Enterprise, McAfee Installation Designer, the McAfee
AutoUpdate Architect utility, or a combination of these products to manage the
AutoUpdate repository list.
The method you select to manage the AutoUpdate repository list depends on your updating requirements.
The following topics are covered in this section:
.
Using VirusScan Enterprise to replicate the update structure
Using McAfee Installation Designer
Using McAfee AutoUpdate Architect
Implementation Guide 29
Managing the AutoUpdate Repository List
Sample updating procedure
This procedure lists the basic steps required to perform an update:
1
Configure the VirusScan Enterprise installation (.
MSI
) file to download from a repository.
a
If you are updating from the default Network Associates
FTP
repository, no changes need to be made to the installation file.
b
If you are updating from either of the following repositories, you can configure the installation file:
Network Associates
HTTP
repository as the main repository.
Internal
FTP
,
HTTP
, or
UNC
/mapped drive as the repository.
2
3
Use McAfee Installation Designer to pre-configure the installation file, or configure VirusScan Enterprise after installation.
See the McAfee Installation Designer Product Guide for details.
For clients updating to an internal update server:
a
Mirror the update structure from either the Network Associates
FTP repository or the
HTTP
repository, to the internal update location on your server. You can use the VirusScan Enterprise mirror task on a single server, to replicate these files from the repository to a location on that server.
See the VirusScan Enterprise Product Guide for more information about using mirror tasks.
b
NOTE
The files located on the Network Associates
FTP
repository and the
HTTP
repository support both VirusScan 4.5.x and
VirusScan Enterprise 7.1.0.
Copy the update structure to the other internal update servers. You may already have an existing method for copying the update files to other internal servers. You can use any existing methods, as long as the entire directory structure is replicated.
You can use McAfee AutoUpdate Architect to manage and automate this process. See the McAfee AutoUpdate Architect Product Guide for details.
Deploy the VirusScan Enterprise 7.1.0 installation (.
MSI
) file to your environment. The installation file should be configured to update to the prepared internal download site, or the external download site.
30 VirusScan
®
Enterprise software version 7.1.0
Using VirusScan Enterprise to replicate the update structure
Using VirusScan Enterprise to replicate the update structure
Create a mirror task with VirusScan Enterprise, then use it to replicate update files to a mirror location. See the VirusScan Enterprise 7.1.0 Product Guide for details about creating and configuring mirror tasks.
1
2
Start the
VirusScan Console
.
Create a new mirror task or open an existing mirror task.
The
VirusScan AutoUpdate Properties
dialog box appears.
Figure 4-1. VirusScan AutoUpdate Properties — Mirror task
3
4
Click
Mirror Location
.
a b
In the
Local Destination Path
text box, enter the mirror location, or click
Browse
to navigate to the desired location.
Click
OK
to return to the
VirusScan AutoUpdate Properties
dialog box.
c d
Click
Mirror Now
to start the mirror task.
Click
OK
to close the
VirusScan AutoUpdate Properties
dialog box and return to the
VirusScan Console
.
Monitor the task progress on the
VirusScan Console
.
Implementation Guide 31
Managing the AutoUpdate Repository List
Each mirror site replicates the Network Associates repository that contains the update files. Computers on your network can then download the files from the mirror site. This approach is practical because it allows you to update any computer on your network, whether or not it has Internet access; and efficient because your computers communicate with a server that is probably closer than a Network
Associates Internet site, therefore economizing access and download time. The most common use of this task is to mirror the contents of the Network Associates download site to a local server.
The VirusScan Enterprise software relies on a directory structure to update itself.
This directory structure also supports VirusScan 4.5.x and NetShield 4.5 for updating, as long as the entire directory structure is replicated in the same locations that VirusScan 4.5.1 used for updating.
The following shows the directory structure in the repository after using a mirror task to replicate the Network Associates repository.
Figure 4-2. Update directory structure in the repository
32 VirusScan
®
Enterprise software version 7.1.0
Using McAfee Installation Designer
The mirror task used for this example downloads from the default
FTP
site, so only the
CATALOG
.
Z
file, the
DAT
file updates, and the engine file were downloaded.
The files listed in the flat structure of the diagram are used with previous versions of VirusScan and NetShield.
The
CATALOG
.
Z
file and the files contained in the Current folder are used with
VirusScan Enterprise 7.1.0.
NOTE
To download a HotFix, a Service Pack, an
EXTRA
.
DAT
, a
Super
DAT
package, or a .
CAB
file, use the McAfee AutoUpdate
Architect utility to check these packages into the AutoUpdate repository list. See
Using McAfee AutoUpdate Architect
on page 37 for more information.
Using McAfee Installation Designer
McAfee Installation Designer allows an administrator to pre-configure a
VirusScan Enterprise software package for installation on another computer or group of computers.
You can use the utility to:
Pre-set installation options for VirusScan Enterprise.
Select additional files to copy to the system during installation.
Set registry keys in addition to those set by the installation.
Install the most current
DAT
and engine files, rather than those that shipped with the product.
Implementation Guide 33
Managing the AutoUpdate Repository List
Use McAfee Installation Designer to create a .
CAB
file that modifies an existing
VirusScan Enterprise installation. See the McAfee Installation Designer Product Guide for details.
1
Start the McAfee Installation Designer utility.
Figure 4-3. McAfee Installation Designer — Welcome
2
Select
Modify an existing installation by generating a new settings file
, then click
Next
.
34 VirusScan
®
Enterprise software version 7.1.0
Using McAfee Installation Designer
The
Source for Configuration
dialog box appears.
Figure 4-4. McAfee Installation Designer — Source for Configuration
3
Select
Existing VirusScan Enterprise settings on local system
, then click
Next
.
Implementation Guide 35
Managing the AutoUpdate Repository List
The
Destination
dialog box appears.
Figure 4-5. McAfee Installation Designer — Destination
4
Specify the options for the configuration folder:
a
In the
New configuration folder
text box, specify the destination for the configuration folder.
b
Select one of these options:
Create one configuration package for both servers and workstations.
Create server configuration package.
Create workstation configuration package.
5
6
To continue, choose from these options:
Click
Next
to continue through the list of options shown in the left panel.
Click
Finish
at any time to review the final configuration.
Click
Save
then click
Exit
.
NOTE
After the installation completes, place the .
CAB
file in the MID folder located in the VirusScan Enterprise installation directory.
36 VirusScan
®
Enterprise software version 7.1.0
Using McAfee AutoUpdate Architect
Using McAfee AutoUpdate Architect
McAfee AutoUpdate Architect allows you to manage updates to your entire company’s anti-virus software. The program creates and maintains an internal software repository where you define exactly which Network Associates updates to deploy to the computers on your network.
Using McAfee AutoUpdate Architect, you can configure an
FTP
server,
HTTP server, or a
UNC
shared directory on your internal network to process all
AutoUpdate requests from your network client computers. Those client computers then retrieve their updates from an internal location, rather than connecting directly to the McAfee web site. This reduces bandwidth consumption and allows faster update transfers.
McAfee AutoUpdate Architect task scheduling features allow you to retrieve the latest anti-virus software updates automatically from the Network Associates repository, and store them on your internal update server. Your internal update server can then deliver those updates to distributed repositories throughout your organization.
You can use VirusScan Enterprise along with McAfee AutoUpdate Architect to download the most current update files.
Use the VirusScan Enterprise AutoUpdate task to download the most current
DAT
file updates and engine upgrades from the Network Associates repository.
Use the McAfee AutoUpdate Architect utility to download a HotFix, a Service
Pack, an
EXTRA
.
DAT
, a Super
DAT
package, or a .
CAB
file, then check these packages into the AutoUpdate repository list.
Implementation Guide 37
Managing the AutoUpdate Repository List
Use McAfee AutoUpdate Architect to check package files into the AutoUpdate repository list. See the McAfee AutoUpdate Architect Product Guide for details.
1
Start the McAfee AutoUpdate Architect utility.
Figure 4-6. McAfee AutoUpdate Architect — Console
2
3
Configure the
Master Repository
, if you have not already done so. See the
McAfee AutoUpdate Architect Product Guide for details.
In the console tree, select
McAfee AutoUpdate Architect
, then under
AutoUpdate
Tasks
, click
Check in package
.
38 VirusScan
®
Enterprise software version 7.1.0
Using McAfee AutoUpdate Architect
The
Check in package
wizard dialog box appears.
Figure 4-7. McAfee AutoUpdate Architect — Check in package wizard
4
Click
Next
to continue.
5
Enter the appropriate information as required, in each of these dialog boxes:
Select package type
Locate catalog file
Package information
Finish
McAfee AutoUpdate Architect verifies the authenticity and integrity of updates, through the use of digital package signatures, to protect against unauthorized modification, tampering, or corruption.
See the McAfee AutoUpdate Architect Product Guide for detailed information on configuring and using the utility.
Implementation Guide 39
Managing the AutoUpdate Repository List
40 VirusScan
®
Enterprise software version 7.1.0
Troubleshooting
5
This section contains troubleshooting information for updating with VirusScan
Enterprise.
The following topics are covered in this section:
Using the AutoUpdate log file to troubleshoot updating issues
AutoUpdate may require Internet Explorer 4.0 or later
DAT file updates using VirusScan 4.5.1 and VirusScan Enterprise 7.1.0
Implementation Guide 41
Troubleshooting
Using the AutoUpdate log file to troubleshoot updating issues
To view the AutoUpdate log file, right-click the AutoUpdate task in the
VirusScan
Console
, and select
View Log
. You can see basic updating information, general errors, and other configuration errors. Network Associates also provides an alternate log file that provides more advanced logging and
HTTP
responses, from the
HTTP
proxy or servers.
The alternate log file name is
AGENT
_<
COMPUTER NAME
>.
LOG
.
The
AGENT
_<
COMPUTER NAME
>.
LOG
file can be found at the following locations, depending on your operating system:
For Windows NT 4.0
— In the VirusScan Enterprise installation directory. By default, Setup installs the VirusScan Enterprise program files to this path:
<drive>:\Program Files\Network Associates\VirusScan
For Windows 2000 and Windows XP
— In the All Users Profile at the following location:
<drive>:\Documents and Settings\All Users\Application
Data\Network Associates\Common Framework\DB
NOTE
The Application Data folder is hidden by default. If you do not have rights to Show hidden files and folders, you cannot view or search for the
AGENT
_<
COMPUTER NAME
>.
LOG
.
AutoUpdate may require Internet Explorer 4.0 or later
Server installations that do not have Microsoft Internet Explorer version 4.0 or later must use McAfee Installation Designer to install the
WININET
.
DLL
and the
SHLWAPI
.
DLL
. Refer to Primus Article Number 30063.
42 VirusScan
®
Enterprise software version 7.1.0
Download catalog.z.
To test whether you can download the
CATALOG
.
Z
file, try using the following methods:
If you are using the Network Associates HTTP repository for updates:
In the web browser, go to the following
URL
and try to download the
CATALOG
.
Z
file: http://update.nai.com/Products/CommonUpdater/catalog.z
If you are using the Network Associates FTP repository for updates:
In the web browser, go to the following
URL
and try to download the
CATALOG
.
Z
file: ftp://ftp.nai.com/CommonUpdater/catalog.z
NOTE
If you are asked to log on, use the following credentials:
User name
= anonymous
Password
= your e-mail address
If you are not able to download the
CATALOG
.
Z
file, but you can see it (in other words, your browser does not allow you to download it), that means you have a proxy issue and need to talk to your network administrator.
If you are able to download the
CATALOG
.
Z
file, VirusScan Enterprise should be able to download it as well. Contact technical support for assistance in troubleshooting your installation of VirusScan Enterprise.
NOTE
If you are using a mirror site for updates, make sure that your mirror site is pointing to the correct repository for updates. If you are unsure, try changing your settings to use the default
Network Associates repository.
DAT file updates using VirusScan 4.5.1 and VirusScan Enterprise 7.1.0
If you have computers that will continue using VirusScan 4.5.x and others using
VirusScan Enterprise 7.1.0, all of these computers can download the most current
DAT
files from the same Network Associates repository.
The default Network Associates
HTTP
repository is located at: http://update.nai.com/Products/CommonUpdater
The default Network Associates
FTP
repository is located at: ftp://ftp.nai.com/CommonUpdater
Implementation Guide 43
Troubleshooting
44 VirusScan
®
Enterprise software version 7.1.0
دانلود
تبلیغات