A Managed Delivery Policy that is set not to perform software compliance check, is downloading the initial package, however, if the package is changed and the policy is executed again the package will remain the old one, although on the package server the package is the updated one.
Will be visible in the Trace logs on the agent, meaning that the task instance is loaded from the cache
The code in the Software Management Framework Agent was altered in rollup V6
The result of this is causing the Agent to turn to the cached task instance when trying to download the new package, the information located in the cached task instance contain the old information about the package hence the new hash and size information is not reflected and package is not getting downloaded
Symantec is aware of the problem and working towards a solution.
It was observed that if the task cache is flushed, the relevant package is downloaded, hence, it is possible to workaround the issue in the following way :
-- On the NS got to --> Manage --> Tasks --> Right Click System Jobs and Tasks --> New --> Task
-- Select Run Script --> Change the name to : Delete Cached Tasks on Agent
-- Select Script Type : VBscript
-- Paste the following script :
Const DeleteReadOnly = True
Set obj = CreateObject("Scripting.FileSystemObject")
-- Set a new schedule for the task and set the target for all the affected machines, The flush of the tasks cache time and frequency will vary depend on the frequency of updated packages (recommend : once a day at a time when packages or tasks are not scheduled to run)
Symantec Mangement Platform 7.1 SP2 MP1 Rollup V6
Symantec Mangement Platform 7.1 SP2 MP1 Rollup V7
Symantec Mangement Platform 7.1 SP2 MP1 Rollup V8
Symantec Mangement Platform 7.1 SP2 MP1 Rollup V9
Agent doesn't update package during execution of MSD policy containing QD tasks, after policy was executed once, and package then was updated
Imported Document ID: TECH222847
Subscribing will provide email updates when this Article is updated. Login is required.