cancel
Showing results for 
Search instead for 
Did you mean: 

Deploy Viruscan automatically when computer is joined to domain

Jump to solution

Hi guys.

One question or what would be the best practices for deploying Viruscan thru EPO in AD environment:

I like the neat option about McAfee agent's being automatically deployed when new systems are discovered. You can configure those options under System Tree/Group Details/Sync Type AD: Push agents to new systems when they are discovered. But I'm curios about deploying AntiVirus system (Viruscan Enterprise) in same way.

Why are you unable to set up deployment of Viruscan in the same configuration settings place? Wouldn't be logically that you wish to deploy both softwares at the same time, because having deployed only McAfee agent on client side does not do you any good in case if that client got infected, true?

I see you need to deploy Viruscan seperatly thru Client Task Catalog/Client Task Assignments. From my point of view, this approach is not really good after you join computer to domain and you set up product deployment Virusscan hourly, this computer stays unprotected that 1 hour.

Questions:

- What would be the best approach to achieve, that after computer is joined to domain it automatically gets Agent + VIRUSSCAN?

- What happens to network bandwith in LAN and to all the systems who already have Virusscan installed if there is a scheduled task (deploy Virusscan every hour) running? Does this means that EPO will molest every client (which already has Virusscan installed) every 1 hour? If we have 200 clients this means that EPO will molest them every hour "for no reason" and impact network bandwith "for no reason"?

With best regards,

agent1.png

agent2.png

Message was edited by: bostjanc on 3/28/14 8:03:14 AM GMT+01:00

Message was edited by: bostjanc on 3/28/14 8:06:59 AM GMT+01:00
1 Solution

Accepted Solutions

Re: Deploy Viruscan automatically when computer is joined to domain

Jump to solution

Please remember that agent installation is a special case because it is the agent that establishes communication to ePO.

All other installs have that already available, but agent installation does not, so it runs separately.

As far as client tasks are concerned, after the agent is installed it will 'phone home' to the ePO server within 10 minutes (randomised) and it will then pick up any tasks or policies assigned to the group where it is added in the system tree.

If you have a 'run immediately' installation task set for that group it would be picked up and as it suggests would immediately initiate a virusscan installation on the client.

Run immediately tasks only run once for a client (unless reset or modified) so this would provide the first-time install hit you might looking for.

If VirusScan is found to be installed already it is not reinstalled, the only thing that happens is the current status of VirusScan is sent back as an event (Typically less than 1k). Local script checks by the agent make sure of that. The impact on bandwidth is therefore small. Deployment tasks of VirusScan that are successful will follow-up with a content update (autoupdate) check so that dats are also updated as soon as possible.

You may find this useful:

https://kc.mcafee.com/corporate/index?page=content&id=PD23282

(ePolicy Orchestrator 4.6 Hardware Sizing and Bandwidth Usage Guide)

If you want a one-hit installation, look up 'McAfee Installation Designer', as you may be able to bundle up your own custom package using it.

https://kb.mcafee.com/resources/sites/MCAFEE/content/live/PRODUCT_DOCUMENTATION/23000/PD23073/en_US/...

2 Replies

Re: Deploy Viruscan automatically when computer is joined to domain

Jump to solution

Please remember that agent installation is a special case because it is the agent that establishes communication to ePO.

All other installs have that already available, but agent installation does not, so it runs separately.

As far as client tasks are concerned, after the agent is installed it will 'phone home' to the ePO server within 10 minutes (randomised) and it will then pick up any tasks or policies assigned to the group where it is added in the system tree.

If you have a 'run immediately' installation task set for that group it would be picked up and as it suggests would immediately initiate a virusscan installation on the client.

Run immediately tasks only run once for a client (unless reset or modified) so this would provide the first-time install hit you might looking for.

If VirusScan is found to be installed already it is not reinstalled, the only thing that happens is the current status of VirusScan is sent back as an event (Typically less than 1k). Local script checks by the agent make sure of that. The impact on bandwidth is therefore small. Deployment tasks of VirusScan that are successful will follow-up with a content update (autoupdate) check so that dats are also updated as soon as possible.

You may find this useful:

https://kc.mcafee.com/corporate/index?page=content&id=PD23282

(ePolicy Orchestrator 4.6 Hardware Sizing and Bandwidth Usage Guide)

If you want a one-hit installation, look up 'McAfee Installation Designer', as you may be able to bundle up your own custom package using it.

https://kb.mcafee.com/resources/sites/MCAFEE/content/live/PRODUCT_DOCUMENTATION/23000/PD23073/en_US/...

Re: Deploy Viruscan automatically when computer is joined to domain

Jump to solution

Rackroyd.

Thank you for a terrific explanation.

with best regards,