Snapshot Data For Nested Components Might Not Be Purged When the Nested Components Get Reinstalled

If a nested component that is installed by way of the installation of a container component, creates snapshots, the snapshot data on the Remote Agent might not get purged when the nested component is uninstalled by the reinstall of the container component. This might lead to the Remote Agent, on which the nested component was installed, to consume more disk space than it should since the orphaned snapshot data was not purged.

Workaround: The orphaned snapshot data might be purged by installing and then uninstalling a simple component that creates snapshots on the Remote Agent with orphaned snapshot data. The install and uninstall cause the Remote Agent to compare its snapshot data with the Master Server. The result is that the snapshot data is purged for all the components that are no longer installed on the Remote Agent.