Symantec Management Agent package downloads from the SMP rather than the closest Package Server
Last Updated December 18, 2018
When pushing the Symantec Management Agent (SMA) to client computers, the clients download the package from the Symantec Management Platform (SMP) rather than from the closest Package Server despite specifying this option in the Agent Settings.
Flag UseClosestPackageServer ignored on agent push as no ready package server associated with the destination computer1.Domain.com was found.
The client was on a subnet which was a part of a defined site, however the Site Server for that site was on a subnet which was not defined as assigned to the Site Server. The push agent installation checks if there is a Site Server assigned to the site and then looks through the subnets defined for the site and checks if there are any Package Servers associated with those subnets. It returns the first package server that it finds which has the agent installation package.
If the subnet that the Site Server is on is not explicitly added to the site, this subnet will not be scanned for a package server and the server will revert to providing its own address as the package source.
Make sure that the subnets which contain the Site Servers for a site are explicitly added to the Subnets list associated with a site.
Imported Document ID: TECH167335
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe