Merge pull request #133 from netwrix/Ayesha/NTP7.4-Cleanup

Ayesha - NTP 7.4 cleanup

Author: AyeshaAz36

docs/threatprevention/7.4/admin/overview_1.md renamed to docs/threatprevention/7.4/admin/Tags.md

@@ -12,8 +12,11 @@ SQLite Agent Queue option dumps the queue and all pending events are lost.
 
 Follow the steps to clear the SQLite Agent queue for an Agent:
 
-**CAUTION:** These events are permanently deleted and are not processed by the Enterprise Manager on
+:::warning
+These events are permanently deleted and are not processed by the Enterprise Manager on
 reconnection. This option is for diagnostic and troubleshooting purposes only.
+:::
+
 
 **Step 1 –** Click Agents in the left pane to launch the Agents interface.
 
@@ -26,10 +29,13 @@ to connect to the target machine and query information about shares. A local Adm
 on the target machine should have access to the system shares. Click **OK** after entering the
 credentials.
 
-**NOTE:** The wizard does not block access to the Administration Console and can be minimized while
+:::note
+The wizard does not block access to the Administration Console and can be minimized while
 actions are in progress. If this wizard is hidden by clicking outside of the dialog box, a flashing
 blue link displays on the upper right corner of the interface with the action name displayed. Click
 this link to bring back the focus to the wizard.
+:::
+
 
 **Step 4 –** On the Access Verification window, the given credentials either succeed or fail during
 a prerequisites or verification check.
@@ -38,8 +44,11 @@ a prerequisites or verification check.
   of prior to the next attempt.
 - Success – Click **Next** to begin clearing the SQLite Agent Queue
 
-**NOTE:** Closing the Administration Console while this action is in process causes problems with
+:::note
+Closing the Administration Console while this action is in process causes problems with
 data collection.
+:::
+
 
 **Step 5 –** The Clear Agent Queue window displays the task in progress and then its status as
 either:

docs/threatprevention/7.4/admin/agents/agentmanagement/clearqueue.md

@@ -22,10 +22,13 @@ to connect to the target machine and query information about shares. A local Adm
 on the target machine should have access to the system shares. Click **OK** after entering the
 credentials.
 
-**NOTE:** The wizard does not block access to the Administration Console and can be minimized while
+:::note
+The wizard does not block access to the Administration Console and can be minimized while
 actions are in progress. If this wizard is hidden by clicking outside of the dialog box, a flashing
 blue link displays on the upper right corner of the interface with the action name displayed. Click
 this link to bring back the focus to the wizard.
+:::
+
 
 **Step 4 –** On the Access Verification window, the given credentials either succeed or fail during
 a prerequisites or verification check.
@@ -34,8 +37,11 @@ a prerequisites or verification check.
   of prior to the next attempt.
 - Success – Click **Next** to begin hardening the Agent.
 
-**NOTE:** Closing the Administration Console while this action is in process causes problems with
+:::note
+Closing the Administration Console while this action is in process causes problems with
 data collection.
+:::
+
 
 **Step 5 –** The Harden Agent window displays the task in progress and then its status as either:
 

docs/threatprevention/7.4/admin/agents/agentmanagement/harden.md

@@ -10,8 +10,11 @@ The Agents Interface displays a list of servers where the Agent has been deploye
 remove a server from this list for any reason, such as when the Agent is no longer required on the
 server.
 
-**NOTE:** If the server has a deployed Agent, it will be added back to the list the next time the
+:::note
+If the server has a deployed Agent, it will be added back to the list the next time the
 Agent sends information to the Enterprise Manager.
+:::
+
 
 Follow the steps to remove a server from the list on the Agents Interface.
 

docs/threatprevention/7.4/admin/agents/agentmanagement/removeserver.md

@@ -22,10 +22,13 @@ to connect to the target machine and query information about shares. A local Adm
 on the target machine should have access to the system shares. Click **OK** after entering the
 credentials.
 
-**NOTE:** The wizard does not block access to the Administration Console and can be minimized while
+:::note
+The wizard does not block access to the Administration Console and can be minimized while
 actions are in progress. If this wizard is hidden by clicking outside of the dialog box, a flashing
 blue link displays on the upper right corner of the interface with the action name displayed. Click
 this link to bring back the focus to the wizard.
