I wanted to create a quick post about this just in case anyone else ever has a (0x0107, 0x0000) message when trying to view a VMs console session using VMM 2012.
This happens when you have a untrusted Hyper-V host in VMM 2012 such as a machine sitting in your DMZ (perimeter host). You will be able to see the Hyper-V host, the VMs and manage the VM properties but not connect to the console. When you try to connect to the VM you will be asked to authenticate against the host and then you will see a warning about an un trusted certificate and once you click OK you will receive the (0x0107, 0x0000) message.
To resolve this issue you need to import the certificate from the Hyper-V host onto the machine where you are running the VMM console.
Logon to your Hyper-V Server and create a new MMC Console. Select the Certificates Snap-In to add use the ‘Services Account’
Locate the ‘Windows Remote Management (WS-Management)’ service account and complete the wizard with the rest of the defaults.
If like me your Hyper-V host is running Windows Serer Core mode instead of using certutil.exe you can use a snap-in on another machine (you will be asked to authenticate against) to remotely manage your certificates.
Once you have the console setup you need to find your server certificate which will be located under ‘WinRM\Trusted Root Certificate Authorities’. Right click on the certificate and follow the export wizard.
On your VMM console machine you need to import the certificate you have just exported into the ‘Trusted Root Certificate Authorities’ of the computer account.
You should now be able to connect to the console of the VM. You will still need to enter your authentication details but you won’t be presented with the certificate warning.