Merge pull request netwrix#543 from netwrix/tm-npsd

Version Privilege Secure Discovery docs under 2.22 and fix Linux wording

Author: TM-PO-Netwrix

…discovery/administration/_category_.json …very/2.22/administration/_category_.jsondocs/privilegesecurediscovery/administration/_category_.json renamed to docs/privilegesecurediscovery/2.22/administration/_category_.json docs/privilegesecurediscovery/administration/_category_.json renamed to docs/privilegesecurediscovery/2.22/administration/_category_.json

@@ -79,8 +79,8 @@ domain
 
 **CAUTION:** This is not a `full_sync`!
 
-- `init_sync` will do a group flattening process, but **will not move stale objects**
-- `full_sync`**will not do a group flattening process,** but _will_ move stale objects
+- `init_sync` will do a group flattening process and **will not move stale objects**
+- `full_sync` moves stale objects and does not perform a group flattening process
 - We have decided to do an `init_sync` as this mimics what Customer Success currently does to
   recover from an AD failure. This feature “automates” this approach within the product.
 
@@ -178,8 +178,8 @@ otherwise-present log fields that are in all ldap logs.
 | Connection has failed, failure criteria for current dc not yet met (retry attempts)                   | warning                                                  | "Domain Controller (DC) Failover: LDAP Sync failed - Retrying current DC  | **current_dc**: server, port of current dc **fail_strategy**: "retry_attempts" **attempts_max**: Max number of retry attempts before trying the next pto a different DC **attempts_current**: number of attempts already completed                                                           |
 | Connection has failed, failure criteria for current dc has been met and we are movig onto the next DC | warning                                                  | "Domain Controller (DC) Failover: LDAP Sync failed - Using next DC"       | **next_dc**: server, port **attempted_dcs**: server, port of attempted (and failed) dcs **remaining_additional_dcs**: server, port of additional DCs to try                                                                                                                                  |
 | Connection has failed, failure criteria for current dc not yet met, waiting to retry                  | info                                                     | "Domain Controller (DC) Failover: Waiting to retry current DC"            | **server**: hostname of current dc **wait_for_sec**: number of seconds waiting in between retry attempts                                                                                                                                                                                     |
-| Initial DC has failed, failover enabled, was able to look up additional DCs via DNS                   | warning                                                  | "Domain Controller (DC) Failover: Found additional DCs"                   | **additional_dcs:** list of alternate DCs that will be attempted (ordered by priority), comprised of server, port **additional_dc_source**: source of additional dcs, currently should just be "dns_priority"                                                                                |
-|                                                                                                       | warning                                                  | "Domain Controller (DC) Failover: Unable to find any additional DCs"      | **additional_dc_source**: source of additional dcs, currently should just be "dns_priority"                                                                                                                                                                                                  |
+| Initial DC has failed, failover enabled, was able to look up additional DCs via DNS                   | warning                                                  | "Domain Controller (DC) Failover: Found additional DCs"                   | **additional_dcs:** list of alternate DCs that will be attempted (ordered by priority), comprised of server, port **additional_dc_source**: source of additional dcs, currently should be "dns_priority"                                                                                |
+|                                                                                                       | warning                                                  | "Domain Controller (DC) Failover: Unable to find any additional DCs"      | **additional_dc_source**: source of additional dcs, currently should be "dns_priority"                                                                                                                                                                                                  |
 | Initial DC success                                                                                    | \* No new log added, it is already logged by svc_ldap \* |                                                                           |                                                                                                                                                                                                                                                                                              |
 | Initial DC failed and failover DC has successfully synced                                             | info                                                     | "Domain Controller (DC) Failover: LDAP Sync failover succeeded"           | **initial_dc**: server, port of initial DC **attempted_dcs**: List of attempted (and failed) dcs, comprised of server, port **failover_dc**: The fail-overed dc hostname **sync_start_ts**: timestamp of sync start **sync_end_ts**: timestamp of sync end, including all faiilover attempts |
 | Initial DC failed and failover not enabled                                                            | error                                                    | "LDAP Sync failed"                                                        | **dc_failover_enabled**: false **error:** dict of error details **sync_start_ts**: start time of sync **sync_end_ts**: end of sync incuding all time spent in failover routine                                                                                                               |

…nistration/configuration/_category_.json …nistration/configuration/_category_.jsondocs/privilegesecurediscovery/administration/configuration/_category_.json renamed to docs/privilegesecurediscovery/2.22/administration/configuration/_category_.json docs/privilegesecurediscovery/administration/configuration/_category_.json renamed to docs/privilegesecurediscovery/2.22/administration/configuration/_category_.json

@@ -145,7 +145,7 @@ The Strategy may be entered with any of following values: OS-BEST-PRACTICE, MANA
 
 The OAM Name Template accepts a string with wildcards expressed by question marks (?). If left blank it will default to the currentvalue, or to "S1_ALT_??????".
 
-The remaining options may be included, but must not conflict with the defined strategy.
+The remaining options may be included when they do not conflict with the defined strategy.
 
 ## Default Settings by Strategy
 
@@ -197,11 +197,11 @@ System: VMTEMP1 [+] System: VMTEMP2
 
 Linux registration prerequisites:
 
-- [Linux Registrations Prerequisites](/docs/privilegesecurediscovery/requirements/technicalpreparation/linuxregistrationsprerequisites.md)
+- [Linux Registrations Prerequisites](../../requirements/technicalpreparation/linuxregistrationsprerequisites.md)
 
 Guide on registering linux system with Postman (using API):
 
-- [Postman Linux Registration](/docs/privilegesecurediscovery/requirements/technicalpreparation/postmanlinuxregistration.md)
+- [Postman Linux Registration](../../requirements/technicalpreparation/postmanlinuxregistration.md)
 
 Troubleshooting Linux Registration:
 
@@ -223,3 +223,5 @@ The full Excel file layout of the QuickStart file is detailed in the picture bel
 
 ![LOAM-S1-1824.webp](/images/privilegesecure/4.2/discovery/admin/configuration/360042878654_oam-s1-1824_941x297.webp)
 ```
+
+

…/configuration/accountinventorycolors.md …/configuration/accountinventorycolors.mddocs/privilegesecurediscovery/administration/configuration/accountinventorycolors.md renamed to docs/privilegesecurediscovery/2.22/administration/configuration/accountinventorycolors.md docs/privilegesecurediscovery/administration/configuration/accountinventorycolors.md renamed to docs/privilegesecurediscovery/2.22/administration/configuration/accountinventorycolors.md

@@ -13,7 +13,7 @@ Apply a Service Account from an existing AD group Directly to a Machine
 ## Overview
 
 All interactive accounts should not have standing privilege, instead these should be using Privilege
-Secure to elevate access when required. This is easy to arrange with Privilege Secure. These
+Secure to elevate access when required. This can be arranged with Privilege Secure. These
 interactive groups should be set as non-persistent. However, sometimes interactive and
 non-interactive (service) accounts exist in the same group. In this case removing the persistence of
 the group would break any process or application that is using the service account. The purpose of
@@ -108,7 +108,7 @@ within the file name. Use the --dry-run flag to check that file will make the in
 
 Tips
 
-If Excel is unwieldly slow rows can be deleted for machines that have not been scanned. But, instead
+If Excel is unwieldly slow rows can be deleted for machines that have not been scanned. Instead
 of filtering and deleting, sort based on the last_scanned column and then delete the unwanted rows.
 Sorting and deleting is many times faster for Excel. This can also resolve issues with Excel
 crashing. Another benefit is the upload back to Privilege Secure will be faster with fewer rows.