Change Auditor - For Advanced Users 7.0.2 - Technical Insight Guide

User counts

The coordinator determines maximum licensed users by comparing the value associated with the component license to the total count of users in each domain. The coordinator does this by issuing LDAP queries to Active Directory using specific filters for a precise count.

(&(objectCategory=Person)(objectClass=user)(userAccountControl:1.2.840.113556.1.4.803:=512)(!userAccountControl:1.2.840.113556.1.4.803:=2))

(&(samAccountType=805306368)(|(&(!userAccountControl:1.2.840.113556.1.4.803:=2)(msExchHomeServerName=*))(&(userAccountControl:1.2.840.113556.1.4.803:=2)(msExchMasterAccountSid=*))))

Workstation counts are based on the actual number of workstations harvested in the topology.

Change Auditor network communications

This section explains the network communications used by Change Auditor including a description of how it uses Service Connection Points (SCPs) to locate the coordinator, the listening ports used for communication between the Change Auditor services, and the network encryption used to secure sensitive information.

Service Connection Points

Change Auditor publishes SCPs in Active Directory so that clients, agents, and other third-party applications can automatically locate the coordinator. When clients or agents start up, they search Active Directory for the SCP objects to retrieve connection information for the coordinator such as host name, listening port, and other authentication information.

The SCP objects are published directly subordinate to the coordinator’s computer object in Active Directory. SCP objects can be viewed and updated using Microsoft ADSI Edit MMC snap-in.

The coordinator installs and maintains two separate SCPs. The coordinator checks and updates these Active Directory objects each time the coordinator service starts up.

CN=ChangeAuditor.Coordinator

The coordinator SCP contains the following key elements, which are stored in its Active Directory attributes: