Comprehensively fix all relative image paths and cross-references in KB articles

- Fixed 110+ auditor files with incorrect image path references
  - Configuration-and-setup files: changed images/ to ../../images/ (2 levels)
  - Other auditor categories: changed images/ to ../../../images/ (3 levels)
- Fixed 5 articles with broken markdown links to reorganized KB articles
  - Updated links to reflect new article locations in subfolders
- 1secure files: verified all image paths are correct

These comprehensive fixes resolve all MDX compilation errors related to broken image references and markdown links in the reorganized KB structure.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: zoeycastillo

docs/kb/auditor/configuration-and-setup/active-directory-auditing/active-directory-exchange-and-group-policy-changes-reported-as-made-by-system.md

@@ -25,7 +25,7 @@ knowledge_article_id: kA00g000000H9SmCAK
 This article contains references to the most popular Active Directory, Exchange, and Group Policy changes which may be reported as made by **System** by Netwrix Auditor:
 
 - [Alert Reported Change Made by System](/docs/kb/auditor/reports-alerts-and-notifications/report-generation/alert-reported-change-made-by-system.md).
-- [System Changed Object Path after Account Name Change](/docs/kb/auditor/system-changed-object-path-after-account-name-change.md).
+- [System Changed Object Path after Account Name Change](/docs/kb/auditor/features-and-operations/glossaries-and-faqs/system-changed-object-path-after-account-name-change.md).
 - [System Changed Client Operating System](/docs/kb/auditor/system-changed-client-operating-system.md).
 - [System Changed Directory Objects for Foreign Security Principals](/docs/kb/auditor/system-changed-directory-objects-for-foreign-security-principals.md).
 - [Workstation Field Reported as Unknown](/docs/kb/auditor/workstation-field-reported-as-unknown.md)
@@ -35,3 +35,4 @@ This article contains references to the most popular Active Directory, Exchange,
 
 
 
+

docs/kb/auditor/configuration-and-setup/sharepoint-and-teams-auditing/troubleshoot_sharepoint_serveron-premise_errors.md

@@ -22,7 +22,7 @@ This is a reference list of articles on troubleshooting errors in SharePoint Ser
 ### Related Articles
 
 - [SharePoint Core Service Deployment Failed](/docs/kb/auditor/configuration-and-setup/sharepoint-and-teams-auditing/sharepoint-core-service-deployment-failed.md)
-- [Timeout Expired Error on SharePoint Core Service D](/docs/kb/auditor/timeout-expired-error-on-sharepoint-core-service-deployment.md)
+- [Timeout Expired Error on SharePoint Core Service D](/docs/kb/auditor/configuration-and-setup/sharepoint-and-teams-auditing/timeout-expired-error-on-sharepoint-core-service-deployment.md)
 - [Event ID 1204 in Health Log](/docs/kb/auditor/event-id-1204-in-health-log.md)
 - [Event ID 1205 in Health Log](/docs/kb/auditor/event-id-1205-in-health-log.md)
 - [Error: Event ID 1206 in Health Log](/docs/kb/auditor/error-event-id-1206-in-health-log.md)
@@ -60,3 +60,4 @@ This is a reference list of articles on troubleshooting errors in SharePoint Ser
 
 
 
+

docs/kb/auditor/configuration-and-setup/sql-server-auditing/cannot-generate-sspi-context-error-in-sql-server-monitoring-plan.md

@@ -102,15 +102,16 @@ Allow the operating systems to select the protocol for incoming and outgoing com
 
 ### Cause #4 – SQL and Netwrix Auditor Servers Time Difference
 
