1 of 1 people found this helpful
Make sure the following policy is enabled & configured according to your environment: McAfee Agent / Repositories / Repository list. As for repository logging, McAfee removed that functionality when they introduced Agent 5.X ePO Agent Log: 22.214.171.1246 vs 126.96.36.1995
Thanks for the prompt reply and information.
Need sometime to disgest the information. Would you please enlighten me on the following questions ?
1. Is there any way to find out from client side (not ePO console) on which type of repository will it be connected ?
2. Is the existense of McAfee Agent in the client a manatory condition before it can work with other distributed repositories ( FTP, HTTP, UNC share and SuperAgents) to receive update ?
1 of 1 people found this helpful
The repository list for a system can be found in SiteList.xml; the filename and path varies slightly by product and version, but a search in McAfee's KB should tell you where to find it for your environment.
The McAfee Agent is the management agent for all things McAfee on the system; it takes care of product installs, updates, policies, etc. As such, yes, it's required for any centralized management, including managing repositories.
Thanks for your information. So I can find where the client will search for update by inspecting the existing SiteList.xml ?
For my second question, as client did not have agent installed, cannot explain why it can search master replicate but not other local replicates for updates ?
- Yes, the SiteList.xml is the repository configuration file for the agents
- If the client doesn't have the agent insalled, then ePO can't manage it. I'm not sure what you mean by "it can search master replicate"? Do you mean it's getting updates from the master repository, but not the distributed repositories? Without an agent, it can't get updates from *any* repository; if they are getting updates, then the agent must be installed. How are you determining that the agent isn't installed?
Thanks again, would like to clarify my meaning of the second question. Your intepretion is correct. The exact phrase is : I was told me my clients can only receive update from master repository (by forcing the client to hardcode using master repository). If not, they cannot receive update from the disbributed repositories (which are more adjacent than master repository).
Unsure whether there is way EPO server can impose VSE signature update from matster repository to its client without McAfee Agent being installed at client side first. From your reply, looks like above situation is impossible, right ?
Summarise on previous discussion, looks like the way to tackle my questions are
a. Check whether SiteList.xml exist in the clients and its contents. It show where the client will go to search for update.
b. Check whether McAfee Agent is installed and its version
After above items are ensure, still need way from client side to check for its connectivity to selective distributed repositories. Is there any tools or way can allow local administrator to perform that ?
Yes, you are correct that you can't push out the repository list without McAfee agent. As such, you have the steps the wrong way round. You want to ensure McAfee Agent is installed; assuming your environment is configured correctly, it'll fix the SiteList.xml itself and the problem should go away. If it doesn't, then there's something else wrong.