_______________________________________________ INSTALLATION REQUIREMENTS To use this release, you must have ePolicy Orchestrator 2.5 or 2.5.1 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 and Setup (binary) files 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 "Configure Software Repository" dialog box appears. 3. Select "Add new software to be managed." 4. Click "Continue" to open the "Select a Software Package" dialog box. 5. Select the Management Package (.NAP) file from the temporary folder you created in Step 1. 6. Click "Open" to add the product to the "Repository." 7. Click "Yes" when asked if you would like to enable deployment. 8. Click "OK" to add the policy page and Setup (binary) files to the "Repository." 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 Setup files were installed: 1. Log on to the desired ePolicy Orchestrator server. 2. Verify that the correct version number appears in the console tree under "ePolicy Orchestrator" | "Repository" | "Products" | Windows" | "McAfee AVERT Stinger" | . _______________________________________________ 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 2.5 or 2.5.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" | "Directory," select the , . The "Policies," "Properties," and "Tasks" tabs appear in the upper details pane. 3. Click the "Policies" tab. 4. Select "McAfee AVERT Stinger ." The "Installation Options" page appears in the lower details pane. 5. Deselect "Inherit." 6. Select "Enforce Policies for McAfee AVERT Stinger " to enforce this policy on client computers. 7. Select "Force Install McAfee AVERT Stinger ." 8. Click "Select" to open the "Software Package" dialog box, then select "McAfee AVERT Stinger " and click "OK." 9. Click "Apply" to save the current entries. 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," , , 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" | "Directory," select the , . The "Policies," "Properties," and "Tasks" tabs appear in the upper details pane. 3. Click the "Policies" tab. 4. Select "McAfee AVERT Stinger ." The "Installation Options" page appears in the lower details pane. 5. Deselect "Inherit." 6. Select "Enforce Policies for McAfee AVERT Stinger " to enforce this policy on client computers. 7. Select "Force Uninstall McAfee AVERT Stinger ." 8. Click "Apply" to save the current entries. 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. REMOVING AVERT STINGER FROM THE REPOSITORY Use this procedure to remove AVERT Stinger from the "Repository" when you no longer want to manage or deploy it, and after you have uninstalled it from client computers. 1. Log on to the desired ePolicy Orchestrator server. 2. In the console tree under "ePolicy Orchestrator" | "Repository" | "Products" | "Windows" | "McAfee AVERT Stinger," right-click . 3. Select "Remove" to delete all of the product files, including the policy page and Setup files.