updated groupid, but not fixed yet

Author: jtviolet

docs/passwordsecure/passwordsecure/configuration/advanced_view/clientmodule/applications/learning_the_applications/start_parameter/start_parameter.md

@@ -43,19 +43,19 @@ Fields can be added via certain placeholders based on their type or their name.
 
 | Field type | Placeholder |
 | --- | --- |
-| Text | {Text} |
-| Password | {Password} |
-| Date | {Date} |
-| Check | {Check} |
-| URL | {Url} |
-| Email | {Email} |
-| Phone | {Phone} |
-| ​List | {List} |
-| Header | {Header} |
-| Multiline text | ​{Memo} |
-| Multiline password text | ​{PasswordMemo} |
-| Integer | {Int} |
-| Floating-point number | {Decimal} |
-| User name | {UserName} |
-| ​IP address | {Ip} |
-| Enter field name | {field:name} |
+| Text | `{Text}` |
+| Password | `{Password}` |
+| Date | `{Date}` |
+| Check | `{Check}` |
+| URL | `{Url}` |
+| Email | `{Email}` |
+| Phone | `{Phone}` |
+| ​List | `{List}` |
+| Header | `{Header}` |
+| Multiline text | ​`{Memo}` |
+| Multiline password text | ​`{PasswordMemo}` |
+| Integer | `{Int}` |
+| Floating-point number | `{Decimal}` |
+| User name | `{UserName}` |
+| ​IP address | `{Ip}` |
+| Enter field name | `{field:name}` |

docs/privilegesecure/privilegesecure/accessmanagement/admin/configuration/integrationdetails/cyberark.md

@@ -119,6 +119,6 @@ $Credential has the values for the Credential generated for lookup, on Checkin t
 | $Credential.SudoCommand | The command to use for performing elevated commands on a Linux/Unix based system. | sudo |
 | $Credential.PasswordValueConnectorId | The vault connector GUID identifier for this credential. This has the same value as the $Options.Connector.Id |  |
 | $Credential.PasswordVaultInfo | A JSON string that contains vault specific options for this credential |  |
-| $Credential.PasswordVaultInfo | A JSON string that contains vault specific | { “safe”: “safename”, “folder”: “root” } |
+| $Credential.PasswordVaultInfo | A JSON string that contains vault specific | `{ “safe”: “safename”, “folder”: “root”` } |
 
 Your custom script block should return the $Credential object passed in, updated with any relevant information.

docs/privilegesecure/privilegesecure/accessmanagement/admin/login.md

@@ -10,7 +10,7 @@ https://ExampleServer01:6500
 
 __NOTE:__ This is the default port. If a custom port is configured, the address to the Privilege Secure Console is:
 
-https://ExampleServer01:[PortNumber]
+`https://ExampleServer01:[PortNumber]`
 
 Depending on the organization’s network environment, use the NetBIOS name, fully qualified domain name (FQDN), or IP Address of the server in the browser. Also, access can be restricted through firewalls.
 

docs/privilegesecure/privilegesecure/accessmanagement/admin/troubleshooting.md

@@ -85,8 +85,8 @@ This table lists available in the Enablement Toolkit with descriptions, notes, a
 | Operation | Description | Required Fields | Notes |
 | --- | --- | --- | --- |
 | Enumerate Active Directory Objects | Enumerates domain or domain controller specified in the Domain field for counts of users, group members, and computers. The target domain / domain controller can be specified by IP or DNS Name | - Domain - Username - Password | Enable the Use TLS checkbox for LDAPS lookups instead of LDAP. |
