DSM packages can be split into two classes: base packages and custom packages. Custom packages "contain" base packages and base packages are the "atoms." Base packages are registered when installed or discovered and are listed as "installed software." When a custom package is delivered and installed using Software Delivery, an installation record is created for the custom package. However, this custom package installation record is not created for a manual installation or installation using infrastructure deployment.
When using Software Delivery to uninstall DSM packages, only the base packages should be uninstalled. The order in which the base packages should be uninstalled is important. First, uninstall the agent language packages, then the DCS add-on, then Asset Management and/or Remote Control. Obviously, the software delivery agent needs to be uninstalled last. One way of implementing this would be to create an software delivery uninstall job container with a job for each stage. When the base packages have been uninstalled, the installation records for the custom packages should be removed using DSM Explorer.
Note that plug-ins like Secure Socket Adapter and DMPrimer are not removed. To remove these plug-ins, uninstall any remaining DSM components on the target computer manually using Add/Remove programs.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|