netwrix · Zulu2460 · Jul 16, 2025 · Jul 15, 2025
@@ -6,10 +6,13 @@ sidebar_position: 10
 
 # Sample Scripts:
 
-**NOTE:** For script debugging and advanced scripting requirements, you may find it easier to use
+:::note
+For script debugging and advanced scripting requirements, you may find it easier to use
 the ‘**Script Console**’ packaged with any Proxy Agent installation. You can run the Script Console
 from _C:\Program Files\NNT Change Tracker Suite\Gen7Agent (NetCore)\NNT.Script.Console.exe_ program
 name **NNT.Script.Console.exe**
+:::
+
 
 The sample scripts provided in this section all include a Main Script and a Logon Script dialogue,
 however, for Production Agentless Tracker’s, the Logon script only is used within the Credentials

@@ -18,8 +18,11 @@ required.
 - $$PASSWORD2$$ - the second level (admin / privilege) password
 - $$RESULTS$$ - the variable whose contents are used as the ‘result text’ of the script.
 
-**NOTE:** Using multiple capturing commands with the same variable will result in the data being
+:::note
+Using multiple capturing commands with the same variable will result in the data being
 appended to the existing value.
+:::
+
 
 ### Script Commands
 

@@ -21,7 +21,10 @@ The **Dashboard** shows recent System Events including:
 - Summaries of currently active planned changes.
 - Highlighted problems with individual devices.
 
-**NOTE:**
+:::note
+
+:::
+
 
 - The **Welcome to Netwrix Change Tracker** widget provides **Guided Setup Wizard**s – use them!
 - Click **Settings** and select an auto refresh period for a dynamic, active Dashboard.
