deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Updated

Browse Source
This commit is contained in:
Meghana Athavale 2021-09-28 11:11:52 +05:30
parent 59409841d4
commit 27d6528a28
2 changed files with 272 additions and 272 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
windows/client-management/mdm/policy-csp-applicationdefaults.md
View File

@ -1,6 +1,6 @@
---
title: Policy CSP - ApplicationDefaults
description: Learn about various Policy configuration service provider (CSP) - ApplicationDefaults, including SyncML, for Windows 10.
description: Learn about various Policy configuration service providers (CSP) - ApplicationDefaults, including SyncML, for Windows 10.
ms.author: dansimp
ms.topic: article
ms.prod: w10
@ -83,9 +83,9 @@ manager: dansimp
<!--/Scope-->
<!--Description-->
This policy allows an administrator to set default file type and protocol associations. When set, default associations will be applied on sign-in to the PC. The association file can be created using the DISM tool (dism /online /export-defaultappassociations:appassoc.xml), and then needs to be base64 encoded before being added to SyncML.
This policy allows an administrator to set default file type and protocol associations. When set, default associations are applied on sign in to the PC. The association file can be created using the DISM tool (dism /online /export-defaultappassociations:appassoc.xml). Then, it needs to be base64 encoded before being added to SyncML.
If policy is enabled and the client machine is Azure Active Directory joined, the associations assigned in SyncML will be processed and default associations will be applied.
If policy is enabled and the client machine is having Azure Active Directory, the associations assigned in SyncML are processed and default associations are applied.
<!--/Description-->
<!--ADMXMapped-->
@ -106,7 +106,7 @@ To create the SyncML, follow these steps:
<li>Paste the base64 encoded XML into the SyncML</li>
</ol>
Here is an example output from the dism default association export command:
Here's an example output from the dism default association export command:
```xml
<?xml version="1.0" encoding="UTF-8"?>
@ -119,13 +119,13 @@ Here is an example output from the dism default association export command:
</DefaultAssociations
```
Here is the base64 encoded result:
Here's the base64 encoded result:
``` syntax
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjxEZWZhdWx0QXNzb2NpYXRpb25zPg0KICA8QXNzb2NpYXRpb24gSWRlbnRpZmllcj0iLmh0bSIgUHJvZ0lkPSJBcHBYNGh4dGFkNzdmYmszamtrZWVya3JtMHplOTR3amYzczkiIEFwcGxpY2F0aW9uTmFtZT0iTWljcm9zb2Z0IEVkZ2UiIC8+DQogIDxBc3NvY2lhdGlvbiBJZGVudGlmaWVyPSIuaHRtbCIgUHJvZ0lkPSJBcHBYNGh4dGFkNzdmYmszamtrZWVya3JtMHplOTR3amYzczkiIEFwcGxpY2F0aW9uTmFtZT0iTWljcm9zb2Z0IEVkZ2UiIC8+DQogIDxBc3NvY2lhdGlvbiBJZGVudGlmaWVyPSIucGRmIiBQcm9nSWQ9IkFwcFhkNG5yejhmZjY4c3JuaGY5dDVhOHNianlhcjFjcjcyMyIgQXBwbGljYXRpb25OYW1lPSJNaWNyb3NvZnQgRWRnZSIgLz4NCiAgPEFzc29jaWF0aW9uIElkZW50aWZpZXI9Imh0dHAiIFByb2dJZD0iQXBwWHEwZmV2em1lMnB5czYybjNlMGZicWE3cGVhcHlrcjh2IiBBcHBsaWNhdGlvbk5hbWU9Ik1pY3Jvc29mdCBFZGdlIiAvPg0KICA8QXNzb2NpYXRpb24gSWRlbnRpZmllcj0iaHR0cHMiIFByb2dJZD0iQXBwWDkwbnY2bmhheTVuNmE5OGZuZXR2N3RwazY0cHAzNWVzIiBBcHBsaWNhdGlvbk5hbWU9Ik1pY3Jvc29mdCBFZGdlIiAvPg0KPC9EZWZhdWx0QXNzb2NpYXRpb25zPg0KDQo=
```
Here is the SyncMl example:
Here's the SyncMl example:
```xml
<?xml version="1.0" encoding="utf-8"?>
@ -211,7 +211,7 @@ Enabling this policy setting enables web-to-app linking so that apps can be laun
Disabling this policy disables web-to-app linking and http(s) URIs will be opened in the default browser instead of launching the associated app.
If you do not configure this policy setting, the default behavior depends on the Windows edition. Changes to this policy take effect on reboot.
If you don't configure this policy setting, the default behavior depends on the Windows edition. Changes to this policy take effect on reboot.
<!--/Description-->
<!--ADMXMapped-->

530
windows/client-management/mdm/policy-csp-audit.md
View File

@ -1,6 +1,6 @@
---
title: Policy CSP - Audit
description: Learn how the Policy CSP - Audit setting causes an audit event to be generated when an account can't log on to a computer because the account is locked out.
description: Learn how the Policy CSP - Audit setting causes an audit event to be generated when an account can't sign in to a computer because the account is locked out.
ms.author: dansimp
ms.topic: article
ms.prod: w10
@ -251,11 +251,11 @@ ms.date: 09/27/2019
<!--/Scope-->
<!--Description-->
This policy setting allows you to audit events generated by a failed attempt to log on to an account that is locked out.
This policy setting allows you to audit events generated by a failed attempt to sign in to an account that is locked out.
If you configure this policy setting, an audit event is generated when an account cannot log on to a computer because the account is locked out. Success audits record successful attempts and Failure audits record unsuccessful attempts.
If you configure this policy setting, an audit event is generated when an account can't sign in to a computer because the account is locked out. Success audits record successful attempts and Failure audits record unsuccessful attempts.
Logon events are essential for understanding user activity and to detect potential attacks.
Sign in events are essential for understanding user activity and to detect potential attacks.
Volume: Low.
@ -268,10 +268,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 (default) — Success
- 2 — Failure
- 3 — Success+Failure
- 0—Off/None
- 1 (default)—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -335,9 +335,9 @@ The following are the supported values:
<!--/Scope-->
<!--Description-->
This policy allows you to audit the group membership information in the user's logon token. Events in this subcategory are generated on the computer on which a logon session is created. For an interactive logon, the security audit event is generated on the computer that the user logged on to. For a network logon, such as accessing a shared folder on the network, the security audit event is generated on the computer hosting the resource.
This policy allows you to audit the group membership information in the user's sign in token. Events in this subcategory are generated on the computer on which a sign in session is created. For an interactive sign in, the security audit event is generated on the computer that the user logged on to. For a network sign in, such as accessing a shared folder on the network, the security audit event is generated on the computer hosting the resource.
When this setting is configured, one or more security audit events are generated for each successful logon. You must also enable the Audit Logon setting under Advanced Audit Policy Configuration\System Audit Policies\Logon/Logoff. Multiple events are generated if the group membership information cannot fit in a single security audit event.
When this setting is configured, one or more security audit events are generated for each successful sign in. Enable the Audit Logon setting under Advanced Audit Policy Configuration\System Audit Policies\Logon/Logoff. Multiple events are generated if the group membership information can't fit in a single security audit event.
Volume: Low on a client computer. Medium on a domain controller or a network server.
<!--/Description-->
@ -349,10 +349,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -432,10 +432,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -502,7 +502,7 @@ The following are the supported values:
This policy setting allows you to audit events generated by Internet Key Exchange protocol (IKE) and Authenticated Internet Protocol (AuthIP) during Main Mode negotiations.
If you configure this policy setting, an audit event is generated during an IPsec Main Mode negotiation. Success audits record successful attempts and Failure audits record unsuccessful attempts.
If you do not configure this policy setting, no audit event is generated during an IPsec Main Mode negotiation.
If you don't configure this policy setting, no audit event is generated during an IPsec Main Mode negotiation.
Volume: High.
<!--/Description-->
@ -514,10 +514,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -583,7 +583,7 @@ The following are the supported values:
<!--Description-->
This policy setting allows you to audit events generated by Internet Key Exchange protocol (IKE) and Authenticated Internet Protocol (AuthIP) during Quick Mode negotiations.
If you configure this policy setting, an audit event is generated during an IPsec Quick Mode negotiation. Success audits record successful attempts and Failure audits record unsuccessful attempts. If you do not configure this policy setting, no audit event is generated during an IPsec Quick Mode negotiation.
If you configure this policy setting, an audit event is generated during an IPsec Quick Mode negotiation. Success audits record successful attempts and Failure audits record unsuccessful attempts. If you don't configure this policy setting, no audit event is generated during an IPsec Quick Mode negotiation.
Volume: High.
<!--/Description-->
@ -595,10 +595,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -662,10 +662,10 @@ The following are the supported values:
<!--/Scope-->
<!--Description-->
This policy setting allows you to audit events generated by the closing of a logon session. These events occur on the computer that was accessed. For an interactive logoff the security audit event is generated on the computer that the user account logged on to.
This policy setting allows you to audit events generated by the closing of a sign in session. These events occur on the computer that was accessed. For an interactive sign out the security audit event is generated on the computer that the user account logged on to.
If you configure this policy setting, an audit event is generated when a logon session is closed. Success audits record successful attempts to close sessions and Failure audits record unsuccessful attempts to close sessions.
If you do not configure this policy setting, no audit event is generated when a logon session is closed.
If you configure this policy setting, an audit event is generated when a sign in session is closed. Success audits record successful attempts to close sessions and Failure audits record unsuccessful attempts to close sessions.
If you don't configure this policy setting, no audit event is generated when a sign in session is closed.
Volume: Low.
<!--/Description-->
@ -677,10 +677,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 (default) — Success
- 2 — Failure
- 3 — Success+Failure
- 0—Off/None
- 1 (default)—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -744,13 +744,13 @@ The following are the supported values:
<!--/Scope-->
<!--Description-->
This policy setting allows you to audit events generated by user account logon attempts on the computer.
Events in this subcategory are related to the creation of logon sessions and occur on the computer which was accessed. For an interactive logon, the security audit event is generated on the computer that the user account logged on to. For a network logon, such as accessing a shared folder on the network, the security audit event is generated on the computer hosting the resource.
This policy setting allows you to audit events generated by user account sign in attempts on the computer.
Events in this subcategory are related to the creation of sign in sessions and occur on the computer that was accessed. For an interactive sign in, the security audit event is generated on the computer that the user account logged on to. For a network sign in, such as accessing a shared folder on the network, the security audit event is generated on the computer hosting the resource.
The following events are included:
- Successful logon attempts.
- Failed logon attempts.
- Logon attempts using explicit credentials. This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch logon configurations, such as scheduled tasks or when using the RUNAS command.
- Security identifiers (SIDs) were filtered and not allowed to log on.
- Successful sign in attempts.
- Failed sign in attempts.
- sign in attempts using explicit credentials. This event is generated when a process attempts to sign in an account by explicitly specifying that account’s credentials. This most commonly occurs in batch sign in configurations, such as scheduled tasks or when using the RUNAS command.
- Security identifiers (SIDs) were filtered and not allowed to sign in.
Volume: Low on a client computer. Medium on a domain controller or a network server.
<!--/Description-->
@ -762,10 +762,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 (default) — Success
- 2 — Failure
- 3 — Success+Failure
- 0—Off/None
- 1 (default)—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -843,10 +843,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 — Success
- 2 — Failure
- 3 (default) — Success+Failure
- 0—Off/None
- 1—Success
- 2—Failure
- 3 (default)—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -910,7 +910,7 @@ The following are the supported values:
<!--/Scope-->
<!--Description-->
Added in Windows 10, version 1903. Also available in Windows 10, versions 1809 and 1803 through servicing. This policy setting allows you to audit other logon/logoff-related events that are not covered in the “Logon/Logoff” policy setting, such as the following:
This policy setting allows you to audit other logon/logoff-related events that aren't covered in the “Logon/Logoff” policy setting, such as the following:
- Terminal Services session disconnections.
- New Terminal Services sessions.
- Locking and unlocking a workstation.
@ -930,10 +930,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -998,8 +998,8 @@ The following are the supported values:
<!--/Scope-->
<!--Description-->
This policy setting allows you to audit events generated by special logons, such as the following:
- The use of a special logon, which is a logon that has administrator-equivalent privileges and can be used to elevate a process to a higher level.
- A logon by a member of a Special Group. Special Groups enable you to audit events generated when a member of a certain group has logged on to your network. You can configure a list of group security identifiers (SIDs) in the registry. If any of those SIDs are added to a token during logon and the subcategory is enabled, an event is logged. For more information about this feature, see [Audit Special Logon](/windows/security/threat-protection/auditing/audit-special-logon).
- The use of a special sign in, which is a sign in that has administrator-equivalent privileges and can be used to elevate a process to a higher level.
- A sign in by a member of a Special Group. Special Groups enable you to audit events generated when a member of a certain group has logged on to your network. You can configure a list of group security identifiers (SIDs) in the registry. If any of those SIDs are added to a token during sign in and the subcategory is enabled, an event is logged. For more information about this feature, see [Audit Special Logon](/windows/security/threat-protection/auditing/audit-special-logon).
Volume: Low.
<!--/Description-->
@ -1011,10 +1011,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 (default) — Success
- 2 — Failure
- 3 — Success+Failure
- 0—Off/None
- 1 (default)—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -1078,11 +1078,11 @@ The following are the supported values:
<!--/Scope-->
<!--Description-->
This policy allows you to audit user and device claims information in the user's logon token. Events in this subcategory are generated on the computer on which a logon session is created. For an interactive logon, the security audit event is generated on the computer that the user logged on to. For a network logon, such as accessing a shared folder on the network, the security audit event is generated on the computer hosting the resource.
This policy allows you to audit user and device claims information in the user's sign in token. Events in this subcategory are generated on the computer on which a sign in session is created. For an interactive sign in, the security audit event is generated on the computer that the user logged on to. For a network sign in, such as accessing a shared folder on the network, the security audit event is generated on the computer hosting the resource.
User claims are added to a logon token when claims are included with a user's account attributes in Active Directory. Device claims are added to the logon token when claims are included with a device's computer account attributes in Active Directory. In addition, compound identity must be enabled for the domain and on the computer where the user logged on.
User claims are added to a sign in token when claims are included with a user's account attributes in Active Directory. Device claims are added to the sign in token when claims are included with a device's computer account attributes in Active Directory. In addition, compound identity must be enabled for the domain and on the computer where the user logged on.
When this setting is configured, one or more security audit events are generated for each successful logon. You must also enable the Audit Logon setting under Advanced Audit Policy Configuration\System Audit Policies\Logon/Logoff. Multiple events are generated if the user and device claims information cannot fit in a single security audit event.
When this setting is configured, one or more security audit events are generated for each successful sign in. You must also enable the Audit Logon setting under Advanced Audit Policy Configuration\System Audit Policies\Logon/Logoff. Multiple events are generated if the user and device claims information cannot fit in a single security audit event.
Volume: Low on a client computer. Medium on a domain controller or a network server.
<!--/Description-->
@ -1094,10 +1094,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -1161,7 +1161,7 @@ The following are the supported values:
<!--/Scope-->
<!--Description-->
This policy setting allows you to audit events generated by validation tests on user account logon credentials.
This policy setting allows you to audit events generated by validation tests on user account sign in credentials.
Events in this subcategory occur only on the computer that is authoritative for those credentials. For domain accounts, the domain controller is authoritative. For local accounts, the local computer is authoritative.
@ -1175,10 +1175,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -1257,10 +1257,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -1339,10 +1339,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -1406,7 +1406,7 @@ The following are the supported values:
<!--/Scope-->
<!--Description-->
This policy setting allows you to audit events generated by responses to credential requests submitted for a user account logon that are not credential validation or Kerberos tickets.
This policy setting allows you to audit events generated by responses to credential requests submitted for a user account sign in that are not credential validation or Kerberos tickets.
Currently, there are no events in this subcategory.
@ -1419,10 +1419,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -1486,7 +1486,7 @@ The following are the supported values:
<!--/Scope-->
<!--Description-->
This policy setting allows you to audit events generated by changes to application groups, such as the following:
This policy setting allows you to audit events generated by changes to application groups as follows:
- Application group is created, changed, or deleted.
- Member is added or removed from an application group.
@ -1503,10 +1503,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -1585,10 +1585,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -1652,7 +1652,7 @@ The following are the supported values:
<!--/Scope-->
<!--Description-->
This policy setting allows you to audit events generated by changes to distribution groups, such as the following:
This policy setting allows you to audit events generated by changes to distribution groups as follows:
- Distribution group is created, changed, or deleted.
- Member is added or removed from a distribution group.
- Distribution group type is changed.
@ -1673,10 +1673,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -1740,7 +1740,7 @@ The following are the supported values:
<!--/Scope-->
<!--Description-->
This policy setting allows you to audit events generated by other user account changes that are not covered in this category, such as the following:
This policy setting allows you to audit events generated by other user account changes that are not covered in this category as follows:
- The password hash of a user account was accessed. This typically happens during an Active Directory Management Tool password migration.
- The Password Policy Checking API was called. Calls to this function can be part of an attack when a malicious application tests the policy to reduce the number of attempts during a password dictionary attack.
- Changes to the Default Domain Group Policy under the following Group Policy paths:
@ -1760,10 +1760,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -1845,10 +1845,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 (default) — Success
- 2 — Failure
- 3 — Success+Failure
- 0—Off/None
- 1 (default)—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -1913,7 +1913,7 @@ The following are the supported values:
<!--/Scope-->
<!--Description-->
This policy setting allows you to audit changes to user accounts.
Events include the following:
The events included are as follows:
- A user account is created, changed, deleted; renamed, disabled, enabled, locked out, or unlocked.
- A user account’s password is set or changed.
- A security identifier (SID) is added to the SID History of a user account.
@ -1934,10 +1934,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 (default) — Success
- 2 — Failure
- 3 — Success+Failure
- 0—Off/None
- 1 (default)—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -2014,10 +2014,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -2097,10 +2097,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -2186,10 +2186,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -2271,10 +2271,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -2353,10 +2353,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -2434,10 +2434,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -2515,10 +2515,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -2596,10 +2596,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -2677,10 +2677,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -2755,10 +2755,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -2839,10 +2839,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -2924,10 +2924,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -3021,10 +3021,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -3104,10 +3104,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -3187,10 +3187,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -3271,10 +3271,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -3363,10 +3363,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -3442,10 +3442,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -3526,10 +3526,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -3608,10 +3608,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -3697,10 +3697,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -3781,10 +3781,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -3862,10 +3862,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -3953,10 +3953,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -4048,10 +4048,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 (default) — Success
- 2 — Failure
- 3 — Success+Failure
- 0—Off/None
- 1 (default)—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -4135,10 +4135,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -4221,10 +4221,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -4310,10 +4310,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -4395,10 +4395,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -4485,10 +4485,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 (default) — Success
- 2 — Failure
- 3 — Success+Failure
- 0—Off/None
- 1 (default)—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -4598,10 +4598,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -4675,10 +4675,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -4771,10 +4771,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -4858,10 +4858,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -4940,10 +4940,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 — Success
- 2 — Failure
- 3 (default) — Success+Failure
- 0—Off/None
- 1—Success
- 2—Failure
- 3 (default)—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -5022,10 +5022,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 (default) — Success
- 2 — Failure
- 3 — Success+Failure
- 0—Off/None
- 1 (default)—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -5106,10 +5106,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 (default) — Off/None
- 1 — Success
- 2 — Failure
- 3 — Success+Failure
- 0 (default)—Off/None
- 1—Success
- 2—Failure
- 3—Success+Failure
<!--/SupportedValues-->
<!--Example-->
@ -5190,10 +5190,10 @@ GP Info:
<!--/DbMapped-->
<!--SupportedValues-->
The following are the supported values:
- 0 — Off/None
- 1 — Success
- 2 — Failure
- 3 (default) — Success+Failure
- 0—Off/None
- 1—Success
- 2—Failure
- 3 (default)—Success+Failure
<!--/SupportedValues-->
<!--Example-->