You can delete a custom configuration object from the Configuration Object Dictionary.
To perform this procedure, the custom configuration object you want to delete cannot exist on any servers, and the latest version of any policy-based objects — that is, component templates, BLPackages, and server object-based Snapshot and Audit Jobs — cannot refer to the custom configuration object.
To remove a custom configuration object from any servers, you must run the Deregister Configuration Object Job (see Creating or modifying Deregister Configuration Object Jobs) on those servers. To remove the custom configuration object from any policy-based objects, you can manually edit those objects or you can use this procedure.
When you perform this procedure, you cannot delete the most recent version of a custom configuration object without also deleting all earlier versions of the same object.
If you are deleting the latest version of a custom configuration object, a message informs you that you must first delete all earlier versions of the object. The message asks if you would like to delete all versions of the object. Click Yes to delete all versions.
If there are dependencies on any of the objects you want to delete, the Found Dependencies dialog box displays the dependent objects. See Deleting a folder, group, smart group, or system object for a description of the actions you can take using the Found Dependencies dialog box.
You can only delete root-level custom configuration objects. If you select a custom configuration object that is not a root-level object, the Delete Configuration Object icon is dimmed.