McAfee MANAGEMENT EDITION 2.5 Administrator's Manual
McAfee MANAGEMENT EDITION 2.5 Administrator's Manual

McAfee MANAGEMENT EDITION 2.5 Administrator's Manual

Hide thumbs Also See for MANAGEMENT EDITION 2.5:
Table of Contents

Advertisement

Quick Links

Management Edition
Administrator's Guide
Version 2.5

Advertisement

Table of Contents
loading

Summary of Contents for McAfee MANAGEMENT EDITION 2.5

  • Page 1 Management Edition Administrator’s Guide Version 2.5...
  • Page 2 Solomon’s, Enterprise Secure Cast, First Aid, ForceField, Gauntlet, GMT, GroupShield, HelpDesk, Hunter, ISDN Tel/Scope, LM 1, LANGuru, Leading Help Desk Technology, Magic Solutions, MagicSpy, MagicTree, Magic University, MagicWin, MagicWord, McAfee, McAfee Associates, MoneyMagic, More Power To You, Multimedia Cloaking, NetCrypto, NetOctopus, NetRoom, NetScan, Net Shield, NetShield, NetStalker, Net Tools, Network Associates, Network General, Network Uptime!, NetXRay, Nuts &...
  • Page 3: Table Of Contents

    Table of Contents Chapter 1. Introducing the Management Edition Program ..11 Introduction ........... . .11 What is the Management Edition program? .
  • Page 4 Table of Contents Chapter 3. Creating Anti-virus Domains ......63 Preparing member machines ........63 Determining initial setup of machines .
  • Page 5 Table of Contents Checking virus scan status ........108 Acknowledging virus scan status .
  • Page 6 Table of Contents Chapter 6. Using the Alert Manager ......161 Enabling centralized alerting ........161 Enabling centralized alerting for the NetShield program .
  • Page 7 Table of Contents Chapter 8. Using Mirror and Linked Repositories ....213 Creating mirror repositories ........213 Creating Windows NT mirrors .
  • Page 8 Table of Contents Installing components ......... . .258 Diagnosing installation problems .
  • Page 9 Table of Contents Understanding Management Edition macros ......299 Directory macros ......... . .299 File transfer macros .
  • Page 10 Table of Contents Management Edition...
  • Page 11: Chapter 1. Introducing The Management Edition Program

    Introducing the Management Edition Program Introduction As a network administrator, your time is valuable. You’re responsible for maintaining your corporate network at its optimum. The Management Edition program solves your need for timely, efficient, and cost-effective enterprise-wide anti-virus software distribution. With it, you can seamlessly install, configure, and manage anti-virus software for remote networked machines within anti-virus domains that you create.
  • Page 12 Introducing the Management Edition Program You can install the Management Edition program on the local hard disk drive of the administrator’s workstation. You will need a Microsoft Windows NT Domain Administrator account. NOTE: You must install the Management Console and the Management Server only on a Windows NT system.
  • Page 13: What Comes With The Management Edition Program

    Introducing the Management Edition Program What comes with the Management Edition program? The Management Edition program consists of several component sets that combine one or more related programs, each of which play a part in defending your computer against viruses and other malicious software. The component sets are: •...
  • Page 14 Introducing the Management Edition Program • Documentation. The Management Edition program documentation includes: – A printed Getting Started Guide, which introduces the product, provides installation instructions, outlines how to respond if you suspect your computer has a virus, and provides a brief product overview.
  • Page 15 Introducing the Management Edition Program Once you’ve installed the Management Edition components, you must install the anti-virus components that you want to manage: • Anti-virus Components. This set consists of the on-access (VShield*) and on-demand scanners used by NetShield or VirusScan. These components include virus definition (.DAT) files, default configuration files, validation files, and other files.
  • Page 16: Management Edition Program Features

    Introducing the Management Edition Program • Command-line Scanner. The VirusScan set consists of SCANPM.EXE, a powerful scanning agent for 32-bit environments, and BOOTSCAN.EXE, a smaller, specialized scanner. The NetShield command-line scanner is SCAN32.EXE. These programs allow you to initiate targeted scan operations from the MS-DOS prompt window or from protected MS-DOS mode.
  • Page 17: Seamlessly Interactive Management Tools

    Introducing the Management Edition Program • This release includes the ability to configure custom tools—such as the additional console required to configure remote NetShield for NetWare servers—that can be launched from the Tools menu in the Management Console. • You can now use the Repository’s Products page to update product files such as SETUP.EXE or SETUP.ISS in addition to script (MCSCRIPT.INI) and extension .DLL files.
  • Page 18: Real-Time Virus Detection And Notification

    Introducing the Management Edition Program Real-time virus detection and notification • On-access (inbound and outbound) anti-virus scanning provides real-time identification of both known and unknown viruses upon file access, create, copy, rename, and run; disk access; system startup; and system shutdown. •...
  • Page 19: How To Contact Network Associates

    Internet support@nai.com CompuServe GO NAI America Online keyword MCAFEE If the automated services do not have the answers you need, contact Network Associates at one of the following numbers Monday through Friday between 6:00 . and 6:00 . Pacific time.
  • Page 20: Network Associates Training

    Introducing the Management Edition Program For retail-licensed customers: Phone (972) 855-7044 (408) 970-9727 To provide the answers you need quickly and efficiently, the Network Associates technical support staff needs some information about your computer and your software. Please have this information ready before you call: •...
  • Page 21: Reporting New Items For Anti-Virus Data File Updates

    Introducing the Management Edition Program Reporting new items for anti-virus data file updates Network Associates anti-virus software offers you the best available detection and removal capabilities, including advanced heuristic scanning that can detect new and unnamed viruses as they emerge. Occasionally, however, an entirely new type of virus that is not a variation on an older type can appear on your system and escape detection.
  • Page 22: International Contact Information

    Introducing the Management Edition Program International contact information To contact Network Associates outside the United States, use the addresses, phone numbers and fax numbers below. Network Associates Network Associates Australia Austria Level 1, 500 Pacific Highway Pulvermuehlstrasse 17 St. Leonards, NSW Linz, Austria Sydney, Australia 2065 Postal Code A-4040...
  • Page 23 Introducing the Management Edition Program Network Associates Network Associates France S.A. Deutschland GmbH 50 Rue de Londres Ohmstraße 1 75008 Paris D-85716 Unterschleißheim France Deutschland Phone: 33 1 44 908 737 Phone: 49 (0)89/3707-0 Fax: 33 1 45 227 554 Fax: 49 (0)89/3707-1199 Network Associates Hong Kong...
  • Page 24 Introducing the Management Edition Program Network Associates Net Tools Network Associates Portugal South Africa Av. da Liberdade, 114 Bardev House, St. Andrews 1269-046 Lisboa Meadowbrook Lane Portugal Epson Downs, P.O. Box 7062 Phone: 351 1 340 4543 Bryanston, Johannesburg Fax: 351 1 340 4575 South Africa 2021 Phone: 27 11 706-1629...
  • Page 25: Chapter 2. Installing The Management Edition Program

    Installing the Management Edition Program System requirements Before installing the Management Edition program, verify that your system has the features shown below, then consider the installation scenarios on page Hardware recommended The Management Edition program will install and run on any IBM PC or PC-compatible computer equipped with: •...
  • Page 26: Defining Anti-Virus Domains

    Installing the Management Edition Program • For anti-virus domain member machines: Windows NT Server or Workstation, v3.51 or later; Windows 95; Windows 98; Windows for Workgroups 3.11; Windows 3.1; and Novell NetWare v3.12 or later • For most machines: a Microsoft peer networking client (except Windows 3.1 or Windows 95 machines with a NetWare client and Name Provider service, and NetWare servers that do not require a network client) Defining anti-virus domains...
  • Page 27: Installation Scenarios

    Installing the Management Edition Program You can install the Management Console program on a machine’s local hard disk drive, or on a shared directory on a file server. Installing it to a file server allows you to run it from different machines that have access to the shared directory.
  • Page 28 Installing the Management Edition Program Option 2: Server/server – more than one anti-virus domain manager We recommend this configuration for sites that have more than one person administering the anti-virus solution. Program Files location: Server Repository location: Server Management Server location: Server The program files in this option are stored on a server rather than a local machine.
  • Page 29 Installing the Management Edition Program The local machine serving as the Management Server should not be powered off. If it is, it may miss on-access virus alerts that are generated by other machines and the scheduler may miss sending scheduled events to member machines while the machine is powered off.
  • Page 30: Installation Steps

    Installing the Management Edition Program Installation steps È IMPORTANT: If you are upgrading from version 2.0 to version 2.5 of the Management Edition program, you must install your new version to the same folder as your previous version to preserve your anti-virus domain configuration.
  • Page 31 Installing the Management Edition Program The Setup program prepares the InstallShield Wizard, which guides you through the installation process, and then the first Welcome dialog box appears (Figure 2-1). Figure 2-1. Welcome dialog box 6. Click Next. A second Welcome dialog box appears (Figure 2-2).
  • Page 32 Installing the Management Edition Program 8. Read the license carefully. Click Yes to accept the terms of the software license and continue the installation. The User Information dialog box appears (Figure 2-3). Figure 2-3. User Information dialog box 9. Enter your name and company (both details are required) in the text boxes, and then click Next to continue the installation.
  • Page 33 Installing the Management Edition Program • You can accept the default directory. • You can select a different folder, by clicking Browse. The Browse for Folder dialog box appears (Figure 2-5). Figure 2-5. Browse for Folder dialog box Select a folder, and click OK. NOTE: If the Management Edition program is installed on a server, you can run the Management Console on other machines that have access to its program folder.
  • Page 34 Installing the Management Edition Program Setup checks that there is enough hard disk space for the installation, and then the Select Program Folder dialog box appears (Figure 2-6). Figure 2-6. Select Program Folder dialog box 12. To add program icons to a folder, you can accept the default, or you can specify a different program folder than the one shown in the Program Folder text box, either by typing its name in the text box or selecting it in the Existing Folders list box.
  • Page 35 Installing the Management Edition Program 14. To review or change the information, click Back. To begin the installation, click Next. If you click Next, the Setup Complete dialog box appears (Figure 2-8). Figure 2-8. Setup Complete dialog box 15. Once the installation is complete, you can do one of the following: •...
  • Page 36: Running The Management Console (Initial Use)

    Installing the Management Edition Program Running the Management Console (initial use) The first time you run the Management Console, it prompts for a location to install the master repository (also known as “the Repository,” as distinguished from mirror repositories, which occur in multiples). Installing the master repository The master repository (i.e., the Repository) is a set of sub-directories that contain all the Management and anti-virus software for distribution around the...
  • Page 37 Installing the Management Edition Program The Repository Setup dialog box appears (Figure 2-9). Figure 2-9. Repository Setup dialog box 2. Enter the server name in the Machine box. Click the browse (...) button next to the Machine box to select a different server in the Network Browser dialog box (Figure 2-10).
  • Page 38 Installing the Management Edition Program Select a suitable server, and click OK. Your selection appears in the Repository Setup dialog box (Figure 2-11). Figure 2-11. Repository Setup dialog box 3. Accept the default location for the master repository, C:\Program Files\ Network Associates\Management Console\Disks on the local machine, in the Repository Path box.
  • Page 39 Installing the Management Edition Program Select a suitable path, and click OK. Your selection appears in the Repository Setup dialog box. 4. If the share directory is to be hidden, select the Hide Shares checkbox. 5. Click OK to begin installing the master repository. The master repository initially needs about 15MB of disk space.
  • Page 40 Installing the Management Edition Program Refer also to the Repository diagram (Figure 2-14). Figure 2-14. Repository diagram The following table lists the Management components: Management Agent Lets you manage each member machine in the anti-virus domain. (It is automatically installed on every Management Edition machine.) Scheduler Helps you schedule on-demand scans for specific times.
  • Page 41 Installing the Management Edition Program • To install anti-virus components after completing the installation of the Management Console, click Cancel when the Browse for Folder dialog box appears. See “Installing anti-virus components in the Repository” on page • To install the anti-virus components now, follow these steps when the Browse for Folder dialog box appears: a.
  • Page 42: Installing Anti-Virus Components In The Repository

    Installing the Management Edition Program Installing anti-virus components in the Repository You have now installed the management components into the master repository. You must now install the anti-virus software into the Repository. Follow these steps to install anti-virus components in the Repository: 1.
  • Page 43 Installing the Management Edition Program The Install New Software dialog box appears (Figure 2-17). Figure 2-17. Install New Software dialog box 3. Click Product to install a new version of the software. The other types of software that you can install via this dialog box are as follows: Extra Dat.
  • Page 44 Installing the Management Edition Program The Browse for Folder dialog box appears (Figure 2-18). Figure 2-18. Browse for Folder dialog box 5. Click the appropriate drive letter, and click OK. The anti-virus software files are copied into the Repository, as shown in the Repository dialog box on the Maintenance page (Figure 2-19).
  • Page 45 Installing the Management Edition Program Once the files are copied, the anti-virus components you installed are added to the list, as shown in the Repository dialog box on the Products page (Figure 2-20). Figure 2-20. Repository dialog box (Products page) 7.
  • Page 46 Installing the Management Edition Program Installing NetShield NetWare in the Repository NOTE: The Management Edition 2.5 software supports NetShield for NetWare v4.1.1 anti-virus software. Management Edition 2.5 software does not work with NetShield for NetWare v4.1.0 or earlier. When you install NetShield NetWare in the Repository, the NetShield installer runs in a special mode to generate the following two packages in your Repository: •...
  • Page 47 Installing the Management Edition Program Figure 2-21. Component Configuration dialog box (NetShield NetWare page) If you click Configure ME, a dialog box with two pages appears. From here, you can configure the following settings: NetShield NDS user object. The NDS (Novell Directory Services) object is required by the NetShield program for authentication on NetWare servers.
  • Page 48 Installing the Management Edition Program Preparing for the NetShield program rollout on NetWare servers Management Edition configures only the on-access scanner settings and sets the other settings to the defaults; you will need to configure these settings with the NetShield NetWare NT Console by connecting to the NetWare servers individually, prior to rollout.
  • Page 49 Installing the Management Edition Program 3. Configure the NetShield NetWare on-demand scanner and Alert Manager settings. For example, you can schedule a nightly on-demand scan of all volumes. 4. To use a different password when connecting to the servers using the NetShield NetWare NT Console, go to the NetWare server console and unload NETSHLD.NLM.
  • Page 50 Installing the Management Edition Program Performing a “silent” installation for rollout of the VirusScan program If you manage a network and want to deploy the VirusScan program as your standard anti-virus security application, you can use the program’s “silent” installation feature to set up the VirusScan program on each network node with little or no interaction from end users.
  • Page 51 Installing the Management Edition Program Here, <X> represents the drive letter for your CD-ROM drive or the path to the folder that contains your extracted VirusScan files. The -R tells Setup to run in its “record” mode. NOTE: If your VirusScan copy came on a VirusScan Security Suite or a Total Virus Defense* CD-ROM disc, you must also specify which folder contains the VirusScan program for Windows 95 and Windows 98.
  • Page 52 Installing the Management Edition Program Specifying an installation directory To install the VirusScan program in a particular directory, do not edit the SETUP.ISS file you created when you installed the VirusScan program on your administrative computer or server. Instead, in the Add/Remove Components dialog box, click the text of the pathname shown in the Install Directory list, and enter the pathname to a different installation directory.
  • Page 53 Installing the Management Edition Program 3. Copy the SETUP.ISS file you created when you ran the recorded installation on your administrative computer to the VirusScan directory on the central server. You’ll find the file you need to copy in the WINDOWS directory on your administrative computer.
  • Page 54: Understanding The Management Console

    Installing the Management Edition Program Understanding the Management Console You can consult the following sections for details about the main areas of the Management Console (Figure 2-22): • “Menu bar” on page • “Toolbar” on page • “Font bar” on page •...
  • Page 55 Installing the Management Edition Program Menu bar Consult the following table for explanations of Management Console’s main menu commands: Menu name Menu commands File New Domain / Machine / Members Group / Scheduler Event. Click this to add one of these types to the anti-virus domain. Print.
  • Page 56 Installing the Management Edition Program Menu name Menu commands Tools Repository. Click this to view the Repository and install software to it. Push On Install. Click this to enable a first-time or upgrade installation of selected Management and anti-virus components from the Repository.
  • Page 57 Installing the Management Edition Program Toolbar The toolbar is displayed across the top of the application window, below the menu bar. The toolbar provides quick mouse access to many functions used in the Management Console. Follow these steps to display or hide the toolbar: 1.
  • Page 58 Installing the Management Edition Program Consult the following table for an explanation of the toolbar icons. Click... Command To... Create a new anti-virus domain. Apply Apply the configuration to all machines in the Configuration current domain, automatically repeating failed updates until they succeed. Print Print the report currently displayed in the right-hand pane.
  • Page 59 Installing the Management Edition Program Right pane The right pane provides information about your entire Microsoft network, and more specific information about the machines, group of machines, or whole anti-virus domains shown in the left pane. The tabs that appear at the bottom of the right-hand pane will vary depending on your selection of items in the left-hand pane.
  • Page 60 Installing the Management Edition Program Left-pane Right-pane view options selection Management Network. Click this tab to view a list of machines in your Server network. Properties. Click this tab to view platform and domain information for the selected domain. Scan Results. Click this tab to view historical results of previous virus scans for the selected domain you’ve created within the main Anti-Virus Domain(s).
  • Page 61 Installing the Management Edition Program Left-pane Right-pane view options selection Members group Network. Click this tab to view a list of machines in your network. Properties. Click this tab to view platform and domain information for machines in the selected Members group. Scan Results.
  • Page 62: Upgrading The Management Edition Program

    Installing the Management Edition Program • The keyboard latch state. When the following keys are latched down, they are indicated on the right side of the status bar: – NUM. The Num Lock key is latched down. – CAP. The Caps Lock key is latched down. –...
  • Page 63: Chapter 3. Creating Anti-Virus Domains

    Creating Anti-virus Domains The Management Console lets you group machines into anti-virus domains. Each anti-virus domain contains a Management Server and one or more member machines. The Management Console can create any number of anti-virus domains, but each machine must reside in only one anti-virus domain. You can use this grouping to match the physical layout of machines within your organization or departments, and thus simplify their management.
  • Page 64 Creating Anti-virus Domains OS platform File sharing is enabled Installation method Windows for Drag and drop Workgroups 3.11 Client installer Windows 3.1 Not available Client installer NetWare Not applicable Drag and drop If “File sharing is enabled” on a machine, then the Microsoft network client has previously been installed and file sharing has been activated.
  • Page 65 Creating Anti-virus Domains Figure 3-1. Management Edition Install Options Flowchart Administrator’s Guide...
  • Page 66: Finding Machines In The Network View

    Creating Anti-virus Domains NP Install "NP Install" is the Name Provider installation method. Run the client installer program (SETUP.EXE or SETUP32.EXE if the machine’s operating system is 16-bit or 32-bit, respectively) on the target machine to install the Management Agent on it. Use the command-line switch /FORCENP to force the client to use Name Provider regardless of whether or not filesharing is enabled.
  • Page 67 Creating Anti-virus Domains Microsoft Windows Visible on Location in the OS platform Client is installed browser list Management Console Windows NT Microsoft Windows Network No (Note 1) Imported Browse List/ Manual Add Machine No (Note 2) Name Provider Windows 95 and Microsoft Windows Windows 98 Network...
  • Page 68: Preparing Machines With Peer Networking

    Creating Anti-virus Domains Name Provider The machine appears under the Name Provider icon in the network view, under its Microsoft computer name. For more information about the Name Provider, see the table of Management components on page Name Provider (Windows 3 .x ) The machine appears under the Name Provider icon in network view, under the unique name generated by the Name Provider service on the Management Server.
  • Page 69 Creating Anti-virus Domains Small organizations can store accounts and resources in one domain. However, large organizations usually establish multiple domains. They can then store accounts in one domain and resources in another. A trust relationship is a link between two Windows NT Server domains, providing security across multiple domains.
  • Page 70: Windows 95 And Windows 98 Machines (User-Level Access)

    Creating Anti-virus Domains The Trust Relationships dialog box appears (Figure 3-3). Figure 3-3. Trust Relationships dialog box 5. Click Add and type the name of the Windows NT Server domain that is to be trusted in the Trusted Domains box. 6.
  • Page 71 Creating Anti-virus Domains The File and Print Sharing dialog box appears (Figure 3-4). Figure 3-4. File and Print Sharing dialog box 3. Select the I want to be able to give others access to my files checkbox, and then click OK. In the Network dialog box, click the Access Control tab.
  • Page 72: Windows 95 And Windows 98 Machines (Share-Level Access)

    Creating Anti-virus Domains 8. Start Control Panel again. 9. Double-click Passwords, then select the Remote Administration tab. The Remote Administration page appears (Figure 3-6). Figure 3-6. Passwords Properties dialog box (Remote Administration page) 10. Select the Enable Remote Administration of this server checkbox. 11.
  • Page 73 Creating Anti-virus Domains The Access Control page appears (Figure 3-7). Figure 3-7. Network dialog box (Access Control page) 3. Select the Share-level access control option. This lets you supply a password for each shared resource. 4. Click OK and reboot the machine for share-level access to take effect. 5.
  • Page 74: Windows For Workgroups 3.11 Machines

    Creating Anti-virus Domains 9. Go to Control panel, double-click Passwords and select the Remote Administration tab. The Remote Administration page appears (Figure 3-6 on page 72). 10. Select the Enable Remote Administration of this server checkbox. 11. Type and confirm a share-level password. The administrator must use this password to create, change, or monitor shared resources on the machine.
  • Page 75: Preparing Machines Without Peer Networking

    Creating Anti-virus Domains If you have specified a password on your Windows for Workgroups 3.11 machine, then on the Management Console’s main menu, click Tools, and then click Options. Click the Remote Installation tab, and enter the password. Preparing machines without peer networking Your site might not use peer networking, or you might have a number of machines that do not.
  • Page 76: Windows 3.1 Machines

    Creating Anti-virus Domains If you are installing a large number of machines to the same anti-virus domain from a shared location, often a directory on a server, you can pre-configure the file so that the installation is completely automatic; no input will be required on the target machine.
  • Page 77 Creating Anti-virus Domains Before the Management Agent can locate a Name Provider to request a computer name, it must be given the name of the anti-virus domain it is to join. You can configure this within the NAMEPROV.INI file before the installer runs, or afterwards, when the Management Agent will request it.
  • Page 78 Creating Anti-virus Domains To pre-configure this file, you must indicate the domain name in the NP_DOMAIN parameter. Do not enclose the domain name in quotes, even if it contains spaces. If you alter the currently supplied line, remove the semicolon prefixing NP_DOMAIN so that the line is no longer treated as a comment.
  • Page 79: Windows Nt, Windows 95, Or Windows 98 Machines

    Creating Anti-virus Domains È IMPORTANT: You must ensure that all of your anti-virus domain names are different within the first ten characters to prevent Name Providers from using the same partial names. Otherwise, duplicate names will be generated. For example, two domains named Sales_Bld1 and Sales_Bld2 are acceptable because they are different within the first ten characters, but Sales_Building1 and Sales_Building2 are not acceptable.
  • Page 80 Creating Anti-virus Domains This information can be configured within the NAMEPROV.INI file prior to running the installer, or afterwards, when the Management Agent will request This is the basic template NAMEPROV.INI file as supplied with the installer: ; This is the section header that needs to be used. This ;...
  • Page 81: Automating Setup Via Netware Login Scripts

    Creating Anti-virus Domains We recommend that you also supply an IP or IPX address. If you supply the IP or IPX address of the network card in the Management Server via the NP_ADDR1 or NP_ADDR2 parameter, then the Management Agent can contact the machine directly without sending a broadcast.
  • Page 82 Creating Anti-virus Domains MAP ROOT F:=SYS:PUBLIC\ME_CLNT #AUTOINST C:\WINDOWS F:\SETUP.EXE The login script changes an example WIN.INI file as follows: Old WIN.INI New WIN. INI [WINDOWS] [WINDOWS] RUN=NWPOPUP.EXE RUN=NWPOPUP.EXE F:\SETUP.EXE AUTOINST.EXE also adds the following section and key to WIN.INI: [NetworkAssociates] NetworkAssociatesInstalled=Yes This prevents AUTOINST from adding the installer’s executable path to the RUN= line more than once.
  • Page 83: Preparing Netware Servers

    Creating Anti-virus Domains NOTE: If you create a new drive mapping that points to the directory where the installer resides, do not remove this drive mapping until after the installer has been run. For more details about AUTOINST, see Appendix A, “Using the AUTOINST Utility.”...
  • Page 84: Installation Method

    Creating Anti-virus Domains Installation method You can only perform an installation via the Push On install method, unless you have placed a mirror repository onto a NetWare server. This restriction occurs because NetWare servers cannot directly access files on Windows NT machines.
  • Page 85: Assigning A Management Server

    Creating Anti-virus Domains If the machine is in a different domain from your own, you can set up a trust relationship between the two domains. For more details, see “Windows NT machines (trust relationships)” on page If the Management Console cannot gain access to a member machine, it prompts the Domain Administrator for a user account and password that does have sufficient rights.
  • Page 86 Creating Anti-virus Domains Figure 3-11. Two anti-virus domains with WAN link Follow these steps to select the Management Server: 1. In the Management Console’s network view, select a Windows NT server that is running continuously. To check the machine’s operating system, right-click the machine and choose Discover.
  • Page 87: Adding Member Machines To An Anti-Virus Domain

    Creating Anti-virus Domains The Management Server is assigned. NOTE: To enable adding machines via the Name Provider, you must click Apply Configuration for the Management Server. This applies to the following machines: - All Windows 3.x machines, - Windows 95 and Windows 98 machines with file sharing disabled, - Windows NT machines with the server service disabled (or the machine name hidden from the browse list via NET CONFIG SERVER /HIDDEN:YES), and...
  • Page 88: Using The Drag-And-Drop Method

    Creating Anti-virus Domains • Drag-and-drop method. Drag the machine from the network view of the Management Console into an anti-virus domain. For details, see “Using the drag-and-drop method” on this page. • Discover method. Right-click the machine in the network view of the Management Console and choose Discover.
  • Page 89: Using The Discover Method

    Creating Anti-virus Domains Next, a dialog box appears, asking you whether you want to add the machines you’ve selected to the anti-virus domain (Figure 3-13). Figure 3-13. Add selected machines dialog box 4. Click Yes to add the selected machines to the anti-virus domain. The machines then appear under Members of the selected anti-virus domain, in the anti-virus domain view.
  • Page 90 Creating Anti-virus Domains Adding newly installed machines If you already have a large number of configured machines in the Name Provider’s list, new machines will be hard to identify. Follow these steps to view a newly installed machine if it is not displayed under the Name Provider: In the Management Console, do one of the following: •...
  • Page 91: Choosing Your Anti-Virus Software

    Creating Anti-virus Domains Choosing your anti-virus software Anti-virus software (the scan engine) is updated approximately every six months. The virus-detection database is updated approximately every six weeks. Because hundreds of new viruses appear each month, frequent updating is necessary to ensure that the anti-virus software can detect them all.
  • Page 92: Selecting Anti-Virus Domain Components

    Creating Anti-virus Domains NOTE: For more information about adding .DAT updates, see “Installing anti-virus components in the Repository” on page For more information about managing anti-virus software, see “Changing anti-virus software versions” on page 134. For more information about managing large networks, see Chapter 7, “Configuring Complex Domains.”...
  • Page 93: Adding Or Removing Components For All Anti-Virus Domains

    Creating Anti-virus Domains Adding or removing components for all anti-virus domains Follow these steps to select anti-virus components for all anti-virus domains: 1. In the anti-virus domain view, right-click Anti-Virus Domain(s) and select Add/Remove Components. The Global Components dialog box appears (Figure 3-16).
  • Page 94 Creating Anti-virus Domains The Installing Entire Domain Model dialog box appears (Figure 3-17). A bar indicates the progress of the Management Console, which may take some time. Figure 3-17. Installing Entire Domain Model dialog box In the anti-virus domain view, the component names appear in bold type as they are installed.
  • Page 95: Adding Or Removing Components For Non-Standard Machines

    Creating Anti-virus Domains Adding or removing components for non-standard machines You can add more or remove existing anti-virus components for individual machines, groups of machines, or domains. The number of machines you affect depends on your selection in the anti-virus domain view. •...
  • Page 96 Creating Anti-virus Domains 4. Right-click the machine name and choose Apply Configuration. This installs the components to, or removes them from, the individual machine only, without affecting the rest of the anti-virus domain. Similarly, the settings for the anti-virus domain no longer affect it. The machine is now considered non-standard.
  • Page 97: Chapter 4. Creating Schedules

    Creating Schedules The Scheduler is a Management component that lets you schedule on-demand scans to occur at specific times. It sends a command to all member machines you specify, to scan themselves. Although the on-access component scans files every time you access a file, a virus might reside in a file you have not accessed for a while.
  • Page 98 Creating Schedules The New Event dialog box appears, with the Event page showing (Figure 4-2). Figure 4-2. New Event dialog box (Event page) 3. In the Name box, type a name (e.g., Midday Scan). In the Type box, choose the default, Scan for Viruses. (If you select Run an Application, you can run another program instead of running an anti-virus program.) 4.
  • Page 99 Creating Schedules When you have finished scheduling a scan and returned to the Scheduler Events page, you’ll notice an icon to the left of the scan event name, which indicates whether it is enabled: The scan event is enabled. The scan event is disabled. 7.
  • Page 100 Creating Schedules NOTE: If most machines are powered off during weekends, the scan will fail on those machines. Also, if the machines were scanned after work on Friday, they do not need scanning again until the next work week begins on Monday. 11.
  • Page 101 Creating Schedules NOTE: To select a group of member machines in the anti-virus domain, click on the first machine you want to include, and then press the Shift key and click on the last consecutive machine. If the machines are not consecutive, press the Control key and click on each machine you want to include.
  • Page 102 Creating Schedules The Scan Settings dialog box appears (Figure 4-5). Figure 4-5. Scan Settings dialog box 14. Enter extra parameters in the Additional command line options text box, or select one from the list of most recently used options. Each machine generates information that you can view remotely via the Management Console.
  • Page 103: Scheduling Similar Scans

    Creating Schedules NOTE: After your scheduled scan has run, an icon to the left of the name of the target machine (in the anti-virus domain view) indicates the results of the scan: The scan experienced a problem. The scan experienced no problems. Scheduling similar scans “Scheduling scans”...
  • Page 104 Creating Schedules 3. Click below the scheduled scan you just copied, and choose Paste. The Change event name dialog box appears (Figure 4-7). Figure 4-7. Change event name dialog box 4. Enter a new name for the event you’re creating. All settings are the same; only the name is changed.
  • Page 105: Running On-Demand Scans

    Creating Schedules Running on-demand scans Follow these steps to run an on-demand scan of an anti-virus domain or Members group: 1. In the Management Console’s anti-virus domain view, right-click an anti-virus domain or Members group, and point to Scan Machines. NOTE: The machines in the anti-virus domain must already have the VirusScan or NetShield programs installed.
  • Page 106 Creating Schedules The Scan Settings dialog box appears (Figure 4-8). Figure 4-8. Scan Settings dialog box 3. Enter any additional command-line options, and then click OK. A dialog box appears, informing you that the scan has been dispatched. The on-demand scanner starts on all selected machines. This can take a few minutes.
  • Page 107: Viewing Results Of On-Demand Scans

    Creating Schedules Viewing results of on-demand scans NOTE: For a graphical view of a virus scan, see “Checking virus scan status” on page 108. The information returned to the Management Server during the scan of a machine represents only part of the information that may be returned by the on-demand scanner.
  • Page 108: Checking Virus Scan Status

    Creating Schedules Checking virus scan status When you have a large number of machines to manage, it is useful to be able to view the entire network at a glance to see whether any machines have a virus. To view a graphical display of the network scan status, right-click Anti-Virus Domain(s), and choose Update Scan Status.
  • Page 109: Acknowledging Virus Scan Status

    Creating Schedules Colored icons indicate the status of the latest virus scan. The following table explains each icon: Icon Status Description Alert A virus was detected, or a disinfection attempt failed. Warning A warning can have several possible causes: - The last virus scan was stopped by the user. - No scan has occurred within a defined period.
  • Page 110 Creating Schedules Again, the icons work in a hierarchical manner. For example, if you acknowledge scan status for a whole group or domain, each machine no longer shows an icon. If you acknowledge an individual machine within a group or domain, only that machine no longer shows an icon. Follow these steps to acknowledge the scan status for an anti-virus domain or Members group: 1.
  • Page 111: Rescanning The Machines

    Creating Schedules Rescanning the machines When you believe that the virus problem has been resolved on a machine or group of machines, or you want to disinfect any machines, you may re-scan them. 1. For single machines, right-click the machine and choose Scan. For a group of machines, right-click the anti-virus domain or Members group, point to Scan, and select the machines to scan: •...
  • Page 112 Creating Schedules Follow these steps to view the scan status report: 1. After a scan has been run on the machine, select the machine in the anti-virus domain view, and then click the Scan Results tab in the right pane to view a report. The Scan Results page shows the contents of the report file (Figure 4-10 on page...
  • Page 113 Creating Schedules The Scan Status Report is dynamically generated and appears on the Scan Results page (Figure 4-10). For example: Figure 4-10. Scan Results page (Scan Status Report) The report includes various counts for alerts and warnings. The virus-scan status for each machine is shown as a single word—OK, Warning, or Alert—and its corresponding line in the report is colored for further effect.
  • Page 114 Creating Schedules The Change Report Formatting dialog box appears (Figure 4-11). Figure 4-11. Change Report Formatting dialog box 4. You can only adjust the appearance of settings for items installed OK, with warnings, or with errors. Make your changes: • Click Set Color to select a different text color. •...
  • Page 115: Refreshing The Display

    Creating Schedules Refreshing the display The display is normally refreshed every 10 seconds, but you can adjust this. If you prefer to disable the automatic refresh, the display will only refresh when you right-click a machine or group and choose Scan, or Update Scan Status. Follow these steps to change the refresh settings: 1.
  • Page 116 Creating Schedules The Tracking Changes page appears (Figure 4-13). Figure 4-13. Options dialog box (Tracking Changes page) 3. Select the Enable update of scan status checkbox. 4. Enter the number of seconds for the frequency that you want the scan status to refresh.
  • Page 117: Setting A Warning Period

    Creating Schedules Setting a warning period Although a machine shows the OK icon, it might have a virus. For example, if the machine has not been scanned for one month, any virus has had ample time to operate. To be sure that the indicated status is recent, you can set a warning period.
  • Page 118: Logging Scheduled Events

    Creating Schedules Logging scheduled events Enabling logging Follow these steps to log scheduled events: 1. Under the Management Server for the anti-virus domain, click Schedule. The Scheduler Events page appears in the right pane (Figure 4-14). Figure 4-14. Scheduler Events page 2.
  • Page 119: Refreshing The Log

    Creating Schedules 2. Click the Scheduler Log tab in the right pane. The Scheduler Log page appears (Figure 4-6 on page 103). You can filter your view of the log information. Each line of information is prefixed by an icon, denoting its type. 3.
  • Page 120: Saving The Log

    Creating Schedules 3. Right-click on the Scheduler Log page and choose one of the refresh options: • Refresh. Choose this option to immediately update the view with the latest information available. • Auto Refresh. Choose this option to enable automatic updating of the view according to your settings in the Refresh Frequency dialog box.
  • Page 121: Changing The Log Appearance

    Creating Schedules Changing the log appearance Follow these steps to change the appearance of the log: 1. Under the Management Server for the anti-virus domain, click Schedule. The Scheduler Events page appears in the right pane (Figure 4-14 on page 118).
  • Page 122 Creating Schedules Management Edition...
  • Page 123: Chapter 5. Updating Your Anti-Virus Software

    Updating Your Anti-virus Software As part of your product license or site license, you can get updates of virus signature (.DAT) files containing new virus detectors, cleaners, and fixes to reported bugs, usually supplied on CD-ROM. You can also get periodic upgrades to the latest version of your anti-virus product, which offers new features, enhancements, and functionality.
  • Page 124 Updating Your Anti-virus Software 2. Select the source directory from which you want the updates for the executable programs to be installed, and click OK. If you are installing from disk, repeat this for each remaining disk in your set until the installation of anti-virus update files is complete. 3.
  • Page 125 Updating Your Anti-virus Software The Browse for Folder dialog box appears (Figure 5-1 on page 123). 6. Select the directory where the anti-virus update files are located, and then click OK. The files are copied, and the anti-virus software is installed in the Repository.
  • Page 126: Installing Extra .Dat Files

    Updating Your Anti-virus Software Installing extra .DAT files You can use interim updates in an emergency to deal with a new virus that has been discovered between monthly versions of the anti-virus software. You can add extra .DATs to the Repository via two methods, including drag and drop. Follow these steps to install interim anti-virus file updates to the Repository: 1.
  • Page 127 Updating Your Anti-virus Software 5. In the Open dialog box, select the drive for the disk you just inserted, and then click Open. The file is copied, and the extra .DAT is installed in the Repository. 6. After the installation is complete, click Close to exit the Repository dialog box.
  • Page 128 Updating Your Anti-virus Software The Components for Anti-Virus Domain ... dialog box appears (Figure 5-6). Figure 5-6. Components for Ant-Virus Domain ... dialog box 2. Select the extra .DAT in the right-hand pane, and click Add. 3. Click OK. Follow these steps to install an extra .DAT to one machine: 1.
  • Page 129: Installing .Dat Updates And .Zip Files

    Updating Your Anti-virus Software • The number of extra .DATs may become quite large, particularly if you have variants of a virus to deal with. Installing and removing them on member machines can become very time-consuming. When to remove extra .DAT files Each extra .DAT is identified by its unique version number.
  • Page 130 Updating Your Anti-virus Software 3. Do one of the following: • Click DAT Update to install a periodic .DAT update. • To install items from a .ZIP file, click Filters. The Platform/Language Filter dialog box appears (Figure 5-8). Figure 5-8. Platform/Language Filter dialog box •...
  • Page 131 Updating Your Anti-virus Software 6. After the installation is complete, click Close to exit the Repository dialog box. Installing .DAT updates and other .ZIP items via drag and drop If you have downloaded your .DAT updates or other .ZIP items into a directory folder on a network drive, or if you receive your .DAT updates or other .ZIP items on disks, you can install them into the Repository by selecting the folder and dragging it onto the Products page of the Repository dialog box.
  • Page 132: Installing Script, Extension .Dll, Or Setup File Updates

    Updating Your Anti-virus Software The Components for Anti-Virus Domain ... dialog box appears (Figure 5-10). Figure 5-10. Components for Ant-Virus Domain ... dialog box 2. Select the .DAT update or other .ZIP item in the right-hand pane, and click Add. The files are copied, and the .DAT update or other .ZIP item is added to all machines in an anti-virus domain.
  • Page 133: Forcing Updates Of Invalid External Mirrors

    Updating Your Anti-virus Software 2. On the Management Console main menu, click Tools, and then click Repository. The Repository dialog box appears, with the Products page showing (Figure 5-2 on page 124). 3. Double-click to expand the list to show the different platforms on which a component is installed.
  • Page 134: Changing Anti-Virus Software Versions

    Updating Your Anti-virus Software Changing anti-virus software versions The Management Console’s main window shows both network and anti-virus domains as hierarchical structures. In the anti-virus domain view, you can change the version of the anti-virus software for all domains, for an individual domain, for a specific group of machines, and for individual machines.
  • Page 135: Changing The Version For Individual Domains

    Updating Your Anti-virus Software 2. Select the product version in the pull-down Version list in the left-hand pane, and click Add. 3. Click OK. 4. Right-click the anti-virus domain, and choose Apply Configuration. The files are copied to all machines in the anti-virus domain. This may take a while.
  • Page 136: Viewing Component Properties In The Repository

    Updating Your Anti-virus Software 2. Select the product version in the pull-down Version list in the left-hand pane, and click Add. 3. Deselect Use the global defaults. 4. Click OK. 5. Right-click the machine, and choose Apply Configuration. The files are copied to the machine. This may take a while. NOTE: This machine is now non-standard.
  • Page 137: Removing Old Versions From The Repository

    Updating Your Anti-virus Software The Component Properties dialog box appears (Figure 5-12). A list of components shows details about the product’s platform, version, and file size, plus the timestamp for when the component was installed. Figure 5-12. Component Properties dialog box A green check mark beside a component’s filename indicates that the file is present in the Repository and that you can install it onto member...
  • Page 138: Marking Shares As Null Session Shares

    Updating Your Anti-virus Software Marking shares as null session shares All repository shares created by the Management Edition program are automatically marked as null session. Therefore, the only time that you must manually mark a share as null session is when you have moved a share location or have inherited an existing share.
  • Page 139: Choosing An Update Method

    Updating Your Anti-virus Software Choosing an update method You can choose from three different methods—Push On, Pull Off, and Batch Install—for installing your anti-virus software onto member machines. The different methods affect how quickly the member machines receive their upgrades and how long the Management Console is busy servicing those requests.
  • Page 140: Using The Pull Off Install

    Updating Your Anti-virus Software Follow these steps to install to member machines using Push On Install: 1. In the Management Console’s main window, add machines to their required anti-virus domain. If necessary, see Chapter 3, “Creating Anti-virus Domains,” for details. 2.
  • Page 141: Using The Batch Install

    Updating Your Anti-virus Software 3. In the anti-virus domain view, right-click the machine, group, or anti-virus domain to which you want to install. Point to Manage Components, and choose Add/Remove Components. The Components dialog box appears (Figure 5-6 on page 128).
  • Page 142 Updating Your Anti-virus Software Batch Install is the best update method for large anti-virus domains, which are possibly spread over many sites or time zones. The Update Manager (DEMON.EXE) is a Windows NT service that is automatically installed by Management Edition on each Management Server. You generate an update request by running the requester, MEUPRQ32.EXE (32-bit) or MEUPRQ16.EXE (16-bit), from a target machine.
  • Page 143 Updating Your Anti-virus Software For scheduled updates, the Update Manager attempts to contact the member machines that it wants to update. If the Update Manager receives a reply from the Management Agent on the target machine, the update takes place and is recorded in the Update Manager’s database.
  • Page 144 Updating Your Anti-virus Software 5. Enter a Retry every ... minute(s) value. If an update fails (usually because the machine has been shut down or powered off), this indicates the amount of time the Update Manager must wait before retrying the machine.
  • Page 145 Updating Your Anti-virus Software 14. Click OK to return to the Options dialog box. 15. Click OK to return to the Management Console. Follow these steps to configure the number of simultaneous updates: 1. In the Management Console’s anti-virus domain view, right-click Anti-Virus Domain(s) and choose Component Configuration.
  • Page 146 Updating Your Anti-virus Software 3. Use the arrow buttons to set the number of member machines you want to update simultaneously. You can set a number from 1 to 500. NOTE: If you are performing a batch update from a local Windows NT repository, you are limited to ten concurrent connections.
  • Page 147 Updating Your Anti-virus Software You can also set the frequency that the Update Manager polls the master upgrade share (master repository), as well as reads and writes to the <Domain> UPGRADES.CFG and <Domain> UPGRADES0.CFG files. By default, it polls every 10 seconds, but you can specify this setting (in seconds) in the [Configuration] section of DEMON.INI, which the Update Manager will read on the fly: [Configuration]...
  • Page 148 Updating Your Anti-virus Software Table 5-1. Update states and icons Icon Text Meaning green Update sent and The update has been sent, and the Update Agent checkmark Update Agent has accessed the mirror repository. started successfully. writing Cancelled by user. The update was cancelled by the user. clock Cancelled by user The update was cancelled by the user while...
  • Page 149 Updating Your Anti-virus Software Consult the following table to understand how the state of an update changes over time (Table 5-2): Table 5-2. Update states over time Parent state Child state Created. Pending. Queued. Update send failed, retrying. Update sent successfully. Cancelled by user.
  • Page 150 Updating Your Anti-virus Software NOTE: Login scripts cannot be used for first-time installation. The machines must have Management Agent already installed and running. However, you can install the Management Agent via right-click Apply Configuration in the console, and then add VirusScan via the update from login script option, making it two separate steps rather than one.
  • Page 151 Updating Your Anti-virus Software Error Error code Description level ERR_FAILED_TO_GET_COMPUTER Failed to get computer name. NAME ERR_FAILED_INTEGRITY_CHECK Failed integrity check. none UNKNOWN Unknown error. Windows 3.11 and Windows 3.1 machines Unlike the 32-bit Update Requester, the 16-bit Update Requester does not do the actual brad packet send, because brad on 16-bit is single-app only.
  • Page 152 Updating Your Anti-virus Software This prevents AUTOINST.EXE from adding the Update Requester’s executable path to the RUN= line several times. If on a subsequent server login AUTOINST runs, it will not alter the RUN= line if it finds the NetworkAssociatesInstalled key. NOTE: If you copy the contents of the NP250\16\Client directory to a server directory to all network-based installations, copy the AUTOINST.EXE utility to the same directory to simplify the automated...
  • Page 153: Globally Applying Configuration

    Updating Your Anti-virus Software Error Error code Description level ERR_INTEGRITY_FAILURE This file has failed its integrity check. none UNKNOWN Unknown error. Follow these steps to initiate an update via login script: 1. In the Management Console’s main menu, click Tools, and then click Batch Install.
  • Page 154 Updating Your Anti-virus Software The Global Component Configuration dialog box appears, with the Upgrade page showing (Figure 5-17). Figure 5-17. Global Configuration dialog box (Upgrade page) 2. Click Reboot. The Reboot Options dialog box appears (Figure 5-18). Figure 5-18. Reboot Options dialog box 3.
  • Page 155: Configuring Custom Update Message Options

    Updating Your Anti-virus Software To force users to reboot after a set number of reminders, select the lower Force a reboot after option, and set the number of reminders and the time between each reminder. You may set up to 60 reminders from 1 to 60 minutes apart.
  • Page 156 Updating Your Anti-virus Software The Custom Update Message dialog box appears (Figure 5-19). Figure 5-19. Custom Update Message dialog box 3. Select the Display this message to users prior to the update checkbox to display your custom message before the update begins. 4.
  • Page 157: Configuring Custom Tools

    Updating Your Anti-virus Software 10. Enter the number of seconds to elapse before the message dialog box time will timeout and the Update Agent can continue. You can also use the arrows to select your preferred value. The default is 30 seconds. 11.
  • Page 158 Updating Your Anti-virus Software 4. Use the right-arrow button to insert a substitution parameter into the path in the Target text box. The parameters are substituted with values according to which machine is selected in the Management Console's anti-virus domain or network view.
  • Page 159 Updating Your Anti-virus Software 6. This is usually the same directory as the one specified in the Target text box, but it can be different (e.g., if the tool must look in a different directory to find some of its files). 7.
  • Page 160 Updating Your Anti-virus Software The default option Don't Care lets the Management Console launch the tool for any selected platform because the tool is either not platform-specific or will work for all platforms. 13. Click OK to save your changes and return to the Configure Custom Tools dialog box.
  • Page 161: Chapter 6. Using The Alert Manager

    Using the Alert Manager The Management Edition program uses Network Associates’ Alert Manager utility to notify you or others when a virus is detected on your servers. An anti-virus software component, Alert Manager includes a wide variety of notification options that you can use individually or in combinations. If you have Alert Manager installed on other computers in your network, you can also forward alert messages to other networked computers to consolidate alert messages on a designated server.
  • Page 162: Enabling Centralized Alerting For The Virusscan Program

    Using the Alert Manager 4. Verify that the Enable Centralized Alerting checkbox is selected. 5. Create a share on the directory shown in the Alert Folder box, and set this to Full Control for Everyone. Note the share name you have chosen. NOTE: If you perform the following steps before distributing anti-virus software to your target machines, the settings will be active immediately upon installation.
  • Page 163 Using the Alert Manager 3. Click the Alert tab. Select the Send network alert checkbox, and enter the UNC path to the share you created in Step 5 of the initial task. The format is \\<Machine>\<Share> (e.g., \\SERVER\ALERT). Follow these steps to enable centralized alerting for the VShield program for Windows 95 and Windows 98: 1.
  • Page 164 Using the Alert Manager For example, Alert Manager can be installed on a machine named SERVER, with an alert directory C:\PROGRAM FILES\NETWORK ASSOCIATES\NETSHIELD\ ALERT. This directory is shared by the name ALERT. The Windows 3.x machines connect to this server and map drive F: to the share (\\SERVER\ALERT).
  • Page 165: Configuring Alerts

    Using the Alert Manager Configuring alerts When you have enabled centralized alerting in both the Netshield and VirusScan programs, you can begin configuring your alert notification options. Follow these steps to enable and configure Alert Manager options: 1. To access the Alert Manager settings from the Management Console, click Anti-Virus Domain(s), an individual domain, a...
  • Page 166: Viewing The Summary Page

    Using the Alert Manager Viewing the Summary page Figure 6-1. Alert Manager Properties dialog box (Summary page) The Summary page lists all of the alert methods that you’ve chosen to notify you when your anti-virus software finds a virus on your server. In the example (Figure 6-1), Alert Manager will generate DMI alerts, send a network message to specified computers, and send alerts to a printer and a pager.
  • Page 167: Forwarding An Alert To A Networked Computer

    Using the Alert Manager Forwarding an alert to a networked computer Alert Manager can forward the alert messages that your anti-virus software generates to other computers on your network. If you have installed Alert Manager on each of the destination computers, they can in turn forward alert messages to the recipients listed in their respective Alert Manager Summary pages.
  • Page 168 Using the Alert Manager • To add a computer to the list, click Add to open the Forward Properties dialog box (Figure 6-3), then enter the name of the computer that will receive forwarded messages in the Computer box. You can enter the computer name in Universal Naming Convention (UNC) notation \\server_name or click Browse to locate the computer on the network.
  • Page 169 Using the Alert Manager In the Priority Level dialog box that appears (Figure 6-4), drag the slider to the right to send the destination computer fewer, but higher priority, messages. Drag the slider to the left to send the destination computer more alert messages, including lower priority messages.
  • Page 170: Sending An Alert As A Network Message

    Using the Alert Manager Sending an alert as a network message Alert Manager can send the alert messages that your anti-virus software generates to other computers or users on your network using a standard Windows NT network message. The alert message appears on the destination computer’s screen and requires the recipient to acknowledge it.
  • Page 171 Using the Alert Manager 3. You can update this list in one of the following ways: • To remove a computer/user from the list, select one of the destination computers/users, then click Remove. • To add a computer/user to the list, click Add to open the Network Message Properties dialog box (Figure 6-6 on page 172), then enter...
  • Page 172 Using the Alert Manager Figure 6-6. Network Message Properties dialog box 4. Click Priority Level to specify which types of alert messages the destination computer will receive. In the Priority Level dialog box (see Figure 6-4 on page 169), drag the slider to the right to send the destination computer fewer, but higher priority, messages.
  • Page 173: Sending An Alert As An Smtp E-Mail Message

    Using the Alert Manager Sending an alert as an SMTP e-mail message Alert Manager can send the alert messages that your anti-virus software generates to a recipient’s e-mail address using standard Internet mail. The alert message appears in the recipient’s mailbox. If your message is particularly urgent, supplement an e-mail message with other methods to ensure that your recipient sees the alert in time to take appropriate action.
  • Page 174 Using the Alert Manager • To add an e-mail address to the list, click Add to open the E-Mail Properties dialog box (Figure 6-8). Enter the e-mail address for your alert recipient in the Address box, enter a subject in the Subject box, then enter your e-mail address in the From box.
  • Page 175 Using the Alert Manager 5. Click SMTP Settings to specify which network server to use to send Internet mail via the Simple Mail Transfer Protocol. In the dialog box that appears (Figure 6-9), enter the server name in the Server box and a username for an active mail account that Alert Manager can use to log on to the server in the Login box.
  • Page 176: Sending An Alert To A Pager

    Using the Alert Manager Sending an alert to a pager Alert Manager can send the alert messages that your anti-virus software generates to a recipient’s pager, provided that you have a modem and telephone line connected to the machine running Alert Manager. Alert Manager supports both alphanumeric pagers and pagers that receive only numeric messages.
  • Page 177 Using the Alert Manager • To add a pager number to the list, click Add to open the Pager Properties dialog box (Figure 6-11 on page 178). Choose the type of pager your recipient uses from the list at the top of the page, then enter the information for that pager type in the boxes provided.
  • Page 178 Using the Alert Manager Figure 6-11. Pager Properties dialog box 4. Click Priority Level to specify which types of alert messages your recipient will receive. In the Priority Level dialog box (see Figure 6-4 on page 169), drag the slider to the right to send the recipient fewer, but higher priority, messages.
  • Page 179 Using the Alert Manager Figure 6-12. Modem dialog box 6. Click Test to send a test message to the pager number you entered. If your recipient uses an alphanumeric pager, Alert Manager sends a text message. If your recipient uses a numeric pager, Alert Manager sends the telephone number or other message that you specified in the Pager Properties dialog box.
  • Page 180: Sending An Alert To A Network Printer

    Using the Alert Manager Sending an alert to a network printer Alert Manager can send anti-virus software alert messages as a print job for your network print server to process. To use this option, you must first set up your printer with the Windows Print Manager and select the correct printer driver for your target printer.
  • Page 181 Using the Alert Manager • To add a printer to the list, click Add to open the Printer Properties dialog box (Figure 6-14), then enter the name of the target printer in the Printer box. You can enter the printer name in Universal Naming Convention (UNC) notation \\server_name\directory_name\printer_name or click Browse to locate the printer on the network.
  • Page 182 Using the Alert Manager 5. Click Test to send the destination printer a test message. The message will print as a simple, unformatted line of text. 6. Click OK to return to the Printer page. 7. To configure other notification options, click a different tab. To save your configuration options and close the Alert Manager Properties dialog box, click OK.
  • Page 183: Sending An Alert As An Snmp Network Message

    Using the Alert Manager Sending an alert as an SNMP network message Alert Manager can send the alert messages that your anti-virus software generates to other computers via the Simple Network Management Protocol (SNMP). To see the alert messages that Alert Manager sends, you must have an SNMP management system configured with an SNMP viewer, such as Hewlett-Packard’s OpenView.
  • Page 184 Using the Alert Manager In the Priority Level dialog box (see Figure 6-4 on page 169), drag the slider to the right to send the SNMP management computer fewer, but higher priority, messages. Drag the slider to the left to send the SNMP management computer more messages, including lower priority messages.
  • Page 185 Using the Alert Manager 4. Click Test to send the SNMP management computer a test message. To see the message you sent, start your SNMP viewer software. 5. To configure other notification options, click a different tab. To save your configuration options and close the Alert Manager Properties dialog box, click OK.
  • Page 186: Sending An Alert To A Dmi Console

    Using the Alert Manager Sending an alert to a DMI console NOTE: DMI (Desktop Management Interface) is an industry interface for keeping track of and monitoring the status of components, including hardware and software, in the computers on your network. For more information about DMI, visit the Desktop Management Task Force website at http://www.dmtf.org.
  • Page 187 Using the Alert Manager 4. Click Priority Level to specify which types of alert messages the destination computer will receive. In the Priority Level dialog box (see Figure 6-4 on page 169), drag the slider to the right to send the destination computer fewer, but higher priority, messages.
  • Page 188: Launching A Program On Alert

    Using the Alert Manager Launching a program on alert NOTE: Any program launched from Alert Manager runs in the background without a visible user interface. Alert Manager can be configured to launch any program or batch file on alert. For example, if your company is using cc:Mail or a special mail package that is not recognized by Alert Manager, you can write a batch file to send notifications to your mail package.
  • Page 189 Using the Alert Manager 4. In the Program box, enter the name and path of the program you want Alert Manager to run upon detection of a virus. You can enter the program name in Universal Naming Convention (UNC) notation \\server_name\directory_name\program_name or click Browse to locate the program on the network.
  • Page 190: Sending An Alert As An Audible .Wav File

    Using the Alert Manager Sending an alert as an audible .WAV file NOTE: To use this option, your system must have a sound card installed. Alert Manager can use .WAV files to sound an audible alert on your system when your anti-virus software detects a virus or when other alerts are generated.
  • Page 191 Using the Alert Manager Leave the box blank to use the default system sound when your anti-virus software detects a virus. 5. Click Priority Level to specify which types of alert messages the destination computer will receive. In the Priority Level dialog box (see Figure 6-4 on page 169), drag the slider to the right to send the destination computer fewer, but higher...
  • Page 192: Logging Alerts

    Using the Alert Manager Logging alerts Alert Manager can log the alert messages that your anti-virus software generates to the computers it is running on or to other computers in your network to the Windows NT Application Event Log. Follow these steps to configure logging of alerts: 1.
  • Page 193 Using the Alert Manager • To add a computer to the list, click Add to open the Logging Properties dialog box (Figure 6-21), then enter the name of the destination computer in the Computer box. You can enter the computer name in Universal Naming Convention (UNC) notation \\server_name or click Browse to locate the computer on the network.
  • Page 194 Using the Alert Manager In the Priority Level dialog box (see Figure 6-4 on page 169), drag the slider to the right to send the destination computer fewer, but higher priority, messages. Drag the slider to the left to send the destination computer more network messages, including lower priority messages.
  • Page 195: Chapter 7. Configuring Complex Domains

    Configuring Complex Domains Designing anti-virus domains The main window of the Management Console program consists of the anti-virus domain view in the left pane and several other possible views in the right pane, each of which is viewable depending on the item selected in the left pane.
  • Page 196: Single Office

    Configuring Complex Domains Single office If you have a small network in one office, you can have one anti-virus domain, which is the same as your network domain (Figure 7-1). Figure 7-1. One anti-virus domain / one network domain Multiple office, one site If your network spans several different departments but all are at the same site, your anti-virus domain can be different from some of your network domains...
  • Page 197: Multiple Site, One Country

    Configuring Complex Domains Multiple site, one country In one country, you can have a network domain spanning several sites. You can have several network domains, with machines on different networks in different cities. They can all be in the same anti-virus domain, or you can have separate domains for each site (Figure 7-3).
  • Page 198: Adding Anti-Virus Domains

    Configuring Complex Domains In order for local staff in each office to respond to virus alerts, you can create an anti-virus domain for each office, including a mirrored repository. For more details, see “Creating mirror repositories” on page 213. Adding anti-virus domains The Management Console can maintain multiple anti-virus domains.
  • Page 199: Moving Machines Between Anti-Virus Domains

    Configuring Complex Domains If you have a large network with many machines in the anti-virus domain, some member machines may be powered down. The Apply Configuration button polls all machines until they are powered on and then configures and installs to them. Moving machines between anti-virus domains After you have created an anti-virus domain, you can change the way it is organized.
  • Page 200: Deleting Machines From Anti-Virus Domains

    Configuring Complex Domains Deleting machines from anti-virus domains During reorganizations of machines, anti-virus domains, or the responsibilities for such domains, you can remove individual machines from anti-virus domains. Follow these steps to remove a machine or anti-virus domain: 1. To remove a machine, right-click the machine and choose Remove, or drag the machine from the anti-virus domain view back across to the network view.
  • Page 201 Configuring Complex Domains NOTE: Each anti-virus domain needs a Management Server to function properly. If you need to change the Management Server, use the Promote and Demote commands. For details, see “Changing the Management Server” on page 246. Uninstalling Windows 3.1 machines Windows 3.1 machines are uninstalled in the same way as all other anti-virus domain members: Either drag the machine out of the anti-virus domain into the network view, or right-click the machine and choose Remove.
  • Page 202: Deleting Anti-Virus Domains

    Configuring Complex Domains You are not allowed to delete the record of a machine that is still in an anti-virus domain. This ensures consistency between the Name Provider’s database and the Management Console’s record of the anti-virus domain members. Deleting anti-virus domains Follow these steps to delete an anti-virus domain: 1.
  • Page 203: Renaming Anti-Virus Domains

    Configuring Complex Domains Renaming anti-virus domains Follow these steps to rename an anti-virus domain: 1. Right-click the anti-virus domain name. 2. Choose Rename Domain. The Rename Anti-Virus Domain dialog box appears (Figure 7-6). Figure 7-6. Rename Anti-Virus Domain dialog box 3.
  • Page 204: Adding Hidden Machines

    Configuring Complex Domains Adding hidden machines The Microsoft browser maintains a list of machines on a Microsoft network. This list is stored on a machine that is selected as the master browser. To reduce the amount of network traffic that this creates, the browser is not often updated.
  • Page 205 Configuring Complex Domains 2. Enter the machine name. 3. Select the operating system (or platform) it uses from the list. 4. Click Check Access to determine whether you have sufficient rights to manage this machine. 5. Click Login to access the machine if your current administrative account does not have sufficient rights to manage the machine.
  • Page 206: Adding Multiple Hidden Machines

    Configuring Complex Domains Adding multiple hidden machines The method described in “Adding hidden machines” on page 204 is suitable for adding a few hidden machines. If your site has a large number of hidden machines, this method becomes time-consuming. Some sites, for example, disable the Microsoft browser to reduce network traffic, which in effect makes all the machines hidden.
  • Page 207: Formatting Imported Browse Lists

    Configuring Complex Domains • Invalid platform type. For valid platform types, see Table 7-1, “Valid platform types,” on page 208. Correct the file with a text editor and try again. Then, in the network view, right-click the filename, and choose Refresh to re-read it. The network view now shows the hidden machines in the browse list.
  • Page 208 Configuring Complex Domains Simple machine entry, no domain (Type 1) Syntax <Machine Name> [,<Platform Type>] [,<Machine Comment>] is the Microsoft Computer name, and is not case-sensitive. It < Machine Name > has a maximum of 15 characters. is optional, and is one of the following: <...
  • Page 209 Configuring Complex Domains NOTE: If your machines are identified only by codes or numbers, include a machine comment to help you identify the machine more easily. For example: ; Site 1A \A10231,95,Admin1 \A10232,95,Admin2 \A10296,NT,Reception \A10297,NT,Mr. Smith Simple machine entry, with domain name (Type 2) Syntax <Domain Name>\<Machine Name>...
  • Page 210: Importing Browse Lists

    Configuring Complex Domains Importing browse lists After you have prepared the imported browse list, you must add its details to the network view in the Management Console. Follow these steps to include the imported browser list in the network: 1. In the Management Console’s network view, right-click Entire Network, and choose Import Browse List.
  • Page 211: Viewing Machine Properties

    Configuring Complex Domains Follow these steps to rename the displayed browse list: 1. In the Management Console’s network view, right-click the name of the import list, and choose Rename Browse List. 2. Enter the new name, and then click OK to confirm. The new name replaces the original in the network view.
  • Page 212: Organizing Machines In An Anti-Virus Domain

    Configuring Complex Domains Organizing machines in an anti-virus domain When you first create an anti-virus domain, you can place a large number of machines within a single domain. All machines except the Management Server can be located in a single Members group; however, having a large number of machines within one group can make management difficult.
  • Page 213: Chapter 8. Using Mirror And Linked Repositories

    Using Mirror and Linked Repositories “Running the Management Console (initial use)” on page 36, you created the master repository (“the Repository”). A large installation might need several repositories. This chapter explains mirror repositories and linked repositories. Each time you receive a new version of the anti-virus software, you can add the software to the Repository and select the newly installed version as the current version of anti-virus components.
  • Page 214 Using Mirror and Linked Repositories Figure 8-1. Two anti-virus domains with a mirror repository You can set up a mirror repository on either a Windows NT server or a NetWare server. The procedure is different for each type of operating system. NOTE: You can mark a mirror as externally updated.
  • Page 215: Creating Windows Nt Mirrors

    Using Mirror and Linked Repositories Creating Windows NT mirrors Follow these steps to set up a mirror repository on a Windows NT server: If you install a mirror repository on a Windows NT server, the necessary directories and shares are set up automatically as a part of the installation process.
  • Page 216 Using Mirror and Linked Repositories The Mirrors page appears (Figure 8-3). Figure 8-3. Repository dialog box (Mirrors page) 3. Right-click the machine shown as the master repository, and choose Add Mirror. The Repository Setup dialog box appears (Figure 8-4). Figure 8-4. Repository Setup dialog box Management Edition...
  • Page 217 Using Mirror and Linked Repositories 4. Select the Create directories and shares option. Do not select Adopt existing shares for mirror repositories located on Windows NT machines. 5. Click the browse (...) button for the Machine box, and select the machine to host the mirror repository.
  • Page 218 Using Mirror and Linked Repositories You are prompted to confirm the creation of the mirror repository. Next, the Assign User Rights dialog box appears (Figure 8-6). Figure 8-6. Assign User Rights dialog box If you are setting up a mirror repository on a machine that is in a different domain, you must assign access rights to the Repository shares to allow administration via the Management Console.
  • Page 219: Creating Netware Mirrors

    Using Mirror and Linked Repositories NOTE: If you exit the Repository without components being fully updated or installed, the Incomplete Components and Mirrors dialog box appears, showing a list of the incomplete components or mirror repositories. This can happen if a WAN connection is dropped or an installation is interrupted.
  • Page 220 Using Mirror and Linked Repositories 4. Create a user ID with full access rights to \REPO for the administrator to add new software to the mirror repository. 5. The \UPGRADES directory is used during batch installations and upgrades. Grant full access rights to this directory for the shared ID used by clients.
  • Page 221: Assigning Different Repositories

    Using Mirror and Linked Repositories Alternatively, you can specify the details manually. You must specify a UNC path, for example: \\MACHINE\SYS\UPGRADES. 15. In the Repository Setup dialog box, click OK. You are prompted by the Query Machine Type dialog box to select the type of operating system the target machine uses (Figure 8-5 on page 217).
  • Page 222: Configuring Mirror Repositories

    Using Mirror and Linked Repositories Configuring mirror repositories You can configure mirror repositories that reside on Windows NT or NetWare machines. • Windows NT machines let you enter a description of the mirror repository. “Configuring Windows NT mirrors” next. • NetWare machines let you enter a description and configure user names and passwords for mirror-repository access via client machines and the administrator’s machine.
  • Page 223: Configuring Netware Mirrors

    Using Mirror and Linked Repositories The Repository Configuration dialog box appears (Figure 8-7). Figure 8-7. Repository Configuration dialog box 4. Type a description of the mirror repository in the Description box. 5. Click OK. Configuring NetWare mirrors The procedure for configuring a mirror repository is slightly different for NetWare 3.x and NetWare 4.x.
  • Page 224 Using Mirror and Linked Repositories NOTE: Depending on which machines you have configured to use the NetWare-based mirror repository, the client login information may be used by Windows-based clients, other NetWare servers, or both during their upgrade. Windows 3.x clients will automatically login to the NetWare server that holds the repository they have been configured to use, if they do not already have a connection to it.
  • Page 225 Using Mirror and Linked Repositories The Repository dialog box appears, with the Products page showing (Figure 8-2 on page 215). 6. Click the Mirrors tab. The Mirrors page appears (Figure 8-3 on page 216). 7. Right-click the name of the mirror repository you want to configure, and choose Configure Mirror.
  • Page 226 Using Mirror and Linked Repositories You can use the Down Arrow button to copy the data from the Administrator/Supervisor Login Information section to the Client Login information section, and use the Up Arrow button for the opposite effect. Use the double-headed arrow to swap entries between the two sections.
  • Page 227: Manually Logging In To The Server

    Using Mirror and Linked Repositories You can use the Down Arrow button to copy the data from the Administrator/Supervisor Login Information section to the Client Login information section, and use the Up Arrow button for the opposite effect. Use the double-headed arrow to swap entries between the two sections.
  • Page 228 Using Mirror and Linked Repositories The Login dialog box appears (Figure 8-8). Figure 8-8. Login dialog box 4. In the Connect As box, type a client user ID that will give you access to the mirror repository. 5. In the Password box, type a client password that will give you access to the mirror repository when used in conjunction with that user ID.
  • Page 229: Promoting Mirror Repositories

    Using Mirror and Linked Repositories Promoting mirror repositories If the machine holding the master repository is unavailable, for example the machine has suffered a disk crash, you can promote a mirror repository to the master repository. Follow these steps to promote a mirror repository to a master repository: 1.
  • Page 230 Using Mirror and Linked Repositories NOTE: To update Windows 95 and Windows 98 machines from a mirror repository on a Windows NT machine, you must have the Client for Microsoft Networks installed. By default, the Management Console gives the built-in group EVERYONE read access to REPO$ and full access to the MEUPGD$ share.
  • Page 231 Using Mirror and Linked Repositories This table identifies scenarios of successful and failed updates for Windows 95 and Windows 98 machines that do not log on to a Windows NT domain: Guest User logged Credentials entered in Successful account Management Console? update? enabled? •...
  • Page 232 Using Mirror and Linked Repositories • If the Windows 95 or Windows 98 machine uses a mirror that is in a different Windows NT domain, you must do one of the following: a. Enable the Guest account on the mirror server. However, keep in mind that enabling the Guest account has its own security issues.
  • Page 233 Using Mirror and Linked Repositories • "Credentials entered in Management Console" refers to whether the user domain, user ID, and password for the mirror repository have been entered in the Management Console’s Configure Mirror dialog box. • “Repository in same or trusted domain” refers to the mirror repository being either in the same domain as or a domain that is trusted by the one to which the Windows 95 or Windows 98 machine logs on.
  • Page 234: Configuring Access To Netware Mirrors

    Using Mirror and Linked Repositories You can find a copy of this file (MEUPRQ32.EXE) in a subdirectory called MEUPREQ\32 in the installation directory for the Management Console. This file is only about 80k in size. Doing this will cause the Management Agent on the workstation to request an update from the server when the users logs on.
  • Page 235: Reducing Wan Traffic

    Using Mirror and Linked Repositories Configuring access to directories After the user IDs have been created for a NetWare-based repository, access rights must also be granted to the relevant directories, as shown in the following table: NetWare user/ Directory Access rights user group ID Repository Client...
  • Page 236 Using Mirror and Linked Repositories 4. Right-click the name of the mirror repository, and choose Configure Mirror. The Repository Configuration dialog box appears (Figure 8-7 on page 223). 5. Select the Console’s connection to this resource is slow checkbox. This prevents the Management Console from automatically checking the status of the mirror repository when you select the Mirrors tab.
  • Page 237: Using Linked Repositories

    Using Mirror and Linked Repositories Protocol in use Port to filter 0x8589 (hex), 34185 decimal. TCP/IP 0x1254 (hex), 4692 decimal. È IMPORTANT: If the mirror repository is at the end of a slow WAN link, machines in that network must use Pull Off Install or Batch Install (not Push On Install).
  • Page 238: Linking Repositories

    Using Mirror and Linked Repositories Repository A is a master repository or a mirror repository. It is the parent of repositories B, C, and D. These three repositories are themselves master repositories of separate domains. Repositories A and B are linked repositories, as are the repositories A and C, and the repositories A and D.
  • Page 239: Listing The Repository Contents

    Using Mirror and Linked Repositories You must get the server address and the sharename (if it is hidden) from the administrator of the parent repository. If the share is hidden (as set in Step 6 on page 217), you will not be able to see it, so type the name in the UNC Path box.
  • Page 240 Using Mirror and Linked Repositories Follow these steps to filter the information in the report: 1. Right-click the report area, point to Filter, and then click Filter On. The Repository Report Filter dialog box appears, with the Platform/Language/Version page showing (Figure 8-9).
  • Page 241: Formatting The Repository Report

    Using Mirror and Linked Repositories 5. Click OK. A filtered report appears. You can right-click in the report area to access additional functions such as print the report or save it as an .RTF file, which can be edited with Microsoft Word.
  • Page 242: Reporting On The Installation

    Using Mirror and Linked Repositories 3. Click OK. NOTE: If you print the file to a black-and-white printer, the color effect is lost; some colors print as grey. Try changing the font instead. Also, consider substituting green with blue to aid readability for users with color blindness.
  • Page 243: Formatting The Installation Log Report

    Using Mirror and Linked Repositories Follow these steps to determine what anti-virus software is installed on any group of machines: 1. Click Anti-Virus Domain(s), an anti-virus domain, or a Members group. 2. Click the Properties tab at the bottom of the right pane. The Properties page appears, showing a report of all selected machines.
  • Page 244 Using Mirror and Linked Repositories Management Edition...
  • Page 245: Chapter 9. Advanced Configuration And Troubleshooting

    Advanced Configuration and Troubleshooting Here you’ll find sections to help you resolve some issues that you might encounter when using the Management Edition program. Topics are grouped into these general categories: • “Managing domains” on this page, • “Viewing items in the console” on page 253, •...
  • Page 246: Changing The Management Server

    Advanced Configuration and Troubleshooting The Mirrors page appears. 3. Right-click on the machine shown as the master repository, and choose Add Mirror. The Repository Setup dialog box appears. 4. Click the Machine browse button (...), and select the machine in the non-trusted domain that you want to manage.
  • Page 247 Advanced Configuration and Troubleshooting Follow these steps to change the Management Server: 1. Right-click another machine, and choose Promote. Click Yes to confirm when prompted. You may only promote a Windows NT server as a Management Server. 2. To demote an existing Management Server, right-click the machine, and choose Demote.
  • Page 248: Running Management Console From Another Workstation

    Advanced Configuration and Troubleshooting Running Management Console from another workstation To run the Management Console from another workstation, you need to enable remote access by sharing the directory in which it resides. Follow these steps to enable access to the Management Console: 1.
  • Page 249: Securing Anti-Virus Domains

    Advanced Configuration and Troubleshooting Securing anti-virus domains If the responsibility for managing multiple anti-virus domains is split between different people, you may want to password-protect one or more domains. Once protected, alterations to a domain via the Management Console are not possible without first entering the domain password.
  • Page 250 Advanced Configuration and Troubleshooting The New Anti-Virus Domain dialog box appears (Figure 9-2). Figure 9-2. New Anti-Virus Domain dialog box 2. Enter the domain name, and then click Set Password. The Set Anti-Virus Domain Password dialog box appears (Figure 9-3). Figure 9-3.
  • Page 251 Advanced Configuration and Troubleshooting Unlocking a password-protected domain Anyone attempting to alter a component, machine, or configuration file within a password-protected domain is prompted to enter a password by the Authentication dialog box (Figure 9-4). Figure 9-4. Authentication dialog box Enter the password, and click OK.
  • Page 252: Collecting Diagnostic Information

    Advanced Configuration and Troubleshooting Collecting diagnostic information If you have difficulty using the Management Edition program, you can contact Technical Support or your distributor. They will ask you to provide information about some or all of the machines in your networks. Management Edition uses a wizard to collect this information automatically for you in a single file.
  • Page 253: Viewing Items In The Console

    Advanced Configuration and Troubleshooting Viewing items in the console Discovering machines The Management Console’s network view is only a logical display of the network domain model. It is not necessarily organized according to location. It can display machines in different countries, towns, or buildings. In one anti-virus domain, you can have machines from one or many network domains.
  • Page 254: Viewing Machine Comments

    Advanced Configuration and Troubleshooting Viewing machine comments The Microsoft Server Manager utility supplied with Windows NT Server lets you associate a descriptive comment with a computer account. Some organizations use this comment for identifying the owner of the machine with the asset or inventory number as the computer name, making it difficult to identify machines within the Management Console.
  • Page 255: Expanding And Collapsing The Member Machines View

    Advanced Configuration and Troubleshooting Expanding and collapsing the member machines view You can expand or collapse the Members view in the Management Console anti-virus domain view to show (or hide) the member machines and their individual machine components. To show all member machines and components: 1.
  • Page 256 Advanced Configuration and Troubleshooting The Find Machines ... dialog box appears (Figure 9-5). For example: Figure 9-5. Find Machines dialog box 3. Enter your search text, which can be a full machine name or the initial part of a machine name. The drop-down list includes the last 16 strings you have used.
  • Page 257: Refreshing The Name Provider View

    Advanced Configuration and Troubleshooting The machines that match your search requirements are added to the list. To highlight a machine in the Management Console, either double-click its name in this list, or select the name and click Go To. To start a new search, click New Search. This clears the list and the current search text.
  • Page 258: Installing Components

    Advanced Configuration and Troubleshooting Installing components Diagnosing installation problems When you choose Apply Configuration, the Management Console tries to update the selected machines. You can monitor the Management Console’s progress in a number of ways: Choose one of the following methods to monitor the progress of the installation: •...
  • Page 259: Submitting Batch Updates

    Advanced Configuration and Troubleshooting • Select a component with a cross next to it, and click Details to see more information about the cause of the failure. As you scroll down the list of commands, any commands that failed will be highlighted with a cross. This provides information on corrective actions you may need to take.
  • Page 260 Advanced Configuration and Troubleshooting a. On the Management Server, create a LOCAL SYSTEM DOS window by using the AT command and find the <domain> UPGRADE.CFG file. b. If you can’t see the file, check the rights on the share, check that it is a null session share, and check the rights on an NTFS partition if the share points to one.
  • Page 261: Installing Anti-Virus Components To Different Directories

    By default, the anti-virus components are installed onto member machines on the system drive, as shown in the following table: Anti-virus components Platform default installation directory Windows NT C:\Program Files\McAfee\VirusScan NT or C:\Program Files\McAfee\NetShield Windows 95 C:\Program Files\Network Associates\McAfee VirusScan Windows 98 Windows 3.x...
  • Page 262 Advanced Configuration and Troubleshooting Follow these steps to change the installation directory: 1. In the anti-virus domain view, right-click Anti-virus Domain(s), and choose Add/Remove Components, Right-click an anti-virus domain, member group or member machine, point to Manage Components, and then choose Add/Remove Components.
  • Page 263: Customizing Installation Options

    Advanced Configuration and Troubleshooting Follow these steps to restore the default installation directory: 1. In the anti-virus domain view, right-click Anti-virus Domain(s), and choose Add/Remove Components. Right-click an anti-virus domain, member group, or member machine, point to Manage Components, and then choose Add/Remove Components.
  • Page 264: Removing The Management Edition Program

    Advanced Configuration and Troubleshooting Removing the Management Edition program Follow these steps to remove the Management Edition program: 1. In the anti-virus domain view, expand all anti-virus domains to show all configured machines. 2. Drag machines from the anti-virus domain view to the network view. Alternatively, right-click the Members group, and choose Remove All.
  • Page 265 Advanced Configuration and Troubleshooting 8. Shut down and restart all machines that have a reboot icon beside their name in the Management Console. A green check mark icon appears next to the machine when the uninstall is successful. If the uninstall does not complete successfully, a red cross icon appears next to the machine.
  • Page 266: Changing Machine Configurations

    Advanced Configuration and Troubleshooting Anti-virus components default installation Operating system directory Windows NT 3.51 or C:\Program Files\McAfee\VirusScan NT or Windows NT 4.0 C:\Program Files\McAfee\NetShield Windows 95 and C:\Program Files\Network Associates\ Windows 98 McAfee VirusScan Windows 3.x C:\NETA\VIRUSCAN 12. Unless you intend to re-install the Management Edition program at a later date, delete the folder containing the Repository on the Management Server.
  • Page 267 Advanced Configuration and Troubleshooting Restricting machine updates Some right-click menu commands are duplicated at different locations within the anti-virus domain view. This hierarchy lets you limit the number of machines that are affected by your actions, as shown in the following table: Icon Right-click this item Affected machines...
  • Page 268: Making Non-Standard Machines Standard

    Advanced Configuration and Troubleshooting Configuring scan options To set all the options provided by VShield (on-access scanner) and VirusScan (on-demand scanner), choose the Component Configuration right-click command at any of four different locations (shown in the table under “Restricting machine updates” on page 267) within the anti-virus domain view.
  • Page 269: Recovering The Name Provider Database

    Advanced Configuration and Troubleshooting To recover a large number of machines, use the right-click menu option Discover at the Microsoft network domain or Microsoft Windows Network level. Recovering the Name Provider database If the database has been accidentally deleted or corrupted, or the machine has suffered a hardware failure preventing the recovery of the up-to-date database, it is possible to regenerate the database from the information stored on each Windows 3.1 machine.
  • Page 270 Advanced Configuration and Troubleshooting NOTE: Both options only refer to the machines in, or destined for, the domain that has lost its database—not to all domains. The process is easier if you configure a larger number of domains with fewer member machines.
  • Page 271: Appendix A. Using The Autoinst Utility

    Using the AUTOINST Utility This section describes the AUTOINST utility in detail. You can use the AUTOINST utility within a login script to install the Management Agent and to run the Update Requester on member machines. NOTE: The option to update software using a NetWare login script and the AUTOINST.EXE utility is only applicable if you’re performing software upgrades (not first-time installs).
  • Page 272 Using the AUTOINST Utility AUTOINST.EXE also adds the following section and key to WIN.INI: [NetworkAssociates] NetworkAssociatesInstalled=Yes These lines prevent AUTOINST from adding the installer’s executable path to the RUN= line more than once. If on a subsequent server login, AUTOINST runs, it will not alter the RUN= line if it finds the NetworkAssociatesInstalled key.
  • Page 273: Appendix B. Using Mcscript To Update Your Script Files

    Using MCScript to Update Your Script Files Determining when to edit your MCSCRIPT.INI files Network Associates strongly recommends that you do not alter your MCSCRIPT.INI files unless you have been advised to do so by PrimeSupport, Global Professional Services, or your company’s software engineers. Compatibility between versions of customized scripts is not guaranteed.
  • Page 274 Using MCScript to Update Your Script Files [ParentComponents] Component0=ACMEScanConsole ACMEScanConsoleStartVersion=1.0 ACMEScanConsoleEndVersion=5.0 [ExcludedComponents] Component0=ExcludeMe [ExtensionDLLs] DLL0=FileName.DLL Name0=DisplayName [Inclusions] Include0=File0 Include1=File1 [Commands] ServerOnlyFlag=FALSE WorkStationOnly=FALSE HasAVScanner=TRUE Unique=Yes Macro0=CLASSID={5D26E881-5015-11cf-8406-00C0A808723C} Macro1==REGKEY="SOFTWARE\ACME\Anti-Virus" PreInst0=Start_Of_Script: PreInst10=COPY !INSTALLPATH!\FILE.1 !INSTALLDIR!\FILE.1 PostRem0=Start_Of_Uninstall: PostRem10=DELETE !INSTALLDIR!\FILE.1 NOTE: Prefer to have an expert work with you to develop scripts for your Management Edition software? See “Getting support for customized scripts”...
  • Page 275: Specifying [Id] Keys

    Using MCScript to Update Your Script Files Specifying [ID] keys The [ID] section contains information that identifies the product. Descriptions of its various keys follow. Version The Version key specifies the version of the product. A valid version string is defined: •...
  • Page 276 Using MCScript to Update Your Script Files Description The Description key contains a brief description of the product (e.g., "Network Associates VirusScan program for Windows NT"). Language The Language key identifies the language of the product; it can either be in plain English or a TLA (Three-Letter Acronym).
  • Page 277: Specifying [Inclusions] Keys

    Using MCScript to Update Your Script Files IconFile The IconFile key specifies the icon to use for the product in the console. It specifies the file (either an *.EXE, *.DLL or *.ICO file) containing the icon. If the IconFile and ImageNo keys are not specified, the product will get the default hammer and spanner icon.
  • Page 278: Specifying [Parentcomponents] Keys

    Using MCScript to Update Your Script Files Specifying [ParentComponents] keys The [ParentComponents] section lists other products of which at least one must be on a machine for the product to be installed. For example, the Dat Update product lists the NetShield and VirusScan programs here. This section is not required.
  • Page 279: Specifying [Commands] Keys

    Using MCScript to Update Your Script Files Specifying [Commands] keys The [Commands] section contains the install and uninstall scripts for the product. You can choose from among four basic sets of keys: • General non-indexed keys (ScriptVersion, ServerOnlyFlag, WorkstationOnly, HasAvScanner, and Unique). These keys define additional product attributes that are important to the install/uninstall.
  • Page 280 Using MCScript to Update Your Script Files Unique This flag is for internal use only. It must always be set to Yes. Unique=Yes Indexed macro assignment keys These keys are of the form Macro <n>=<MACRO_ASSIGNMENT>, where <MACRO_ASSIGNMENT> specifies <MACRO_NAME> = <MACRO_VALUE> <MACRO_NAME>: This variable specifies a macro name consisting of alphanumeric characters.
  • Page 281: Editing Mcscript Files For Versions Or Languages

    Using MCScript to Update Your Script Files Indexed uninstallation script keys These keys are of the form PostRem <n>=<SCRIPT_COMMAND> . These keys are indexed (repeated in numeric sequence) as PostRem0, PostRem1, PostRem2, and so forth. The script command can contain macro substitutions enclosed between (!) exclamation marks.
  • Page 282: Understanding Mcscript Commands

    Using MCScript to Update Your Script Files Understanding MCScript commands This section contains details of the script commands that can be used in the [COMMANDS] section. The command set is the same for both the install and uninstall scripts. The following tables outline commands for the file system, Program Manager, private profiles, registry, service control, flow control statements, and NetWare file handling.
  • Page 283 Using MCScript to Update Your Script Files Min # Command name Usage, examples, and comments params MKDIR MKDIR <DIR_PATH> COPYDIR COPYDIR [/IFNEW] [/REBOOT] <SRC> <DST> [/SUB] /IFNEW, /REBOOT: See COPY command. /SUB: Copies files in sub-directories. MOVEDIR MOVEDIR [/IFNEW] [/REBOOT] [/SUB] <SRC>...
  • Page 284: Program Manager Commands

    Using MCScript to Update Your Script Files Program Manager commands NOTE: [..] Indicates optional parameters and switches. Min # Command name Usage, examples, and comments params PMEXEC PMEXEC <CMD_STR> Executes a Program Manager command. PMCREATEGROUP <GROUP_NAME> PMCREATEGROUP [<GROUP_PATH>] Example: PMCREATEGROUP !PMGroup! "!INSTALLDIR!"...
  • Page 285 Using MCScript to Update Your Script Files Min # Command name Usage, examples, and comments params PMGROUPEXISTS PMGROUPEXISTS <GROUP_NAME> Tests whether group exists. Sets the function result to TRUE/FALSE. PMITEMEXISTS <GROUP_NAME> PMITEMEXISTS <ITEM_NAME> Tests whether item exists in a group. Sets the function result to TRUE/FALSE.
  • Page 286: Private Profile Commands

    Using MCScript to Update Your Script Files Private profile commands NOTE: [..] Indicates optional parameters and switches. Min # Command name Usage, examples, and comments params WRITEPRIVATE WRITEPRIVATE [/NEW] <FILE_NAME> <SECTION> <KEY> <VALUE> Writes a profile string using direct file system call (see ADDPRIVATE).
  • Page 287 Using MCScript to Update Your Script Files Min # Command name Usage, examples, and comments params PRIVATEEXISTS PRIVATEEXISTS <FILE_NAME> <SECTION> <KEY> [<VALUE_STR>] Tests whether the key exists or whether it exists with the optional <VALUE_STR>. Sets the function result to TRUE/FALSE. <FILE_NAME>...
  • Page 288: Miscellaneous Commands

    Using MCScript to Update Your Script Files Miscellaneous commands NOTE: [..] Indicates optional parameters and switches. Min # Command name Usage, examples, and comments params STOPTASKHANDLER Stops the Management Agent. If you don't do this before an upgrade/removal, some of the files will be locked open.
  • Page 289 Using MCScript to Update Your Script Files Min # Command name Usage, examples, and comments params WRITECFG Windows: <SECTION> <KEY> WRITECFG <VALUE> NetWare: <FILE> <SECTION> <KEY> WRITECFG <VALUE> Writes a value to MEUP.CFG on Windows or a defined config file on NetWare. NetWare example: WRITECFG SYS:SYSTEM\NTME\THDEFS.CFG...
  • Page 290 Using MCScript to Update Your Script Files Min # Command name Usage, examples, and comments params EQUALSTRING EQUALSTRING <STR1> <STR2> Case-sensitive comparison of the strings. Sets the function result to TRUE/FALSE. Example: EQUALSTRING !CUR_GINA! "AFILE.DLL" IF EQUALSTRING REGSETVAL LOCAL !NEWGINA! GinaDLL SZ !OLDGINAVAR! CREATEPROCESS <COMMAND>...
  • Page 291 Using MCScript to Update Your Script Files Min # Command name Usage, examples, and comments params KILLPROCESS KILLPROCESS <PROCESS_NAME> Example: KILLPROCESS AFILE.EXE CREATESHARE <SHARE_PATH> CREATESHARE <SHARE_NAME> <FILE_PATH> LOADLIBRARYCHECK LOADLIBRARYCHECK <FAIL_MACRO_NAME> <FAIL_MACRO_VALUE> Checks whether the specified library can be loaded. If not, the specified macro is set to the specified value.
  • Page 292 Using MCScript to Update Your Script Files Min # Command name Usage, examples, and comments params GETOSBUILD GETOSBUILD <OSBUILD_MACRO> Note: Win 32 only. Returns the operating system build number. GETFILECHECKSUM GETFILECHECKSUM <FILE> <DEFAULT_CHECKSUM_VALUE> <CHECKSUM_MACRO> Generates a 32-bit CRC for the specified file.
  • Page 293: Registry Commands

    Using MCScript to Update Your Script Files Registry commands NOTE: [..] Indicates optional parameters and switches. Min # Command name Usage, examples, and comments params REGSETVAL REGSETVAL <BASE_KEY> <LOCAL_KEY> <VAL_NAME> <VAL_TYPE> <VALUES> Sets a registry value. <VALUES>: Single value or list if MULTI. <VAL_TYPE>: ‘MULTI’...
  • Page 294 Using MCScript to Update Your Script Files Min # Command name Usage, examples, and comments params REGGETVAL REGGETVAL <BASE_KEY> <LOCAL_KEY> <VAL_NAME> <VAL_TYPE> <DEFAULT> <MACRO> Gets registry value and stores it in <MACRO>. Example: REGGETVAL LOCAL !SCAN_SETTINGS! OldGina SZ MSGINA.DLL OLDGINAVAR APPLYREGFILE <REGEDIT_V4_FILE>...
  • Page 295: Service Control Commands

    Using MCScript to Update Your Script Files Service control commands NOTE: [..] Indicates optional parameters and switches. Min # Command name Usage, examples, and comments params STARTSERVICE STARTSERVICE <SERVICE_NAME> [<TIMEOUT_SECS>] /DEPENDENT /DEPENDENT: Starts dependent services. <TIMEOUT_SECS>: Time to wait for service to start.
  • Page 296: Flow Control Statements

    Using MCScript to Update Your Script Files Flow control statements NOTE: [..] Indicates optional parameters and switches. Command Min # Usage, examples, and comments name params GOTO GOTO <GOTO_LABEL> Example: GOTO EndOfScript ; Script commands…. EndOfScript: GOTODEFER 1 <GOTO_LABEL> GOTODEFER Commands between the command and the label are deferred until a user logs into the machine (Windows NT only).
  • Page 297: Netware File Manipulation Commands

    Using MCScript to Update Your Script Files NetWare file manipulation commands NOTE: [..] Indicates optional parameters and switches. Min # Command name Usage, examples, and comments params WRITECONFIGKEY WRITECONFIGKEY [/NEW] <FILE> <SECTION> <KEY> <VALUE> CLEARCONFIGKEY [/ALL] <FILE> CLEARCONFIGKEY <SECTION> <KEY> [<VALUE>] ADDTOCONFIGKEY ADDTOCONFIGKEY [/ALL] <FILE>...
  • Page 298: Netware Operating System Commands

    Using MCScript to Update Your Script Files NetWare operating system commands NOTE: [..] Indicates optional parameters and switches. Min # Command name Usage, examples, and comments params LOADNLM LOADNLM <NLM_NAME> UNLOADNLM UNLOADNLM <NLM_NAME> Example: UNLOADNLM NETSHLD.NLM ISNLMLOADED <NLM_NAME> ISNLMLOADED WAITFORUNLOAD <NLM_NAME>...
  • Page 299: Understanding Management Edition Macros

    Using MCScript to Update Your Script Files Understanding Management Edition macros The following tables list directory, file transfer, and miscellaneous macro variables that will automatically be expanded to their actual values while an install/update/uninstall is in progress. Directory macros Macro name Description !SYSDIR! The Windows system directory (e.g.,...
  • Page 300: Miscellaneous Macros

    Using MCScript to Update Your Script Files Miscellaneous macros Macro name Description !PLATFORM! The platform the script is running on. Can be “WNT,” “W95,” “W3X,” or “NW.” !MANSERVERNAME! Name of the Management Server for this machine. !MACHINENAME! Name of the machine that the script is being run on. !LANG! Standard TLA (Three-Letter Acronym) for the language of the component/product.
  • Page 301: Understanding Autorepo Commands

    Using MCScript to Update Your Script Files Understanding AutoRepo commands Here are the commands that can be used in the AutoRepo scriptlet: # of Command name Usage Description params COPY <SRC> <DEST> Copies <SRC> to <DEST> . COPY MOVE <SRC> <DEST> Moves <SRC> to <DEST> . MOVE DELETE DELETE...
  • Page 302: Getting Support For Customized Scripts

    Using MCScript to Update Your Script Files Getting support for customized scripts Prefer to have an expert work with you to develop scripts for your Management Edition software? Consult a Network Associates software engineer. To arrange personal assistance with your custom scripts by a Global Professional Services or PrimeSupport engineer: •...
  • Page 303: Appendix C. Network Associates Support Services

    Network Associates Support Services Adding value to your Network Associates product Choosing Network Associates anti-virus, network management, and security software helps to ensure that the critical technology you rely on functions smoothly and effectively. Taking advantage of a Network Associates support plan extends the protection you get from your software by giving you access to the expertise you need to install, monitor, maintain and upgrade your system with the latest Network Associates technology.
  • Page 304 Network Associates Support Services If you purchased a perpetual license for your Network Associates product, you can purchase a PrimeSupport KnowledgeCenter plan for an annual fee. To receive your KnowledgeCenter password or to register your PrimeSupport agreement with Network Associates, visit: http://www.nai.com/asp_set/support/introduction/default.asp Your completed form will go to the Network Associates Customer Care Center.
  • Page 305 Network Associates Support Services The PrimeSupport Connect 24-By-7 plan The PrimeSupport Connect 24-By-7 plan gives you round-the-clock telephone access to essential product assistance from experienced Network Associates technical support staff members. You can purchase PrimeSupport Connect 24-By-7 on an annual basis when you purchase a Network Associates product, either with a subscription license or a one-year license.
  • Page 306: Ordering A Corporate Primesupport Plan

    Network Associates Support Services By calling in advance, your PrimeSupport Enterprise representative can help to prevent problems before they occur. If, however, an emergency arises, the PrimeSupport Enterprise plan gives you a committed response time that assures you that help is on the way. You may purchase the PrimeSupport Enterprise plan on an annual basis when you purchase a Network Associates product, either with a subscription license or a one-year license.
  • Page 307 Network Associates Support Services Table C-1. Corporate PrimeSupport Plans at a Glance Plan Knowledge Feature Center Connect Connect 24-By-7 Enterprise Technical support via website Software updates Technical — Monday–Friday Monday–Friday, after Monday–Friday, after support via hours emergency hours emergency telephone access access North America:...
  • Page 308: Primesupport Options For Home Users

    – Visit the Network Associates CompuServe forum at GO NAI – Visit Network Associates on America Online: keyword MCAFEE • Free access to the PrimeSupport KnowledgeBase: online access to technical solutions from a searchable knowledge base, electronic incident submission, and technical documents such as user’s guides, FAQs, and release notes.
  • Page 309: How To Reach International Home User Support

    • Quarterly Disk/CD Plan. This plan gives you automatic quarterly delivery of upgrade disks or CDs if you cannot obtain product upgrades online. This service is available for McAfee VirusScan and NetShield software only. How to reach international home user support The following table lists telephone numbers for technical support in several international locations.
  • Page 310: Ordering A Primesupport Plan For Home Users

    Network Associates Support Services Country or Region Phone Number* Bulletin Board System Germany +49 (0)69 21901 300 +49 89 894 28 999 France +33 (0)1 4993 9002 +33 (0)1 4522 7601 United Kingdom +44 (0)171 5126099 +44 1344-306890 Italy +31 (0)55 538 4228 +31 (0)20 586 6128 Netherlands +31 (0)55 538 4228...
  • Page 311: Network Associates Consulting And Training

    Network Associates Support Services Network Associates consulting and training The Network Associates Total Service Solutions program provides you with expert consulting and comprehensive education that can help you maximize the security and performance of your network investments. The Total Service Solutions program includes the Network Associates Professional Consulting arm and the Total Education Services program.
  • Page 312: Total Education Services

    Network Associates Support Services Network consulting Network Associates consultants provide expertise in protocol analysis and offer a vendor-independent perspective to recommend unbiased solutions for troubleshooting and optimizing your network. Consultants can also bring their broad understanding of network management best practices and industry relationships to speed problem escalation and resolution through vendor support.
  • Page 313: Glossary

    Glossary Alert Manager One of the anti-virus components, the Alert Manager runs on the Management Server and receives alerts from the Management Agents. There is only one for each anti-virus domain. Using the Management Console, you can define who to alert and how to alert them. anti-virus components The anti-virus components are the on-access and on-demand scanners.
  • Page 314 Glossary linked repository A linked repository is a remote copy of another repository, or database of files for distribution. Updates to this repository (the child) are copied from another repository (the parent). The parent repository can be a master repository or a mirror repository, or even another child repository;...
  • Page 315 Glossary Management Console Running on Windows NT only, the Management Console controls the configuration and installation of anti-virus components on machines in the anti-virus domain. It does not need to run on the Management Server because it does not need to run all the time. You can run the Management Console on a local machine and/or on a server, letting you run it from different machines;...
  • Page 316 Glossary mirror repository A mirror repository is a remote copy of a master repository, or database of files for distribution. If you have two anti-virus domains separated by a WAN link, or one domain spread over multiple sites, copying new anti-virus files to each member machine over the WAN link can be slow and expensive.
  • Page 317 Glossary on-demand scanner The on-demand scanner is one of the anti-virus components. It can scan all files for viruses when scheduled by the Scheduler. A repository is a set of subdirectories that contain all the repository components for distribution around the network. Member machines have read-only access to it.
  • Page 318 Glossary Update Manager One of the Management components, the Update Manager runs on the Management Server and provides one of three methods for updating member machines. It can retry updates to machines that are powered off. You can configure the number of retries and specify the maximum number of machines to simultaneously update, using traffic limitation.
  • Page 319: Index

    Index Alert Manager About button as integrated service access audible alerting granting rights configuring in progress definition Microsoft Domain Administration DMI alerting rights forwarding to a networked to directories computer to repositories logging alerts Windows 95 share-level problems Windows 95 user-level sending a network printer notification Windows 98 share-level...
  • Page 320 Index anti-virus domain anti-virus software selecting components changing versions anti-virus domains choosing See also domains components adding deleting from Repository adding components distributed by the Management Edition adding machines program adding member machines installation adding Windows 3.1 machines licenses adding Windows 95 machines reporting new viruses not detected by to adding Windows 98 machines Network Associates...
  • Page 321 Index batch updates changing completed all domain versions Created, marked as domains default timeout individual domain versions inaccessible mirrors individual machine versions pending language for anti-virus software Pending, marked as Management Server setting timeout period passwords submitting checking Update Manage Repository contents viewing status of virus scan status...
  • Page 322 Index components Create a New Domain button See also anti-virus components creating hiding anti-virus domains installed linked repositories installing to different directories master repository from mirror Management components Members groups properties mirror repositories showing new passwords updates NT trust relationships components, included with Management CUSTOM.REG Edition program...
  • Page 323 Index descriptions, of Management Edition program DOS error levels components drag and drop diagnosing installation problems adding machines diagnostic information extra .DAT files collecting installing anti-virus software reporting machines into domains sending via e-mail member machines directories Repository updates configuring access default for anti-virus components default for Management Console educational services, description of...
  • Page 324 Index Filter command failed updates, purging filtering features, latest in release notes file manipulation commands, MCScript ports file system commands, MCScript Repository reports files WAN routers <domain>UPGRADE.CFG finding AUTOEXEC.NCF machines in large network AUTOINST.EXE machines in the network view CUSTOM.REG flow control statements, MCScript DEMON.EXE font bar...
  • Page 325 Index installation icons "silent" batch update after initial one anti-virus software filter Batch blue circle with "i" customizing the options red stop sign diagnosing problems yellow circle with exclamation directories mark gold coin, spinning monitoring progress green check mark Pull Off grey question mark Push On in toolbar...
  • Page 326 Index languages, changing, and editing machine comments, searching for MCSCRIPT.INI files machines launching a program on alert See also member machines licenses, product or site adding multiple hidden linked repositories adding to anti-virus domains creating automatically add to anti-virus definition domains using changing versions for...
  • Page 327 Index macros Management Edition program AutoRepo anti-virus software supported directory, set by Management Edition components included with program description file transfer, set by Management Edition description of program program components miscellaneous, set by Management features Edition program administrative ease Management Agent automated distribution as integrated service Batch Install update upon login...
  • Page 328 Index managing ID keys non-trusted domains Description rights IconFile Marburg virus ImageNo master browsers InstallDir master repository Language See also repositories Platform definition Product See also mirror repositories SortOrder MCNWSCRI.INI Version MCScript Inclusions keys commands miscellaneous commands Commands keys miscellaneous NetWare commands general non-indexed keys NetWare file manipulation commands...
  • Page 329 Index member machines miscellaneous commands, MCScript See also machines MSAUTO.NCF adding adding or removing components definition N/S, non-standard initial setup NAIAV.NCF installing Management Agent Name Provider moving adding machines via multiple extra .DAT files definition organizing in domains functions preparing partial name relocating recovering the database...
  • Page 330 Index NetWare NetWare program access rights extracting file set from NetShield package AUTOEXEC.NCF network bindery ID login problem configuring mirror access rights peer-to-peer configuring mirror repositories verifying configuration configuring remote servers network access, spinning gold coin CUSTOM.REG Network Associates customizing NetShield install options consulting services from customizing on-access settings...
  • Page 331 Index notification methods via .WAV PASSWORD.PWD via DMI passwords via forwarding to a networked changing computer creating via logging for new domains via network printer PASSWORD.PWD via pager protection for domains via program launch removing via SMTP unlocking domains via SNMP peer networking via standard network message preparing machines with...
  • Page 332 Index private profile commands, MCScript red cross icon Professional Consulting Services refreshing description of program components, included with Name Provider view Management Edition program REGISTER MEMORY command Program Manager commands, registry commands, MCScript MCScript registry key, null session Promote command release notes promoting removing...
  • Page 333 Index repositories see also master repositories saving log see also mirror repositories scan options, configuration adding components scanning on-demand anti-virus components scans assigning scheduling configuring access viewing results disk space Scheduler linking definition promoting mirror functions Repository log of scans adding scheduled updates on-demand scans component properties...
  • Page 334 Index service control commands, MCScript support corporate setup files, updating via the Repository at a glance Setup, using "silent" and "record" KnowledgeCenter modes ordering SETUP.EXE, updating setup files via the PrimeSupport Connect Repository PrimeSupport Connect 24-By-7 SETUP.ISS file, use of PrimeSupport Enterprise SETUP.ISS, updating setup files via the corporate PrimeSupport...
  • Page 335 Index Total Service Solutions target machines contacting TCP/IP tracking changes, setting a warning period technical support training for Network Associates corporate products at a glance scheduling KnowledgeCenter troubleshooting ordering accessing remote machines PrimeSupport Connect adding machine names in Windows PrimeSupport Connect 24-By-7 PrimeSupport Enterprise changing component configuration corporate PrimeSupport...
  • Page 336 Index removing old components from the emergency Repository forcing, of invalid external mirrors removing the Management Edition program installing to member machines restricting machine updates interim running Management Console from pending remote workstation periodic scheduling scans zipped section overview updates and upgrades, website address for securing anti-virus domains obtaining submitting batch updates...
  • Page 337 Index virus scan versions acknowledging status changing all checking status changing all domains formatting reports changing domains hierarchy of icons changing individual domains printing reports changing individual refreshing the display machines rescanning changing, and editing MCSCRIPT.INI saving reports files setting a warning period deleting old status icons using different...
  • Page 338 Index Windows 3.1 adding machine names ZIP files, installing via drag and drop AUTOINST.EXE ZIP files. See periodic .DAT files automating the setup changing Management Server in anti-virus domains login scripts Name Provider NAMEPROV.INI WIN.INI Windows 3.11, login scripts Windows 95 in anti-virus domains login scripts Name Provider...

Table of Contents