HP Insight Orchestration 6.0 User Guide

For more information on using Insight Orchestration console, see the Insight Orchestration console help
system.
Console access to deployed servers
Insight Orchestration supports console access to deployed servers from Insight Orchestration console and
Self-Service Portal. Supported console types include Remote Desktop (RDP), telnet and VM console to ESX
VMs.
Limitations
Telnet and RDP access depend upon network connectivity from the client to deployed servers. Servers deployed
to non-routable networks cannot be accessed by telnet and RDP. Further, for deployed servers that use DHCP
the server hostname must be resolvable for a console connection to succeed.
VM console access depends upon network connectivity from the client to the ESX server that hosts the deployed
VM.
For Internet Explorer (IE) version 7 or later, telnet console must be enabled by editing the registry on the
client. See below for details.
Configuration
Enabling VM console
In order to enable VM console access to deployed VMs in the Insight Orchestration console and Self-Service
portal, complete the following steps to copy the VMware MKS browser plug-ins from an ESX 3.5 update 3
server:
1. On the CMS at a Command Prompt, type cd <IO_install_dir> /conf/console/mks
2. scp –r
<superUser>@<esxHost>:/usr/lib/vmware/webAccess/tomcat/apache-tomcat-*/webapps/ui/plugin/*.
Enabling telnet for IE7 or later
Copy the content below into a file called telnet.reg. Double-click the file to enable IE execution of the
telnet protocol on your client and then restart IE if already open.
Registry file contents:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet
Explorer\Main\FeatureControl\FEATURE_DISABLE_TELNET_PROTOCOL]
"iexplore.exe"=dword:00000000
Support
RDP console is supported for all Windows clients.
Telnet console is supported for Firefox and Internet Explorer clients running on Linux, Windows XP or Windows
2003.
VM console launch is supported for Firefox and Internet Explorer clients running on Linux, Windows XP or
Windows 2003. Console access is supported for all ESX VM guest platforms running on ESX3, ESX3i, ESX4
and ESX4i VM hosts.
Known issues
When launching VM console from an IE client running on the CMS, VM console launch fails. You can work
around this by copying (not moving) libeay32.dll and ssleay32.dll from C:\Program
Files\Internet Explorer\plugins to C:\Program Files\Internet Explorer on the CMS.
Console access to deployed servers 55