From e1a3e75949853d83d6f8157ee7647e4708dcaff3 Mon Sep 17 00:00:00 2001 From: hilram7 <212961752+hilram7@users.noreply.github.com> Date: Tue, 30 Jun 2026 18:48:18 -0400 Subject: [PATCH 1/7] =?UTF-8?q?feat(kb):=20add=2010=20Change=20Tracker=20K?= =?UTF-8?q?B=20articles=20(batch=202b=20=E2=80=94=20Denis)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Migrates 10 configuration, database, and general troubleshooting articles from staging repo. Fixes applied: truncated frontmatter restored, kb.netwrix.com links removed, Salesforce CDN images replaced with placeholders, typos and encoding errors fixed, copy/paste errors corrected, structure aligned to KB standards. --- .../planned-changes-report.md | 47 +++++++++++++ .../express-agent-database-log-location.md | 37 ++++++++++ .../fast-cloud-proxy-settings.md | 47 +++++++++++++ .../fileaccessed-events.md | 69 +++++++++++++++++++ .../upload-compliance-template.md | 40 +++++++++++ .../change-db-location-windows.md | 35 ++++++++++ .../mongodb-out-of-memory.md | 59 ++++++++++++++++ .../mongodump-binary-not-found.md | 55 +++++++++++++++ .../mongodump-socket-buffer-error.md | 47 +++++++++++++ .../object-reference-error-groups-page.md | 61 ++++++++++++++++ 10 files changed, 497 insertions(+) create mode 100644 docs/kb/changetracker/audit-and-logging/planned-changes-report.md create mode 100644 docs/kb/changetracker/configuration-and-setup/express-agent-database-log-location.md create mode 100644 docs/kb/changetracker/configuration-and-setup/fast-cloud-proxy-settings.md create mode 100644 docs/kb/changetracker/configuration-and-setup/fileaccessed-events.md create mode 100644 docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md create mode 100644 docs/kb/changetracker/database-and-diagnostics/change-db-location-windows.md create mode 100644 docs/kb/changetracker/database-and-diagnostics/mongodb-out-of-memory.md create mode 100644 docs/kb/changetracker/database-and-diagnostics/mongodump-binary-not-found.md create mode 100644 docs/kb/changetracker/database-and-diagnostics/mongodump-socket-buffer-error.md create mode 100644 docs/kb/changetracker/troubleshooting-and-errors/object-reference-error-groups-page.md diff --git a/docs/kb/changetracker/audit-and-logging/planned-changes-report.md b/docs/kb/changetracker/audit-and-logging/planned-changes-report.md new file mode 100644 index 0000000000..2174c4cbf5 --- /dev/null +++ b/docs/kb/changetracker/audit-and-logging/planned-changes-report.md @@ -0,0 +1,47 @@ +--- +title: How to Run a Report That Shows Created Planned Changes and Who Made Them +description: >- + Shows how to run an events report that includes Created Planned Changes, + Approved Changes, and the user who performed these actions in Netwrix Change + Tracker. +sidebar_label: Planned Changes Report +keywords: + - planned change + - events + - report + - export + - audit + - Netwrix Change Tracker + - CSV + - event filter + - approved changes + - Comma Separated Text +products: + - change-tracker +tags: + - kb + - audit-and-logging +knowledge_article_id: +--- + +# How to Run a Report That Shows Created Planned Changes and Who Made Them + +## Overview + +This article shows how to run a report that displays Created Planned Changes, Changes That Were Approved, and the User that performed these actions in Netwrix Change Tracker. + +## Instructions + +1. Go to **Events**. +2. Select specific or all devices and click **Filter**. +3. In the **Event Filter** window, enter `Planned Change` in the Text Search field. Select **Audit** in Event Type and click **Apply**. + + + +4. To export these reports, click **Export** and select your preferred file type. + + + +The exported report includes details such as Created Planned Changes, Approved Changes, and the user who performed each action. The available file types include Comma Separated Text (CSV). + + diff --git a/docs/kb/changetracker/configuration-and-setup/express-agent-database-log-location.md b/docs/kb/changetracker/configuration-and-setup/express-agent-database-log-location.md new file mode 100644 index 0000000000..d5b0d63dda --- /dev/null +++ b/docs/kb/changetracker/configuration-and-setup/express-agent-database-log-location.md @@ -0,0 +1,37 @@ +--- +title: "How to Change the Location of the Express Agent's Database and Log Files" +description: >- + Use the ConfigPath switch in expressAgent.ini to change the Express Agent + database and log files location on Netwrix Change Tracker. +sidebar_label: Express Agent Database and Log Location +keywords: + - express agent + - ConfigPath + - expressAgent.ini + - database location + - log files + - /var/nnt + - configuration + - Netwrix Change Tracker + - agent settings + - file path +products: + - change-tracker +tags: + - kb + - configuration-and-setup +knowledge_article_id: +--- + +# How to Change the Location of the Express Agent's Database and Log Files + +## Instructions + +Change the Express Agent's database and log files location by editing the `ConfigPath` switch in `expressAgent.ini`: + +```ini +[ExpressAgent] +ConfigPath=/var/nnt/expressagent/ +``` + +Set the `ConfigPath` value to the desired directory where the Express Agent should store its database and log files. diff --git a/docs/kb/changetracker/configuration-and-setup/fast-cloud-proxy-settings.md b/docs/kb/changetracker/configuration-and-setup/fast-cloud-proxy-settings.md new file mode 100644 index 0000000000..4ea07e8b36 --- /dev/null +++ b/docs/kb/changetracker/configuration-and-setup/fast-cloud-proxy-settings.md @@ -0,0 +1,47 @@ +--- +title: How to Configure the FAST Cloud Integration with Proxy Internet Settings +description: >- + If you use a proxy on your Netwrix Change Tracker Server and FAST Cloud does + not work, configure the proxy for IIS processes by adding a system environment + variable. This article shows the exact steps to set the ALL_PROXY variable. +sidebar_label: FAST Cloud Proxy Settings +keywords: + - Netwrix Change Tracker + - FAST Cloud + - proxy + - ALL_PROXY + - environment variable + - IIS + - proxy settings + - server restart + - internet connection + - system variables +products: + - change-tracker +tags: + - kb + - configuration-and-setup +knowledge_article_id: +--- + +# How to Configure the FAST Cloud Integration with Proxy Internet Settings + +## Overview + +If you have set up a proxy internet connection on your Netwrix Change Tracker Server and you find that FAST Cloud is not working as expected, follow the instructions below to configure proxy settings for the IIS processes. + +## Instructions + +1. Open **Windows Control Panel**. +2. Choose **System**. +3. Choose **Advanced system settings**. +4. On the Advanced tab, click **Environment Variables**. +5. Click **New** to create a new environment variable under the **System Variables** heading. +6. Enter Variable Name: **ALL_PROXY**. +7. Enter Variable Value: `http://IPADDRESS:PORT`. + + > **NOTE:** This should be the IP and port of the proxy server. + +8. Select **OK**. +9. After creating the environment variable, click **OK** to apply the changes. +10. Once the environment variable is configured, restart the Netwrix Change Tracker Server. The FAST Cloud should now function as expected. diff --git a/docs/kb/changetracker/configuration-and-setup/fileaccessed-events.md b/docs/kb/changetracker/configuration-and-setup/fileaccessed-events.md new file mode 100644 index 0000000000..e905ae49f5 --- /dev/null +++ b/docs/kb/changetracker/configuration-and-setup/fileaccessed-events.md @@ -0,0 +1,69 @@ +--- +title: Why Am I Receiving FileAccessed Events in Change Tracker? +description: >- + Explains why you are receiving File Access ("fileaccessed") events in Netwrix + Change Tracker, what they indicate, and how to enable or disable them via + configuration templates. +sidebar_label: FileAccessed Events +keywords: + - fileaccessed + - file access + - Netwrix Change Tracker + - configuration template + - tracked attributes + - baseline + - device templates + - file monitoring + - read operation + - file attributes +products: + - change-tracker +tags: + - kb + - configuration-and-setup +knowledge_article_id: +--- + +# Why Am I Receiving FileAccessed Events in Change Tracker? + +## Overview + +This article describes why you are receiving File Access events in Netwrix Change Tracker, what they are, and how to disable or enable them. + +The "fileaccessed" event is a "read" operation for the file shown in the details. This does not mean someone changed the file — it simply means the file was accessed (or read), whether by a person or software. Think of it as someone opening a Word document. If you were tracking that, you would see the same notification for the Word document simply being opened. + + + +## How to Enable or Disable FileAccessed Events + +The steps below show you how to enable or disable these event types in Netwrix Change Tracker. + +### Disabling File Access Events + +To disable file access events, follow the steps below: + +1. This setting is configured from a device **Configuration Template** which is appended to a group. Devices within that group then receive the template. +2. Go to the **Settings Tile** > Click on the **Configuration Templates** Navigation button to the left. +3. Find the Configuration Template that you want to use for these event types, or create a new one by pressing the **Create a Template** button. +4. Click the **Edit** button on the template you want to modify. +5. For the desired path, locate the **Tracked Attributes** column. Click the **Edit** button and change this to `File attributes (excluding contents) only`. +6. Click **Save Changes** at the top of the page. +7. If this is a new template, apply it to the group of devices by going to **Settings** > **Groups** > Select the group > **Device Templates** > **Add a template**. + +> **NOTE:** When you update a configuration template, the agent does a re-baseline of the files within the defined parameters. Changes to the files are not visible until after the baseline is completed. A baseline typically takes about 15-20 minutes to complete on a Windows device. If you are going to test a change on this folder, and you update it as per the instructions above, please test it about 30 minutes after you have saved the change to the template so that the agent has adequate time to complete its baseline process. + +### Enabling File Access Events + +To enable file access events, follow the steps below: + +1. This setting is configured from a device **Configuration Template** which is appended to a group. Devices within that group then receive the template. +2. Go to the **Settings Tile** > Click on the **Configuration Templates** Navigation button to the left. +3. Find the Configuration Template that you want to use for these event types, or create a new one by pressing the **Create a Template** button. +4. Click the **Edit** button on the template you want to modify. +5. For the desired path, locate the **Tracked Attributes** column. Click the **Edit** button and change this to `All file and folder attributes excluding contents`. +6. Click **Save Changes** at the top of the page. +7. If this is a new template, apply it to the group of devices by going to **Settings** > **Groups** > Select the group > **Device Templates** > **Add a template**. + +> **NOTE:** When you update a configuration template, the agent does a re-baseline of the files within the defined parameters. Changes to the files are not visible until after the baseline is completed. A baseline typically takes about 15-20 minutes to complete on a Windows device. If you are going to test a change on this folder, and you update it as per the instructions above, please test it about 30 minutes after you have saved the change to the template so that the agent has adequate time to complete its baseline process. + + diff --git a/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md b/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md new file mode 100644 index 0000000000..e43a2e82b9 --- /dev/null +++ b/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md @@ -0,0 +1,40 @@ +--- +title: How to Upload a Compliance Template to Change Tracker +description: >- + This article shows how to upload a compliance template to Netwrix Change + Tracker using the Settings > Compliance Reports Templates page, with + step-by-step instructions. +sidebar_label: Upload Compliance Template +keywords: + - Netwrix Change Tracker + - compliance template + - upload template + - compliance reports + - templates + - Compliance Reports Templates + - settings + - overwrite template + - configuration + - compliance reporting +products: + - change-tracker +tags: + - kb + - configuration-and-setup +knowledge_article_id: +--- + +# How to Upload a Compliance Template to Change Tracker + +## Overview + +This guide provides step-by-step instructions on how to upload a compliance template into Netwrix Change Tracker. + +## Instructions + +1. Click on the **Settings** tile. +2. On the left Navigation Menu, select **Compliance Reports Templates**. +3. Click on the **Upload Templates** button and browse to your template. +4. Once your template is selected, you can decide if you want Netwrix Change Tracker to automatically overwrite templates of the same name. If you do, check the corresponding box; if not, do not check it. +5. Click the **Upload Template** button. +6. The progress bar shows 100% once it has completed uploading. diff --git a/docs/kb/changetracker/database-and-diagnostics/change-db-location-windows.md b/docs/kb/changetracker/database-and-diagnostics/change-db-location-windows.md new file mode 100644 index 0000000000..be909e29f8 --- /dev/null +++ b/docs/kb/changetracker/database-and-diagnostics/change-db-location-windows.md @@ -0,0 +1,35 @@ +--- +title: Windows — Change the DB Location +description: >- + Instructions to change the MongoDB database file location used by Netwrix + Change Tracker on Windows. Steps include stopping IIS and MongoDB services, + editing mongod.conf, and restarting services. +sidebar_label: Change DB Location (Windows) +keywords: + - MongoDB + - mongod.conf + - dbpath + - iisreset + - Netwrix Change Tracker + - Windows Services + - Change DB location + - Mongo DB service + - NNT Change Tracker Suite + - database migration +products: + - change-tracker +tags: + - kb + - database-and-diagnostics +knowledge_article_id: +--- + +# Windows — Change the DB Location + +## Instructions + +1. Stop the IIS Web server using the command line `iisreset /stop`, or use the **IIS Management Console**, or use the **Windows Services Console**. +2. Stop the MongoDB service using the **Windows Services Console**. +3. Edit the `mongod.conf` file located in `C:\Program Files\NNT Change Tracker Suite\Gen7\MongoDB\conf`. +4. Edit the `dbpath` parameter to change the location for DB files. +5. Start the MongoDB service, followed by `iisreset /start`. diff --git a/docs/kb/changetracker/database-and-diagnostics/mongodb-out-of-memory.md b/docs/kb/changetracker/database-and-diagnostics/mongodb-out-of-memory.md new file mode 100644 index 0000000000..90e03dadff --- /dev/null +++ b/docs/kb/changetracker/database-and-diagnostics/mongodb-out-of-memory.md @@ -0,0 +1,59 @@ +--- +title: "MongoDB Log Fix: Out of Memory" +description: >- + Explains how to resolve MongoDB "out of memory" errors by configuring Windows + virtual memory (page file) to System managed so the Netwrix Change Tracker + database and Hub Server can function properly. +sidebar_label: "MongoDB Out of Memory" +keywords: + - MongoDB + - out of memory + - virtual memory + - page file + - Netwrix Change Tracker + - SYSDM.CPL + - Windows performance + - database crash + - Hub Server + - system managed +products: + - change-tracker +tags: + - kb + - database-and-diagnostics +knowledge_article_id: +--- + +# MongoDB Log Fix: Out of Memory + +## Symptom + +The MongoDB service crashes with an out of memory error. An example log entry: + +```text +2017-10-27T10:23:48.348-0400 F - [conn3080] out of memory. +``` + +## Cause + +The MongoDB service crashed because the system ran out of physical and virtual memory. Typically, this is due to misconfigured Page File settings. + +## Resolution + +If you are receiving this error, the Netwrix Change Tracker database and Hub Server are NOT functioning. This is a critical error and monitoring cannot continue until it is resolved. To resolve this error: + +1. Open **Run** by pressing the `Windows+R` keys on your keyboard. +2. Type `SYSDM.CPL` and press **Enter**. +3. This opens **Advanced System Settings**. Click on the **Advanced** tab. +4. Under Performance, click **Settings...**. +5. In the Performance Options menu, click the **Advanced** tab. +6. Under Virtual Memory, click **Change**. +7. Verify that Virtual Memory is set to **System managed**. + + + +8. If it is not set to **System managed**, configure it by selecting the **System managed size** radio button. +9. Click **OK**. +10. In some scenarios, it may be best to reboot the server. + +> **NOTE:** MongoDB has garbage collection which cleans up physical and virtual memory. MongoDB tries to reserve as much memory as possible, even though it is not using it. It gladly gives up this memory to the systems that need it. Any queries run get stored into the page file for easy access. If this is not system managed, when it reaches the limit, it crashes the MongoDB database service. Having the C drive set to system managed is the best way to ensure excellent performance from both the system and the database itself. diff --git a/docs/kb/changetracker/database-and-diagnostics/mongodump-binary-not-found.md b/docs/kb/changetracker/database-and-diagnostics/mongodump-binary-not-found.md new file mode 100644 index 0000000000..e23ad939a3 --- /dev/null +++ b/docs/kb/changetracker/database-and-diagnostics/mongodump-binary-not-found.md @@ -0,0 +1,55 @@ +--- +title: "How to Fix: Mongodump Binary Does Not Exist in Specified Location Error" +description: >- + This article explains how to resolve the "Mongodump binary does not exist in + specified location" error when exporting a database in Netwrix Change Tracker + by adding the MongoDumpPath configuration setting. +sidebar_label: Mongodump Binary Not Found +keywords: + - mongodump + - MongoDB + - MongoDumpPath + - Change Tracker + - export + - configuration + - mongodump binary + - system settings + - database export + - advanced options +products: + - change-tracker +tags: + - kb + - database-and-diagnostics +knowledge_article_id: +--- + +# How to Fix: Mongodump Binary Does Not Exist in Specified Location Error + +## Symptom + +When exporting a database in Netwrix Change Tracker, you receive the following error: + +```text +Mongodump binary does not exist in specified location +``` + + + +## Resolution + +1. Open **Settings**. +2. In the sidebar, click **System Settings**. +3. Scroll down and click **Show Advanced Options**. +4. Scroll down until you see **Configuration Settings**. +5. In **Configuration Settings**, click **Add Config Item**. +6. In the **Description** box, type `MongoDumpPath`. +7. In the **Value** box, enter the MongoDump path. Example: `C:\Program Files\NNT Change Tracker Suite\Gen7\MongoDB\bin\mongodump.exe` + + > **NOTE:** Be sure to change the drive path depending on where you have MongoDB installed. + +8. Click the **Update** button to save this information. + + + + diff --git a/docs/kb/changetracker/database-and-diagnostics/mongodump-socket-buffer-error.md b/docs/kb/changetracker/database-and-diagnostics/mongodump-socket-buffer-error.md new file mode 100644 index 0000000000..c04578ed5c --- /dev/null +++ b/docs/kb/changetracker/database-and-diagnostics/mongodump-socket-buffer-error.md @@ -0,0 +1,47 @@ +--- +title: >- + MongoDB Log Fix: Error Reading Collection — An Operation on a Socket Could Not + Be Performed Because the System Lacked Sufficient Buffer Space +description: >- + Shows how to troubleshoot a MongoDump failure caused by a Windows socket + buffer issue and links to Microsoft guidance for resolution. +sidebar_label: MongoDump Socket Buffer Error +keywords: + - MongoDump + - MongoDB + - WSARecv + - WSAENOBUFS + - socket buffer + - TCP port + - Windows networking + - mongodump error + - buffer space + - error reading collection +products: + - change-tracker +tags: + - kb + - database-and-diagnostics +knowledge_article_id: +--- + +# MongoDB Log Fix: Error Reading Collection — An Operation on a Socket Could Not Be Performed + +## Symptom + +When you attempt to perform a MongoDump on your MongoDB database, the dump fails with the following error: + +```text +Failed: error reading collection: WSARecv tcp 127.0.0.1:50290: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. +``` + +## Cause + +This error is linked to a Windows issue rather than a MongoDB issue. The error occurs when a system tries to connect to a TCP port that is greater than 5000. The TCP port number is referenced in the error message. + +## Resolution + +Review the Microsoft guidance on this issue: +[https://learn.microsoft.com/en-GB/troubleshoot/windows-client/networking/connect-tcp-greater-than-5000-error-wsaenobufs-10055](https://learn.microsoft.com/en-GB/troubleshoot/windows-client/networking/connect-tcp-greater-than-5000-error-wsaenobufs-10055) + +If possible, implement the steps the Microsoft article recommends and then re-run the MongoDump task. diff --git a/docs/kb/changetracker/troubleshooting-and-errors/object-reference-error-groups-page.md b/docs/kb/changetracker/troubleshooting-and-errors/object-reference-error-groups-page.md new file mode 100644 index 0000000000..6563a36fe6 --- /dev/null +++ b/docs/kb/changetracker/troubleshooting-and-errors/object-reference-error-groups-page.md @@ -0,0 +1,61 @@ +--- +title: >- + System Error — Object Reference Not Set to an Instance of an Object — Cannot + View Groups Page in Netwrix Change Tracker +description: >- + You can log in to Netwrix Change Tracker but receive "System Error - Object + Reference not set to an instance of an object" when opening the Groups page. + This article explains how to resolve the issue by verifying user rights and + Active Directory integration settings. +sidebar_label: Object Reference Error on Groups Page +keywords: + - Change Tracker + - Netwrix Change Tracker + - Object Reference + - groups page + - permissions + - AD integration + - users + - login error + - system error + - user rights + - FQDN + - Active Directory +products: + - change-tracker +tags: + - kb + - troubleshooting-and-errors +knowledge_article_id: +--- + +# System Error — Object Reference Not Set to an Instance of an Object — Cannot View Groups Page in Netwrix Change Tracker + +## Symptom + +Netwrix Change Tracker lets you log in; however, when you go to **Settings > Groups** you receive the following error: + +```text +System Error - Object Reference not set to an instance of an object +``` + + + +## Cause + +This error occurs when your account does not have the correct user rights to view the Groups page. + +## Resolution + +1. Log out of the Netwrix Change Tracker user account that you are currently logged in as. +2. Log in as the default **admin** account in Netwrix Change Tracker. +3. Navigate to the **Groups** tab in the **Settings** tile. +4. Do you see the groups? You should be able to. This means that the account you previously had logged in as did not have the user rights to view the device groups. +5. Go to **Settings > Users**. +6. Do you have Active Directory integration enabled? If so, does your AD integration require you to supply the FQDN in order to log in? + + + +7. If the above is true, view the username in **Settings > Users** of Netwrix Change Tracker. This needs to be the same as the exact username you provide during login. The username must include the full domain prefix (e.g., `DOMAIN\username`) to match what Active Directory expects. + + From ce3522bb148e7db7180cbf7e21b790a62fb3a449 Mon Sep 17 00:00:00 2001 From: hilram7 <212961752+hilram7@users.noreply.github.com> Date: Wed, 1 Jul 2026 16:15:56 -0400 Subject: [PATCH 2/7] fix(kb): apply SME feedback to batch 2b Change Tracker articles - fileaccessed-events: update terminology to match 8.2 UI (Configuration Templates to Policy Templates, Device Templates to Policy Templates, Groups to Device Groups); correct Tracked Attributes dropdown text - Retire change-db-location-windows (near-duplicate of existing 8.2 product doc at install/databasecustompathoverview/databasecustompathwindows) - Add knowledge_article_id to fast-cloud-proxy-settings and fileaccessed-events --- .../fast-cloud-proxy-settings.md | 2 +- .../fileaccessed-events.md | 32 ++++++++--------- .../change-db-location-windows.md | 35 ------------------- 3 files changed, 17 insertions(+), 52 deletions(-) delete mode 100644 docs/kb/changetracker/database-and-diagnostics/change-db-location-windows.md diff --git a/docs/kb/changetracker/configuration-and-setup/fast-cloud-proxy-settings.md b/docs/kb/changetracker/configuration-and-setup/fast-cloud-proxy-settings.md index 4ea07e8b36..19adde9c6d 100644 --- a/docs/kb/changetracker/configuration-and-setup/fast-cloud-proxy-settings.md +++ b/docs/kb/changetracker/configuration-and-setup/fast-cloud-proxy-settings.md @@ -21,7 +21,7 @@ products: tags: - kb - configuration-and-setup -knowledge_article_id: +knowledge_article_id: ka0Qk000000D34vIAC --- # How to Configure the FAST Cloud Integration with Proxy Internet Settings diff --git a/docs/kb/changetracker/configuration-and-setup/fileaccessed-events.md b/docs/kb/changetracker/configuration-and-setup/fileaccessed-events.md index e905ae49f5..dc93ae3c64 100644 --- a/docs/kb/changetracker/configuration-and-setup/fileaccessed-events.md +++ b/docs/kb/changetracker/configuration-and-setup/fileaccessed-events.md @@ -3,16 +3,16 @@ title: Why Am I Receiving FileAccessed Events in Change Tracker? description: >- Explains why you are receiving File Access ("fileaccessed") events in Netwrix Change Tracker, what they indicate, and how to enable or disable them via - configuration templates. + policy templates. sidebar_label: FileAccessed Events keywords: - fileaccessed - file access - Netwrix Change Tracker - - configuration template + - policy template - tracked attributes - baseline - - device templates + - device groups - file monitoring - read operation - file attributes @@ -21,7 +21,7 @@ products: tags: - kb - configuration-and-setup -knowledge_article_id: +knowledge_article_id: ka0Qk000000DlkHIAS --- # Why Am I Receiving FileAccessed Events in Change Tracker? @@ -42,28 +42,28 @@ The steps below show you how to enable or disable these event types in Netwrix C To disable file access events, follow the steps below: -1. This setting is configured from a device **Configuration Template** which is appended to a group. Devices within that group then receive the template. -2. Go to the **Settings Tile** > Click on the **Configuration Templates** Navigation button to the left. -3. Find the Configuration Template that you want to use for these event types, or create a new one by pressing the **Create a Template** button. +1. This setting is configured from a device **Policy Template** which is appended to a group. Devices within that group then receive the template. +2. Go to the **Settings Tile** > Click on the **Policy Templates** Navigation button to the left. +3. Find the Policy Template that you want to use for these event types, or create a new one by pressing the **Create a Template** button. 4. Click the **Edit** button on the template you want to modify. -5. For the desired path, locate the **Tracked Attributes** column. Click the **Edit** button and change this to `File attributes (excluding contents) only`. +5. For the desired path, locate the **Tracked Attributes** column. Click the **Edit** button and change this to `File Attributes – Excluding contents only`. 6. Click **Save Changes** at the top of the page. -7. If this is a new template, apply it to the group of devices by going to **Settings** > **Groups** > Select the group > **Device Templates** > **Add a template**. +7. If this is a new template, apply it to the group of devices by going to **Settings** > **Device Groups** > Select the group > **Policy Templates** > **Add a template**. -> **NOTE:** When you update a configuration template, the agent does a re-baseline of the files within the defined parameters. Changes to the files are not visible until after the baseline is completed. A baseline typically takes about 15-20 minutes to complete on a Windows device. If you are going to test a change on this folder, and you update it as per the instructions above, please test it about 30 minutes after you have saved the change to the template so that the agent has adequate time to complete its baseline process. +> **NOTE:** When you update a policy template, the agent does a re-baseline of the files within the defined parameters. Changes to the files are not visible until after the baseline is completed. A baseline typically takes about 15-20 minutes to complete on a Windows device. If you are going to test a change on this folder, and you update it as per the instructions above, please test it about 30 minutes after you have saved the change to the template so that the agent has adequate time to complete its baseline process. ### Enabling File Access Events To enable file access events, follow the steps below: -1. This setting is configured from a device **Configuration Template** which is appended to a group. Devices within that group then receive the template. -2. Go to the **Settings Tile** > Click on the **Configuration Templates** Navigation button to the left. -3. Find the Configuration Template that you want to use for these event types, or create a new one by pressing the **Create a Template** button. +1. This setting is configured from a device **Policy Template** which is appended to a group. Devices within that group then receive the template. +2. Go to the **Settings Tile** > Click on the **Policy Templates** Navigation button to the left. +3. Find the Policy Template that you want to use for these event types, or create a new one by pressing the **Create a Template** button. 4. Click the **Edit** button on the template you want to modify. 5. For the desired path, locate the **Tracked Attributes** column. Click the **Edit** button and change this to `All file and folder attributes excluding contents`. 6. Click **Save Changes** at the top of the page. -7. If this is a new template, apply it to the group of devices by going to **Settings** > **Groups** > Select the group > **Device Templates** > **Add a template**. +7. If this is a new template, apply it to the group of devices by going to **Settings** > **Device Groups** > Select the group > **Policy Templates** > **Add a template**. -> **NOTE:** When you update a configuration template, the agent does a re-baseline of the files within the defined parameters. Changes to the files are not visible until after the baseline is completed. A baseline typically takes about 15-20 minutes to complete on a Windows device. If you are going to test a change on this folder, and you update it as per the instructions above, please test it about 30 minutes after you have saved the change to the template so that the agent has adequate time to complete its baseline process. +> **NOTE:** When you update a policy template, the agent does a re-baseline of the files within the defined parameters. Changes to the files are not visible until after the baseline is completed. A baseline typically takes about 15-20 minutes to complete on a Windows device. If you are going to test a change on this folder, and you update it as per the instructions above, please test it about 30 minutes after you have saved the change to the template so that the agent has adequate time to complete its baseline process. - + diff --git a/docs/kb/changetracker/database-and-diagnostics/change-db-location-windows.md b/docs/kb/changetracker/database-and-diagnostics/change-db-location-windows.md deleted file mode 100644 index be909e29f8..0000000000 --- a/docs/kb/changetracker/database-and-diagnostics/change-db-location-windows.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Windows — Change the DB Location -description: >- - Instructions to change the MongoDB database file location used by Netwrix - Change Tracker on Windows. Steps include stopping IIS and MongoDB services, - editing mongod.conf, and restarting services. -sidebar_label: Change DB Location (Windows) -keywords: - - MongoDB - - mongod.conf - - dbpath - - iisreset - - Netwrix Change Tracker - - Windows Services - - Change DB location - - Mongo DB service - - NNT Change Tracker Suite - - database migration -products: - - change-tracker -tags: - - kb - - database-and-diagnostics -knowledge_article_id: ---- - -# Windows — Change the DB Location - -## Instructions - -1. Stop the IIS Web server using the command line `iisreset /stop`, or use the **IIS Management Console**, or use the **Windows Services Console**. -2. Stop the MongoDB service using the **Windows Services Console**. -3. Edit the `mongod.conf` file located in `C:\Program Files\NNT Change Tracker Suite\Gen7\MongoDB\conf`. -4. Edit the `dbpath` parameter to change the location for DB files. -5. Start the MongoDB service, followed by `iisreset /start`. From 39e61a079a17c13c1c1df9a3411d4483f650757d Mon Sep 17 00:00:00 2001 From: hilram7 <212961752+hilram7@users.noreply.github.com> Date: Wed, 1 Jul 2026 16:19:34 -0400 Subject: [PATCH 3/7] chore(kb): add knowledge_article_id to remaining batch 2b articles --- .../changetracker/audit-and-logging/planned-changes-report.md | 2 +- .../express-agent-database-log-location.md | 2 +- .../configuration-and-setup/upload-compliance-template.md | 2 +- .../database-and-diagnostics/mongodb-out-of-memory.md | 2 +- .../database-and-diagnostics/mongodump-binary-not-found.md | 2 +- .../database-and-diagnostics/mongodump-socket-buffer-error.md | 2 +- .../object-reference-error-groups-page.md | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/kb/changetracker/audit-and-logging/planned-changes-report.md b/docs/kb/changetracker/audit-and-logging/planned-changes-report.md index 2174c4cbf5..dceb06d202 100644 --- a/docs/kb/changetracker/audit-and-logging/planned-changes-report.md +++ b/docs/kb/changetracker/audit-and-logging/planned-changes-report.md @@ -21,7 +21,7 @@ products: tags: - kb - audit-and-logging -knowledge_article_id: +knowledge_article_id: ka04u000000Hd9zAAC --- # How to Run a Report That Shows Created Planned Changes and Who Made Them diff --git a/docs/kb/changetracker/configuration-and-setup/express-agent-database-log-location.md b/docs/kb/changetracker/configuration-and-setup/express-agent-database-log-location.md index d5b0d63dda..eddbcddd15 100644 --- a/docs/kb/changetracker/configuration-and-setup/express-agent-database-log-location.md +++ b/docs/kb/changetracker/configuration-and-setup/express-agent-database-log-location.md @@ -20,7 +20,7 @@ products: tags: - kb - configuration-and-setup -knowledge_article_id: +knowledge_article_id: ka04u000000HdBHAA0 --- # How to Change the Location of the Express Agent's Database and Log Files diff --git a/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md b/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md index e43a2e82b9..182e2b726d 100644 --- a/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md +++ b/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md @@ -21,7 +21,7 @@ products: tags: - kb - configuration-and-setup -knowledge_article_id: +knowledge_article_id: ka04u000000Hd9XAAS --- # How to Upload a Compliance Template to Change Tracker diff --git a/docs/kb/changetracker/database-and-diagnostics/mongodb-out-of-memory.md b/docs/kb/changetracker/database-and-diagnostics/mongodb-out-of-memory.md index 90e03dadff..870b46fc5e 100644 --- a/docs/kb/changetracker/database-and-diagnostics/mongodb-out-of-memory.md +++ b/docs/kb/changetracker/database-and-diagnostics/mongodb-out-of-memory.md @@ -21,7 +21,7 @@ products: tags: - kb - database-and-diagnostics -knowledge_article_id: +knowledge_article_id: ka04u000000QmjwAAC --- # MongoDB Log Fix: Out of Memory diff --git a/docs/kb/changetracker/database-and-diagnostics/mongodump-binary-not-found.md b/docs/kb/changetracker/database-and-diagnostics/mongodump-binary-not-found.md index e23ad939a3..ff4dbab679 100644 --- a/docs/kb/changetracker/database-and-diagnostics/mongodump-binary-not-found.md +++ b/docs/kb/changetracker/database-and-diagnostics/mongodump-binary-not-found.md @@ -21,7 +21,7 @@ products: tags: - kb - database-and-diagnostics -knowledge_article_id: +knowledge_article_id: ka04u000000Hd9lAAC --- # How to Fix: Mongodump Binary Does Not Exist in Specified Location Error diff --git a/docs/kb/changetracker/database-and-diagnostics/mongodump-socket-buffer-error.md b/docs/kb/changetracker/database-and-diagnostics/mongodump-socket-buffer-error.md index c04578ed5c..3f0a1c4e42 100644 --- a/docs/kb/changetracker/database-and-diagnostics/mongodump-socket-buffer-error.md +++ b/docs/kb/changetracker/database-and-diagnostics/mongodump-socket-buffer-error.md @@ -22,7 +22,7 @@ products: tags: - kb - database-and-diagnostics -knowledge_article_id: +knowledge_article_id: ka04u000000QmlUAAS --- # MongoDB Log Fix: Error Reading Collection — An Operation on a Socket Could Not Be Performed diff --git a/docs/kb/changetracker/troubleshooting-and-errors/object-reference-error-groups-page.md b/docs/kb/changetracker/troubleshooting-and-errors/object-reference-error-groups-page.md index 6563a36fe6..42f7a7d39a 100644 --- a/docs/kb/changetracker/troubleshooting-and-errors/object-reference-error-groups-page.md +++ b/docs/kb/changetracker/troubleshooting-and-errors/object-reference-error-groups-page.md @@ -26,7 +26,7 @@ products: tags: - kb - troubleshooting-and-errors -knowledge_article_id: +knowledge_article_id: ka04u000000HdAGAA0 --- # System Error — Object Reference Not Set to an Instance of an Object — Cannot View Groups Page in Netwrix Change Tracker From 660c796b2ee919a6bd38176921e41f6cc2e7ee64 Mon Sep 17 00:00:00 2001 From: hilram7 <212961752+hilram7@users.noreply.github.com> Date: Wed, 1 Jul 2026 19:04:59 -0400 Subject: [PATCH 4/7] fix(kb): apply pre-review polish to batch 2b articles --- .../planned-changes-report.md | 7 ++-- .../express-agent-database-log-location.md | 9 ++++- .../fileaccessed-events.md | 40 +++++++++---------- .../upload-compliance-template.md | 5 ++- .../mongodb-out-of-memory.md | 2 +- .../mongodump-binary-not-found.md | 4 ++ .../mongodump-socket-buffer-error.md | 4 +- .../object-reference-error-groups-page.md | 11 ++--- 8 files changed, 44 insertions(+), 38 deletions(-) diff --git a/docs/kb/changetracker/audit-and-logging/planned-changes-report.md b/docs/kb/changetracker/audit-and-logging/planned-changes-report.md index dceb06d202..b9fd6f47f0 100644 --- a/docs/kb/changetracker/audit-and-logging/planned-changes-report.md +++ b/docs/kb/changetracker/audit-and-logging/planned-changes-report.md @@ -15,7 +15,6 @@ keywords: - CSV - event filter - approved changes - - Comma Separated Text products: - change-tracker tags: @@ -38,10 +37,10 @@ This article shows how to run a report that displays Created Planned Changes, Ch -4. To export these reports, click **Export** and select your preferred file type. +4. To export the report, click **Export** and select your preferred file type. - + > **NOTE:** For details on available export formats, see [Exporting Events to CSV, PDF, or XLSX](/docs/kb/changetracker/configuration-and-setup/exporting-events-to-csv-pdf-or-xlsx). The exported report includes Created Planned Changes, Approved Changes, and the user who performed each action. -The exported report includes details such as Created Planned Changes, Approved Changes, and the user who performed each action. The available file types include Comma Separated Text (CSV). + diff --git a/docs/kb/changetracker/configuration-and-setup/express-agent-database-log-location.md b/docs/kb/changetracker/configuration-and-setup/express-agent-database-log-location.md index eddbcddd15..f99d48efee 100644 --- a/docs/kb/changetracker/configuration-and-setup/express-agent-database-log-location.md +++ b/docs/kb/changetracker/configuration-and-setup/express-agent-database-log-location.md @@ -25,13 +25,18 @@ knowledge_article_id: ka04u000000HdBHAA0 # How to Change the Location of the Express Agent's Database and Log Files + + ## Instructions -Change the Express Agent's database and log files location by editing the `ConfigPath` switch in `expressAgent.ini`: +1. Change the Express Agent's database and log files location by editing the `ConfigPath` switch in `expressAgent.ini`: ```ini [ExpressAgent] ConfigPath=/var/nnt/expressagent/ ``` -Set the `ConfigPath` value to the desired directory where the Express Agent should store its database and log files. +2. Set the `ConfigPath` value to the desired directory where the Express Agent should store its database and log files. diff --git a/docs/kb/changetracker/configuration-and-setup/fileaccessed-events.md b/docs/kb/changetracker/configuration-and-setup/fileaccessed-events.md index dc93ae3c64..bdf565de5c 100644 --- a/docs/kb/changetracker/configuration-and-setup/fileaccessed-events.md +++ b/docs/kb/changetracker/configuration-and-setup/fileaccessed-events.md @@ -30,40 +30,36 @@ knowledge_article_id: ka0Qk000000DlkHIAS This article describes why you are receiving File Access events in Netwrix Change Tracker, what they are, and how to disable or enable them. -The "fileaccessed" event is a "read" operation for the file shown in the details. This does not mean someone changed the file — it simply means the file was accessed (or read), whether by a person or software. Think of it as someone opening a Word document. If you were tracking that, you would see the same notification for the Word document simply being opened. +The `fileaccessed` event is a read operation for the file shown in the details. This does not mean someone changed the file — it simply means the file was accessed (or read), whether by a person or software. Think of it as someone opening a Word document. If you were tracking that, you would see the same notification for the Word document simply being opened. ## How to Enable or Disable FileAccessed Events -The steps below show you how to enable or disable these event types in Netwrix Change Tracker. +These events are controlled from a **Policy Template** applied to a device group — devices in the group inherit the template's settings. -### Disabling File Access Events +> **NOTE:** When you update a policy template, the agent does a re-baseline of the files within the defined parameters. Changes to the files are not visible until after the baseline is completed. A baseline typically takes about 15-20 minutes to complete on a Windows device. If you are testing a change to this folder, wait about 30 minutes after saving the template so the agent has time to complete its baseline process. -To disable file access events, follow the steps below: +### Disabling File Access Events -1. This setting is configured from a device **Policy Template** which is appended to a group. Devices within that group then receive the template. -2. Go to the **Settings Tile** > Click on the **Policy Templates** Navigation button to the left. -3. Find the Policy Template that you want to use for these event types, or create a new one by pressing the **Create a Template** button. -4. Click the **Edit** button on the template you want to modify. -5. For the desired path, locate the **Tracked Attributes** column. Click the **Edit** button and change this to `File Attributes – Excluding contents only`. -6. Click **Save Changes** at the top of the page. -7. If this is a new template, apply it to the group of devices by going to **Settings** > **Device Groups** > Select the group > **Policy Templates** > **Add a template**. +To disable file access events: -> **NOTE:** When you update a policy template, the agent does a re-baseline of the files within the defined parameters. Changes to the files are not visible until after the baseline is completed. A baseline typically takes about 15-20 minutes to complete on a Windows device. If you are going to test a change on this folder, and you update it as per the instructions above, please test it about 30 minutes after you have saved the change to the template so that the agent has adequate time to complete its baseline process. +1. Go to the **Settings Tile** > Click on the **Policy Templates** Navigation button to the left. +2. Find the Policy Template that you want to use for these event types, or create a new one by pressing the **Create a Template** button. +3. Click the **Edit** button on the template you want to modify. +4. For the desired path, locate the **Tracked Attributes** column. Click the **Edit** button and change this to `File Attributes – Excluding contents only`. +5. Click **Save Changes** at the top of the page. +6. If this is a new template, apply it to the group of devices by going to **Settings** > **Device Groups** > Select the group > **Policy Templates** > **Add a template**. ### Enabling File Access Events -To enable file access events, follow the steps below: - -1. This setting is configured from a device **Policy Template** which is appended to a group. Devices within that group then receive the template. -2. Go to the **Settings Tile** > Click on the **Policy Templates** Navigation button to the left. -3. Find the Policy Template that you want to use for these event types, or create a new one by pressing the **Create a Template** button. -4. Click the **Edit** button on the template you want to modify. -5. For the desired path, locate the **Tracked Attributes** column. Click the **Edit** button and change this to `All file and folder attributes excluding contents`. -6. Click **Save Changes** at the top of the page. -7. If this is a new template, apply it to the group of devices by going to **Settings** > **Device Groups** > Select the group > **Policy Templates** > **Add a template**. +To enable file access events: -> **NOTE:** When you update a policy template, the agent does a re-baseline of the files within the defined parameters. Changes to the files are not visible until after the baseline is completed. A baseline typically takes about 15-20 minutes to complete on a Windows device. If you are going to test a change on this folder, and you update it as per the instructions above, please test it about 30 minutes after you have saved the change to the template so that the agent has adequate time to complete its baseline process. +1. Go to the **Settings Tile** > Click on the **Policy Templates** Navigation button to the left. +2. Find the Policy Template that you want to use for these event types, or create a new one by pressing the **Create a Template** button. +3. Click the **Edit** button on the template you want to modify. +4. For the desired path, locate the **Tracked Attributes** column. Click the **Edit** button and change this to `All file and folder attributes excluding contents`. +5. Click **Save Changes** at the top of the page. +6. If this is a new template, apply it to the group of devices by going to **Settings** > **Device Groups** > Select the group > **Policy Templates** > **Add a template**. diff --git a/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md b/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md index 182e2b726d..8cf83cd39b 100644 --- a/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md +++ b/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md @@ -35,6 +35,7 @@ This guide provides step-by-step instructions on how to upload a compliance temp 1. Click on the **Settings** tile. 2. On the left Navigation Menu, select **Compliance Reports Templates**. 3. Click on the **Upload Templates** button and browse to your template. -4. Once your template is selected, you can decide if you want Netwrix Change Tracker to automatically overwrite templates of the same name. If you do, check the corresponding box; if not, do not check it. +4. If you wish to automatically overwrite existing templates with the same name, check the corresponding box. 5. Click the **Upload Template** button. -6. The progress bar shows 100% once it has completed uploading. + +The progress bar should show 100% once the upload completes. diff --git a/docs/kb/changetracker/database-and-diagnostics/mongodb-out-of-memory.md b/docs/kb/changetracker/database-and-diagnostics/mongodb-out-of-memory.md index 870b46fc5e..3aaf5a2a3f 100644 --- a/docs/kb/changetracker/database-and-diagnostics/mongodb-out-of-memory.md +++ b/docs/kb/changetracker/database-and-diagnostics/mongodb-out-of-memory.md @@ -56,4 +56,4 @@ If you are receiving this error, the Netwrix Change Tracker database and Hub Ser 9. Click **OK**. 10. In some scenarios, it may be best to reboot the server. -> **NOTE:** MongoDB has garbage collection which cleans up physical and virtual memory. MongoDB tries to reserve as much memory as possible, even though it is not using it. It gladly gives up this memory to the systems that need it. Any queries run get stored into the page file for easy access. If this is not system managed, when it reaches the limit, it crashes the MongoDB database service. Having the C drive set to system managed is the best way to ensure excellent performance from both the system and the database itself. +> **NOTE:** MongoDB reserves as much memory as it can and stores queries in the page file for quick access. When the page file is not set to system managed, it can hit its size limit and crash MongoDB. System managed sizing lets Windows expand the page file as needed. diff --git a/docs/kb/changetracker/database-and-diagnostics/mongodump-binary-not-found.md b/docs/kb/changetracker/database-and-diagnostics/mongodump-binary-not-found.md index ff4dbab679..6f6dc311a4 100644 --- a/docs/kb/changetracker/database-and-diagnostics/mongodump-binary-not-found.md +++ b/docs/kb/changetracker/database-and-diagnostics/mongodump-binary-not-found.md @@ -36,6 +36,10 @@ Mongodump binary does not exist in specified location +## Cause + +The `MongoDumpPath` configuration setting is missing or points to the wrong location. Netwrix Change Tracker uses this setting to locate the mongodump binary when exporting a database. + ## Resolution 1. Open **Settings**. diff --git a/docs/kb/changetracker/database-and-diagnostics/mongodump-socket-buffer-error.md b/docs/kb/changetracker/database-and-diagnostics/mongodump-socket-buffer-error.md index 3f0a1c4e42..419c607326 100644 --- a/docs/kb/changetracker/database-and-diagnostics/mongodump-socket-buffer-error.md +++ b/docs/kb/changetracker/database-and-diagnostics/mongodump-socket-buffer-error.md @@ -41,7 +41,7 @@ This error is linked to a Windows issue rather than a MongoDB issue. The error o ## Resolution -Review the Microsoft guidance on this issue: +1. Review the Microsoft guidance on this issue: [https://learn.microsoft.com/en-GB/troubleshoot/windows-client/networking/connect-tcp-greater-than-5000-error-wsaenobufs-10055](https://learn.microsoft.com/en-GB/troubleshoot/windows-client/networking/connect-tcp-greater-than-5000-error-wsaenobufs-10055) -If possible, implement the steps the Microsoft article recommends and then re-run the MongoDump task. +2. If possible, implement the steps the Microsoft article recommends and then re-run the MongoDump task. diff --git a/docs/kb/changetracker/troubleshooting-and-errors/object-reference-error-groups-page.md b/docs/kb/changetracker/troubleshooting-and-errors/object-reference-error-groups-page.md index 42f7a7d39a..a44274f727 100644 --- a/docs/kb/changetracker/troubleshooting-and-errors/object-reference-error-groups-page.md +++ b/docs/kb/changetracker/troubleshooting-and-errors/object-reference-error-groups-page.md @@ -33,7 +33,7 @@ knowledge_article_id: ka04u000000HdAGAA0 ## Symptom -Netwrix Change Tracker lets you log in; however, when you go to **Settings > Groups** you receive the following error: +You can log in to Netwrix Change Tracker, but when you go to **Settings > Groups**, you receive the following error: ```text System Error - Object Reference not set to an instance of an object @@ -47,15 +47,16 @@ This error occurs when your account does not have the correct user rights to vie ## Resolution -1. Log out of the Netwrix Change Tracker user account that you are currently logged in as. +1. Log out of the Netwrix Change Tracker user account that you are currently using. 2. Log in as the default **admin** account in Netwrix Change Tracker. 3. Navigate to the **Groups** tab in the **Settings** tile. -4. Do you see the groups? You should be able to. This means that the account you previously had logged in as did not have the user rights to view the device groups. +4. Verify that the groups are visible. If they are, the previous account lacks the user rights required to view device groups. 5. Go to **Settings > Users**. -6. Do you have Active Directory integration enabled? If so, does your AD integration require you to supply the FQDN in order to log in? +6. Check whether Active Directory integration is enabled and whether it requires a fully qualified domain name (FQDN) for login. -7. If the above is true, view the username in **Settings > Users** of Netwrix Change Tracker. This needs to be the same as the exact username you provide during login. The username must include the full domain prefix (e.g., `DOMAIN\username`) to match what Active Directory expects. +7. If AD integration requires an FQDN, review the username in **Settings > Users**. +8. Verify that the username matches exactly what the user provides at login, including the domain prefix (for example, `DOMAIN\username`). From a6524b46745d968f39e4e79078911f1e35c2825d Mon Sep 17 00:00:00 2001 From: dgoskolli Date: Wed, 8 Jul 2026 15:14:07 -0400 Subject: [PATCH 5/7] Update planned-changes-report.md Added additional details for Date/Time as well as updated navigation for exporting the report --- .../audit-and-logging/planned-changes-report.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/kb/changetracker/audit-and-logging/planned-changes-report.md b/docs/kb/changetracker/audit-and-logging/planned-changes-report.md index b9fd6f47f0..48301aa8b1 100644 --- a/docs/kb/changetracker/audit-and-logging/planned-changes-report.md +++ b/docs/kb/changetracker/audit-and-logging/planned-changes-report.md @@ -33,11 +33,12 @@ This article shows how to run a report that displays Created Planned Changes, Ch 1. Go to **Events**. 2. Select specific or all devices and click **Filter**. -3. In the **Event Filter** window, enter `Planned Change` in the Text Search field. Select **Audit** in Event Type and click **Apply**. +3. In the **Date & Time** Window, select the time period for which you'd like to view created planned changes. +4. In the **Event Filter** window, enter `Planned Change` in the Text Search field. Select **Audit** in Event Type and click **Apply**. -4. To export the report, click **Export** and select your preferred file type. +5. To export the report, click **Query/Report** > **Export Now** and select your preferred file type. > **NOTE:** For details on available export formats, see [Exporting Events to CSV, PDF, or XLSX](/docs/kb/changetracker/configuration-and-setup/exporting-events-to-csv-pdf-or-xlsx). The exported report includes Created Planned Changes, Approved Changes, and the user who performed each action. From bfb5a77bf51204f496954242d27c0280e2443cda Mon Sep 17 00:00:00 2001 From: dgoskolli Date: Wed, 8 Jul 2026 15:23:55 -0400 Subject: [PATCH 6/7] Update upload-compliance-template.md Updated navigation steps to the correct page, changing from "Compliance Report Templates" to "Policy Templates". Also Updated title to Compliance/Tracking as both are performed using the same steps --- .../upload-compliance-template.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md b/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md index 8cf83cd39b..aa12a766ad 100644 --- a/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md +++ b/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md @@ -1,13 +1,14 @@ --- -title: How to Upload a Compliance Template to Change Tracker +title: How to Upload a Compliance/Tracking Template to Change Tracker description: >- - This article shows how to upload a compliance template to Netwrix Change - Tracker using the Settings > Compliance Reports Templates page, with + This article shows how to upload a compliance/tracking template to Netwrix Change + Tracker using the Settings > Policy Templates page, with step-by-step instructions. -sidebar_label: Upload Compliance Template +sidebar_label: Upload Compliance/Tracking Template keywords: - Netwrix Change Tracker - compliance template + - tracking template - upload template - compliance reports - templates @@ -24,17 +25,16 @@ tags: knowledge_article_id: ka04u000000Hd9XAAS --- -# How to Upload a Compliance Template to Change Tracker +# How to Upload a Compliance/Tracking Template to Change Tracker ## Overview -This guide provides step-by-step instructions on how to upload a compliance template into Netwrix Change Tracker. +This guide provides step-by-step instructions on how to upload a compliance/tracking template into Netwrix Change Tracker. ## Instructions -1. Click on the **Settings** tile. -2. On the left Navigation Menu, select **Compliance Reports Templates**. -3. Click on the **Upload Templates** button and browse to your template. +1. Click on the **Settings** dropdown, then click **Policy Templates**. +2. Click the **Actions** dropdown, then click **Upload Templates** button and browse to your template. 4. If you wish to automatically overwrite existing templates with the same name, check the corresponding box. 5. Click the **Upload Template** button. From f7c0f2f8e9307513bcd50945769997520b468acb Mon Sep 17 00:00:00 2001 From: hilram7 <212961752+hilram7@users.noreply.github.com> Date: Wed, 8 Jul 2026 16:53:00 -0400 Subject: [PATCH 7/7] proofread updates: fix numbering, articles, contraction, preposition, keyword. --- .../audit-and-logging/planned-changes-report.md | 2 +- .../upload-compliance-template.md | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/kb/changetracker/audit-and-logging/planned-changes-report.md b/docs/kb/changetracker/audit-and-logging/planned-changes-report.md index 48301aa8b1..21a0af58e3 100644 --- a/docs/kb/changetracker/audit-and-logging/planned-changes-report.md +++ b/docs/kb/changetracker/audit-and-logging/planned-changes-report.md @@ -33,7 +33,7 @@ This article shows how to run a report that displays Created Planned Changes, Ch 1. Go to **Events**. 2. Select specific or all devices and click **Filter**. -3. In the **Date & Time** Window, select the time period for which you'd like to view created planned changes. +3. In the **Date & Time** window, select the time period for which you want to view created planned changes. 4. In the **Event Filter** window, enter `Planned Change` in the Text Search field. Select **Audit** in Event Type and click **Apply**. diff --git a/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md b/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md index aa12a766ad..151fd9ce62 100644 --- a/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md +++ b/docs/kb/changetracker/configuration-and-setup/upload-compliance-template.md @@ -12,7 +12,7 @@ keywords: - upload template - compliance reports - templates - - Compliance Reports Templates + - Policy Templates - settings - overwrite template - configuration @@ -33,9 +33,9 @@ This guide provides step-by-step instructions on how to upload a compliance/trac ## Instructions -1. Click on the **Settings** dropdown, then click **Policy Templates**. -2. Click the **Actions** dropdown, then click **Upload Templates** button and browse to your template. -4. If you wish to automatically overwrite existing templates with the same name, check the corresponding box. -5. Click the **Upload Template** button. +1. Click the **Settings** dropdown, then click **Policy Templates**. +2. Click the **Actions** dropdown, then click the **Upload Templates** button and browse to your template. +3. If you wish to automatically overwrite existing templates with the same name, check the corresponding box. +4. Click the **Upload Template** button. The progress bar should show 100% once the upload completes.