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
106xxx | LDAP Feature for the RCSxxx
aspects of AD. DNS is used to determine the network coordinates of each
Domain Controller so that the Dell RCSs can gracefully handle situations where
some Domain Controllers are not available on the network. DNS SRV records
are used for this purpose so the Dell RCSs always attempt to contact alternative
Domain Controllers at the nearest site first, depending on the administrative
settings configured in the SRV records.
Object Classes
Within each domain, there is another hierarchy of objects designed to store
information about various entities and groupings of entities. Such entities are
represented in AD by object classes used to define “containers” that help
organize groupings of objects. Other object classes represent entities such as
network users, computers, printers, or network services. Two types of container
object classes are of special interest: Group and Organizational Unit (OU).
These two object classes allow the AD Administrator to define groupings of
entities for the purpose of simplifying the application of access controls and
other administrative policies. For example, a domain may be configured to have
an OU container named Engineering, which contains several Group objects
named according to function, like Hardware, Software, and Support; each of the
groups is configured with a membership list of User objects and perhaps
Computer objects. Yet another level of hierarchy can be configured by nesting
groups; a nesting is formed by including the name of a Group object in the
membership of another Group object. It should be noted here that each AD
Group object has an associated scope that is used to configure the types of
nesting relationships it is allowed to have with other groups; for example, when
scope is set to Universal, the group may participate in nesting that crosses
domain boundaries but when scope is set to Local it may not participate in
such nesting. Rules for nesting are available in the AD product documentation
available from Microsoft. The suite of Dell RCSs is designed to support all
nesting rules defined for AD.