Information about installing Virtual Machine Manager and App Controller on same computer


It is possible to install Microsoft System Center 2012 Virtual Machine Manager and App Controller on the same computer. However, as a best practice and for better performance, we recommend that you install these server roles on separate computers.

For more information about this, see the "Additional Information" section of the following TechNet article:

However, if you must install both server roles on the same computer, we recommend that you use one of the following methods:
  • During Virtual Machine Manager setup, select a port other than port 443 for Background Intelligent Transfer Service (BITS).
  • During App Controller setup, select a port other than port 443.
If Virtual Machine Manager 2012 is using port 443 for BITS, and you install App Controller on the same virtual machine, you will encounter a certificate-binding issue. Because only one certificate can be associated with a port, BITS on Virtual Machine Manager 2012 and App Controller will have to share the same certificate. BITS uses a self-signed certificate and makes sure that the certificate is bound to the port. App Controller is best used with a certificate from a trusted certification authority.

Note You can select any other free port whose number is less than 32768 (for example, port 8500).

More Information

If App Controller and Virtual Machine Manager 2012 are installed on the same computer, you may encounter the following error:

Error (2912)
An internal error has occurred trying to contact an agent on the Hostname server: NO_PARAM: NO_PARAM.
Unknown error (0x80072f0d)

Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.

To resolve this issue, configure Virtual Machine Manager 2012 to use another port for BITS transfers between its Library servers and the virtualization hosts. 

Note Make sure that the newly selected port is not blocked by a firewall between the hosts in question. 

To configure Virtual Machine Manager 2012 to use another port for BITS transfers, follow these steps:

  1. On your Virtual Machine Manager server, open the registry.
  2. Navigate to the following subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings
  3. Locate BITSTcpPort. This should have a value of decimal 443. Change this to some unused port in your environment (for example, port 8500).
  4. Restart the Virtual Machine Manager service so that the change takes effect.

Article ID: 2933853 - Last Review: Feb 21, 2014 - Revision: 1