SCVMM Bits transfer may conflict with HTTPS

SCVMM Bits transfer may conflict with HTTPS

  • Comments 4

Recently, I've seen some problems related with BITS (Background Intelligent Transfer Service) during VM creation from SCVMM.

One error I've seen is that the process appears to hang but was indeed extremely slow (1MB in 1 hour), the other was an error message in SCVMM like:

 

Error (12700)  <path to vhd on destination host> 'The file or directory is corrupted and unreadable' (0x80070570)

 

During VM creation VMM uses BITS to initiate a file transfer from the VMM Library Server to the destination host. The Library Server could be the VMM Server itself (default) or any other server you added as a Library Server. By default the Library Server is using TCP port 443 to handle the transfer, and a SCVMM Certificate is used to encrypt the transfer 

 

In the errors I've seen, there was also a Web Server running on the Library Server and configured to handle HTTPS. It is also listening on port 443 and another Certificate is used. So we have a potential conflict.

To solve this problem you could either move or re-configure the Web Server (e.g. listening on other IP) or change the BITS port SCVMM is using during transfers:

1. On your VMM Server open the Registry

2. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings

3. Locate BITSTcpPort which should have a value of decimal 443. Change this to some port unused in your environment. (e.g. 8500)

3. Restart Virtual Machine Manager Service so that the change takes effect.

 

Cheers

Robert

 

  • Thanks Robert.  That did the trick after a week of digging.

  • Great, it works! And something else - you can change the port while installing SCVMM server/engine.

  • I changed the port as per instructions above since I want to install App Controller on the same VM as SCVMM 2012 SP1 is, but deployment of machines through templates fails. I opened a thread: social.technet.microsoft.com/.../519ed054-1d69-4084-9403-00b351fa192a

    It appears I'm not the only one with this issue: social.technet.microsoft.com/.../d50e46de-1418-4c6e-9333-91e8239db898

    Any assistance would be appreciated.

  • Excellent. Thanks a lot Robert. We were debugging this issue for more than week.

Page 1 of 1 (4 items)
Leave a Comment
  • Please add 2 and 5 and type the answer here:
  • Post