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

Directory-enabled remote management 103
Directory-enabled remote management
In this section
Introduction to directory-enabled remote management .............................................................................. 103
Creating roles to follow organizational structure ...................................................................................... 103
How directory login restrictions are enforced........................................................................................... 105
Using bulk import tools.......................................................................................................................... 108
Introduction to directory-enabled remote management
This section is for administrators who are familiar with directory services and the RILOE II product and
want to use the HP schema directory integration option for RILOE II. You must be familiar with the
“Directory services (on page 75)" section and comfortable with setting up and understanding the
examples.
Directory-enabled remote management enables you to:
• Create Lights-Out Management Objects
You must create one LOM device object to represent each device that will use the directory service to
authenticate and authorize users. Refer to the "Directory services (on page 75)" section for
additional information on creating LOM device objects for Active Directory ("Directory services for
Active Directory" on page 83) and eDirectory ("Directory services for eDirectory" on page 92). In
general, you can use the HP provided snap-ins to create objects. It is useful to give the LOM device
objects meaningful names, such as the device network address, DNS name, host server name, or
serial number.
• Configure the Lights-Out management devices
Every LOM device that uses the directory service to authenticate and authorize users must be
configured with the appropriate directory settings. Refer to "Configuring directory settings" for
details on the specific directory settings. In general, you can configure each device with the
appropriate directory server address, LOM object distinguished name, and any user contexts. The
server address is either the IP address or DNS name of a local directory server or, for more
redundancy, a multi-host DNS name.
Creating roles to follow organizational structure
Often, the administrators within an organization are placed into a hierarchy in which subordinate
administrators must assign rights independently of ranking administrators. In this case, it is useful to have
one role that represents the rights assigned by higher-level administrators and to allow the subordinate
administrators to create and manage their own roles.
Using existing groups
Many organizations will have their users and administrators arranged into groups. In many cases, it is
convenient to use the existing groups and associate the groups with one or more Lights-Out Management
role objects. When the devices are associated with the role objects, the administrator controls access to
the Lights-Out devices associated with the role by adding or deleting members from the groups.










