Knowing what is actually going on under the hood is important. Especially if you are planning implementing firewalls in between the SCVMM box and the HyperV servers or you are installing another application such as Citrix Essentials or any other management app on the same SCVMM box. You need to ensure that you do not have a port conflict. You know, it's hard to find this information. Thought I would at least share.
Name | Direction | Port | NOTES |
SCVMM Admin Consol | Admin PC to SCVMM Server | 8100 | WCF |
SCVMM Self Service Console | Admin PC to Self Service Portal (Host Header) | 80 | WCF |
SCVMM Agent | SCVMM Server to hyperV server | 80 | WRM |
SCVMM Agent | SCVMM Server to hyperV server | 443 | BITS |
SCVMM Library | SCVMM Library to HyperV Host | 80 | BITS |
SCVMM Database | SCVMM Server to SQL Server | 1433 | SQL |
HyperV Host Communication | HyperV host to HyperV host | 80 | BITS |
VM Connect | SCVMM to Hyperv Hosts | 2179 | custom |
SCVMM Self Service portal to HV host | SCVMM to Hyperv Hosts | 3389 | RDP |
SCVMM Self Service portal to VM host | SCVMM Self Service to VM Hosts | 5900 | VMRC |
SCVMM to ESX Management | SCVMM to ESX | 443 | HTTPS |
SCVMM to ESX File Transfer | SCVMM to ESX | 22 | SSH |
Ops Manager Reporting Server | SCVMM to OPS Manager Reporting Server | 80 | HTTP |
I hope this helps, I will add to it when I find more information.
- If you are planning to install the Self Service Console on the SCVMM box, you will have to add a host header. This can be done during install.
