McAfee VIRUSSCAN 8.7I User Manual
VirusScan® Enterprise
Draft for Beta 1
version 8.7i
Installation Guide
revision 1.0
McAfee®
Proven Security
Industry-leading intrusion prevention solutions
VirusScan® Enterprise
version 8.7i
Installation Guide
revision 1.0
®™
McAfee®
Proven Security
Industry-leading intrusion prevention solutions
COPYRIGHT
Copyright © 2008 McAfee, 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 McAfee, Inc., or its suppliers or affiliate companies.
TRADEMARK ATTRIBUTIONS
ACTIVE FIREWALL, ACTIVE SECURITY, ACTIVESECURITY (AND IN KATAKANA), ACTIVESHIELD, CLEAN-UP, DESIGN (STYLIZED E), DESIGN
(STYLIZED N), ENTERCEPT, EPOLICY ORCHESTRATOR, FIRST AID, FOUNDSTONE, GROUPSHIELD, GROUPSHIELD (AND IN KATAKANA),
INTRUSHIELD, INTRUSION PREVENTION THROUGH INNOVATION, MCAFEE, MCAFEE (AND IN KATAKANA), MCAFEE AND DESIGN,
MCAFEE.COM, MCAFEE VIRUSSCAN, NET TOOLS, NET TOOLS (AND IN KATAKANA), NETSCAN, NETSHIELD, NUTS & BOLTS, OIL CHANGE,
PRIMESUPPORT, SPAMKILLER, THREATSCAN, TOTAL VIRUS DEFENSE, VIREX, VIRUS FORUM, VIRUSCAN, VIRUSSCAN, VIRUSSCAN (AND IN
KATAKANA), WEBSCAN, WEBSHIELD, WEBSHIELD (AND IN KATAKANA) are registered trademarks or trademarks of McAfee, Inc. and/or its
affiliates in the US and/or other countries. The color red in connection with security is distinctive of McAfee brand products. All other registered
and unregistered trademarks herein 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 MCAFEE 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 and software written by Tim J. Hudson. • 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 McAfee 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. • Software written by Douglas W. Sauder. • Software developed by the
Apache Software Foundation (http://www.apache.org/). A copy of the license agreement for this software can be found at
www.apache.org/licenses/LICENSE-2.0.txt. • International Components for Unicode (“ICU”) Copyright ©1995-2002 International Business
Machines Corporation and others. • Software developed by CrystalClear Software, Inc., Copyright ©2000 CrystalClear Software, Inc. • FEAD
Optimizer
Outside In
© 1998, 1999, 2000. • Software copyrighted by Expat maintainers. • Software copyrighted by The Regents of the University of California, © 1996,
1989, 1998-2000. • Software copyrighted by Gunnar Ritter. • Software copyrighted by Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
California 95054, U.S.A., © 2003. • Software copyrighted by Gisle Aas. © 1995-2003. • Software copyrighted by Michael A. Chase, © 1999-2000.
• Software copyrighted by Neil Winton, ©1995-1996. • Software copyrighted by RSA Data Security, Inc., © 1990-1992. • Software copyrighted by
Sean M. Burke, © 1999, 2000. • Software copyrighted by Martijn Koster, © 1995. • Software copyrighted by Brad Appleton, © 1996-1999.
• Software copyrighted by Michael G. Schwern, ©2001. • Software copyrighted by Graham Barr, © 1998. • Software copyrighted by Larry Wal l
and Clark Cooper, © 1998-2000. • Software copyrighted by Frodo Looijaard, © 1997. • Software copyrighted by the Python Software Foundation,
Copyright © 2001, 2002, 2003. A copy of the license agreement for this software can be found at www.python.org. • Software copyrighted by
Beman Dawes, © 1994-1999, 2002. • Software written by Andrew Lumsdaine, Lie-Quan Lee, Jeremy G. Siek © 1997-2000 University of Notre
Dame. • Software copyrighted by Simone Bordet & Marco Cravero, © 2002. • Software copyrighted by Stephen Purcell, © 2001. • Software
developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/). • Software copyrighted by International Business
Machines Corporation and others, © 1995-2003. • Software developed by the University of California, Berkeley and its contributors. • Software
developed by Ralf S. Engelschall <rse@engelschall.com> for use in the mod_ssl project (http:// www.modssl.org/). • Software copyrighted by
Kevlin Henney, © 2000-2002. • Software copyrighted by Peter Dimov and Multi Media Ltd. © 2001, 2002. • Software copyrighted by David
Abrahams, © 2001, 2002. See http://www.boost.org/libs/bind/bind.html for documentation. • Software copyrighted by Steve Cleary, Beman
Dawes, Howard Hinnant & John Maddock, © 2000. • Software copyrighted by Boost.org, © 1999-2002. • Software copyrighted by Nicolai M.
Josuttis, © 1999. • Software copyrighted by Jeremy Siek, © 1999-2001. • Software copyrighted by Daryle Walker, © 2001. • Software copyrighted
by Chuck Allison and Jeremy Siek, © 2001, 2002. • Software copyrighted by Samuel Krempp, © 2001. See http://www.boost.org for updates,
documentation, and revision history. • Software copyrighted by Doug Gregor (gregod@cs.rpi.edu), © 2001, 2002. • Software copyrighted by
Cadenza New Zealand Ltd., © 2000. • Software copyrighted by Jens Maurer, ©2000, 20 01. • Software copyrighted by Jaakko Järvi
(jaakko.jarvi@cs.utu.fi), ©1999, 2000. • Software copyrighted by Ronald Garcia, © 2002. • Software copyrighted by David Abrahams, Jeremy
Siek, and Daryle Walker, ©1999-2001. • Software copyrighted by Stephen Cleary (shammah@voyager.net), ©2000. • Software copyrighted by
Housemarque Oy <http://www.housemarque.com>, © 2001. • Software copyrighted by Paul Moore, © 1999. • Software copyrighted by Dr. John
Maddock, © 1998-2002. • Software copyrighted by Greg Colvin and Beman Dawes, © 1998, 1999. • Software copyrighted by Peter Dimov, © 2001,
2002. • Software copyrighted by Jeremy Siek and John R. Bandela, © 2001. • Software copyrighted by Joerg Walter and Mathias Koch,
© 2000-20 02. • Software copyrighted by Carnegie Mellon University © 1989, 1991, 1992. • Software copyrighted by Cambridge Broadband Ltd.,
© 2001-2003. • Software copyrighted by Sparta, Inc., © 2003-2004. • Software copyrighted by Cisco, Inc. and Information Network Center of
Beijing University of Posts and Telecommunications, © 2004. • Software copyrighted by Simon Josefsson, © 2003. • Software copyrighted by
Thomas Jacob, © 2003-2004. • Software copyrighted by Advanced Software Engineering Limited, © 2004. • Software copyrighted by Todd C.
Miller, © 1998. • Software copyrighted by The Regents of the University of California, © 1990, 1993, with code derived from software contributed
to Berkeley by Chris Torek.
®
technology, Copyright Netopsystems AG, Berlin, Germany. • Outside In® Viewer Technology ©1992-2001 Stellent Chicago, Inc. and/or
®
HTML Export, © 2001 Stellent Chicago, Inc. • Software copyrighted by Thai Open Source Software Center Ltd. and Clark Cooper,
®
PATENT INFORMATION
Protected by US Patents 6,006,035; 6,029,256; 6,035,423; 6,151,643; 6,230,288; 6,266,811; 6,269,456; 6,457,076; 6,496,875; 6,542,943; 6,594,686;
6,611,925; 6,622,150; 6,668,289; 6,697,950; 6,735,700; 6,748,534; 6,763,403; 6,763,466; 6,775,780; 6,851,058; 6,886,099; 6,898,712; 6,928,555;
6,931,540; 6,938,161; 6,944,775; 6,963,978; 6,968,461; 6,971,023; 6,973,577; 6,973,578.
Issued APRIL 2008/ VirusScan® Enterprise software version 8.7i - Beta 1
DBN-001-EN
Contents
1 Introducing VirusScan Enterprise 6
2 Pre-Installation Information 8
3 Installing VirusScan Enterprise 14
Using this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Getting product software and documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Reviewing release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Verifying installation rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Preserving settings during product upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Meeting system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Deploying, updating, and managing options . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Upgrading the product license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Using the Setup utility to install program files . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Using the command line to install program files . . . . . . . . . . . . . . . . . . . . . . . . . .18
Command-line syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Installation scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installation options and properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Command-line examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4 Modifying, Repairing & Removing VirusScan Enterprise 26
Modifying installed features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Using the Setup utility to modify installed features . . . . . . . . . . . . . . . . . . . . 27
Using the command line to modify installed features . . . . . . . . . . . . . . . . . . 28
Reinstalling or repairing program files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Using the Setup utility to reinstall or repair program files . . . . . . . . . . . . . . . 29
Using the command line to reinstall or repair program files . . . . . . . . . . . . . 30
Removing program files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Using the Setup utility to remove program files . . . . . . . . . . . . . . . . . . . . . . 31
Using the command line to remove program files . . . . . . . . . . . . . . . . . . . . 31
Using the Add/Remove Programs utility to remove program files . . . . . . . . . 31
5 Post-Installation Tasks 32
Testing your installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Locating installed files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Product files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
System files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
A Getting information 35
Product documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Contact information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Index 37
5
1
Introducing VirusScan Enterprise
McAfee
and mobile design to protect you from viruses, worms, Trojan horses, as well as
potentially unwanted code and programs.
This guide provides information about installing, modifying, and removing VirusScan
Enterprise software.
®
VirusScan Enterprise 8.7i offers easily scalable protection, fast performance,
Using this guide
Consider the following when using this guide:
Audience.
Conventions on page 7.
Audience
This information is intended primarily for two audiences:
Network administrators who are responsible for their company’s security program.
Users who are responsible for installing this product, updating detection definition
(
DAT) files on their computers, or configuring the software’s detection options.
6
VirusScan® Enterprise software version 8.7i Installation Guide Introducing VirusScan Enterprise
Using this guide
Conventions
This guide uses the following conventions:
1
Bold
Condensed
All words from the interface, including options, menus, buttons, and dialog
box names.
Example:
Type the
User name and Password of the appropriate account.
Courier The path of a folder or program; text that represents something the user
types exactly (for example, a command at the system prompt).
Examples:
The default location for the program is:
C:\Program Files\McAfee\EPO\3.5.0
Run this command on the client computer:
scan --help
Italic For emphasis or when introducing a new term; for names of product
documentation and topics (headings) within the material.
Example:
Refer to the VirusScan Enterprise Product Guide for more information.
Blue A web address (
URL) and/or a live link.
Example:
Visit the McAfee website at:
http://www.mcafee.com
<TERM> Angle brackets enclose a generic term.
Example:
In the console tree, right-click <
SERVER>.
Note: Supplemental information; for example, another method of
Note
executing the same command.
Tip: Suggestions for best practices and recommendations from McAfee for
Tip
threat prevention, performance and efficiency.
Caution: Important advice to protect your computer system, enterprise,
Caution
software installation, or data.
7
2
Pre-Installation Information
McAfee recommends that you review these topics before installing the VirusScan
Enterprise 8.7i software:
Getting product software and documentation.
Reviewing release notes.
Verifying installation rights.
Preserving settings during product upgrade on page 9.
Meeting system requirements on page 10.
Deploying, updating, and managing options on page 11.
Preconfiguring the installation package on page 11.
Installing and configuring the software for use with other products on page 11.
Upgrading the product license on page 13.
8
VirusScan® Enterprise software version 8.7i Installation Guide Pre-Installation Information
Getting product software and documentation
Getting product software and documentation
Get the VirusScan Enterprise software and documentation from one of these locations:
The product CD.
The McAfee download site at:
https://secure.nai.com/us/forms/downloads/upgrades/login.asp
Logon credentials are required to download products from this website.
Note
Reviewing release notes
Review the release notes, README.TXT, to identify last minute changes or known
issues.
2
Verifying installation rights
Verify that you have local administrator rights for the computer where you plan to install
VirusScan Enterprise.
Preserving settings during product upgrade
If you are installing VirusScan Enterprise on a computer with an earlier version of
VirusScan Enterprise, you can preserving settings from the earlier version.
Configuration settings for saved tasks.
User-specified extensions.
Exclusions settings.
Access protection rules are preserved using this logic:
1 The current VirusScan Enterprise rules are read from the registry.
2 Each of the local VirusScan Enterprise rules are compared against all of the
VirusScan Enterprise 8.0 default rules.
3 If no exact match is found when comparing local rules to the default rules, then the
rule is added to the list of rules to preserve.
4 For port blocking rules, if the local rule differs from the default rule only in its
inclusions, then the rule is placed in a separate list of rules to be merged with the
equivalent VirusScan Enterprise 8.7i rules.
5 The white list for each of the port rules, from Step 4, is merged with the white list of
the equivalent VirusScan Enterprise 8.7i rule, and a newly formed rule is written to
the registry for use by VirusScan Enterprise 8.7i.
6 The modified default rules, if any from Step 3, are converted to the new VirusScan
Enterprise 8.7i rule format and written to the registry. These preserved rules are
included in the user-defined rules.
9
VirusScan® Enterprise software version 8.7i Installation Guide Pre-Installation Information
Meeting system requirements
The decision to combine the white lists of the port blocking rules that have only had
their white list modified is based on the assumption that the user has specific software
Note
that they do not want blocked by the default port blocking rule.
Detection definition (DAT) file version, if the previous version is later than the
version in the installation package.
Scanning engine version, if the previous version is later than the version in the
installation package.
Log file names and locations are preserved.
Although the name and location are preserved, the log file format is changed from ANSI
to
Note
UTF8. When the format is changed, the log file is renamed to *.BAK.
The registry keys containing installation file locations and product versions are not
preserved.
If you do not want to preserve settings, you can deselect the option during installation
or remove the previous version of the software before installing the current version.
2
Meeting system requirements
These are preliminary requirements for the Beta 1 release. Verify that your server or
workstation meets these system requirements before you start the installation
process:
These requirements apply only to VirusScan Enterprise 8.7i. You must also consider
system requirements for any other products you are installing, such as ePolicy
Note
Orchestrator.
Processor — An Intel processor or compatible architecture. McAfee recommends
an Intel Pentium or Celeron processor running at a minimum of 166
Operating system — Any of these Microsoft
Server Workstation
Windows 2000 Server, with Service Pack 4 Windows 2000 Professional, with Service
Windows 2000 Advanced Server, with
Service Pack 4
Windows Server 2003, with Service Pack 1
or 2
Windows Server 2003 R2 Windows XP Tablet PC Edition, with
Windows Storage Server 2003 Windows XP Professional x64 Edition, with
Windows Server 2008 Windows Vista Home Basic
MHz.
®
Windows® platforms:
Pack 4
Windows XP Home Edition, with Service
Pack 1, 2, or 3
Windows XP Professional, with Service
Pack 1, 2 or 3.
Service Pack 3.
Service Pack 1, 2, or 3.
Windows Vista Home Premium
Windows Vista Business
Windows Vista Enterprise
Windows Vista Ultimate
10
VirusScan® Enterprise software version 8.7i Installation Guide Pre-Installation Information
Browser — Microsoft Internet Explorer, version 5.0 or later.
Windows Installer — Microsoft Windows Installer (MSI), version 3.1 or later.
Memory — <to be determined>MB RAM minimum. For information on optimal
operating system performance, review the Microsoft guidelines for minimum
Deploying, updating, and managing options
RAM
configuration.
Free disk space — <to be determined>mb for a complete installation of all the
VirusScan Enterprise 8.7i features and components, including a copy of the
installation
Other — A CD-ROM drive or an Internet connection from which you can install or
MSI file for repair ability.
download the product software.
Deploying, updating, and managing options
Decide whether you want to preconfigure the installation package and how you want
to perform updates and deploy the product. The installation procedure may vary if you
use supporting tools to deploy, preconfigure, update, or manage VirusScan Enterprise.
2
Preconfiguring the installation package
Use McAfee Installation Designer 8.5 to preconfigure or customize the installation
options for VirusScan Enterprise. When preconfiguring the installation package, we
recommend including:
Where and how you get updates.
When you check for updates (the default is daily at 17:00 local time to the
computer).
Which policy settings should be defined.
See the McAfee Installation Designer 8.5 Product Guide for more information.
Deploying the installation package
Use ePolicy Orchestrator version 3.5 or later to push the software to client computers.
We recommend that before you push the software to client computers, you use
McAfee Installation Designer to replace or update the default detection definition (
Tip
and engine files included in the installation package. This ensures that the client
computer has the most current protection at installation time. It also saves network
bandwidth by not having to retrieve the updated files after installation.
DAT)
Installing and configuring the software for use with other products
When installing VirusScan Enterprise software where third-party products are installed,
or when using it with supporting products, you may need to change the installation
procedure or perform additional configuration
11
VirusScan® Enterprise software version 8.7i Installation Guide Pre-Installation Information
Deploying, updating, and managing options
For example, if you are using the Setup utility to install the VirusScan Enterprise
software where Windows 2003 with Terminal Services is installed, the installation
stops and you are notified that you must install the program files using the Windows
Add/Remove Programs utility.
This installation method is not required if you are using ePolicy Orchestrator to deploy
VirusScan Enterprise.
Note
2
12
Loading...