Setting Disable communication at startup and after blockouts for up to and blockout period on startup can prevent policies from ever firing

Products

• IT Management Suite

Issue/Introduction

If a customer disables communication at startup for their agents and delivers policies while the agent is  in a blockout, then the policies will not fire
until the agent service is manually restarted.  Rebooting the client ocmputer will not fix the issue, as communications are disabled on startup.

To Reproduce:
* Enable Agent plugins to have something to see later
1. Disable communication at startup by 5 minutes in Targetted Agent settings
2. Enable a blockout period ("download") from an hour before the current time
3. Install the Symantec Management Agent on a new client machine
4. Change the Agent to point to the NS, get new config, send basic inventory and do a delta on the SMP to get the machine into the appropriate places

The client machine will now have all the plugins enabled previously waiting to install after the blockout (in an hour from now in the example above).  These
plugins will never install.  After the hour has passed, the plugins will continue to sit there, if you reboot the machine the same thing will happen.

 

On the client machine, you will see the status of the agent plugins "Package not yet downloaded".

 

Resolution

This issue is under investigation by Development.

Applies To

Symantec Management Platform SP5