How to clean up a failed Vcenter 5.5 install of a second vCenter server in linked mode

Hello,

First, my situation:

I’ve successfully installed the following services on a single box:

vCenter Single Sign-On (Vcenter Single Sign-on for your first vCenter Server)

vSphere Web Client

vCenter Inventory Service

vCenter Server

The first vCenter (SRMVC.test.local) Installed properly.  

I then ran the install on the second vCenter server (SRMVCDR.test.local) 

vCenter Single Sign-On (vCenter Single Sign-on for an additional vCenter Server with a new site)

vSphere Web Client

vCenter Inventory Service

vCenter Server (linked mode) *Failed*

I ran into an error joining the vCenter in linked mode.  I then attempted to force it which also failed, and the install rolled back.   I believe I am dealing with this issue described in this kb:

Linking two vCenter Servers fails with the error: Error 28039.Setup cannot join vCenter Server to the linked mode group (1026087)

  http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2006850

Now I see a series of issues with the VM which may be the root cause.  When I open server manager there is an error when I try to display roles or features.   The error I’m seeing is:

Unexpected error refreshing  Server Manager:  Element not found (Exception from HRESULT:0x80070490)

To make a very long story short:

I don’t really want to fix the issue on the VM.  I believe there could be an issue with the template I deployed this VM from, and I would just like to blow it  way and redeploy from a new template. The issue is that in previous installs I have had trouble reinstalling a second vCenter after a failed install  because various services have already been registered with the first SSO server.

My question:

How to I fully clean up all the necessary components on the first vCenter server after a failed install of a second vCenter server in linked mode?  I  believe that the second server has registered itself not only with its own SSO server, but also with the first site’s SSO server located on  SRMVC.test.local.  I want to blow all traces of it away so that the environment is pristine, and so that I can use the same name of the second vcenter (VCSRMDR.test.local) when I reinstall.