Device remains blacklisted after deep clean even though Prevent Rediscovery is not ticked
search cancel

Device remains blacklisted after deep clean even though Prevent Rediscovery is not ticked

book

Article ID: 392825

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After Using Deep clean to remove a device or robot from Operator Console (OC), the system stays in blacklist even though we have not selected the "Prevent Rediscovery" Checkbox. 

We are no longer able to install a robot on a sever that was deep cleaned, but we did not check the option "Prevent Rediscovery" when we deleted the device. 

Environment

DX UIM 23.4.2 (CU2) / 23.4.3 (CU3)

Cause

By Design, when using the "Deep Clean" a Device added to blacklist during OC deep clean process. However, due to a defect in DX UIM 23.4.2 (CU2) and 23.4.3 (CU3), the deep clean process might fail and show a wrong Status in Device Status and after the process fails or never ends, leaving the Device in the CM_BLACKLIST_DEVICE and CM_BLACKLIST_COMPUTER_SYSTEM tables. 

Resolution

Additional Information