When using System Center Virtual Machine Manager (SCVMM) to perform a Physical to Virtual (P2V) conversion, the job may fail at 60% with the following error:
Error (2912) An internal error has occurred trying to contact an agent on the vmmserver.contoso.com server.
Recommended Action Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.
Cause:
During the 'Make operating system virtualizable' step, files are copied from the destination host (the server that will host the virtualized system) to the SCVMM Server. This BITS operation fails due to a certificate problem as indicated by the error 0x80072F0C (ERROR_INTERNET_CLIENT_AUTH_CERT_NEEDED).
Resolution:
To resolve this issue, remove the managed host from the SCVMM server and also delete any residual certificates from the host on the VMM server, then re-add the host:
1. On the SCVMM server, remove the managed host from the console. The steps on how to remove a managed host are outlined in the following TechNet article:
http://technet.microsoft.com/en-us/library/cc956121.aspx (http://technet.microsoft.com/en-us/library/cc956121.aspx)
2. Now we need to locate and delete any certificates for the Host computer.
3. Open the Certificate console on the SCVMM server.
a. Open a new mmc and add the certificates snap-in. b. Select the option of 'computer account' and 'local computer'. c. Select Finish and Ok to load the snap-in.
4. The certificates for the Host computer can be in any of the following locations.
a. Personal Certificates. b. Trusted People (if the host is W2K8 or W2K8 R2). c. Trusted Root Authorities (If the host is W2K3).
5. In each store, expand the Friendly Name field and locate the certificate[s] for the Host server that have a Friendly Name starting with 'SCVMM_CERTIFICATE_KEY_CONTAINER' followed by either the FQDN / IP address / NetBIOS name of the Host server and delete them.
6. Re-add the host in SCVMM which recreates the certificates as needed.
More Information:
SCVMM uses BITS to transfer payload between SCVMM managed computers. These data transfers are encrypted by using a self-signed certificate generated at the time a host machine is added to SCVMM. If these certificates are missing or corrupted from the SCVMM server or managed computers, the payload deployment job can fail. Deleting the certificates and re-adding the host will cause the certificates to be regenerated.
For the latest information on this issue see the following Knowledge Base article:
KB2385280 - P2V fails with Error 2912 0x80072F0C with System Center Virtual Machine Manager 2008 or System Center Virtual Machine Manager 2008 R2
J.C. Hornbeck | System Center Knowledge Engineer
When you try to connect to a Virtual Machine (VM) from the System Center Virtual Machine Manager console you may get the following error:
"A certification authority could not be contacted for authentication.
If you are using a Remote Desktop Gateway with a smart card, try connecting to the remote computer using a password.
For assistance, contact your administrator or technical support"
This can occur if you have performed an authoritative restoration on the Users container in the Active Directory directory service. When this is done the version number of the KRBTGT account increases which is a service account that is used by the Kerberos Key Distribution Center (KDC) service.
This is essentially the same issue as the one documented in the following Knowledge Base article:
KB939820 - Events 1925, 1006, 1645, 1055, 40961 on a Windows Server 2008-based domain controller or error message: "No authority could be contacted for authentication" when you use Remote Desktop Connection
To resolve the issue apply the hotfix specified in the Knowledge Base article above. Note that you must restart the computer after you apply this hotfix.
Satish Phatge | System Center Support Engineer
When using System Center Virtual Machine Manager to install virtual guest services the job may fail with the following error.
Error (13206) Virtual Machine Manager cannot locate the boot or system volume on virtual machine <virtual machine name>. The resulting virtual machine might not start or operate properly.
Error (13206)
Virtual Machine Manager cannot locate the boot or system volume on virtual machine <virtual machine name>. The resulting virtual machine might not start or operate properly.
A trace of the job will contain a variation of the following entry.
MountedVhd.cs,87,0x00000000,MountedVhd windows volume not found,{00000000-0000-0000-0000-000000000000},4,
The boot and system files are on different partitions, with the Windows directory being on an extended partition instead of a primary partition. The Windows volume is not found when the VHD is mounted for integration services integration.
Two possible workarounds:
It is possible to fully automate the installation of integration components on VMs by copying required files to the VM and executing the process remotely. No user interaction is required. Be aware that the VM will reboot automatically if needed.
For more information on psexec refer to the Sysinternals product page (http://technet.microsoft.com/en-us/sysinternals/default.aspx)
Further information can be found here:
KB962226 - Setup.exe from the Integration Services Setup Disk has no command line options
The 'autorun.inf' file in the root of an .ISO can also be modified as shown below. If autorun is enabled on the VM operating system this will automatically install integration components in the same manner as previously described.
[AutoRun] action=@support\x86\setup.exe,-2000 label=Integration Services Setup open=support\x86\setup.exe /quiet [DeviceInstall]
For the latest version of this article please see the following Knowledge Base article:
KB2313592 - System Center Virtual Machine Manager Guest Services installation fails with Error 13206