If the Carbon Black Cloud Workload appliance is unreachable and unresponsive, you can redeploy the appliance. To redeploy the same appliance, you must register with the same SSO and vCenter Server. You must regenerate the API ID and the key for the appliance from the Carbon Black Cloud console and use the new API ID and key to establish a connection between the appliance and the Carbon Black Cloud.
You are unable to connect to the appliance or appliance is unresponsive. You are not able to log in to the appliance even after resetting the password multiple times. To resolve the appliance issue, you decided to redeploy the appliance.
- Delete the old Carbon Black Cloud Workload appliance from the vCenter Server. For details, refer to Delete Appliance from vCenter Server.
- Deploy Carbon Black Cloud Workload appliance as described in Step 1A: Deploy Carbon Black Cloud Workload appliance in the vCenter Server.
Note: If you are not able to access appliance UI, clear the web browser SSL certificate cache, and then log in to the appliance.
- Register appliance with the same SSO and vCenter Server as described in Register Appliance with On-Premises vCenter Server.
- Generate the API ID and key. For details, refer Step 1C: Generate API ID and API Secret Key.
Important: The appliance name must be UNIQUE for your Carbon Black Cloud organization. You cannot use the original appliance name or API ID and API secret key of the already registered appliance.
- Register appliance using the API ID and API secret key. For details, refer Connect Carbon Black Cloud Workload Appliance with Carbon Black Cloud.