I have 6 building each with an Active directory server and approx. 350 client computers. I configured a repository on each one of these servers and I'm pushing the updates from ePO server to them. Can I configure/edit the repository list so each building will pull first from the server in that building without crossing the network? I know I can edit each PC manually, but in todays world, why should I have too. Any help would be greatly appreciated.
Providing configuration details at least ePO version will be appreciated. My fortune teller says that for ePO 4.0 it might be achieved by creating separate groups system->system tree than system->policy catalog->choose mcafee agent from drop down list create separate policy. In policy setup on repositores path unmark repositories others than local one. hope you'll manage....
I'm running ePO 4.5 on Win server 2003 and the clients are XP w/ sp3 running McAfee 8.7i. Thanks a bunch...
I was able to create this new policy and I can see it in Policy Catalog, although it says no assignments. I did a cut and paste of the repository windows, note the radio buttons did not show up...so I put *'s next to the options I choose.
Repository list selection: Use this repository list * Use other repository list
(Move up and down are grayed out and whatever I do, I cannot rearrange the order of the reposoitory list) ( cannot edit them or delete them, I'm guessing because I created these as Distributed repositories)
I created my groups and sub groups like my active directory tree.
Building name (root OU) Room number (sub OU)
Islip Arts Building R200 (each have approx 25 pc's in it) R201 R202
In your mcafee agent policy you should have all (appropriate) repositories enabled. Then just select SUBNET DISTANCE. What it does is that clients contact the local repository for updates. To check go to http://machine-name:8081 try one machine from each site and you should see them contacting their local repository.
I'll definitely suggest making copy of default policy and don't modify this. Just in case you will change to much – this gives you easy rollback... Few words of explanations: I've some country branch offices, every office have it's own repository. Unfortunately some links between countries are poor quality and counting distance algorithm does not work properly. I’ve to hardcode which location can use which repository. I’ve achieved it using different policy for different locations (there were some other reasons to have separate policies per country).
I also use different policies based on the location. We have some very large remote locations so those each have their own repository and also have their own policy that lists their repository first and they dont have other certain repositories listed in their policy because of the extremely slow connection between certain sites.
Using import button wink Hint: don;t search in right bottom but at right 1/3 from top wink it let to import/export all policies - If you would screw up something.... Why not use moving up and down interface?