Your ePO admin might have created a single policy that contains all the repositories. Then it would do what you say. A policy per site, as painful as it sounds, might make more sense.
That's actually less painful with the new Policy Assignment Rules in ePO 4.6. That feature alone is probably worth the upgrade. I'm not saying repository management will be loads of fun but you can easily follow a process like this:
1. Create an automatic tag for a site based on IP range (or whatever you can use to guess this).
2. Create a policy (part of the McAfee agent) for that site that includes a specific list
3. Create a policy assignment rule that applies the policy (#2) to any machines with the tag (#1)
4. Repeat (This might not be fun if you have zillions of repositories but if you do have zillions then you're probably doing something wrong)
That is going to be a long list of tags... but a good idea!
shame on me for not reading the message correctly the first time...
200 repositories is WAY too many for any customer. I need to update my blog with my repository science in the next day.
Agreed. Their MA has a policy applied to use every Repository. And 200 is way too many.
So this is expected behavior (pinging 200+ servers at each reboot) ?
But it could be resolved by better configuration ?
Yeah because you have 200 repositories. So I guess that is expected behavior.
Cool... thanks everyone. Sorry for the newb questions.
I'm not very experienced with McAfee administration.
Appreciate all the help !
ultimately you probably only need a small handful (5 to 10). Start by disabling any repository that doesnt service at least 300 machines.
if it were my server i would create 1 per datacenter and delete the rest. However we can do this in baby steps.
In a day or so Ill update my blog with Repository Science to give you the measurement tools. If you want to wait i understand.