Safe Deletion of drsShellVM after decommissioning an ORG and PVDC in VMware Cloud Director
search cancel

Safe Deletion of drsShellVM after decommissioning an ORG and PVDC in VMware Cloud Director

book

Article ID: 396949

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

In some cases, after decommissioning an Organization and its associated Provider Virtual Data Center in VMware Cloud Director, the drsShellVM may still remain in the vCenter cluster. This raises concerns about whether it is safe to delete the drsShellVM before proceeding with the removal of blades and the cluster itself.

Environment

VMware Cloud Director 10.x

Cause

The drsShellVM may remain in the vCenter cluster after decommissioning the ORG and PVDC if it wasn’t properly cleaned up during the process. It is used for specific operations within VMware Cloud Director but may not always be removed once the associated ORG or PVDC is decommissioned.

Resolution

Verify Dependencies:

  • Check that no VCD instances or configurations are using or associated with the drsShellVM.

Safe Deletion:

  • If no dependencies exist, it is safe to delete the drsShellVM from the vCenter cluster.

  • Confirm that the VM is not actively tied to any active VCD instances or configurations before deletion.

Impact Assessment:

  • Deleting the drsShellVM will not affect the functionality of vCenter or VMware Cloud Director as long as it is not associated with any active services.