Solution 1: 1 PowerConvert Server - PowerPoint PPT Presentation

1 / 4
About This Presentation
Title:

Solution 1: 1 PowerConvert Server

Description:

WMI (RPC & DCOM): 135, 137, 138, 139, and 445 TCP (plus randomly assigned ports see Q20341) ... WMI (RPC & DCOM): 135, 137, 138, 139, and 445 TCP (plus ... – PowerPoint PPT presentation

Number of Views:35
Avg rating:3.0/5.0
Slides: 5
Provided by: peter531
Category:

less

Transcript and Presenter's Notes

Title: Solution 1: 1 PowerConvert Server


1
For X2V Conversions (except VMware Infrastructure
3)
Target VM
Source
File transfer 3725 TCP Can be encrypted with
128-bit AES
HTTP Port 80 TCP (or HTTPS Port 443 TCP)
HTTP Port 80 TCP (or HTTPS Port 443 TCP)
Target Host
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.
  • 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)

PowerConvert Server
HTTP Port 80 TCP (or HTTPS Port 443 TCP)
PowerConvert Client
GENERAL NOTE Once a controller is installed on
a source or target, the controller will download
all subsequent packages via HTTP/HTTPS
2
For X2V Conversions To VMware Infrastructure 3.x
Target VM
Source
File transfer 3725 TCP Can be encrypted with
128-bit AES
HTTP Port 80 TCP (or HTTPS Port 443 TCP)
HTTP Port 80 TCP (or HTTPS Port 443 TCP)
Target Host
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.
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
PowerConvert Server
HTTP Port 80 TCP (or HTTPS Port 443 TCP)
PowerConvert Client
GENERAL NOTE Once a controller is installed on
a source or target, the controller will download
all subsequent packages via HTTP/HTTPS
3
For X2I Conversions
PlateSpin Image Server
Source
File transfer 3725 TCP Can be encrypted with
128-bit AES
HTTP Port 80 TCP (or HTTPS Port 443 TCP)
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)

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
PowerConvert Server
HTTP Port 80 TCP ( or HTTPS Port 443 TCP)
PowerConvert Client
GENERAL NOTE Once a controller is installed on
a source or target, the controller will download
all subsequent packages via HTTP/HTTPS
4
For X2P Conversions
Physical Target
Source
File transfer 3725 TCP Can be encrypted with
128-bit AES
HTTP Port 80 TCP (or HTTPS Port 443 TCP)
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)

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
PowerConvert Server
HTTP Port 80 TCP (or HTTPS Port 443 TCP)
PowerConvert Client
GENERAL NOTE Once a controller is installed on
a source or target, the controller will download
all subsequent packages via HTTP/HTTPS
Write a Comment
User Comments (0)
About PowerShow.com