-| Verify Domain Group Membership for Credential | Verifies that a domain group exists and that the user specified in the Domain / User field is a member of that group. The Domain / User field is the <domain>\<user> to be queried for the domain group in the Group field.  The Username and Password fields are used for authentication to the domain, which can be any domain user. The target domain / domain controller can be specified by either IP, DNS Name, or domain name. | - Domain / User - Group - Username - Password | Enable the Use TLS checkbox for LDAPS lookups instead of LDAP. |
-| Verify Local Windows Group Membership for User Account | Verifies that a local Windows group exists and that the user specified in the User / Host field is a member of that group.  The User / Host field is the <user>@<hostname> to be queried for the local Windows group in the Group field. This needs to be in the format:  <user@hostname>  The Username (ex. domain\user) and Password fields are used for authe ntication to the Windows host as a local administrator.  Both Domain and local accounts can be used for authentication as long as the account is a local administrator. | - User / Host - Group - Username - Password | A domain user must be used for authentication if verifying domain user group membership. |
+| Verify Domain Group Membership for Credential | Verifies that a domain group exists and that the user specified in the Domain / User field is a member of that group. The Domain / User field is the `<domain>\\<user>` to be queried for the domain group in the Group field.  The Username and Password fields are used for authentication to the domain, which can be any domain user. The target domain / domain controller can be specified by either IP, DNS Name, or domain name. | - Domain / User - Group - Username - Password | Enable the Use TLS checkbox for LDAPS lookups instead of LDAP. |
+| Verify Local Windows Group Membership for User Account | Verifies that a local Windows group exists and that the user specified in the User / Host field is a member of that group.  The User / Host field is the `<user>@<hostname>` to be queried for the local Windows group in the Group field. This needs to be in the format:  `<user@hostname>`  The Username (ex. domain\user) and Password fields are used for authe ntication to the Windows host as a local administrator.  Both Domain and local accounts can be used for authentication as long as the account is a local administrator. | - User / Host - Group - Username - Password | A domain user must be used for authentication if verifying domain user group membership. |
 | Verify WinRM Status for Host | Checks the following criteria related to WinRM (PSRemoting) connectivity to the Host:   - Port scan for port 5985 - Verify WinRM is enabled - Verify supplied credentials can authenticate - Verify Invoke-Command runs with supplied credentials   The Host field is the host to be tested. The Username and Password fields are used for authentication.  If only the Host field is used, the only the port scan and WinRM are tested. If Host, Username, and Password fields are used, then all tests will run. | - Host | Only port 5985 is used for testing WinRM (PSRemoting). Port 5986 is not tested. |
 | Port Scan for Host | Scans the Host for will-known ports:   - SSH (Port 22) - RDP (Port 3389) - WinRM (Port 5985) - WinRM (Port 5986) | - Host | A ping test is also performed and is reported in the output's heading. |
 | Verify SSH Connectivity for Host | Verifies SSH connectivity and authentication to the target Host. The well-known SSH port (port 22) is used by default but can be customized. The Username and Password fields are used to authenticate the SSH session.  The ability to run sudo commands, specify which sudo commands the user has access to, and whether or not the user's sudo commands use the "NOPASSWD" directive are also checked. | - Host - Port - Username - Password | N/A |

docs/privilegesecure/privilegesecure/accessmanagement/enduser/configure/rdcmanager.md

@@ -14,7 +14,7 @@ To configure the remote connection client, use a connection string with the foll
 
 Connection String Format:
 
-<username>+<activity>+<resource>+<access policy>+<notes>
+`<username>+<activity>+<resource>+<access policy>+<notes>`
 
 Connection String Example:
 
@@ -38,7 +38,7 @@ Configuration parameters for PuTTY (SSH).
 
 Host Name Format:
 
-- <connection string>@<proxyhostname>
+- `<connection string>@<proxyhostname>`
 
 Host Name Example:
 
@@ -57,7 +57,7 @@ Configuration parameters for MobaXterm (SSH).
 
 Remote Host Format:
 
-- <connection string>@<proxyhostname>
+- `<connection string>@<proxyhostname>`
 
 Resource Host Example:
 
@@ -81,15 +81,15 @@ Configuration parameters for MobaXterm (RDP).
 
 Remote Host:
 
-- <proxyhostname>
+- `<proxyhostname>`
 
 Example:
 
 sbpamhost
 
 Username:
 
-- <connection string>
+- `<connection string>`
 
 Example:
 
@@ -112,15 +112,15 @@ Configuration parameters for Microsoft Remote Desktop Connection (RDP).
 
 Computer:
 
-<proxyhostname>:<port>
+`<proxyhostname>:<port>`
 
 __Example:__
 
 Sbpamhost:4489
 
 User Name Format:
 
-- <connection string>
+- `<connection string>`
 
 User Name Example:
 
@@ -137,15 +137,15 @@ Configure the Microsoft Remote Desktop Connection Manager (RDC Manager).
 
 Server name:
 
-<proxyhostname>:<port>
+`<proxyhostname>:<port>`
 
 Server name example:
 
 Sbpamhost:4489
 
 User Name Format:
 
-\<connection string>
+`\<connection string>`
 
 __NOTE:__ The user name starts with _\_ (back slash).
 

docs/recoveryforactivedirectory/recoveryforactivedirectory/troubleshooting/troubleshooting.md

@@ -37,7 +37,7 @@ __Step 5 –__ Navigate from the AD Configuration Partition folder until __CN=Di
 
 __Step 6 –__ Double-click on the proper locale (such as CN=409). A list is displayed in the middle pane. Right click on any of the Display Specifiers and select __Properties__ from the menu. The Properties window is displayed. Select the adminContextMenu attribute or click Edit to show the Multi-valued String Editor listing known GUIDs. In the list, the RSAT Extension GUID entry is:
 
-{50fb3a3c-5700-4232-ae3b-c6d49a6a97ab}
+`{50fb3a3c-5700-4232-ae3b-c6d49a6a97ab}`
 
 __NOTE:__ The adminContextMenu attribute of every object in the active locale (i.e. CN=409 for US English), should have the GUID above.