@@ -45,8 +48,11 @@ If you do not see an Agent at all then please contact
 [Netwrix Support](https://www.netwrix.com/support.html) for further help or use the Agent
 Troubleshooting of the Admin Guide.
 
-**NOTE:** You can pop-out the **Groups and Device** selection panel by clicking on the tag as shown
+:::note
+You can pop-out the **Groups and Device** selection panel by clicking on the tag as shown
 above. Make sure the ‘Search Groups’ is set to ‘All Devices.’
+:::
+
 
 Once the Agent registration process has completed you will see that the Device Name and IP Address
 have been identified and the Operating System. By default, Netwrix Change Tracker is provided with a

@@ -22,9 +22,12 @@ collated into a single screen.
 
 ![DevicesTab](/img/product_docs/changetracker/8.0/admin/tabs/devicestab.webp)
 
-**NOTE:** Go to **Tracking Configuration** tab to see a ‘read-only’ representation of the tracking
+:::note
+Go to **Tracking Configuration** tab to see a ‘read-only’ representation of the tracking
 template assigned, note that this will be a merged version of all Policy Templates inherited by the
 device.
+:::
+
 
 To view the groups that any asset is a member of, click the group name. See **Settings** ->
 **Groups** and show the additional group members.

@@ -26,6 +26,9 @@ additional information.
 create/expand a Planned Change definition – use Resubmit to then review other previous events
 automatically for inclusion within the Planned Change ID.
 
-**NOTE:** Right-click while hovering over an event to invoke the Quick Export, Quick Filter and
+:::note
+Right-click while hovering over an event to invoke the Quick Export, Quick Filter and
 Resubmit options. Using a combination of these functions, you can quickly focus in on exactly the
 event type or period of interest
+
+:::
@@ -15,15 +15,21 @@ created.
 
 The example below shows the sequence of steps to create a new schedule with a new ruleset.
 
-**NOTE:** In Step 2, you can re-use rulesets where available or choose to create a new set. Rules
+:::note
+In Step 2, you can re-use rulesets where available or choose to create a new set. Rules
 can be created manually in Step 3 or again selected from the list of available rulesets.
+:::
+
 
 In Step 4, the **Edit Schedule** button allows Groups and/or Devices to be added to the schedule.
 
 ![PlannedChangeRulesExample](/img/product_docs/changetracker/8.0/admin/wizards/plannedchangerulesexample.webp)
 
-**NOTE:** If you want to let Netwrix Change Tracker self-learn rules by recording change activity
+:::note
+If you want to let Netwrix Change Tracker self-learn rules by recording change activity
 during the schedule, check the **In Event Recording Mode** box.
+:::
+
 
 ![PlannedChangeEventRecordingMode](/img/product_docs/changetracker/8.0/admin/wizards/plannedchangeeventrecordingmode.webp)
 ![page_guide_35](/img/product_docs/changetracker/8.0/admin/wizards/page_guide_35.webp)
@@ -29,10 +29,13 @@ Any Planned Change comprises the following elements:
 - Use the new **Planned Change Wizard** to guide you through the steps required to create a Planned
   Change Schedule and Rule Set.
 
-**NOTE:** Rules can also be created directly from an observed event using the Actions button on the
+:::note
+Rules can also be created directly from an observed event using the Actions button on the
 [Events Tab](/docs/changetracker/8.0/admin/events/events.md), or by recording
 events directly from a device group. Note that an additional Planned Change Schedule filter is
 available in the **Filter Control** panel. Planned Change Schedules can be re-used – use the Clone
 button to create a copy.
+:::
+
 
 ![PlannedChangesRules](/img/product_docs/changetracker/8.0/admin/tabs/plannedchangesrules.webp)
@@ -29,9 +29,12 @@ updates, any unplanned changes - which may be breach activity - are exposed and
   interest.
 - Equally the Query/Report functions are the same as for the Events screen.
 
-**NOTE:** The **Show Rules** button is for non-admin users and shows a ‘read only’ view of rules.
+:::note
+The **Show Rules** button is for non-admin users and shows a ‘read only’ view of rules.
 Click alongside any Planned Change Schedule Name to display a graphical view of changes and a full
 list of devices with changes below.
+:::
+
 
 ![PlannedChangesTab](/img/product_docs/changetracker/8.0/admin/tabs/plannedchangestab.webp)
 

@@ -8,8 +8,11 @@ sidebar_position: 10
 
 To export the events displayed, use the Export button – choices of PDF, Excel or csv are provided.
 
-**NOTE:** The events exported will be governed by the filter settings, not simply what is visible on
+:::note
+The events exported will be governed by the filter settings, not simply what is visible on
 the screen nor selected using the checkboxes against events. To export a subset of displayed events,
 apply further filter controls then export.
+:::
+
 
 ![page_guide_4](/img/product_docs/changetracker/8.0/admin/tabs/page_guide_4.webp)
@@ -17,14 +17,20 @@ See the
 [Export Reports](/docs/changetracker/8.0/admin/events/eventsexportreports.md)
 topic for additional information.
 
-**NOTE:** The **Configuration Template** report has a context-sensitive option for Query Settings,
+:::note
+The **Configuration Template** report has a context-sensitive option for Query Settings,
 allowing selection of all Policy Templates to include in the report. Often an auditor will request
 details of configuration attributes being tracked and this report provides a convenient way to
 extract these on a scheduled basis.
+:::
+
 
 ![ReportTemplateQuerySettings](/img/product_docs/changetracker/8.0/admin/tabs/reporttemplatequerysettings.webp)
 
-**NOTE:** The **Table of Contents** treatment for the output. Links to sections are only supported
+:::note
+The **Table of Contents** treatment for the output. Links to sections are only supported
 in the exported PDF, not the Web Browser-rendered report.
+:::
+
 
 ![ReportTemplateTOC](/img/product_docs/changetracker/8.0/admin/tabs/reporttemplatetoc.webp)
@@ -30,7 +30,8 @@ Change** tabs.
 
 ![ReportsAndQuesriesTab](/img/product_docs/changetracker/8.0/admin/tabs/reportsandquesriestab.webp)
 
-**NOTE:** Report formatting is controlled by the built-in Compliance reports templates. See the
+:::note
+Report formatting is controlled by the built-in Compliance reports templates. See the
 [Template Management](/docs/changetracker/8.0/compliance/compliancereportstemplates.md) topic for additional information. You will
 see that any report has a ‘Results available until xx yy zz – this retention period is in place to
 ensure that reports are not stored forever and using storage resource unnecessarily. Most reports
@@ -39,6 +40,8 @@ need to store reports long term at the Change Tracker Hub. Don’t worry, the ev
 long as needed, governed by the separate DaysToKeepEventsFor system setting. See the
 [System Settings](/docs/changetracker/8.0/admin/settingstab/systemsettings/systemsettings.md) topic for additional information. Reports can be
 regenerated at any time if needed at a subsequent future date.
+:::
+
 
 ![ReportsReportViewerDialog](/img/product_docs/changetracker/8.0/admin/tabs/reportsreportviewerdialog.webp)
 

@@ -26,16 +26,25 @@ name of the config file used for agents.
 
 **Step 3 –** Select the devices or groups of devices to configure and then enter the desired values.
 
-**CAUTION:** Altering the URL could cause the agent to be unable to communicate with the Hub and
+:::warning
+Altering the URL could cause the agent to be unable to communicate with the Hub and
 require direct manual intervention to resolve.
+:::
 
-**CAUTION:** Altering the agent username or password could cause the agent to be unable to
+
+:::warning
+Altering the agent username or password could cause the agent to be unable to
 communicate with the Hub if a matching user account does not exist. This too would require direct
 manual intervention to resolve.
+:::
+
 
-**CAUTION:** Altering the username or password of the user account used by any agent will render
+:::warning
+Altering the username or password of the user account used by any agent will render
 those agents incapable of communicating with the Hub. A corrective password will not be able to be
 broadcast to the now offline agents. Direct manual intervention would be required to resolve.
+:::
+
 
 For most fields, leaving a blank value will ensure that the current values for those fields in the
 target agent's configuration files will remain as they are. Leaving the Name prefix field blank will

@@ -33,13 +33,19 @@ The existing agent account can be seen in the Users section of the Hub.
 
 ![agentaccountmanagement](/img/product_docs/changetracker/8.0/admin/settings/agentaccountmanagement.webp)
 
-**CAUTION:** Changing the password of an account used by agents to authenticate will cause the
+:::warning
+Changing the password of an account used by agents to authenticate will cause the
 agents to go offline as they will be attempting to authenticate with the old password.
+:::
 
-**_RECOMMENDED:_** For a smooth transition, it is recommended to create a new account with just the
+
+:::info
+For a smooth transition, it is recommended to create a new account with just the
 **Agent** role. This account will have a different user name and password. Once created, the agent's
 configuration can be updated to use the new account. When all agents have been migrated, the old
 agent account can be removed.
+:::
+
 
 Follow the steps to create the new agent account.
 

@@ -20,15 +20,21 @@ can be edited below.
 - Event Send Block allows events to be temporarily blocked for a Device, for example, in case a
   misconfigured template is generating too much noise.
 
-**NOTE:** Use the **Filter Control Panel** to allow focus on just the Devices or Groups of interest.
+:::note
+Use the **Filter Control Panel** to allow focus on just the Devices or Groups of interest.
+:::
+
 
 ![Graphical user interface, application
 
 Description automatically
 generated](/img/product_docs/changetracker/8.0/admin/settings/page_guide_24.webp)
 
-**NOTE:** Click on the ‘burger’ icon alongside any column heading to get a full list of column
+:::note
+Click on the ‘burger’ icon alongside any column heading to get a full list of column
 options.
+:::
+
 
 ![Graphical user interface, text, application, email
 

@@ -16,7 +16,10 @@ event options for each Device Group.
 Access the **User Notification Email** page via **Settings** -> **User Notification Emails** and
 select a user, then dial in **Notification Types** for the selected Device Group.
 
-**NOTE:** Core system settings such as the Syslog Server and SMTP details will also need to be
+:::note
+Core system settings such as the Syslog Server and SMTP details will also need to be
 defined via **Settings** -> **System Settings** in the Change Tracker . See the
 [System Settings](/docs/changetracker/8.0/admin/settingstab/systemsettings/systemsettings.md)
 topic for additional information.
+
+:::
@@ -53,7 +53,10 @@ The key tags within the file are as follows:
 [How to: Retrieve the Thumbprint of a Certificate](https://msdn.microsoft.com/en-us/library/ms734695(v=vs.110).aspx)
 Microsoft article for additional information.
 
-**NOTE:** Agent also supports additional nodes – **NamePrefix** and **NameSuffix**.
+:::note
+Agent also supports additional nodes – **NamePrefix** and **NameSuffix**.
+:::
+
 
 Agent does not need the **UseNewHub** node to be defined – this will default to true.
 

@@ -47,7 +47,10 @@ application hack/modification will be detected and alerted.
 
         - **File Attributes** – Excluding contents only
 
-            **NOTE:** Contents tracking is defined under the **File Contents** tab
+            :::note
+            Contents tracking is defined under the **File Contents** tab
+            :::
+
 
         - **Folder/Directory Attributes** – Only or All File and Folder Attributes. Default is to
           use File Attributes only as tracking changes at the Folder level in Windows may sometimes
@@ -71,6 +74,9 @@ will still be identified as being a changed file.
 
 Exclusions are configured in a similar manner to the inclusive tracking above.
 
-**NOTE:** For Advanced Options: see
+:::note
+For Advanced Options: see
 [File and Folder Match Filters](/docs/changetracker/8.0/admin/matchrules/filefolderrules.md)
 for more information.
+
+:::
@@ -6,7 +6,10 @@ sidebar_position: 60
 
 # Policy Templates: Installed Software and Updates
 
-**NOTE:** This template applicable to Windows OS only.
+:::note
+This template applicable to Windows OS only.
+:::
+
 
 Software installations and updates are critical dimensions of a host’s configuration. It is
 therefore essential that these are tracked and recorded from compliance, security, and configuration

@@ -6,17 +6,23 @@ sidebar_position: 100
 
 # Policy Templates: Local User/Domain Controller Account Tracker
 
-**NOTE:** This template applicable to Windows OS only.
+:::note
+This template applicable to Windows OS only.
+:::
+
 
 Netwrix Change Tracker can also be used to track changes to **Local User Account Settings**.
 Typically local User Accounts should be limited and usage restricted in favor of centralized
 identity and access management authority such as a Domain Controller. As such the monitoring of
 local user accounts is a key security consideration.
 
-**NOTE:** When an Netwrix Change Tracker Agent is used on a Domain Controller, tracking the local
+:::note
+When an Netwrix Change Tracker Agent is used on a Domain Controller, tracking the local
 user accounts will in effect track the **Domain** user accounts – in cases where this is not
 required, uncheck the **Track account information on Domain Controllers** box to limit tracking to
 just the Built-In accounts only.
+:::
+
 
 There is minimal configuration required to activate the Change Tracker – just check the **Track
 local user account settings in this template** box and define the poll period then save settings to

@@ -34,7 +34,10 @@ Files(x86)\Nmap), Linux: /usr/bin/)
 The **Network Port Tracker** is configured by specifying port ranges to include and exclude from the
 scan. In addition, the protocol used for each range can also be selected, either TCP, UDP or both.
 
-**NOTE:** As with any UDP scan, the non-acknowledged nature of UDP requires a more intensive, slower
+:::note
+As with any UDP scan, the non-acknowledged nature of UDP requires a more intensive, slower
 approach which may result in scan times exceeding 24 hours.
+:::
+
 
 ![PolicyTemplatesNetworkPortTrackerTab](/img/product_docs/changetracker/8.0/admin/settings/policytemplates/policytemplatesnetworkporttrackertab.webp)
@@ -10,7 +10,10 @@ Edit and upload/download configuration policy templates – the default template
 Netwrix Change Tracker are already aligned to default Device Groups, but this association can be
 changed together with the make-up of the Configuration Monitoring policy
 
-**NOTE:** Always click the **Save Changes** button after any edit.
+:::note
+Always click the **Save Changes** button after any edit.
+:::
+
 
 To configure additional File/Folder/Registry Match Pattern definitions, click on the **Show Advanced
 Options** button.

@@ -6,16 +6,22 @@ sidebar_position: 70
 
 # Policy Templates: Registry
 
-**NOTE:** This template applicable to Windows OS only.
+:::note
+This template applicable to Windows OS only.
+:::
+
 
 The Windows Registry was designed as the core repository for configuration settings. Monitoring of
 Registry Keys and Values is another way to ‘fingerprint’ an application or device configuration
 state.
 
-**NOTE:** To select a Registry Key to monitor, the best way is to use the Microsoft ‘regedit’
+:::note
+To select a Registry Key to monitor, the best way is to use the Microsoft ‘regedit’
 program (start -> run -> regedit). You can then browse all Registry Keys for the device and at any
 point use a ‘right click’ to access the tools menu which includes an option to ‘copy key name’. You
 can then paste the key name into the **Compliance Hub** field.
+:::
+
 
 Click **Add new registry key** and type or paste the Key into monitor. Once you have added a Key to
 monitor, click **Insert** then **Save Settings to Device**.