_______________________________________________ INSTALLATION REQUIREMENTS To use this release, you must have ePolicy Orchestrator 3.0 installed on the ePolicy Orchestrator server that you intend to update with this release. NOTE: This release does not work with earlier versions of the ePolicy Orchestrator software. INSTALLATION STEPS 1. Create a temporary folder on the hard drive of the ePolicy Orchestrator server. 2. Click here to download . 3. Extract the ZIP file to the temporary folder that you created in Step 1. To add the policy page to the "Repository:" 1. Log on to the desired ePolicy Orchestrator server. 2. In the console tree under "ePolicy Orchestrator" | , right-click "Repository," then select "Configure Repository." The "Software Repository Configuration Wizard" appears. 3. Select "Add new software to be managed," then click "Next." The "Select a Software Package" dialog box appears. 4. Select the policy page (.NAP) file from the temporary folder you created, then click "Open." To check the product package into the master repository: 1. Log on to the desired ePolicy Orchestrator server using a global administrator user account. 2. In the console tree under "ePolicy Orchestrator" | , select "Repository." 3. In the details pane under "AutoUpdate Tasks," click "Check in package." The "Check in package" wizard appears. 4. Click "Next" to open the package type dialog box. 5. Select "Products or updates," then click "Next." The catalog file dialog box appears. 6. Type the path of the package catalog (PKGCATALOG.Z) file, or click "Browse" to select this file from the temporary folder you created, then click "Next." The summary dialog box appears. 7. Click "Finish" to check in the package. 8. Click "Close" after the package has been checked in. TESTING YOUR INSTALLATION To verify that the policy page was installed: 1. Log on to the desired ePolicy Orchestrator server. 2. In the console tree under "ePolicy Orchestrator," select "Directory." The "Policies," "Properties," and "Tasks" tabs appear in the upper details pane. 3. Click the "Policies" tab. 4. Verify that "McAfee AVERT Stinger " appears in the upper details pane. To verify that the package was checked into the master repository: 1. Log on to the desired ePolicy Orchestrator server. 2. In the console tree under "ePolicy Orchestrator" | , select "Repository." 3. In the details pane under "AutoUpdate Tasks," click "Manage packages." 4. Verify that the correct version of McAfee AVERT Stinger is listed on the "Packages" page. REPLICATING PACKAGES TO DISTRIBUTED REPOSITORIES To replicate packages to global and SuperAgent distributed repositories: 1. Log on to the desired ePolicy Orchestrator server using a global administrator user account. 2. In the console tree under "ePolicy Orchestrator" | , select "Repository." 3. In the details pane under "AutoUpdate Tasks," click "Replicate now." The "Replicate Now" wizard appears. 4. Click "Next" to open the distributed repositories dialog box. 5. Click "Select All" to select all global and SuperAgent distributed repositories, then click "Next." The replication type dialog box appears. 6. Select "Incremental replication," then click "Finish" to run the task. 7. Click "Close" after the task has completed. NOTE: Since local distributed repositories can only be accessed from client computers, replication tasks do not copy packages from the master repository to local distributed repositories; you must manually update local distributed repositories with the desired packages. To verify that the package has been replicated to global or SuperAgent distributed repositories: 1. In the console tree under "ePolicy Orchestrator" | | "Repository" | "Software Repositories" | "Distributed," select . 2. Verify that the correct version of McAfee AVERT Stinger is listed on the "Packages" page. _______________________________________________ DEPLOYMENT AND ON-DEMAND SCAN DEPLOYING AVERT STINGER TO CLIENT COMPUTERS You can use ePolicy Orchestrator to deploy AVERT Stinger to any computer with the ePolicy Orchestrator 3.0 or 3.1 agent installed on it. AVERT Stinger is installed to C:\PROGRAM FILES\NETWORK ASSOCIATES\MCAFEEAVERTSTINGER. 1. Log on to the desired ePolicy Orchestrator server. 2. In the console tree under "ePolicy Orchestrator" | , right-click "Directory," , , or . The "Policies," "Properties," and "Tasks" tabs appear in the details pane. 3. Click the "Tasks" tab. 4. Double-click "Deployment" under "Task Name." The "ePolicy Orchestrator Scheduler" dialog box appears. 5. On the "Task" tab, click "Settings." The "Task Settings" dialog box appears. 6. Deselect "Inherit." 7. Next to "McAfee AVERT Stinger," select "Install" in "Action." 8. To specify command-line options, click "..." next to the desired product. Separate multiple options with a space. To scan all local drives, type "/ADL." To save the AVERT Stinger log (STINGER.LOG) file in the installation directory, type "/LOG." 9. If you want this task to also be enforced during the policy enforcement interval, select "Run this task at every policy enforcement interval." 10. Click "OK" to return to the "ePolicy Orchestrator Scheduler" dialog box. For more information, see "Scheduling client tasks" in the ePolicy Orchestrator 3.0 Product Guide or Help. NOTE: To send this policy to client computers immediately, send an agent wakeup call to the affected computers. Otherwise, client computers won't receive it until the next agent-to-server communication interval (ASCI). To ensure that AVERT Stinger was successfully deployed, run the All Installations query, the Product Protection Summary report or another compliance report. CREATING ON-DEMAND SCAN TASKS 1. Log on to the desired ePolicy Orchestrator server. 2. In the console tree under "ePolicy Orchestrator," right-click "Directory," , , or , then select "Schedule Task." The "Schedule New Task" dialog box appears. 3. Type a "New Task Name." 4. Select "McAfee AVERT Stinger " | "On-Demand Scan" from the list of tasks. 5. Click "OK" to create the new task. 6. On the "Tasks" tab in the details pane, right-click the "Task Name" you entered in Step 3, then select "Edit Task." The "ePolicy Orchestrator Scheduler" dialog box appears. 7. Click "Settings" to open the "Task Settings" dialog box. 8. Deselect "Inherit." 9. To scan all local drives, select "/ADL - Scan all local drives." 10. To save the AVERT Stinger log (STINGER.LOG) file in the installation directory, select "/LOG - Save the log file after scans." NOTE: The "Use additional command line options" box is for future use. 11. Click "OK" to return to the "ePolicy Orchestrator Scheduler" dialog box. For more information, see "Scheduling client tasks" in the ePolicy Orchestrator 3.0 Product Guide or Help. NOTE: To ensure that all virus infections were successfully cleaned from all client computers, run the Action Summary report, Outbreak Transmissions report or another infection report. _______________________________________________ REMOVING THIS RELEASE UNINSTALLING AVERT STINGER FROM CLIENT COMPUTERS You can use ePolicy Orchestrator to remove AVERT Stinger from client computers as needed. 1. Log on to the desired ePolicy Orchestrator server. 2. In the console tree under "ePolicy Orchestrator" | , right-click "Directory," , , or . The "Policies," "Properties," and "Tasks" tabs appear in the details pane. 3. Click the "Tasks" tab. 4. Double-click "Deployment" under "Task Name." The "ePolicy Orchestrator Scheduler" dialog box appears. 5. On the "Task" tab, click "Settings." The "Task Settings" dialog box appears. 6. Deselect "Inherit." 7. Next to "McAfee AVERT Stinger," select "Remove" in "Action." 8. If you want this task to also be enforced during the policy enforcement interval, select "Run this task at every policy enforcement interval." 9. Click "OK" to return to the "ePolicy Orchestrator Scheduler" dialog box. For more information, see "Scheduling client tasks" in the ePolicy Orchestrator 3.0 Product Guide or Help. NOTE: To send this policy to client computers immediately, send an agent wakeup call to the affected computers. Otherwise, client computers won't receive it until the next agent-to-server communication interval (ASCI). To ensure that AVERT Stinger was successfully uninstalled, run the All Installations query, the Product Protection Summary report or another compliance report. DELETING POLICY PAGES FROM THE REPOSITORY To remove policy pages that you no longer want to manage via ePolicy Orchestrator: 1. Log on to the desired ePolicy Orchestrator server. 2. In the console tree under "ePolicy Orchestrator" | | "Repository" | "Managed Products" | "Windows," right-click "McAfee AVERT Stinger" or , then select "Remove." 3. Click "Yes" when asked whether you want to remove the selected software. The policy pages and tasks for the product are removed. DELETING PACKAGES FROM THE MASTER REPOSITORY To delete packages from the master repository, complete these steps. NOTE: Do not manually delete packages from repositories. You cannot delete packages while pull or replication tasks are executing. 1. Log on to the desired ePolicy Orchestrator server using a global administrator user account. 2. In the console tree under "ePolicy Orchestrator" | , select "Repository." 3. In the details pane under "AutoUpdate Tasks," click "Manage packages." The "Packages" page appears. 4 Select the desired packages, then click "Delete."