a blog about nothing

In SCVMM 2012 R2 we suddenly couldn’t deploy VMs from a template, install “Virtual Guest Services Tools”, etc. All jobs failed with the following:

Error (2912)

An internal error has occurred trying to contact the server.domain.com server: NO_PARAM: NO_PARAM.

WinRM: URL: [http://server.domain.com:5985], Verb: [INVOKE], Method: [GetError], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/microsoft/bits/BitsClientJob?JobId={62469246-350C-4ADE-A0BE-80D9E30C382D}]

Unknown error (0x80072f05)

Recommended Action

Check that WS-Management service is installed and running on server server.domain.com. For more information use the command “winrm helpmsg hresult”. If server.domain.com is a host/library/update server or a PXE server role then ensure that VMM agent is installed and running. Refer to http://support.microsoft.com/kb/2742275 for more details.

We verified that we could connect to “server.domain.com” on TCP 5985 from the VMM server.

[PowerShell]:

tnc server.domain.com -Port 5985

Checking the self-signed certificate on the VMM server it showed that it was expired. (01.01.2018)

Resolution:

Delete the expired certificate from the VMM server’s Personal Store and create a new one:

[PowerShell]:

$credential = get-credential

Get-VMMManagedComputer -ComputerName “VMM-Server.domain.com” | Register-SCVMMManagedComputer -Credential $credential

You will now get a new certificate which is valid for 5 years.

If you are going to live migrate from a Hyper-V 2012 cluster to a Hyper-V 2012R2 cluster, the virtual switch name must be the same on the hosts.

We needed to rename the switch on the 2012R2 host, so we just deleted the switch in VMM and recreated it with the same name as the 2012 servers had.

Doing so gave us this error:

Error (25230)

Unable to find extension (0d37c9f0-ea6c-47a0-9c42-4baeba3768d1) on 
virtual switch (Hyper-V Logical Switch)

Recommended Action

Verify the extensions installed on the host and retry the operation.

Searching the Internet did not give us any leads.

Ran: Get-VMSwitchExtension -VMSwitchName “Hyper-V Logical Switch” | select id

This returned the IDs from the extensions attached to the virtual switch, and we saw the ID from the 25230 error was missing.

Solution:

Uninstall the DHCP extension from Add-Remove program. It was not removed when the virtual switch was removed.

Creating a new virtual switch added the DHCP extension back to the server.

COYS