Ensure that no application on machine host.domain.tld listens for HTTP traffic on TCP port 443 during the conversion. Ensure that no application on host.domain.tld machine listens for HTTP traffic on TCP port 443 during the conversion. Alternatively use registry key HKLM\Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\P2VBITSTcpPort on the VMM server to change the P2V transfer port number and add the necessary firewall rule for TCP port 443 on machine tbcdc03. Alternatively use registry key HKLM\Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\P2VBITSTcpPort on the VMM server to change the transfer P2V portnumber and add the necessary firewall rule for TCP port 443 on machine.

1. Open Regedit on SCVMM server.
2. Go to –> HKLM \Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings
3. Create a new DWORD (32) entry with the name: P2VBITSTcpPort
4. Give it a port value of say: 441 instead of default of 443.
5. Restart the VMM server to apply the setting.

I have seen this documented in a couple of places now – but I also see a number of people still wondering why this is happening and how to stop it, so I thought I would post it here too.  When you first add a Hyper-V host to SCVMM 2008 you may see a warning icon displayed with the message "Needs Attention" and "Virtualization service version status is not up-to-date".  To get rid of this alert there are three updates that need to be applied to the Hyper-V server:

• KB950050: This is the RTM update for Hyper-V
• KB956589:  This is an update to Hyper-V specifically for SCVMM compatibility
• KB956774: This is an update to the Background Intelligent Transfer Service (BITS) client in Windows Server 2008

Once you have these three updates installed everything should come up green.