I’ve just been doing some P2V work when I encountered the below warning for the first time. I had just run a system scan:
“There is already an SSL certificate associated with port 443 on machine MachineToP2v.yourdomain.com.
Ensure that no application on machine MachineToP2v.yourdomain.com listens for HTTP traffic on TCP port 443 during the conversion. Alternatively use registry key HKLMSoftwareMicrosoftMicrosoft System Center Virtual Machine Manager ServerSettingsP2VBITSTcpPort on the VMM server to change the P2V transfer port number and add the necessary firewall rule for TCP port 443 on machine MachineToP2v.yourdomain.com.
ID: 13252”
The physical server I am going to convert to virtual (P2V) is running an IIS site on TCP 443 or SSL. This would interfere with the P2V conversion because it runs on 443 by default.
The solution was simple:
- Identify an alternative port that you figure is free on your entire network, e.g. I picked 30666.
- Ensure that there are no communication problems between the physical machine and the VMM 2008 server on your alternative port. Check physical and Windows firewalls.
- Add a REG_DWORD called “P2VBITSTcpPort” to “HKLMSoftwareMicrosoftMicrosoft System Center Virtual Machine Manager ServerSettings”. Set the decimal value to your alternative port number.
- Restart the Virtual Machine Manager Service on the VMM 2008 server.
- Start the P2V all over.
That worked fine for me.