McAfee VirusScan Enterprise 8.
COPYRIGHT Copyright © 2010 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.
Contents Introducing VirusScan Enterprise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Using the console to reinstall or repair program files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Using the command line to reinstall or repair program files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Removing program files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Using the Setup utility to remove program files. . . . . . . . . . . . . . . . . .
Introducing VirusScan Enterprise ® ® McAfee VirusScan Enterprise software protects your system from viruses, worms, Trojan horses, and potentially unwanted code and programs. This guide provides system requirements for VirusScan Enterprise software, and information about installing it as a standalone and as a managed product, as well as modifying, repairing, removing, and reinstalling the software.
Introducing VirusScan Enterprise Finding product documentation Finding product documentation McAfee provides the information you need during each phase of product implementation, from installing to using and troubleshooting. After a product is released, information about the product is entered into the McAfee online KnowledgeBase. 1 Go to the McAfee Technical Support ServicePortal at http://mysupport.mcafee.com. 2 Under Self Service, access the type of information you need: To access... Do this...
Pre-Installation Tasks Before installing the VirusScan Enterprise software, you need to make sure your system is ready. This section presents a high-level process of tasks to complete before installing the software, and information that can help you prepare for the installation.
Pre-Installation Tasks System requirements System requirements Verify that your server or workstation meets these system requirements before you start the installation process. NOTE: These are minimum requirements and are not optimal for performance. They apply only to VirusScan Enterprise. You must also consider system requirements for any other products you are installing, such as ePolicy Orchestrator.
Pre-Installation Tasks System requirements Operating system SP 32-bit 64-bit Processor Microsoft Windows 7 Home Premium, Professional, and Ultimate X 1 GHz or greater RAM Minimum hard disk space 2 GB 500 MB * You must install McAfee Agent version 4.0 before installing this version of VirusScan Enterprise on Microsoft Windows 2000 Professional SP4 systems. ** At least 250 MB of free memory space must be available to update DAT and engine files.
Pre-Installation Tasks Product upgrade and preserving settings • Microsoft Outlook — Microsoft Outlook client versions Microsoft Outlook 2003, Microsoft Outlook 2007, and Microsoft Outlook 2010 (both 32-bit and 64-bit). • Lotus Notes — Lotus Notes version 7.0x, and 8.0x through 8.5.1. • Browsers — The following browsers are supported with VirusScan Enterprise ScriptScan: NOTE: For ePolicy Orchestrator browsers supported refer to the ePolicy Orchestrator documentation.
Pre-Installation Tasks Options for preconfiguring, deploying, updating, and managing VirusScan Enterprise 4 For port blocking rules, if the local rule differs from the default rule only in its inclusions, the rule is placed in a separate list of rules to be merged with the equivalent VirusScan Enterprise 8.8 rules. 5 The whitelist for each of the port rules from Step 4 is merged with the whitelist of the equivalent VirusScan Enterprise 8.7i rule.
Pre-Installation Tasks Product license and performing an upgrade Product license and performing an upgrade If you are installing a licensed version over an evaluation version of VirusScan Enterprise, you must upgrade the license. The license is not automatically upgraded from an evaluation version. CAUTION: Perform the license upgrade before the evaluation period expires.
Installing VirusScan Enterprise You can install the standalone and ePolicy Orchestrator managed versions of the VirusScan Enterprise software using the Setup utility or the command line.
Installing VirusScan Enterprise Using the Setup utility to install the software By default, Setup installs the VirusScan Enterprise program files to :\Program Files\McAfee\VirusScan Enterprise\. • Typical — (Recommended) Installs the software with all features. • Custom — Installs the software with all or selected features and allows you to customize some settings.
Installing VirusScan Enterprise Using the command line to install the software repository list. See the Updating detection definitions section of the VirusScan Enterprise Product Guide for more information. • Enable On-Access Scanner at the end of installation — (Recommended) Automatically start the on-access scanner upon completion of the installation process. 10 In the Security Configuration dialog box, specify password security and which system tray options users can access.
Installing VirusScan Enterprise Using the command line to install the software Task • Open the Command Prompt or the Run dialog box and type this command: SetupVSE.exe PROPERTY=VALUE[,VALUE] [/option] This syntax does not require any specific order in its elements, except that you can’t separate a property and its value. The syntax consists of: • File name — The name of the executable file, SetupVSE.exe.
Installing VirusScan Enterprise Using the command line to install the software Scenario Definition Login Script Add a Setup command to your login script to install VirusScan Enterprise software when each of your destination computers starts. Include all of the options and properties for governing how Setup runs. For example, you can add a property to look for the VirusScan Enterprise default program location.
Installing VirusScan Enterprise Using the command line to install the software Installation progress options To record installation progress in a log file, add this option and parameter to the Setup command line: /l*v "c:\temp\log.txt" Here, c:\temp\log.txt is any location and any file name for the log file. This option logs all installer activity including all files copied, all registry keys added, and all .ini file changes.
Installing VirusScan Enterprise Using the command line to install the software Properties Definition LOCKDOWNSHORTCUTS False = Not valid. True = Do not display any shortcuts under the Start menu. The default is an empty string. To allow the shortcuts to be installed, set the property to "", an empty string. For example: LOCKDOWNSHORTCUTS="" PRESERVESETTINGS False = Not valid. True = Preserve settings (default). Preserves settings when upgrading from an earlier version of VirusScan Enterprise.
Installing VirusScan Enterprise Placing the product under ePolicy Orchestrator management To do this... Run this command... Install more than one feature Use a comma to separate more than one feature. For example, to install the on-access scanner and Script Scan, run SetupVSE.exe ADDLOCAL=OnAccessScanner,ScriptScan /q Install all features except one SetupVSE.exe ADDLOCAL=ALL REMOVE=ScriptScan /q Silently remove all features SetupVSE.
Installing VirusScan Enterprise Migrating the ePolicy Orchestrator policies • epo45_help_vse_880.zip — Contains the Help files used to describe the VirusScan Enterprise 8.8 features and user interface for ePolicy Orchestrator 4.5 and 4.6. NOTE: This file does not provide ePolicy Orchestrator 4.0 Help files. Before you begin You must have the appropriate permissions to perform this task. Task For option definitions, click ? in the interface.
Installing VirusScan Enterprise Migrating the ePolicy Orchestrator policies Task 1 Browse to where you saved the VirusScan Enterprise 8.8 installation files (described in Preparation for installing the software) and double-click the ePOPolicyMigration.exe file. NOTE: When upgrading VirusScan Enterprise 8.5i policies and tasks, use the command-line option with the force switch as follows: ePOPolicyMigration.
Post-Installation Tasks After installing the VirusScan Enterprise program files, it is important to test your installation to make sure your system can detect malware and potentially unwanted programs (PUPs). You can also check the location on your system where the program files were installed.
Post-Installation Tasks Location of installed files Testing for potentially unwanted programs detection The EICAR-PUO test file is used to confirm VirusScan Enterprise is installed correctly and can properly scan and find potentially unwanted programs. NOTE: This file is not a virus — it cannot spread, infect other files, or harm your system. Delete the file when you have finished testing your installation to avoid alarming other users.
Post-Installation Tasks Location of installed files condl.dll mcupdate.exe readme.html consl.dll MERTool.url restartvse.exe coptcpl.dll mfeann.exe scan32.exe csscan.exe mfeapconfig.dll ScnCfg32.Exe Emabout.dll midutil.dll shcfg32.exe EmCfgCpl.dll mytilus3.dll shext.dll EmHelp.dll mytilus3_server.dll shstat.dll ftcfg.dll mytilus3_worker.dll shstat.exe ftl.dll NaEvent.Dll shutil.dll graphics.dll naiann.dll vscan.bof license.bin nailite.dll VsEvntUI.DLL lockdown.dll NCDaemon.
Post-Installation Tasks Location of installed files avvclean.dat avvnames.dat avvscan.dat config.dat license.dat mcscan32.dll messages.dat signlic.txt 32-bit operating system files The system files for 32-bit operating systems are installed in the System32 folder. The default location for system files is: :\Windows\System32 mfeOtlk.dll mfeOtlkAddin.dll The default location for 32-bit operating system drivers is: :\Windows\System32\drivers Mfeapfk.sys Mfebopk.sys Mfehidk.
Post-Installation Tasks Location of installed files SystemCore 64-bit operating system folder For 64-bit operating systems the default location of the SystemCore files is: :\Program Files (x86)\Common Files\McAfee\SystemCore lockdown.dll mytilus3_worker.dll ScriptSn.yyyymmddhhmmss.dll mcshield.dll OtlkScan.dll scriptsn.dll MfeOtlk.dll OtlkUI.yyyymmddhhmmss.dll Strings.bin MfeOtlkAddin.dll OtlkUI.dll mytilus3.dll scriptff.
Maintenance Tasks Use the Program Maintenance feature to modify, repair, remove, or reinstall the VirusScan Enterprise program files. Contents Modifying installed features Reinstalling or repairing program files Removing program files Modifying installed features As the requirements for your installation change, use the Program Maintenance feature to change which VirusScan Enterprise features are installed.
Maintenance Tasks Reinstalling or repairing program files Using the command line to modify installed features You can use the command line to change which features are installed in VirusScan Enterprise 8.8. Task 1 To access the Windows command-line component, refer to Using the command line to install the software. 2 Install or remove features individually using a comma-separated list, or you can specify the all property. • Add a feature — SetupVSE.
Maintenance Tasks Reinstalling or repairing program files • Detect and repair missing or corrupt files — Finds missing or corrupt program files and repairs them. NOTE: This feature does not support repairing update components. If an AutoUpdate file is removed or corrupted, you must remove the AutoUpdate component, then reinstall it. • Rewrite registry keys — Rewrites registry keys as necessary during the repair process (available only for Detect and repair missing or corrupt files).
Maintenance Tasks Removing program files • Command-line options — Use any combination of these options: • p — Reinstall only if file is missing. • o — Reinstall if file is missing or if an older version is installed. • e — Reinstall if file is missing or an equal or older version is installed. • d — Reinstall if file is missing or a different version is installed. • c — Reinstall if file is missing, or if the stored checksum does not match the calculated value.
Maintenance Tasks Removing program files example, the aseinst.log is used for debugging and is left in the %TEMP%\MCAFEELOGS folder. 4 (Recommended) Restart your computer before reinstalling the software. Using the command line to remove program files To remove program files, use the command line. Task 1 Type this syntax at the command prompt: :\SetupVSE.exe /x where : represents the path of the location of the extracted program files.
Index features (continued) selecting and installing 13, 17 A Access Protection feature default levels of protection 13 installing from the command line 17 installing with Setup 13 Add/Remove Programs, removing program files 32 administrator rights silent installation 16 system requirements 7 Alert Manager, installing 13 audience for this guide 5 AutoUpdate feature installing from the command line 17 installing with Setup 13 B Buffer Overflow Protection installing from the command line 17 installing with S
Index Program Maintenance feature modifying installed features 28 reinstalling or repairing 29 R release notes, viewing 13 removal of program files 31 repository list, importing 13 requirements for installation 8 restart after installation 13 after removing program files 31, 32 command-line options 17 Right-click Scan feature installing from the command line 17 installing with Setup 13 S scanners, selecting features 13, 17 Script Scan feature installing from the command line 17 installing with Setup 13 s
