This content has been marked as final. Show 2 replies
https://knowledge.mcafee.com:443/SupportSite/search.do?cmd=displayKC&docType=kc& externalId=NAI35873&sliceId=SAL_Public&dialogID=27868796&stateId=1%200%202786645 3
here you can read how the subnet value feature will behave. so it is not your best friend.
user defined lists would be, but with a lot of initial clickwork, and then again everytime you add a new repository.
(you would have to remove the new rep from all agentpolicies)
i think you might be able to do both tasks by some sql-statements.
but i guess creating these statements is also a a lot of work and would mean an inappropriate intrusion into the db/risk if it is done by someone else than mcafee.
it would also be possible to let agents choose by pingtime and make sure that agent x from remote site 1 cannot connect to repository 1 in remote site 2. the firewall configuration then depends on exactly what type of repository you have. for example when the rep is a unc rep, the agent should not be able to connect via icmp and unc ports. here you can find some more information: https://knowledge.mcafee.com:443/SupportSite/search.do?cmd=displayKC&docType=kc& externalId=KB38993&sliceId=SAL_Public&dialogID=27868854&stateId=1%200%2027866481
I could create for each site a custom agent policy --> custom list, telling each site separately which repository they should use. --> that´s a lot of work!
But what I do not like is, that each time a new repository is added I will have to change each agent policy again and deactivate this new repository in my user defined list.
Can I somehow change this default behaviour in the ePO Server? I would be nice if new repositories are not enabled but disabled in my user defined list per default. This way I would not have to change each agent policy again. I would only have to change the agent policy for the new site which the new repository is for.
As far as i´ve read, ePO4 does not have any improvments regarding this situation/problem, right?