Understanding the User/Endpoint Directory

The User/Endpoint Directory is a graphical representation of the organization of your Control Manager network. Control Manager 6.0 Service Pack 2 allows you to organize your network into groups of users or endpoints.

The default User/Endpoint Directory follows this structure:
Note:
All users are placed in the Users tree under the following circumstances:
  • If a local user logs on to a registered endpoint

  • If they are part of Active Directory and the administrator enables Active Directory integration

Users cannot be removed from the complete users list even if a user creates their own grouping.

Consequently, all endpoints are lumped in the Endpoints tree, with Endpoint Type and Operating System as default filters. These default trees and grouping can neither be deleted nor renamed.

  • Users: Offers a list of all users in your managed network

  • Endpoints: Offers a list of all endpoints and devices in your managed network (from endpoint-based managed products)

  • Active Directory: Offers a one-to-one mapping of your Active Directory structure

    Control Manager supports synchronization of Active Directory domains coming from the same forest.

You can organize the User/Endpoint Directory through any of these methods:
  • Filter-based grouping: Use filters to group users or endpoints based on specific characteristics

  • Tag-based grouping: Use tags to assign users or endpoints manually

  • Active Directory mapping: Synchronize automatically with your Active Directory server

User/Endpoint Directory on Parent Control Manager Servers

Administrators of parent Control Manager can monitor entities of child servers through the User/Endpoint Directory. By default, child servers will sync the following information with its parent server hourly:
Note:

The timing is based on the time interval setting in the SystemConfiguration.xml.

The default is every 30 minutes, as set by the m_uiCasMcpChildTriggerDataSyncFreqInMin parameter.

  • Managed entity and physical machine relationship

  • Corresponding policy of each endpoint entity

  • Non-Active Directory users in the incident log