Just a quick heads up on a new KB article we published today:
=====
SymptomsInstallation of Virtual Guest Services (integration components) fails in System Center Virtual Machine Manager 2008 (SCVMM) but can be successfully installed manually in Hyper-V. Also, Physical to Virtual (P2V) jobs may fail when installing Virtual Guest Services. Another version of this error displays (Unknown error (0x80072f06)) under the Warning section below:
Warning (2912)
An internal error has occurred trying to contact an agent on the SCVMMMSVR.Contoso.com server.
(The directory is not empty (0x80070091))
Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.
Warning (2912)
An internal error has occurred trying to contact an agent on the SCVMMMSVR.Contoso.com server.
(The directory is not empty (0x80072f06))
Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.
There are two possible reasons for this condition:
Realtime antivirus is interfering with communications.
or
Multiple ports exist with an SSL binding to port 443.
Realtime Antivirus
To determine if realtime antivirus is scanning port 443:
At an elevated command prompt run the following command:
netstat –ano | find "443"
If any IP address in the ‘Local Address’ column (besides the ones below) are listening on port 443, there is a conflict.
a. 0.0.0.0:443
b. [::]:443
C:\Windows\system32>netstat -ano
Active Connections
Proto
Local Address
Foreign Address
State
PID
TCP
0.0.0.0:443
0.0.0.0:0
LISTENING
4
TCP
192.168.1.63:443
0.0.0.0:0
LISTENING
1044
SSL Certificates
To determine if there are SSL certificates bound to two or more ports:
At an elevated command prompt run the following command:
netsh http show sslcert
If any two IP addresses (except the defaults below) share the same Certificate Hash, there is a conflict.
a. IPv4 0.0.0.0:443
b. IPv6 all address [::]:443
C:\Windows\system32>netsh http show sslcert
SSL Certificate bindings:
-------------------------
IP:port : 192.168.1.61:443
Certificate Hash : b435bdda9cab32b4272a80b94b6985acc96bc2de
…
IP:port : 192.168.1.63:443
Certificate Hash : b435bdda9cab32b4272a80b94b6985acc96bc2de
…
Possible solutions are listed below. The best solution is to change the default ports used by SCVMM from 443 to another port such as 765. Specific solutions based on problems found are also included.
Best solution for both problems
Change the BITS port used by SCVMM from the default of 443 to another non-used port such as port 765. To do this, perform these steps on the SCVMM server and all managed Hosts:
1. Open Regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings.
2. Locate the BITSTcpPort name on the right. It’s data value should be 443.
a. Double click BITSTcpPort in order to modify the data. Make sure the Base is set to ‘Decimal’.
b. Change 443 to 765, or any other number less than 32768. Do not use a port that another protocol uses such as RDP (3389).
c. Click ‘OK’ to save this value.
3. Restart the ‘Virtual Machine Manager’ and ‘Virtual Machine Manager Agent’ services on the SCVMM server (On managed hosts simply restart the ‘Virtual Machine Manager Agent’ service’).
4. Once complete on the SCVMM server and all Hosts, you can continue using SCVMM.
Solution for Realtime Antivirus
If realtime antivirus is listening on port 443 as ‘192.168.1.63:443’ is in the example above, disable realtime antivirus on the system or make an exclusion for port 443.
Solution for SSL Certificate Binding
If there are multiple ports with an SSL binding to port 443, determine what application is using the binding then remove it if possible. Follow instructions at the following location for more details:
http://msdn.microsoft.com/en-us/library/ms733791.aspx
More InformationPort 443 is the default port used by SCVMM for SSL and BITS. When there is a conflict with this port various health and operations issues will appear with SCVMM.
=====For the most current version of this article please see the following:
J.C. Hornbeck | System Center Knowledge Engineer
App-V Team blog:
http://blogs.technet.com/appv/
AVIcode Team blog:
http://blogs.technet.com/b/avicode
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/
OOB Support Team blog:
http://blogs.technet.com/oob/
Opalis Team blog:
http://blogs.technet.com/opalis
Orchestrator Support Team blog:
http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog:
http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog:
http://blogs.technet.com/mdm/
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/