I already installed SCVMM on a WS2012 server (SQL is a different, remote server), now I want to install App Controller on the same server where SCVMM is installed.

I came accross this post: http://social.technet.microsoft.com/Forums/en-US/appcontroller/thread/13a6215c-40be-4226-ab84-8c88833891f9/ and this article: http://blogs.msdn.com/b/robertvi/archive/2010/04/30/scvmm-bits-transfer-may-conflict-with-https.aspx

Since SCVMM is already installed I'm unable to change the BITS port to a different on during install that's why I made the change using the above article. Service was restarted, but when I'm trying to create a VM using a VM Template it fails with (this worked minutes before changing the BITS port):

Error (2940)
VMM is unable to complete the requested file transfer. The connection to the HTTP server SCVMM.interexport.local could not be established.
Unknown error (0x80072ee2)

Recommended Action
Ensure that the HTTP service and/or the agent on the machine SCVMM.interexport.local are installed and running and that a firewall is not blocking HTTP/HTTPS traffic on the configured port.

I opened up the firewall using the new BITS TCP 8500 port, made several restarts, but the error in step 1.5 Installing Components does not go away.

Any assistance is greatly appreciated. Avoiding a clean install during which I can choose the BITS port during setup is very much desired.

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

I just tried Storage Migration (we're running 2008 R2 hosts) and it also failed.

EDIT: I changed the port back to 443, restarted the services and it now fails with the default port as well. Please help me out.

• Edited by CypherMike Wednesday, March 27, 2013 1:20 PM

Getting the same thing here. Looks like we are chasing the same bug.

BTW it works now for me with the default 443 port. It appears I restarted the wrong service. Still I need to be able to change this to something else then 443 so I can install App Controller on this server.

Hopefully we'll get some assistance soon.

So you reverted your changes and it functions? I can't revert mine, I have an SSL'ed site running on that particular library server. Using 443 causes everything from the library to fail (attaching ISO's, bits transfers for clones, whatever). If I flip the port, I can attach ISO's, but nothing else functions as expected, and bits fails.

Yes, I reverted, but only for testing purposes. A different solution is needed, unless someone tells me how to run App Controller on a different port.

I'm still waiting for someone from MS to join in this topic.

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

I managed to run App Controller on a custom port.

1. Change the bindig to the desired port (like 444) in IIS Management for the App Controller site

2. Change HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\SiteBindingPort to the desired port (like 444)

3. Change  HKLM\Software\Microsoft\Microsoft SystemCenter App Controller\Settings\Setup\Installer\PortalURL to "https://hostname:444" (where hostname is you server's name)

4. Enable the desired port in the firewall input policy.

5. Restart.

This way I can use my certificate, and I don't have to modify BITS port.

I hope it helps.

• Proposed as answer by Richard RundleMicrosoft employee, Owner Tuesday, June 25, 2013 5:36 AM

Thank you for this. I'll most probably try it soon, do you perhaps know if this is a supported solution? I'm trying to avoid any problems when updates come out...

Can't anyone offer any additional assistance regarding my options (supported ones)? Any one from MSTF?

Same exact problem here - Hoping for an answer.

The fully supported way to do this would be during the installation of App Controller select a port binding other than 443 on the "Configure website" page of App Controller setup.

If you have an existing App Controller install that you want to change this for you can perform an uninstall with retain database and then reinstall and use the same database.

Kind Regards,

Richard

Hey Richard,
I found a KB Article that details steps on how to change BITS to use another port, doesn't that mean these steps would be supported by MS?

http://support.microsoft.com/kb/2405062

To resolve this issue, configure SCVMM to use another port for BITS transfers between its Library Server(s) and the Virtualization Hosts.

Note: You need to ensure that the newly selected port is not blocked by a Firewall between the involved hosts.

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)

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

Hi Keith,

The article you mention applies to, and is a supported process for Virtual Machine Manager 2008.

The steps are not supported for 2012 / 2012 R2. 

Kind Regards,

Richard

Ah my mistake Richard. I take it there is no similar supported solution for 2012 and 2012 R2 then. I ended up just moving my App Controller onto another machine.