diff --git a/docs/changetracker/8.0/install/agent/windows.md b/docs/changetracker/8.0/install/agent/windows.md index c7096a45db..dc40cf70ee 100644 --- a/docs/changetracker/8.0/install/agent/windows.md +++ b/docs/changetracker/8.0/install/agent/windows.md @@ -33,7 +33,7 @@ In order to maximize performance, Gen 7 Agent operational files are located in _%PROGRAMDATA%\NNT\gen7agent.service_, similarly if you are ever required to provide the **rolling-log.txt** file to [Netwrix Support](https://www.netwrix.com/support.html) this is where it is located. See the -[First Run – HubDetails.xml File](/docs/changetracker/8.0/admin/settingstab/devicegroups.md#first-run-hubdetailsxml-file) +[First Run – HubDetails.xml File](/docs/changetracker/8.0/admin/settingstab/devicegroups.md#first-run--hubdetailsxml-file) topic for additional information on downloading the .xml file for agents. ::: diff --git a/docs/endpointpolicymanager/knowledgebase/gettingstarted/knowledgebase/tipstricksandfaqs/eventcategories.md b/docs/endpointpolicymanager/knowledgebase/gettingstarted/knowledgebase/tipstricksandfaqs/eventcategories.md index 3bda460bab..bea347697a 100644 --- a/docs/endpointpolicymanager/knowledgebase/gettingstarted/knowledgebase/tipstricksandfaqs/eventcategories.md +++ b/docs/endpointpolicymanager/knowledgebase/gettingstarted/knowledgebase/tipstricksandfaqs/eventcategories.md @@ -8,7 +8,7 @@ sidebar_position: 180 ## Feature Specific Events -[List of Endpoint Policy Manager Event Categories and IDs](#list-of-endpoint-policy-manager-event-categories-and-ids) +[Remote Work Delivery Manager](#remote-work-delivery-manager) [Feature Manager for Windows](#feature-manager-for-windows) diff --git a/docs/pingcastle/3.3/index.md b/docs/pingcastle/3.3/index.md index 9e3a390bee..d16484f5a1 100644 --- a/docs/pingcastle/3.3/index.md +++ b/docs/pingcastle/3.3/index.md @@ -42,7 +42,7 @@ securing Active Directories. You can get more information about this methodology by visiting the website https://www.pingcastle.com/methodology/ -# How to use PingCastle +## How to use PingCastle The following sections describe how to use PingCastle. @@ -168,7 +168,7 @@ the "interactive mode" can be activated manually using the command: PingCastle.exe --log --interactive ``` -# Performing an Active Directory health check +## Performing an Active Directory health check The report can be generated in the interactive mode by choosing "healthcheck" or just by pressing Enter. Indeed it is the default @@ -240,7 +240,7 @@ link. It contains data to help identify the underlying objects. ![](/img/product_docs/pingcastle/basicuser/image14.png) -# Perform domain discovery +## Perform domain discovery **Option 1: performing multiple health check reports (recommended)** @@ -361,7 +361,7 @@ to find a specific IP address. ![](/img/product_docs/pingcastle/basicuser/image24.png) -# Deploying PingCastle +## Deploying PingCastle PingCastle has been designed to be scalable and used in a decentralized architecture. @@ -668,7 +668,7 @@ You can query a PingCastle API server or build a client or server from The description of the API in swagger format can be found [here](https://gist.githubusercontent.com/vletoux/c6c565c8af07b4df5df65ed01ffeb917/raw/fca7a288050b7b17ba6024f2a23ef8c4d46fd813/pingcastle-swagger.json). -# Getting an overview with multiple reports +## Getting an overview with multiple reports How much users or computers to you have ? Should you purchase additional support for Windows XP or Windows 2003 ? Should you plan an @@ -730,7 +730,7 @@ The third file is a map build on all trusts. See [domain discovery](#perform-dom [Example](https://www.pingcastle.com/PingCastleFiles/ad_hc_summary_simple_node_map.html) -# Scanners +## Scanners PingCastle has some builtin program to check for specific features. These programs are called \"scanners\" and are accessible from the @@ -828,7 +828,7 @@ Then enter the domain which will be used as a pivot PingCastle --scanner foreignusers --foreigndomain --server ``` -# Annex +## Annex **Command line reference**