Chatee ahora con Soporte
Chat con el soporte

Change Auditor - For Advanced Users 7.3 - Technical Insight Guide

Change Auditor Services Change Auditor licensing processes Component Start-up Considerations Change Auditor network communications Coordinator internal tasks Registry Settings Change Auditor built-in fault tolerance Change Auditor protection Database Considerations Account exclusions best practices

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
•
Ports and protocols

CN=ChangeAuditor.Coordinator

•
Used by Change Auditor clients, Change Auditor agents and SDK users
•
Used to publish the coordinator’s FQDN, port, and installation name

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

 
Table 5. Quest.ChangeAuditor.Coordinator SCP
Attribute
Attribute Syntax
Function
Default Value

CN

String

SCP Name

CN=ChangeAuditor.Coordinator

keywords

Multi-Value

Storage for the product GUID to facilitate location of only Change Auditor SCPs

F0E51C1A-4424-4387-B7DA-3A245CCEF0

ChangeAuditor.Coordinator

serviceBindinginformation

Multi-Value

Contains Client Port, Public SDK Port, Agent WCF Port, coordinator Version and the InstallationName

<XML>

serviceClassName

String

Used to store the service class for authentication

NPRepository4

serviceDNSName

String

FQDN of the computer running the coordinator service

<Server FQDN>

serviceDNSNameType

String

The DNS record type of the host listed in the serviceDNSName

A

Ports and protocols

Change Auditor uses the following incoming communications ports (listening ports) to establish communication:

 
Table 6. Change Auditor incoming communication ports

Change Auditor client

None

Change Auditor agents

None

Change Auditor coordinators

The coordinator uses the following listening ports that can be dynamically or statically assigned.

•
Client Port
•
Public SDK Port
•
Agent WCF Port
NOTE: By default, the incoming ports are dynamically assigned by Windows. However, you can use the Coordinator Configuration Tool to specify static ports for each of these listening ports. To access the Coordinator Configuration Tool, right-click the coordinator system tray icon and select Coordinator Configuration.

The following table describes each segment of communication that occurs in the Change Auditor system along with technical details of each type of communication.

 
Table 7. Change Auditor communication segments
From/To
Description
Originating Port
Protocol
Destination Port

Client to Coordinator Service

WCF (Windows Communication Foundation)

Dynamic

TCP

Dynamic

Client to Agents
(server and workstation agents)

WCF (Windows Communication Foundation) for configuration refresh

If WCF configuration refresh call fails, falls back to WMI (DCOM) and port 135.

Dynamic

TCP

Dynamic

 

Client to Agents
(server and workstation agents)

SCM (ServiceControlManager) for Agent Service Start\Stop

Dynamic

TCP

135

Coordinator to Server Agents

WCF for Azure/Office 365 configuration information

 

 

8373

Client to SQL Server Database

Connection for archive databases only

Dynamic

TCP

1433

Agent to Coordinator Service

WCF (Windows Communication Foundation)

Dynamic

TCP

Dynamic

Agent to SharePoint SQL Server database

OLEDB SQL Client

Dynamic

TCP

1433

SDK User\Service to Coordinator Service

WCF (Windows Communication Foundation)

Dynamic

TCP

Dynamic

Coordinator to SQL Server Database

.NET SQL

Dynamic

TCP

1433

Coordinator to Azure SQL Managed Instance Database (Private endpoint)

 

.NET SQL

Dynamic

TCP

1433

Coordinator to Azure SQL Managed Instance Database (Public endpoint)

.NET SQL

Dynamic

TCP

3342

Coordinator to Agents
(server and workstation agents)

SMB File Share for Agent Deployment

Dynamic

TCP

445

Coordinator to Agents
(server and workstation agents)

Remote Registry for Agent Deployment (RPC)

Dynamic

TCP

135

*Coordinator to Active Directory LDAP

.NET Directory Services

Dynamic

TCP

389

*Coordinator to Active Directory

Kerberos authenticated connections

Dynamic

TCP

88

*Coordinator to Active Directory GC (Global Catalog)

.NET Directory Services

Dynamic

TCP

3268

Coordinator to DNS Server

DNS name resolution for .NET Directory Services

Dynamic

TCP

53

Web Client to Coordinator

WCF (Windows Communication Foundation)

Dynamic

TCP

Dynamic

Internet Browser (for example, Chrome™ and Internet Explorer) to web client

HTTP/HTTPS

Dynamic

TCP

80/443

*The coordinator requires connectivity to domain controllers in the domain that the server is a member of and also the forest root domain.

Network encryption

Change Auditor uses the following different types of network encryption to protect sensitive information.

•
SMB protocol and share encryption
•
Secure password storage
•
Client to coordinator connection
•
Agent to coordinator connection (version 6.x and 7.0.1)
•
Coordinator to SQL Server connection
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación