1. Source Target Host PowerConvert Server PowerConvert Client HTTP: Port 80 TCP (or HTTPS: Port 443 TCP) In addition to HTTP/HTTPS, the following ports are required when communicating with the source: 1) For Windows Source Machines WMI (RPC & DCOM): 135, 137, 138, 139, and 445 TCP (plus randomly assigned ports – see Q20341) SMB: Used during Take Control to transfer the Take Control Package to the source 2) For Linux Source Machines, the following ports are required: SSH & SCP: 22 TCP SCP is used during discovery and take control for Linux sources. HTTP: Port 80 TCP (or HTTPS: Port 443 TCP) In addition to the web services traffic, the following ports are required when communicating with the target: 1) For VMware ESX 2.5.x or earlier, the following port(s) are required: SSH & SCP: 22 TCP -SCP is used during the discovery and deployment of the PlateSpin Take control image 2) For VMware GSX/VMware Server/MSVS hosts -WMI (RPC & DCOM): 135, 137, 138, 139, and 445 TCP (plus randomly assigned ports – see Q20341) File transfer: 3725 TCP Can be encrypted with 128-bit AES GENERAL NOTE: Once a controller is installed on a source or target, the controller will download all subsequent packages via HTTP/HTTPS Target VM HTTP: Port 80 TCP (or HTTPS: Port 443 TCP) For X2V Conversions (except VMware Infrastructure 3)

2. Source Target Host PowerConvert Server PowerConvert Client HTTP: Port 80 TCP (or HTTPS: Port 443 TCP) In addition to HTTP/HTTPS, the following ports are required when communicating with the source: 1) For Windows Source Machines WMI (RPC & DCOM): 135, 137, 138, 139, and 445 TCP (plus randomly assigned ports – see Q20341) SMB: Used during Take Control to transfer the Take Control Package to the source 2) For Linux Source Machines, the following ports are required: SSH & SCP: 22 TCP SCP is used during discovery and take control for Linux sources. HTTPS: Port 443 TCP HTTP: Port 80 TCP (or HTTPS: Port 443 TCP) In addition to the web services traffic on Port 443, the following ports are required for VMware Infrastructure 3 targets, : SSH & SCP: Port 22 TCP - SCP is used during the discovery and deployment of the PlateSpin Take control image File transfer: 3725 TCP Can be encrypted with 128-bit AES GENERAL NOTE: Once a controller is installed on a source or target, the controller will download all subsequent packages via HTTP/HTTPS Target VM HTTP: Port 80 TCP (or HTTPS: Port 443 TCP) For X2V Conversions To VMware Infrastructure 3.x

3. Source PowerConvert Server PowerConvert Client HTTP: Port 80 TCP ( or HTTPS: Port 443 TCP) In addition to HTTP/HTTPS, the following ports are required when communicating with the Windows source: WMI (RPC & DCOM): 135, 137, 138, 139, and 445 TCP (plus randomly assigned ports – see Q20341) SMB: Used during Take Control to transfer the Take Control Package to the source HTTP: Port 80 TCP (or HTTPS: Port 443 TCP) In addition to the web services traffic, the following ports are required when communicating with the PlateSpin Image Server: -WMI (RPC & DCOM): 135, 137, 138, 139, and 445 TCP (plus randomly assigned ports – see Q20341) File transfer: 3725 TCP Can be encrypted with 128-bit AES GENERAL NOTE: Once a controller is installed on a source or target, the controller will download all subsequent packages via HTTP/HTTPS PlateSpin Image Server HTTP: Port 80 TCP (or HTTPS: Port 443 TCP) For X2I Conversions

4. Source PowerConvert Server PowerConvert Client HTTP: Port 80 TCP (or HTTPS: Port 443 TCP) In addition to HTTP/HTTPS, the following ports are required when communicating with the Windows source: WMI (RPC & DCOM): 135, 137, 138, 139, and 445 TCP (plus randomly assigned ports – see Q20341) SMB: Used during Take Control to transfer the Take Control Package to the source HTTP: Port 80 TCP (or HTTPS: Port 443 TCP) In addition to the web services traffic, the following ports are required when communicating with the Target Physical Machine: -WMI (RPC & DCOM): 135, 137, 138, 139, and 445 TCP (plus randomly assigned ports – see Q20341) File transfer: 3725 TCP Can be encrypted with 128-bit AES GENERAL NOTE: Once a controller is installed on a source or target, the controller will download all subsequent packages via HTTP/HTTPS Physical Target HTTP: Port 80 TCP (or HTTPS: Port 443 TCP) For X2P Conversions