User's Manual
Table Of Contents
- HP Remote Insight Lights-Out Edition II User Guide
- Notice
- Contents
- Operational overview
- Installing the RILOE II
- Configuring the RILOE II
- Using the RILOE II
- Accessing RILOE II for the first time
- Features of the RILOE II
- Managing the user and configuration settings of the RILOE II
- Using the Remote Console
- Terminal Services pass-through option
- Using virtual devices
- Resetting the RILOE II to the factory default settings
- Getting help
- Pocket PC access with RILOE II
- RILOE II security
- Systems Insight Manager integration
- Directory services
- Overview of directory integration
- Benefits of directory integration
- How directory integration works
- Advantages and disadvantages of schema-free and HP Extended
- Setup for Schema-free directory integration
- Setting up HP schema directory integration
- Features supported by HP schema directory integration
- Setting up directory services
- Directory services support
- Schema required software
- Schema installer
- Management snap-in installer
- Directory services for Active Directory
- Active Directory Lights-Out management
- Directory services for eDirectory
- User login using directory services
- Directory settings
- Directory-enabled remote management
- Scripting, command line, and utility options
- Overview of the Lights-Out DOS utility
- Lights-Out directories migration utilities
- Compatibility
- Pre-migration checklist
- HP Lights-Out directory package
- HPQLOMIG operation
- Finding management processors
- Upgrading firmware on management processors
- Selecting a directory access method
- Naming management processors
- Configuring directories when HP Extended schema is selected
- Configuring directories when schema-free integration is sele
- Setting up management processors for directories
- HPQLOMGC operation
- Lights-Out Configuration Utility
- Using Perl with the XML scripting interface
- HPONCFG
- Remote Insight command language
- RIBCL sample scripts
- RIBCL general guidelines
- XML header
- Data types
- Response definitions
- RIBCL
- LOGIN
- USER_INFO
- ADD_USER
- DELETE_USER
- GET_USER
- MOD_USER
- GET_ALL_USERS
- GET_ALL_USER_INFO
- RIB_INFO
- RESET_RIB
- GET_NETWORK_SETTINGS
- MOD_NETWORK_SETTINGS
- GET_GLOBAL_SETTINGS
- MOD_GLOBAL_SETTINGS
- CLEAR_EVENTLOG
- UPDATE_RIB_FIRMWARE
- GET_FW_VERSION
- HOTKEY_CONFIG
- DIR_INFO
- GET_DIR_CONFIG
- MOD_DIR_CONFIG
- SERVER_INFO
- RESET_SERVER
- INSERT_VIRTUAL_FLOPPY
- EJECT_VIRTUAL_FLOPPY
- COPY_VIRTUAL_FLOPPY
- GET_VF_STATUS
- SET_VF_STATUS
- GET_HOST_POWER_STATUS
- SET_HOST_POWER
- GET_VPB_CABLE_STATUS
- GET_ALL_CABLES_STATUS
- GET_TWOFACTOR_SETTINGS
- MOD_TWOFACTOR_SETTINGS
- Troubleshooting the RILOE II
- Supported client operating systems and browsers
- Supported hardware and software
- Server PCI Slot and Cable Matrix
- Network connection problems
- Alert and trap problems
- NetWare initialization errors
- Miscellaneous problems
- Accessing System Partition Utilities
- Inability to reboot the server
- Inability to upgrade the RILOE II firmware
- Incorrect time or date of entries in the event log
- Interpreting LED indicators
- Invalid Source IP address
- Login name and password problems
- Remote Console mouse control issue
- Resetting the RILOE II to Factory Default Settings
- Virtual Floppy media applet is unresponsive
- Video Problems
- Troubleshooting the host server
- Directory Services errors
- Directory Services schema
- Technical support
- Regulatory compliance notices
- Acronyms and abbreviations
- Index
Using the RILOE II 43
1.
Start the Terminal Services Client Connection Manager, and create a new connection to the terminal
server.
2. Highlight the icon created, and select File>Export. Rename the file with a .cns extension. For
example: myilo.cns.
3. Edit the myilo.cns file by looking for the line Server Port=3389. Replace 3389 with your new port
number and save the file.
4. From the Client Connection Manager, highlight the New Connection icon, and click
File>Import.
5. Double-click the newly created icon to launch terminal server and connect to the new port.
Enabling the Terminal Services Pass-Through option
By default, the Terminal Services pass-through feature is disabled and must be enabled in Global Settings.
Until the Terminal Services pass-through feature is enabled, the Remote Console has the Terminal Services
button deactivated, and the console session error message Remote Session already in use by
another user is misleading.
Use of the Terminal Services pass-through feature requires installation of the latest Lights-Out Management
Interface Driver and Terminal Services pass-through Service for Microsoft® Windows® on the server. The
interface driver must be installed before installing the service.
When the Terminal Services pass-through option is set to Enabled or Automatic on the Global Settings
page and the Terminal Services Client is installed on the Windows® client (installs by default on
Windows® XP), the Terminal Services button is enabled. When the Terminal Services button is clicked, the
applet tries to launch the Terminal Services, even if the server is not running a Windows® operating
system.
You must comply with Microsoft® license requirements which are the same as connecting through the
server's NIC. For instance, when set for administrative access, Terminal Services does not allow more
than two connections, regardless of whether the connections are through the server's NIC or RILOE II or
both.
Terminal Services Pass-Through status
The RILOE II Status page displays the status of the Terminal Services pass-through feature, as follows:
• Server software not detected
• Available for use
• In use
The UID light flashes whenever a Terminal Services connection is active through the RILOE II. It flashes at
the same frequency and duty cycle as when the Remote Console is active.
Terminal Services warning message
Terminals Services users operating on Windows® 2003 Server might notice the following when using the
Terminal Services pass-through feature of RILOE II. If a Terminal Services session is established through
RILOE II and a second Terminal Services session is established by a Windows® administrator (Console
mode), the first Terminal Services session is disconnected. However, the first Terminal Services session
does not receive the warning message indicating the disconnection until approximately one minute later.
During this one-minute period, the first Terminal Services session is available or active. This is normal
behavior, but it is different than the behavior observed when both Terminal Services sessions are
established by Windows® administrators. In that case, the warning message is received by the first
Terminal Services session immediately.










