KNOWN ISSUE: The Symantec Management Agent is not resuming functions and downloading packages after agent blockout period has expired.
Last Updated May 11, 2012
It appears there is a defect in the Symantec Management Agent that prevents it from resuming functions and downloading packages after agent blockout period has expired.
Steps to Duplicate: 1. In the SMP Console, go into Settings>Symantec Management Agent>Settings and select the "Blockouts" tab from one of the targeted agent settings. 2. Add a blockout period that starts at the current time you are testing and lasts for 10 minutes. Set the "Unit" column to "Download". Apply. 3. In Agent Interface, under the Software Delivery tab, make sure that "Enable bandwidth control" is enabled (seems to be tied to blockout functionality). 4. Refresh the agent configuration of a computer that is affected by the agent configuration policy. If the policy is taking effect you will see "Package download is currently disabled" under the Network Status section. 5. Configure and enable a Managed Software Delivery policy, or an agent plug-in policy that hasn't been installed on the target computer yet to download and run on the computer when the agent checks in. 6. Refresh the agent configuration again. The software delivery package should pop into the software delivery window, but it will not download the package due the blockout. The agent logs should confirm this. You will also see that the files do not get downloaded to ".\Program Files\Altiris\Altiris Agent\Agents\SoftwareManagement\Software Delivery\" 7. When the blockout period has expired you should see in the logs something like: OnBlockoutExpired() Communication blockout expired. 8. In the Software Delivery window, although the blockout period has expired, the agent does nothing. It doesn't download the package or run it. If you restart the agent services then it will immediately initiate the download of the package and run it.
This issue has been reported to the Symantec Development Team. This was fixed with the SMP 7.1 SP2 release.
A pointfix has been created for this issue for the SMP 7.1 SP1 version. Please contact NS Support team for a copy of the pointfix