o Each vCenter Converter server must be associated with only one vCenter Server.
o You can install vCenter Converter on:
o Windows Server 2000 SP4 with Update Rollup 1
o Windows Server 2003 SP2 (32 bit & 64 bit)
o Windows Server 2003 R2 SP2 (32 bit & 64 bit)
o Windows Server 2008 vcp-410 (32 bit & 64 bit)
o Windows Vista SP1 (32 bit & 64 bit)
o Windows XP Professional SP3 (32 bit & 64 bit)
o You can install the vCenter Converter CLI on Linux computers.
o The operating system on which you install vCenter Converter server determines which VMs & third-party images you can import, export, &
reconfigure.
o VMs must be powered off before you import them. You cannot import suspended VMs.
o Ports required by vCenter Converter:
Communication path Port
vCenter Converter server to remote physical machine TCP– 445, 139 UDP– 137, 138
vCenter Converter server to vCenter Server 443
vCenter Converter client to vCenter Converter server 443
Physical machine to vCenter Server 443
Physical machine to ESX/ESXi 902
o You must install the Microsoft Sysprep tools on your vCenter Server machine in the appropriate location: C:\Documents & Settings\All
Users\Application Data\VMware\VMware VCENTER\sysprep.
o You can export VMs that vCenter Server manages to managed formats or hosted formats.
o You can download & use the VMware peTool to add storage & network drivers to the boot CD ISO image.
o You can migrate physical & virtual source machines by using the converter-tool executable file & the command-line interface (CLI). This
provides access to functionality without requiring the vSphere Client plug-in. Can run on Windows & Linux computers.
o The vCenter Converter installer does not support Linux. You must download the latest version of the Linux installer.
vCenter Orchestrator 4.0 – Installation and Configuration Guide
o vCenter Orchestrator is a development and process-automation platform that provides a library of extensible workflows.
o Orchestrator exposes every operation in the vCenter Server API.
o Three global user roles: vmware vcp 410 Administrators, Developers, and End Users.
o Support for several OS:
o Server 2003 R2, 32bit, 64bit
o Server 2008, 32bit, 64bit
o Supported directory service types:
o Active Directory
o OpenLDAP
o eDirectory
o Sun Java Directory Server
o Supported browsers:
o IE 6.0 and 7.0
o Firefox 3.0.6 or later
o Safari 3.x (experimental)
o The database is separate from the standard vCenter database.
o Microsoft SQL Server 2005 Enterprise (SP2) and x64 and (SP1)
o Microsoft SQL Server 2005 Standard (SP2), (SP1)
o Microsoft SQL Server 2000 Enterprise (SP4)
o Microsoft SQL Server 2000 vmware vcp 4 Standard (SP4)
o Oracle 10g Enterprise Release 2 (10.2.0.3.0) x32 and x64
o Orchestrator does not support IPv6 operating systems.
o Orchestrator Configuration Service startup type is set to Manual by default.
o http://<computer_DNS_name_or_IP_address>:8282.
o HTTPS connection through port 8283, you must configure Jetty to use SSL.
o You cannot change the vmware default user name.
o You can install vCenter Converter on:
o Windows Server 2000 SP4 with Update Rollup 1
o Windows Server 2003 SP2 (32 bit & 64 bit)
o Windows Server 2003 R2 SP2 (32 bit & 64 bit)
o Windows Server 2008 vcp-410 (32 bit & 64 bit)
o Windows Vista SP1 (32 bit & 64 bit)
o Windows XP Professional SP3 (32 bit & 64 bit)
o You can install the vCenter Converter CLI on Linux computers.
o The operating system on which you install vCenter Converter server determines which VMs & third-party images you can import, export, &
reconfigure.
o VMs must be powered off before you import them. You cannot import suspended VMs.
o Ports required by vCenter Converter:
Communication path Port
vCenter Converter server to remote physical machine TCP– 445, 139 UDP– 137, 138
vCenter Converter server to vCenter Server 443
vCenter Converter client to vCenter Converter server 443
Physical machine to vCenter Server 443
Physical machine to ESX/ESXi 902
o You must install the Microsoft Sysprep tools on your vCenter Server machine in the appropriate location: C:\Documents & Settings\All
Users\Application Data\VMware\VMware VCENTER\sysprep.
o You can export VMs that vCenter Server manages to managed formats or hosted formats.
o You can download & use the VMware peTool to add storage & network drivers to the boot CD ISO image.
o You can migrate physical & virtual source machines by using the converter-tool executable file & the command-line interface (CLI). This
provides access to functionality without requiring the vSphere Client plug-in. Can run on Windows & Linux computers.
o The vCenter Converter installer does not support Linux. You must download the latest version of the Linux installer.
vCenter Orchestrator 4.0 – Installation and Configuration Guide
o vCenter Orchestrator is a development and process-automation platform that provides a library of extensible workflows.
o Orchestrator exposes every operation in the vCenter Server API.
o Three global user roles: vmware vcp 410 Administrators, Developers, and End Users.
o Support for several OS:
o Server 2003 R2, 32bit, 64bit
o Server 2008, 32bit, 64bit
o Supported directory service types:
o Active Directory
o OpenLDAP
o eDirectory
o Sun Java Directory Server
o Supported browsers:
o IE 6.0 and 7.0
o Firefox 3.0.6 or later
o Safari 3.x (experimental)
o The database is separate from the standard vCenter database.
o Microsoft SQL Server 2005 Enterprise (SP2) and x64 and (SP1)
o Microsoft SQL Server 2005 Standard (SP2), (SP1)
o Microsoft SQL Server 2000 Enterprise (SP4)
o Microsoft SQL Server 2000 vmware vcp 4 Standard (SP4)
o Oracle 10g Enterprise Release 2 (10.2.0.3.0) x32 and x64
o Orchestrator does not support IPv6 operating systems.
o Orchestrator Configuration Service startup type is set to Manual by default.
o http://<computer_DNS_name_or_IP_address>:8282.
o HTTPS connection through port 8283, you must configure Jetty to use SSL.
o You cannot change the vmware default user name.
