User's Manual
Table Of Contents
- Product Overview
- Features and Benefits
- Reduce Cable Bulk
- KVM Switching Capabilities
- Multiplatform Support
- True Serial Capabilities
- Local and Remote User Interfaces
- Virtual Media and Smart Card-capable Switches
- On-board Web Interface
- Access the Switch Using a Standard TCP/IP Network
- Encryption
- Video
- Flash Upgradeable
- Tier Expansion
- Avocent Management Software Plug-in
- FIPS cryptographic module
- Sample Configuration
- Safety Precautions
- General
- LAN Options
- Features and Benefits
- Installation
- Local and Remote Configuration
- Local User Interface (UI)
- OBWI
- Using the User Interfaces
- Launching a Session
- Scan Mode
- Viewing System Information
- RCS Tools
- Network Settings
- DNS Settings
- NTP Settings
- SNMP Settings
- Auditing Event Settings
- Setting Event Destinations
- Ports - Configuring SIPs
- Power Device Settings
- Local Port UI Settings
- Modem Settings
- Setup Settings - Port Security
- Sessions
- Setting Up User Accounts
- LDAP
- Override Admin
- Active Sessions
- The Video Viewer Window
- LDAP Feature for the RCS
- The Structure of Active Directory
- Standard Schema versus Dell Extended Schema
- Standard Installation
- Configure the Override Admin Account
- Configuring DNS Settings
- Configuring the Network Time Protocol (NTP) Settings
- Configuring the LDAP Authentication Parameters
- Enabling LDAP Authentication
- Entering Authentication Parameters - Operational Modes
- Entering Extension Options - Active Directory LDAP
- Entering Authentication Parameters - Standard LDAP
- Entering Authentication Parameters - Custom IP Port Assignments
- Completing LDAP Configuration
- Secondary LDAP Settings - Standard Configuration
- Setting up the RCS for performing Standard LDAP queries
- Search Configuration Settings
- Query Mode Selection Settings
- Group Configuration Parameters
- Secondary LDAP Settings - Active Directory Configuration
- LDAP SSL Certificates
- CA Certificate Information Display
- Configuring Group Objects
- Configuring Active Directory with Dell Schema Extensions to Access Your RCS
- Adding Users and Privileges to Active Directory with Dell Schema Extensions
- Using Dell Association Objects Syntax
- Console Redirection Access Security
- Using Active Directory to Log In to the RCS
- Target Device Naming Requirements for LDAP Implementation
- Frequently Asked Questions
- Appendix A: Terminal Operations
- Appendix B: Using SIPs
- Appendix C: MIB and SNMP Traps
- Appendix D: Cable Pinouts Information
- Appendix E: UTP Cabling
- Appendix F: Sun Advanced Key Emulation
- Appendix G: Technical Specifications
- Appendix H: Technical Support
- Bookmarks

LDAP Feature for the RCSxxx | xxx139
Dell Extended Schema Active Directory Object Overview
For each of the physical RCSs on the network that you want to integrate with
Active Directory for Authentication and Authorization, you must create at least
one RCS Device Object to represent the physical switch and one Association
Object. The Association object is used to link together the users or groups with
a specific set of privileges to one or more SIPs. This model provides an
Administrator maximum flexibility over the different combinations of users,
RCS privileges, and SIPs on the Remote Console Switch without adding too
much complexity
The RCS Device Object is the link to the RCS for querying Active Directory for
authentication and authorization. When a RCS is added to the network, the
Administrator must configure the RCS and its device object with its Active
Directory name so that users can perform authentication and authorization with
Active Directory. The Administrator will also need to add the Remote Console
Switch to at least one Association Object in order for users to authenticate.
You can create as many Association Objects as you want, and each Association
Object can be linked to as many users, groups of users, or RCS Device Objects
as desired. The users and RCS Device Objects can be members of any domain
in the enterprise.
However, each Association Object may be linked (or, may link users, groups of
users, or RCS Device Objects) to only one Privilege Object. A Privilege Object
allows an Administrator to control which users have what kind of privileges on
specific SIPs.
The following figure illustrates that the Association Object provides the
connection that is needed for all of the Authentication and Authorization.
Figure 5.11: Typical Setup for Active Directory Objects