Here’s a new Knowledge Base article we published. This one talks about an issue where attempting to remove VMware vCenter from VMM 2012 fails with error 0x8007274D.
When trying to remove the VMware vCenter 4.1 from System Center 2012 Virtual Machine Manager (VMM), the action fails with the error: VMM cannot complete the VMware operation on the SERVERNAME$ server because of the error: Unable to connect to the remote server Resolve the issue in VMware and then try the operation again. ID: 12701 Details: No connection could be made because the target machine actively refused it (0x8007274D) Also, every few minutes the following error is displayed under the Jobs tab:
Error (12701) VMM cannot complete the VMware operation on the SERVERNAME$ server because of the error: Unable to connect to the remote server No connection could be made because the target machine actively refused it (0x8007274D) Recommended action Resolve the issue in VMware and then try the operation again.
System Center 2012 Virtual Machine Manager needs to communicate with the VMware vCenter in order to remove it from the VMM server. In situations when VMM is not able to communicate with the VMware vCenter (i.e. vCenter server was lost or network issues), it is not possible to directly remove the VMware vCenter.
One option is re-install VMM with the new database.
The second option requires a few steps. In summary, a new virtual machine needs to be created and then joined to the domain under the same name as the previous vCenter server. VMware vCenter server will need to be also installed on this virtual machine. By doing this, VMM will think that the old vCenter server is back. However, since by default the communication between the VMM and vCenter servers is encrypted, VMM will give an error stating that it cannot communicate with vCenter server because of the invalid certificates. Thus, we will also have to generate a new vCenter certificate on the VMM server. More detailed steps are shown below:
1. Create a new Virtual Machine.
2. Install Windows Server 2008 R2 (or older Windows version supported by VMware vCenter) with the required updates.
3. Join the Virtual Machine to the domain under the same computer name as the original computer with which the contact was lost. For example, if the original vCenter server's computer name was vcenter.contoso.com then the newly created Virtual Machine should be joined to the domain as vcenter.contoso.com.
4. Install VMware vCenter and VMware vSphere client on the newly created VM.
5. On the VMM server, open the Certificates Snap-in (Computer Account) (http://msdn.microsoft.com/en-us/library/ms788967.aspx) and delete the VMware default certificate located under Trusted People/Certificates.
6. Launch the VMM PowerShell on the VMM server, type and run the following command:
$Virtman = Get-virtualizationmanager –computername “VirtMgrServer01.Contoso.com” $Cert = Get-certificate –computername “VirtMgrServer01.Contoso.com” Set-VirtualizationManager –VirtualizationManager $VirtMan –Certificate $Cert
Where VirtMgrServer01.Contoso.com is the FQDN of your newly created VMware vCenter server.
7. In the VMM console, right click on the VMware vCenter server and select Refresh. vCenter server should be successfully refreshed.
8. Right click on the VMware vCenter and select Remove. The vCenter should be successfully removed from the VMM server.
How to: View Certificates with the MMC Snap-in: http://msdn.microsoft.com/en-us/library/ms788967.aspx How to Replace the Certificate for a VMware VirtualCenter Server: http://technet.microsoft.com/en-us/library/cc974213
For the most current version of this article please see the following:
2730029 - Attempting to remove VMware vCenter from System Center 2012 Virtual Machine Manager fails with error 0x8007274D
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
or you can save a lot more time via this method:
This is completely unacceptable. Going through hoops to complete a simple task.
A fix is in order.