+:::
+
 
 **Step 4 –** On the Access Verification window, the given credentials either succeed or fail during
 a prerequisites or verification check.
@@ -34,8 +37,11 @@ a prerequisites or verification check.
   of prior to the next attempt.
 - Success – Click **Next** to begin softening the Agent.
 
-**NOTE:** Closing the Administration Console while this action is in process causes problems with
+:::note
+Closing the Administration Console while this action is in process causes problems with
 data collection.
+:::
+
 
 **Step 5 –** The Soften Agent window displays the task in progress and then its status as either:
 

docs/threatprevention/7.4/admin/agents/agentmanagement/soften.md

@@ -22,10 +22,13 @@ to connect to the target machine and query information about shares. A local Adm
 on the target machine should have access to the system shares. Click **OK** after entering the
 credentials.
 
-**NOTE:** The wizard does not block access to the Administration Console and can be minimized while
+:::note
+The wizard does not block access to the Administration Console and can be minimized while
 actions are in progress. If this wizard is hidden by clicking outside of the dialog box, a flashing
 blue link displays on the upper right corner of the interface with the action name displayed. Click
 this link to bring back the focus to the wizard.
+:::
+
 
 **Step 4 –** On the Start Agent window, the Agent will be started. One of two status messages
 display:

docs/threatprevention/7.4/admin/agents/agentmanagement/start.md

@@ -13,11 +13,14 @@ Prevention administrator must start the Active Directory module. See the
 [Agent Safe Mode](/docs/threatprevention/7.4/admin/agents/safemode.md)
 topic for additional information.
 
-**_RECOMMENDED:_** If multiple DCs are in the Start Pending Modules state, this means one of the
+:::info
+If multiple DCs are in the Start Pending Modules state, this means one of the
 monitored system DLLs was changed from when the Agent was last run. This could impact the operation
 of the Agent. It is recommended to enable the pending modules on one DC initially and verify that
 Threat Prevention is collecting events as expected from this specific DC and that the DC appears to
 be stable before starting the pending modules on additional DCs.
+:::
+
 
 Follow the steps to start pending modules on a server.
 

docs/threatprevention/7.4/admin/agents/agentmanagement/startpendingmodules.md

@@ -21,10 +21,13 @@ to connect to the target machine and query information about shares. A local Adm
 on the target machine should have access to the system shares. Click **OK** after entering the
 credentials.
 
-**NOTE:** The wizard does not block access to the Administration Console and can be minimized while
+:::note
+The wizard does not block access to the Administration Console and can be minimized while
 actions are in progress. If this wizard is hidden by clicking outside of the dialog box, a flashing
 blue link displays on the upper right corner of the interface with the action name displayed. Click
 this link to bring back the focus to the wizard.
+:::
+
 
 **Step 4 –** On the Stop Agent window, the Agent will be stopped. One of two status messages
 display:

docs/threatprevention/7.4/admin/agents/agentmanagement/stop.md

@@ -39,6 +39,9 @@ currently in use to the installer downloaded.
 - If the downloaded version is newer, the message displays both version numbers and provides an
   option to apply the update. Click **Apply Update**.
 
-**NOTE:** When the Agent installer is replaced with a newer version, all Agents’ versions in the
+:::note
+When the Agent installer is replaced with a newer version, all Agents’ versions in the
 Agents interface are highlighted to indicate they are not the current version. Agents should then be
 updated to the new version, using the Upgrade Agent option on the right-click menu.
+
+:::

docs/threatprevention/7.4/admin/agents/agentswindows/agentinstallerupdate.md

@@ -46,4 +46,7 @@ manually deploy the Agent. It has the following fields:
 - Click **Copy** to copy the enrollment secret and enter it in the Certificates window of the Agent
   Setup wizard during manual Agent installation.
 
-**NOTE:** Restarting the Enterprise Manager cancels the current enrollment secret.
+:::note
+Restarting the Enterprise Manager cancels the current enrollment secret.
+
+:::