Controls are often used to meet legal or regulatory requirements. After they are implemented and tested, controls should be uninstalled only after careful consideration.
When a control is uninstalled, the status for the control reverts to Not Implemented and child content is deleted from the Sentinel system. There are a few exceptions and special cases:
Dependencies are checked to ensure that no content that is still in use is deleted. Some examples of this include a dynamic list that is used by a correlation rule created in the target Sentinel system, a report that is used in a control that is still installed, an iTRAC workflow template that is used in a Solution Pack that is still installed, or a folder that still contains other content.
Reports copied to a local system cannot be removed if the uninstall is performed from a Sentinel Control Center on a different machine.
JavaScript files associated with Execute Script Correlation actions remain on the correlation engines.
Maps (.csv files) and the data they contain are not deleted.
Roles associated with workflows are not deleted.
To uninstall a Control:
Right-click the control you want to uninstall and select
. Alternatively, you can click the icon. The Controls To Uninstall window displaysClick
If the control you are uninstalling includes one or more reports, you are prompted whether to uninstall the reports from the local server or the Crystal Reports Server. Ideally, this information was recorded on the
tab when the reports were installed.Click
. The Uninstall Content window displays.Click
. The selected contents are uninstalled.You cannot uninstall local reports from a different Sentinel Control Center machine than the one that they were installed on or if the files were copied to a new location after installation. If the Solution Manager cannot find the .rpt files in the expected location, a message is logged in the Sentinel Control Center log file.
Click
.For trademark and copyright information, see Legal Notices.