A month ago I published an article explaining the benefits of virtualizing your corporate Exchange Servers, this helps people planning and deigning their Exchange deployment solution in the early project stage. While virtualization on one end brings numerous benefits and server consolidation at your infrastructure layer, it also brings few of the challenging part for managing this virtualized environment with possible automation and management challenges.
Microsoft System Center 2012 is Microsoft Cloud Management and Orchestration product suite, which helps organization to build and manage their private cloud using various available hypervisor product in the market.
Recently I happened to create bunch of virtual machine for an Exchange deployment at one of the client side, where we used System Center 2012 (SP1) Virtual Machine Manager for creating virtual machine using VM template on Windows Server 2012 RTM based Hyper-V Servers. While we were doing it we saw that one we used SCVMM to create virtual machine on one Hyper-V server it gets created flawlessly while the same template based new virtual machine fails to create on another Hyper-V Server.
Problem:
We found that the below error we receive every time whenever we try to create virtual machine on one of the Windows Server 2012 Hyper-V Server”
| Error (2912)An internal error has occurred trying to contact the SCVMM.Domain.net server: NO_PARAM: NO_PARAM.WinRM: URL: [http://scvmm.domain.net:5985], Verb: [INVOKE], Method: [GetError], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/microsoft/bits/BitsClientJob?JobId={2B83957B-1F35-49F5-8701-771D17A25293}]
Unknown error (0x80072f0d) Recommended Action Check that WS-Management service is installed and running on server scvmm.domain.net. For more information use the command “winrm helpmsg hresult”. If scvmm.domain.net is a host/library/update server or a PXE server role then ensure that VMM agent is installed and running. |
Solution:
For fixing this problem we carried out the following tasks in order:
- Remove the affected Hyper-V host from the SCVMM Hyper-V cluster group by running the Remove-SCVMHost CMD-Let with force parameter.
- Remove the corresponding Hyper-V Server host SCVMM partnership based certificate from Trusted People certificate store of SCVMM Server. You can do this by opening the certificate MMC on the SCVMM server and from there go to the local computer certificate store and remove all the corresponding Hyper-V server name based certificate. Mostly you will find it only in the Trusted People store but in case if you find it anywhere else also delete it.
- Now re-add the Hyper-V host in the SCVMM using SCVMM Management console. This step will re-create the certificate in the SCVMM people trusted or necessary store for the newly added Hyper-V host.
Once you re-add the Hyper-V host to the SCVMM give a re-start to the Hyper-V server and then try to re-create the virtual machine using template, and this time it should work without failing.
Cheers!
Azure Hybrid & Cloud Migration Blog 
Leave a comment