The Netwrix Network Traffic Compression Service option

The Netwrix Network Traffic Compression Service option
Email It to Me Print this Page
The Netwrix Network Traffic Compression Service (previously known as Lightweight Agent) (*) is realized by a tiny executable that runs on Domain Controllers, collects and pre-filters data and then sends it to the Netwrix Auditor in a highly compressed format. The Traffic Compression Service can help to increase scalability and optimize traffic in poorly connected environments (e.g., if you have multiple Domain Controllers distributed among several geographic locations).

The serviceis non-intrusive and very light weight.It creates a service on the DC and copies a 6KB folder to the machine. The service only runs when the Netwrix Auditor server calls it. In congested systems with a high latency period the servicecan substantially improve data transfer without a significant impact on bandwidth. Using the service results in about a100x reduction in the amount of data being transferred and hasa negligible impact on the targets computer's performance.

Note: If you do not want any extra services running on the Domain Controllers, you can configure Netwrix Auditor to work without the service.

You can adjust the service’s properties by using agent.ini file. Thisallows you to override the default configuration for the particular server you specify.
  1. Navigate to the Netwrix Auditor installtion directory. For example, C:\Program Files (x86)\NetWrix\AD Change Reporter Full Version.
  2. Open agent.ini.
  3. Update it using the syntax below:

  • servername – name of a domain controller for which you want to configure the Network Traffice Compression Serviceusage
  • remote – means that theservice will NOT be used on this particular domain controller
  • agent – means that the serviceWILLbe used to collect data from this particular domain controller
  • skip – means that data will not be collected from this particular domain controller (this option can be used, for example, if the domain controller goes down and should be thus excluded from data collection).
  • skipSilent – same as skip but with all the warnings suppressed
  • suppressWarnings – the data is collected from the particular domain controller but warnings are not reported.
Note: Using 'skip' or ‘skipSilent’ setting can produce incomplete reports (incorrect values in Who Changed/When Changed fields).

Example:  example:

(*) – Only available in the Enterprise Edition of the product
Was this information helpful?