SCVMM Integrate VMWare vCenter or Hosts

To integrate VMware vCenter and ESXi hosts with SCVMM, you need to ensure specific network ports are open between:

• SCVMM server ↔ vCenter Server
• SCVMM server ↔ ESXi hosts

This is required for discovery, inventory, and V2V migrations.

---

Required Networking Ports for SCVMM → VMware

1. To vCenter Server

Protocol	Port	Purpose
HTTPS	443	vCenter API communication
HTTP	80	Optional – fallback redirect
TCP	902	File copy & remote console (used during V2V)

These are essential for adding vCenter to SCVMM, discovering VMs, and initiating migrations.

---

 2. To ESXi Hosts

Protocol	Port	Purpose
HTTPS	443	Direct access (if no vCenter)
TCP	902	VIX/V2V file transfer agent
TCP	903	(Optional) Remote console (VMRC)
SSH	22	(Optional) Troubleshooting only

During V2V migration, SCVMM connects to port 902 on the ESXi host to transfer disk files (VMDK) and convert them to VHDX.

---

 

SCVMM → Hyper-V

Make sure SCVMM also has the correct ports open to your Hyper-V hosts:

Protocol	Port	Purpose
WMI/DCOM	135, 49152–65535	Remote management
WinRM	5985 (HTTP), 5986 (HTTPS)	PowerShell remoting
SMB	445	File transfer during V2V
BITS	80/443	Background file transfer

---

Firewall and NAT Considerations

• Open ports bi-directionally if SCVMM and vCenter/ESXi are in different VLANs or across firewalls.
• If using NAT, port forwarding must preserve TCP 902 directly to the ESXi host being migrated.