cancel
Showing results for 
Search instead for 
Did you mean: 

Install VSE with each policy enforcement?

Jump to solution

Hi all,

I'm trying to diagnose some performance issues on several machines.  I notice in the agent log on one particular PC that with every policy enforcement (every 5 minutes), the scheduler is invoking tasks to install VSE 8.7 and AntiSpyware Enterprise Module.  This appears on several logs that I've looked at this morning.  What I don't understand is if the agent is actually running the installer for VSE every 5 minutes (which would explain the poor PC performance), or if the agent is just acknowlegding that the task exists, checking that VSE is already installed, and not actually running the installer.

I'm running ePO 4.0.  I have two tasks for installing VSE 8.7 and AntiSpyware EM.  Both are set to run immediately and at every policy enforcement.

Perhaps I have this configured wrong.  I obviously don't want these products to install every 5 minutes, but rather install if they don't exist yet.

Thank you in advance for any help you can provide.

-Mike

Here is a sample of the agent log from one of these PCs.

Thursday, January 14, 2010 10:56:32 AM
Info
Agent
Agent Started Enforcing  policies
Thursday, January 14, 2010 10:56:32 AM
Info
Management
Enforcing Policies for  VIRUSCAN8700
Thursday, January 14, 2010 10:56:33 AM
Info
Management
Enforcing Policies for  SITEADV_2000
Thursday, January 14, 2010 10:56:34 AM
Info
Management
Enforcing Policies for  EPOAGENT3000META
Thursday, January 14, 2010 10:56:34 AM
Info
Management
Enforcing Policies for  EPOAGENT3000
Thursday, January 14, 2010 10:56:34 AM
Info
Management
Enforcing Policies for McAfee  Agent
Thursday, January 14, 2010 10:56:35 AM
Info
Scheduler
Added a new task Install VirusScan 8.7  to Scheduler's task list
Thursday, January 14, 2010 10:56:36 AM
Info
Scheduler
Added a new task Install AntiSpyware  Enterprise Module (ASEM) to Scheduler's task list
Thursday, January 14, 2010 10:56:36 AM
Info
Scheduler
Scheduler: Invoking task [Install  AntiSpyware Enterprise Module (ASEM)]...
Thursday, January 14, 2010 10:56:37 AM
Info
Updater
Checking update packages from repository  ePO_SERVER
Thursday, January 14, 2010 10:56:37 AM
Info
Updater
Initializing update...
Thursday, January 14, 2010 10:56:37 AM
Info
Updater
Verifying catalog.z.
Thursday, January 14, 2010 10:56:37 AM
Info
Updater
Extracting catalog.z.
Thursday, January 14, 2010 10:56:37 AM
Info
Updater
Loading update configuration from:  catalog.xml
Thursday, January 14, 2010 10:56:38 AM
Info
Agent
Agent finished Enforcing  policies
Thursday, January 14, 2010 10:56:38 AM
Info
Agent
Next policy enforcement in 5  minutes
Thursday, January 14, 2010 10:56:38 AM
Info
Updater
Verifying MAS870det.mcs.
Thursday, January 14, 2010 10:56:39 AM
Info
Updater
Verifying MAS870det.mcs.
Thursday, January 14, 2010 10:56:39 AM
Info
Updater
Update Finished
Thursday, January 14, 2010 10:56:39 AM
Info
Scheduler
The task Install AntiSpyware Enterprise  Module (ASEM) is successful
Thursday, January 14, 2010 10:56:39 AM
Info
Scheduler
Scheduler: Task [Install AntiSpyware  Enterprise Module (ASEM)] is finished
Thursday, January 14, 2010 10:56:39 AM
Info
Scheduler
Scheduler: Invoking task [Install  VirusScan 8.7]...
Thursday, January 14, 2010 10:56:41 AM
Info
Updater
Checking update packages from repository  ePO_SERVER.
Thursday, January 14, 2010 10:56:41 AM
Info
Updater
Initializing update...
Thursday, January 14, 2010 10:56:41 AM
Info
Updater
Verifying catalog.z.
Thursday, January 14, 2010 10:56:41 AM
Info
Updater
Extracting catalog.z.
Thursday, January 14, 2010 10:56:41 AM
Info
Updater
Loading update configuration from:  catalog.xml
Thursday, January 14, 2010 10:56:42 AM
Info
Updater
Verifying VSE870Det.McS.
Thursday, January 14, 2010 10:56:42 AM
Info
Updater
Verifying VSE870Det.McS.
Thursday, January 14, 2010 10:56:42 AM
Info
Updater
Update Finished
Thursday, January 14, 2010 10:56:43 AM
Info
Scheduler
The task Install VirusScan 8.7 is  successful
Thursday, January 14, 2010 10:56:43 AM
Info
Scheduler
Scheduler: Task [Install VirusScan 8.7]  is finished
1 Solution

Accepted Solutions
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: Install VSE with each policy enforcement?

Jump to solution

Hi...

(A bit of background - bear with me )

Install and update tasks that are executed by the agent are essentially scripts - that is, the agent has a script engine, and a script file to tell it what to do. For install and update tasks, there are a pair of scripts: a detection script, and an install script. When you run a task to (for example) install a product, the agent runs the detection script, which tells the script engine if that product is already installed. If the answer was "no", then the script engine would proceed to run the installation script and install the product. (In the case of update tasks, the detection script works out if the product needs updating, and the installation script applied the update.)

So what you're seeing here is that every time the task runs, the script engine is executing the detection script (VSE870Det.mcs). This is returning "the product is already installed", so the task exits at this point.

In a nutshell, you have it configured correctly, it's not executing the installer every time but only the detection script, and what you're seeing is normal

Regards -

Joe

2 Replies
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: Install VSE with each policy enforcement?

Jump to solution

Hi...

(A bit of background - bear with me )

Install and update tasks that are executed by the agent are essentially scripts - that is, the agent has a script engine, and a script file to tell it what to do. For install and update tasks, there are a pair of scripts: a detection script, and an install script. When you run a task to (for example) install a product, the agent runs the detection script, which tells the script engine if that product is already installed. If the answer was "no", then the script engine would proceed to run the installation script and install the product. (In the case of update tasks, the detection script works out if the product needs updating, and the installation script applied the update.)

So what you're seeing here is that every time the task runs, the script engine is executing the detection script (VSE870Det.mcs). This is returning "the product is already installed", so the task exits at this point.

In a nutshell, you have it configured correctly, it's not executing the installer every time but only the detection script, and what you're seeing is normal

Regards -

Joe

Re: Install VSE with each policy enforcement?

Jump to solution

Hello Mike_TNJ,

in addition to Joe's post, if you want the task not being executed every policy enforcement you will need to modify the task settings in your ePO 4.0 console and untick the option "Run at every policy enforcement (Windows Only)" under the "Configuration" tab.

Rene