Rolling out the Patch Management Agent Plug-in and the client fails to get the package.
No package could be found for the selected Agent installation policy
Could not get config xml for specified item - Software Update Plug-in Install / Upgrade
Cloning the Software Update Plug-in Install / Upgrade policies can cause the connection to the package codebase for the Patch Management Agent Package to be disconnected.
Advisory: Cloning will cause the Install / Upgrade Policy to spawn 3 sub policies:
The sub policies is where the connection to the package URL / UNC is lost when referencing the database.
Delete the cloned policy. The 3 sub policies will be cleared out.
Configure the targeted filter on the Software Update Plug-in Install / Upgrade policy to only roll out updates for specific clients.
Ensure the policies are configured to run ASAP and on a daily schedule to ensure the client is updated as outlined:
Note: The process to clone the Software Update Plug-in Install / Upgrade Policies is supported for PM 7.1 SP2 MP1.
Patch Management 7.0, 7.1, 7.1 SP1 & 7.1 SP2
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe
7.1.2, 7.1.1, 7.1, 7.0
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.