-Synchronize the time on both SQL and Netwrix Auditor servers to eliminate clock skew. For more information, see Clock Skew Is Too Great: [Clock Skew Is Too Great](/docs/kb/auditor/clock-skew-is-too-great.md)
+Synchronize the time on both SQL and Netwrix Auditor servers to eliminate clock skew. For more information, see Clock Skew Is Too Great: [Clock Skew Is Too Great](/docs/kb/auditor/features-and-operations/glossaries-and-faqs/clock-skew-is-too-great.md)
 
 ## Related Articles
 
 - [SQL Server Ports](https://docs.netwrix.com/docs/auditor/10_8/configuration/sqlserver/ports)
 - Cannot Generate SSPI Context – Fix the Error with Kerberos Configuration Manager · Microsoft: https://learn.microsoft.com/en-US/troubleshoot/sql/database-engine/connect/cannot-generate-sspi-context-error#fix-the-error-with-kerberos-configuration-manager-recommended
 - Register Service Principal Name for Kerberos Connections – Automatic SPN Registration · Microsoft: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/register-a-service-principal-name-for-kerberos-connections?view=sql-server-ver16#Auto
 - [Client and Server Cannot Communicate, Because They Do Not Possess a Common Algorithm](/docs/kb/auditor/troubleshooting-and-errors/data-collection-errors/client-and-server-cannot-communicate-because-they-do-not-possess-a-common-algorithm.md)
-- [Clock Skew Is Too Great](/docs/kb/auditor/clock-skew-is-too-great.md)
+- [Clock Skew Is Too Great](/docs/kb/auditor/features-and-operations/glossaries-and-faqs/clock-skew-is-too-great.md)
+
 
 
 

docs/kb/auditor/configuration-and-setup/sql-server-auditing/how-do-i-migrate-the-reporting-database-to-another-ms-sql-server-instance-lower-version.md

@@ -34,48 +34,49 @@ There are a few options to downgrade the database from a higher version of SQL S
 
 1.1 In Object Explorer connect to the SQL server, right-click the database, expand **Tasks** and choose **Generate Scripts**.
 
-![User-added image](images/ka04u000000HcOn_0EM700000005TB6.png)
+![User-added image](../../images/ka04u000000HcOn_0EM700000005TB6.png)
 
 1.2 This launches the **Generate and Publish Scripts** wizard. Click **Next** to skip the Introduction screen and proceed to the Choose Objects page.
 
-![User-added image](images/ka04u000000HcOn_0EM700000005TBB.png)
+![User-added image](../../images/ka04u000000HcOn_0EM700000005TBB.png)
 
 1.3 On the Choose Objects page, choose **Script entire database and all database objects**, and then click **Next** to proceed to the **Set Scripting Options** page.
 
-![User-added image](images/ka04u000000HcOn_0EM700000005TBG.png)
+![User-added image](../../images/ka04u000000HcOn_0EM700000005TBG.png)
 
 1.4 On the **Set Scripting Options** page, specify the location where you want to save the script file, and then click the **Advanced** button.
 
-![User-added image](images/ka04u000000HcOn_0EM700000005TBL.png)
+![User-added image](../../images/ka04u000000HcOn_0EM700000005TBL.png)
 
 1.5 In the **Advanced Scripting Options** dialog box, set `Script Triggers`, `Indexes` and `Primary Key` options to `True`, set `Script for Server Version` to ``<version of the destination SQL server instance>``, and set `Types of data to script` to `Schema and Data`. This last option is key because this is what generates the data per table.
 
-![User-added image](images/ka04u000000HcOn_0EM700000005TC4.png)
+![User-added image](../../images/ka04u000000HcOn_0EM700000005TC4.png)
 
 1.6 Once done, click **OK** to close the **Advanced Scripting Options** dialog box and return to the **Set Scripting Options** page. In the **Set Scripting Options** page, click **Next** to continue to the Summary page.
 
 1.7 After reviewing your selections on the Summary page, click **Next** to generate scripts.
 
-![User-added image](images/ka04u000000HcOn_0EM700000005TBV.png)
+![User-added image](../../images/ka04u000000HcOn_0EM700000005TBV.png)
 
 1.8 Once scripts are generated successfully, choose the **Finish** button to close the **Generate and Publish Scripts** wizard.
 
-![User-added image](images/ka04u000000HcOn_0EM700000005TBa.png)
+![User-added image](../../images/ka04u000000HcOn_0EM700000005TBa.png)
 
 2. Connect to the destination SQL Server instance, and then run the SQL scripts that were generated, to create the database schema and copy its data.
 
 2.1 In Object Explorer connect to the destination SQL Server instance and then in SQL Server Management Studio open the SQL Server script you saved in Step 1.
 
-![User-added image](images/ka04u000000HcOn_0EM700000005TBf.png)
+![User-added image](../../images/ka04u000000HcOn_0EM700000005TBf.png)
 
-![User-added image](images/ka04u000000HcOn_0EM700000005TBk.png)
+![User-added image](../../images/ka04u000000HcOn_0EM700000005TBk.png)
 
-![User-added image](images/ka04u000000HcOn_0EM700000005TBp.png)
+![User-added image](../../images/ka04u000000HcOn_0EM700000005TBp.png)
 
 2.2 Modify the script to specify the correct location for the database data and log files. Once done, run the script to create the database on the destination SQL Server instance.
 
-![User-added image](images/ka04u000000HcOn_0EM700000005TCE.png)
+![User-added image](../../images/ka04u000000HcOn_0EM700000005TCE.png)
 
 2.3 Upon successful execution, refresh the Database folder in Object Explorer.
 
-![User-added image](images/ka04u000000HcOn_0EM700000005TC9.png)
+![User-added image](../../images/ka04u000000HcOn_0EM700000005TC9.png)
+

docs/kb/auditor/configuration-and-setup/sql-server-auditing/how-to-migrate-netwrix-auditor-databases-to-another-sql-server-instance.md

@@ -56,10 +56,10 @@ Yes, you are able to migrate audit databases to another Microsoft SQL Server ins
 8. In the main Netwrix Auditor menu, select **Settings** > **Audit Database** tab, and specify the new SQL Server and Reporting Service settings.
 
 > **NOTE:** If you receive the following pop-up message, click **Yes** to proceed with modifying the Audit Database settings:
-> ![Audit Database modification prompt](images/servlet_image_3823966b1661.png)
+> ![Audit Database modification prompt](../../images/servlet_image_3823966b1661.png)
 
 9. Click **Yes** when the following message appears:
-   ![Confirmation dialog: Data will become unavailable until the new database is configured](images/servlet_image_3823966b1661.png)
+   ![Confirmation dialog: Data will become unavailable until the new database is configured](../../images/servlet_image_3823966b1661.png)
 10. In the main Netwrix Auditor menu, select **Settings** > **Investigations** tab. Click **Modify** to specify the new SQL Server settings.
 11. Run a search with the filter **When | Equals | Last 7 days**. If you see the relevant data, the databases were migrated successfully and the new SQL Server is being used.
 12. **Optional:** Start the old SQL Server instance if it is used for any other tasks.
@@ -70,3 +70,4 @@ Yes, you are able to migrate audit databases to another Microsoft SQL Server ins
 - [SQL Server Reporting Services](https://docs.netwrix.com/docs/auditor/10_8/requirements/overview)
 - [How to Prepare the Netwrix Server for a SQL Upgrade](/docs/kb/auditor/how-to-prepare-the-netwrix-server-for-a-sql-upgrade.md)
 - [Deploying the Report Server Database](/docs/kb/auditor/deploying-the-report-server-database.md)
+

docs/kb/auditor/configuration-and-setup/sql-server-auditing/specify-custom-sql-server-port-for-netwrix-auditor-audit-database.md

@@ -35,4 +35,5 @@ How to specify a custom port for Netwrix Auditor to communicate with the SQL Ser
 SERVER-SQL\TEST-SQL,14337
 ```
 
-![Specify custom SQL Server port image](images/ka04u00000117sv_0EM4u000008LXSz.png)
+![Specify custom SQL Server port image](../../images/ka04u00000117sv_0EM4u000008LXSz.png)
+

docs/kb/auditor/configuration-and-setup/sql-server-auditing/sql-server-express-database-size-reached-10gb.md

@@ -68,10 +68,11 @@ While it is highly recommended to implement either a SQL Server Standard or Ente
 
 - Split items in multiple monitoring plans to decrease the amount of data written to a single database.
 
-- Decrease the database retention period. Refer to the following article for additional information: [How to Reduce Audit Database Size for Netwrix Auditor](/docs/kb/auditor/how-to-reduce-audit-database-size-for-netwrix-auditor.md)
+- Decrease the database retention period. Refer to the following article for additional information: [How to Reduce Audit Database Size for Netwrix Auditor](/docs/kb/auditor/system-administration/database-management/how-to-reduce-audit-database-size-for-netwrix-auditor.md)
 
 ## Related Articles
 
 - [Investigations](https://docs.netwrix.com/docs/auditor/10_8/admin/settings/investigations)
-- [How to Reduce Audit Database Size for Netwrix Auditor](/docs/kb/auditor/how-to-reduce-audit-database-size-for-netwrix-auditor.md) 
+- [How to Reduce Audit Database Size for Netwrix Auditor](/docs/kb/auditor/system-administration/database-management/how-to-reduce-audit-database-size-for-netwrix-auditor.md) 
 - [Could Not Allocate Space for Object (ObjectName) in Database (DatabaseName)](/docs/kb/auditor/could-not-allocate-space-for-object-objectname-in-database-databasename.md)
+

docs/kb/auditor/configuration-and-setup/windows-server-monitoring/auditing-policies-are-not-being-enabled-on-all-or-several-domain-controllers-in-monitored-domain.md

@@ -38,11 +38,11 @@ The reasons why the auditing policies are not being enabled on domain controller
 - Run Resultant Set of Policy (RSoP): `Start > Run` > type `rsop.msc` and press Enter.
 - Expand Audit Policy as shown in the picture below and make sure you see the corresponding source GPO (the GPO which you enabled auditing policies in) for auditing policies and ensure there are no warnings or errors. In our case we see that Audit Account Management policy is set to Failure, while for successful auditing we need to have this policy set to Success.
 
-![rsop](images/ka04u000000HcSR_0EM7000000053Be.png)
+![rsop](../../images/ka04u000000HcSR_0EM7000000053Be.png)
 
 - To fix this problem open **Group Policy Management Console** (**Start > Administrative Tools > Group Policy Management**), select the **Domain Controllers** node, open the **Group Policy Inheritance** tab and in the right pane review the order the GPOs are being applied to the Domain Controllers OU. In our case the Default Domain Policy is enforced and being applied first which causes a GPO conflict. Manage your GPO inheritance to exclude the necessary policy settings from being overridden. For more details regarding GPO inheritance please refer to the following Microsoft KB article: http://technet.microsoft.com/en-us/library/cc757050(v=ws.10).aspx
 
-![gpmc](images/ka04u000000HcSR_0EM7000000053Bj.png)
+![gpmc](../../images/ka04u000000HcSR_0EM7000000053Bj.png)
 
 ## If GPO distribution is correct but auditing settings still not applied
 
@@ -52,7 +52,7 @@ If you resolved the inheritance issue and corresponding GPOs are being distribut
 2. Open Local Group Policy Editor: `Start > Run` > `secpol.msc`.
 3. Expand Audit Policy as shown in the picture below and make sure that the necessary auditing policies are set to Success (for example, Audit Account Management, Audit Directory Service Access) and are equal to the ones you see in Resultant Set of Policy (RSoP).
 
-![secpol](images/ka04u000000HcSR_0EM7000000053Bo.png)
+![secpol](../../images/ka04u000000HcSR_0EM7000000053Bo.png)
 
 - If the Local Group Policy Editor indicates different auditing settings (different from the ones you configured and see in Resultant Set of Policy (RSoP)), this may indicate an issue with GPO applying on that particular domain controller. To troubleshoot this issue please refer to the following Microsoft KB articles:
 
@@ -61,3 +61,4 @@ If you resolved the inheritance issue and corresponding GPOs are being distribut
   - Group Policy Analysis and Troubleshooting Overview: http://technet.microsoft.com/en-us/library/jj134223.aspx
   - Fixing Group Policy problems by using log files: http://technet.microsoft.com/en-us/library/cc775423(WS.10).aspx
   - SceCli 1202 events are logged every time Computer Group Policy settings are refreshed on a computer that is running Windows Server 2008 R2: http://support.microsoft.com/kb/974639/en-us
+

docs/kb/auditor/configuration-and-setup/windows-server-monitoring/high-cpu-usage-on-domain-controllers.md

@@ -39,7 +39,7 @@ There are two options to fix the issue:
    3. Create a DWORD called `UseWatcher` with value `1`
    4. Restart the **Netwrix Account Lockout Examiner service** via **Services.msc**
 
-   ![User-added image](images/ka04u000000HcUT_0EM7000000052iw.png)
+   ![User-added image](../../images/ka04u000000HcUT_0EM7000000052iw.png)
 
 2. If the above does not help, disable usage of WMI to communicate with domain controllers. (A .Net-based mechanism will be used for it.)
 
@@ -50,4 +50,5 @@ There are two options to fix the issue:
    3. Change the `UseWMI` value to `0`
    4. Restart the **Netwrix Account Lockout Examiner service** via **Services.msc**
 
-   ![User-added image](images/ka04u000000HcUT_0EM7000000052jG.png)
+   ![User-added image](../../images/ka04u000000HcUT_0EM7000000052jG.png)
+

docs/kb/auditor/configuration-and-setup/windows-server-monitoring/how-to-exclude-non-operable-domain-controllers-from-monitoring-in-netwrix-auditor.md

@@ -51,8 +51,9 @@ To exclude domain controllers from monitoring, refer to the following steps:
    MYDC.MYDOMAIN.LOCAL
    ```
 
-   ![User-added image](images/ka0Qk0000003W1l_0EMQk000003oywv.png)
+   ![User-added image](../../images/ka0Qk0000003W1l_0EMQk000003oywv.png)
 
 3. Save the changes. Inactive User Tracker will exclude this domain controller.
 
 Refer to the following article for additional information: Monitoring Plans — User Activity Monitoring Scope — v10.6.
+