The McAfee Agent 5.5.1 tries to pull an update and deployment packages from only the fallback repository. It ignores all other enabled repositories when the following criteria are True:
- The McAfee Agent Repository policy is configured to sort repositories based on ping time.
- The client is unable to ping any of the distributed repositories enabled in the McAfee Agent Repository policy.
The above can result in undesirable and unexpected behavior. The default fallback site,
update.nai.com, also known as
McAfeeHTTP, does not host installation packages (deployments) or product updates. It only hosts content updates.
For example, a client update task configured to push VirusScan Enterprise 8.8 Update 11 completes and reports success without applying the required update. The issue occurs because the only repository tried, update.nai.com, does not contain VirusScan Enterprise update data.
In this same example, a client update task configured to push a DAT content file succeeds if
update.nai.com is reachable. The reason is because the fallback site does host update content (not updates or installers).
