vCenter Chargeback Uninstallation – Rogue Plug-in

Doing a proof of concept of VMware vCenter Chargeback, install and usage went great and product does everything you’d expect it to do. Although I’d would’ve liked to seen tighter integration with the vSphere Client, hopefully we can see this in the 1.5 or 2.0 release!

Well, POC was finished and time to uninstall.  Should be pretty easy, Delete from Disk the Virtual Appliance you installed and delete the database. However, if you forget one crucial step you’ll end up with a rogue plug-in in your vSphere Client!

Oh No! The vCenter Chargeback plug-in is still there! What do we do?!

Well, the step you need to do prior to removing the Virtual Appliance is to uncheck the Register As VI Client Plugin box in the vCenter Server settings screen (Settings->vCenter Servers->Edit).  Once you do this, the plug-in will be removed from the vCenter server and you can continue with the removal of the Virtual Appilance and back-end database.





*click on photos to enlarge

Created on August 21, 2009 by Rick Scherer

Posted under vCenter, vSphere.

This blog has 4,429 views.

Tags: ,

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)

2 Comments so far

  1. Jason Boche
    8:35 pm on September 30th, 2009

    Pain in the ass. I’m now stuck with the Chargeback plugin as my 60 day Chargeback license has expired and I can’t get into the appliance to disable the VI Client plugin.

  2. Abhi
    3:05 pm on October 7th, 2009 might help reduce the pain. Relevant stuff from the community post is as below.

    Currently, to unregister this dangling Chargeback plugin you can follow some steps:

    1) Goto VMware vCenter Server Managed Object Browser URL https://{vCenter-Server-ip}/mob
    2) Navigate to Service Content > ManagedObjectReference:ExtensionManager
    3) In extensionList you will see an extension with name extensionList if chargeback is registered as plugin.
    4) From methods table on same page invoke UnregisterExtension with extension key as vCenter Chargeback.


Leave a Comment

Name (required)

Email (required)



More Blog Post

Previous Post: