Chat now with support
Chat with Support

Change Auditor - For Advanced Users 7.0.1 - Technical Insight Guide

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

Scheduled archive job

select to create a yearly archive database for older events that are no longer required to be represented in your reports.

When scheduling an archive job for the first time it may take a long time to complete (depending on how many years of data you are asking to be archived). Batch limit does not apply to an archive type job.

When running an archive job, you need to pay attention to disk space growth on the SQL server.

 

* 
CAUTION: Carefully review your current jobs before creating a new job or altering an existing job, as it is possible to create purge and archive conflicts.
* 
NOTE: If you have specific purge jobs that you want to complete before a scheduled archive, ensure that you leave enough time between the purge only jobs and the archive job.

Before scheduling a job, ensure that you have reviewed the best practice information in the Change Auditor User Guide - Purging and Archiving your Change Auditor Database: Planning your jobs section.

Scheduled report job

The scheduled report job task checks every five minutes to determine if reporting is enabled and needs to email a search query report. The scheduled reporting feature uses the same SMTP configuration defined for alerting to distribute search query reports via email. Using the Report tab (Search Properties tabs) for a search, you can enable reporting and schedule the distribution of the report. When the scheduled report job task determines a report is to be sent, the report is sent as an attachment via email to the designated recipients. The default is to zip the attachment when the report is 1 MB or greater.

Coordinator Registry Settings

This section provides information about the different registry settings that can be used to control the coordinator.

•
Force agent port
•
Force agent WCF port
•
Force client port
•
Force SDK port
•
Use predefined GC for name resolution
•
Allow collation switch
•
Report zip limit
•
SQL command timeout
•
Enable ChangeAuditor Agent service to start with the Microsoft security update (KB2264107)

Force agent port

Use the following registry setting to force the coordinator to use a specific port to listen for legacy (5.x) agent connections.

Table 10. Registry setting: Force agent port

Location

Registry

Path

HKEY_LOCAL_MACHINE\SOFTWARE\Quest\ChangeAuditor\Coordinator

Value Name

Agent Port

Value Type

DWORD

Value

Port number

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating