1 of 1 people found this helpful
Bear in mind that the sitelist will get updated by the ePO server anyway if it's managed, so you're probably better installing as normal then setting an appropriate repository policy instead.
Thanks rackroyd. I've been asked how we configure a system that would be isolated from our network that could still connect to the internet, how would we configure an agent package so that it only goes to the internet for DAT updates. Is this feasable? Would you simply give it the regular agent package and let it figure out to use http after it fails to connect back to EPO?
PUEDES Modificar la Directiva del Agente de ESE Equipo Para Qué tomoe las ACTUALIZACIONES de McAfee HTTP
You can Change Directive Agent why take that computer upgrades McAfee HTTP
El mensaje fue editado por: c0nfick3r on 20/06/14 17:19:24 CDT
Yes, i'd do that unless you thing a one-time potential hit of extra traffic to the external site before it gets its policy is a risk to you.
This is assuming such an isolated system can still talk to an ePO server or Agent Handler to get a revised sitelist in the first place of course...
Thanks guys, well I'm not sure about that method (if I'm understanding it correctly). What if I were to install the agent with our regular package and then manually update the repository autoupdate list for that machine? I'm wondering if it would almost make sense having a consumer-type McAfee antivirus product on that particular system since we don't need to manage it like all of our other systems.