HP Insight Orchestration 6.3 User Guide

Displays a list of available server resources, and enables you to view server details and
manage server resources, create new server pools, and manage the users of a server pool.
• Storage
Displays a list of available storage resources, and enables you to view storage details and
manage storage resources.
• Users
Displays a list of current users and groups, the resources assigned to each user and group,
and role.
• Networks
Displays the available networks and enables you to configure these networks.
• Software
Enables you to view all software and annotate available server deployment folders.
• Calendar
Enables you to search for and view utilization information for users, services, and templates,
graphically displaying usage and conflicts.
For more information on using Insight Orchestration console, see the Insight Orchestration console
online-help system by clicking the ? button in the upper-right portion of the console window.
Create service
To create a service from a template:
1. Select the Templates tab.
2. From the templates list, select the desired template and click Create Service.
3. In the Create Service From Template dialog, set or enter the desired options. If you enter
multiple email addresses in the Email field, separate the addresses with a semicolon (;).
4. Click Submit.
During service creation, IO must generate unique server hostnames. In the Create Service From
Template dialog, the Hostname Completion field specifies the base part of the server hostname.
Hostname Completion has the following limitations:
• Server hostname length: 2–15 characters (15 is a Windows BIOS hostname limitation)
• Server hostname must begin with a letter and end with a number
• The remaining characters in the server hostname can be letters, numbers, or “-”, but cannot
include the following strings: “-TAC”,” -GATEWAY” or “-GW”.
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.
Insight Orchestration Console 73