mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
Corrections to note styles and types on code blocks
This commit is contained in:
Gary Moore
parent
c14a83b932
commit
9c0de61a76
@ -19,8 +19,8 @@ The ActiveSync configuration service provider is used to set up and change setti
|
||||
|
||||
Configuring Windows Live ActiveSync accounts through this configuration service provider is not supported.
|
||||
|
||||
> **Note**
|
||||
The target user must be logged in for the CSP to succeed. The correct way to configure an account is to use the ./User/Vendor/MSFT/ActiveSync path.
|
||||
> [!NOTE]
|
||||
> The target user must be logged in for the CSP to succeed. The correct way to configure an account is to use the ./User/Vendor/MSFT/ActiveSync path.
|
||||
|
||||
On the desktop, only per user configuration (./User/Vendor/MSFT/ActiveSync) is supported. However, the ./Vendor/MSFT/ActiveSync path will work if the user is logged in. The CSP fails when no user is logged in.
|
||||
|
||||
@ -65,8 +65,8 @@ ActiveSync
|
||||
<a href="" id="--user-vendor-msft-activesync"></a>**./User/Vendor/MSFT/ActiveSync**
|
||||
The root node for the ActiveSync configuration service provider.
|
||||
|
||||
> **Note**
|
||||
The target user must be logged in for the CSP to succeed. The correct way to configure an account is to use the ./User/Vendor/MSFT/ActiveSync path.
|
||||
> [!NOTE]
|
||||
> The target user must be logged in for the CSP to succeed. The correct way to configure an account is to use the ./User/Vendor/MSFT/ActiveSync path.
|
||||
|
||||
On the desktop, only per user configuration (./User/Vendor/MSFT/ActiveSync) is supported. However, the ./Vendor/MSFT/ActiveSync will work if the user is logged in. The CSP fails when no user is logged in.
|
||||
|
||||
@ -261,8 +261,8 @@ Valid values are one of the following:
|
||||
<a href="" id="options-contenttypes-content-type-guid-name"></a>**Options/ContentTypes/*Content Type GUID*/Name**
|
||||
Required. A character string that specifies the name of the content type.
|
||||
|
||||
> **Note** In Windows 10, this node is currently not working.
|
||||
|
||||
> [!NOTE]
|
||||
> In Windows 10, this node is currently not working.
|
||||
|
||||
|
||||
Supported operations are Get, Replace, and Add (cannot Add after the account is created).
|
||||
|
||||
@ -17,8 +17,8 @@ ms.date: 06/26/2017
|
||||
|
||||
The AllJoynManagement configuration service provider (CSP) allows an IT administrator to enumerate the AllJoyn devices that are connected to the AllJoyn bus. The devices must support the Microsoft AllJoyn configuration interface (com.microsoft.alljoynmanagement.config). You can also push configuration files to the same devices. To populate the various nodes when setting new configuration, we recommend that you do a query first, to get the actual values for all the nodes in all the attached devices. You can then use the information from the query to set the node values when pushing the new configuration.
|
||||
|
||||
> **Note**
|
||||
The AllJoynManagement configuration service provider (CSP) is only supported in Windows 10 IoT Core (IoT Core).
|
||||
> [!NOTE]
|
||||
> The AllJoynManagement configuration service provider (CSP) is only supported in Windows 10 IoT Core (IoT Core).
|
||||
|
||||
This CSP was added in Windows 10, version 1511.
|
||||
|
||||
|
||||
@ -122,7 +122,7 @@ The following table provides the result of this policy based on different values
|
||||
|False|False|True|Not Reachable.|
|
||||
|False|False|False|*Not Reachable.|
|
||||
|
||||
`*` denotes a valid intermediary state; however, if an MDM transaction results in this state configuration, the END_COMMAND_PROCESSING will result in a fail.
|
||||
\* denotes a valid intermediary state; however, if an MDM transaction results in this state configuration, the END_COMMAND_PROCESSING will result in a fail.
|
||||
|
||||
<a href="" id="applicationcontrol-policies-policyguid-policyinfo-status"></a>**ApplicationControl/Policies/_Policy GUID_/PolicyInfo/Status**
|
||||
This node specifies whether the deployment of the policy indicated by the GUID was successful.
|
||||
@ -140,7 +140,7 @@ Value type is char.
|
||||
|
||||
## Microsoft Endpoint Manager (MEM) Intune Usage Guidance
|
||||
|
||||
For customers using Intune standalone or hybrid management with Configuration Manager (MEMCM) to deploy custom policies via the ApplicationControl CSP, refer to [Deploy Windows Defender Application Control policies by using Microsoft Intune](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/deploy-windows-defender-application-control-policies-using-intune)
|
||||
For customers using Intune standalone or hybrid management with Configuration Manager (MEMCM) to deploy custom policies via the ApplicationControl CSP, refer to [Deploy Windows Defender Application Control policies by using Microsoft Intune](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/deploy-windows-defender-application-control-policies-using-intune).
|
||||
|
||||
## Generic MDM Server Usage Guidance
|
||||
|
||||
@ -152,7 +152,7 @@ In order to leverage the ApplicationControl CSP without using Intune, you must:
|
||||
|
||||
Below is a sample certutil invocation:
|
||||
|
||||
```cmd
|
||||
```console
|
||||
certutil -encode WinSiPolicy.p7b WinSiPolicy.cer
|
||||
```
|
||||
|
||||
@ -308,7 +308,7 @@ The ApplicationControl CSP can also be managed locally from PowerShell or via Mi
|
||||
Run the following command. PolicyID is a GUID which can be found in the policy xml, and should be used here without braces.
|
||||
|
||||
```powershell
|
||||
New-CimInstance -Namespace $namespace -ClassName $policyClassName -Property @{ParentID="./Vendor/MSFT/ApplicationControl/Policies";InstanceID="<PolicyID>";Policy=$policyBase64}
|
||||
New-CimInstance -Namespace $namespace -ClassName $policyClassName -Property @{ParentID="./Vendor/MSFT/ApplicationControl/Policies";InstanceID="<PolicyID>";Policy=$policyBase64}
|
||||
```
|
||||
|
||||
### Querying all policies via WMI Bridge
|
||||
|
||||
@ -332,7 +332,7 @@ The following table show the mapping of information to the AppLocker publisher r
|
||||
|
||||
Here is an example AppLocker publisher rule:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<FilePublisherCondition PublisherName="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" ProductName="Microsoft.Reader" BinaryName="*">
|
||||
<BinaryVersionRange LowSection="*" HighSection="*" />
|
||||
</FilePublisherCondition>
|
||||
@ -343,7 +343,9 @@ You can get the publisher name and product name of apps using a web API.
|
||||
**To find publisher and product name for Microsoft apps in Microsoft Store for Business**
|
||||
|
||||
1. Go to the Microsoft Store for Business website, and find your app. For example, Microsoft OneNote.
|
||||
|
||||
2. Copy the ID value from the app URL. For example, Microsoft OneNote's ID URL is https://www.microsoft.com/store/apps/onenote/9wzdncrfhvjl, and you'd copy the ID value, **9wzdncrfhvjl**.
|
||||
|
||||
3. In your browser, run the Store for Business portal web API, to return a JavaScript Object Notation (JSON) file that includes the publisher and product name values.
|
||||
|
||||
<table>
|
||||
@ -366,13 +368,13 @@ Here is the example for Microsoft OneNote:
|
||||
|
||||
Request
|
||||
|
||||
``` syntax
|
||||
```http
|
||||
https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9wzdncrfhvjl/applockerdata
|
||||
```
|
||||
|
||||
Result
|
||||
|
||||
``` syntax
|
||||
```json
|
||||
{
|
||||
"packageFamilyName": "Microsoft.Office.OneNote_8wekyb3d8bbwe",
|
||||
"packageIdentityName": "Microsoft.Office.OneNote",
|
||||
|
||||
@ -60,7 +60,7 @@ Starting in Windows 10, version 1607, you can use a provisioned app to configur
|
||||
|
||||
Here's an example:
|
||||
|
||||
``` syntax
|
||||
```json
|
||||
{"Account":"contoso\\kioskuser","AUMID":"Microsoft.Windows.Contoso_cw5n1h2txyewy!Microsoft.ContosoApp.ContosoApp"}
|
||||
```
|
||||
|
||||
@ -104,7 +104,8 @@ In Windows 10, version 1803, Assigned Access runtime status only supports monito
|
||||
| KioskModeAppNotFound | This occurs when the kiosk app is not deployed to the machine. |
|
||||
| KioskModeAppActivationFailure | This happens when the assigned access controller detects the process terminated unexpectedly after exceeding the max retry. |
|
||||
|
||||
Note that status codes available in the Status payload correspond to a specific KioskModeAppRuntimeStatus.
|
||||
> [!NOTE]
|
||||
> Status codes available in the Status payload correspond to a specific KioskModeAppRuntimeStatus.
|
||||
|
||||
|Status code | KioskModeAppRuntimeStatus |
|
||||
|---------|---------|
|
||||
@ -123,7 +124,8 @@ In Windows 10, version 1809, Assigned Access runtime status supports monitoring
|
||||
|ActivationFailed|The AssignedAccess account (kiosk or multi-app) failed to sign in.|
|
||||
|AppNoResponse|The kiosk app launched successfully but is now unresponsive.|
|
||||
|
||||
Note that status codes available in the Status payload correspond to a specific AssignedAccessRuntimeStatus.
|
||||
> [!NOTE]
|
||||
> Status codes available in the Status payload correspond to a specific AssignedAccessRuntimeStatus.
|
||||
|
||||
|Status code|AssignedAccessRuntimeStatus|
|
||||
|---|---|
|
||||
@ -580,7 +582,7 @@ Escape and CDATA are mechanisms when handling xml in xml. Consider it’s a tran
|
||||
|
||||
This example shows escaped XML of the Data node.
|
||||
|
||||
```
|
||||
```xml
|
||||
<SyncML xmlns='SYNCML:SYNCML1.2'>
|
||||
<SyncBody>
|
||||
<Add>
|
||||
@ -649,8 +651,10 @@ This example shows escaped XML of the Data node.
|
||||
</SyncBody>
|
||||
</SyncML>
|
||||
```
|
||||
|
||||
This example shows escaped XML of the Data node.
|
||||
```
|
||||
|
||||
```xml
|
||||
<SyncML xmlns='SYNCML:SYNCML1.2'>
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -721,7 +725,8 @@ This example shows escaped XML of the Data node.
|
||||
```
|
||||
|
||||
This example uses CData for the XML.
|
||||
```
|
||||
|
||||
```xml
|
||||
<SyncML xmlns='SYNCML:SYNCML1.2'>
|
||||
<SyncBody>
|
||||
<Add>
|
||||
@ -792,7 +797,8 @@ This example uses CData for the XML.
|
||||
```
|
||||
|
||||
Example of Get command that returns the configuration in the device.
|
||||
```
|
||||
|
||||
```xml
|
||||
<SyncML xmlns='SYNCML:SYNCML1.2'>
|
||||
<SyncBody>
|
||||
<Get>
|
||||
@ -809,7 +815,8 @@ Example of Get command that returns the configuration in the device.
|
||||
```
|
||||
|
||||
Example of the Delete command.
|
||||
```
|
||||
|
||||
```xml
|
||||
<SyncML xmlns='SYNCML:SYNCML1.2'>
|
||||
<SyncBody>
|
||||
<Delete>
|
||||
@ -1129,6 +1136,7 @@ Shell Launcher V2 uses a separate XSD and namespace for backward compatibility.
|
||||
</xs:element>
|
||||
</xs:schema>
|
||||
```
|
||||
|
||||
### Shell Launcher V2 XSD
|
||||
|
||||
```xml
|
||||
@ -1158,7 +1166,8 @@ Shell Launcher V2 uses a separate XSD and namespace for backward compatibility.
|
||||
## ShellLauncherConfiguration examples
|
||||
|
||||
ShellLauncherConfiguration Add
|
||||
```
|
||||
|
||||
```xml
|
||||
<SyncML xmlns='SYNCML:SYNCML1.2'>
|
||||
<SyncBody>
|
||||
<Add>
|
||||
@ -1227,7 +1236,8 @@ ShellLauncherConfiguration Add
|
||||
```
|
||||
|
||||
ShellLauncherConfiguration Add AutoLogon
|
||||
```
|
||||
|
||||
```xml
|
||||
<SyncML xmlns='SYNCML:SYNCML1.2'>
|
||||
<SyncBody>
|
||||
<Add>
|
||||
@ -1275,7 +1285,8 @@ ShellLauncherConfiguration Add AutoLogon
|
||||
```
|
||||
|
||||
ShellLauncher V2 Add
|
||||
```
|
||||
|
||||
```xml
|
||||
<SyncML xmlns='SYNCML:SYNCML1.2'>
|
||||
<SyncBody>
|
||||
<Add>
|
||||
@ -1330,7 +1341,8 @@ xmlns:V2="http://schemas.microsoft.com/ShellLauncher/2019/Configuration">
|
||||
```
|
||||
|
||||
ShellLauncherConfiguration Get
|
||||
```
|
||||
|
||||
```xml
|
||||
<SyncML xmlns='SYNCML:SYNCML1.2'>
|
||||
<SyncBody>
|
||||
<Get>
|
||||
|
||||
@ -17,6 +17,7 @@ The BitLocker configuration service provider (CSP) is used by the enterprise to
|
||||
|
||||
> [!NOTE]
|
||||
> Settings are enforced only at the time encryption is started. Encryption is not restarted with settings changes.
|
||||
>
|
||||
> You must send all the settings together in a single SyncML to be effective.
|
||||
|
||||
A Get operation on any of the settings, except for RequireDeviceEncryption and RequireStorageCardEncryption, returns
|
||||
@ -243,18 +244,18 @@ EncryptionMethodWithXtsRdvDropDown_Name = Select the encryption method for remov
|
||||
If you want to disable this policy use the following SyncML:
|
||||
|
||||
```xml
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/EncryptionMethodByDriveType</LocURI>
|
||||
</Target>
|
||||
<Meta>
|
||||
<Format xmlns="syncml:metinf">chr</Format>
|
||||
</Meta>
|
||||
<Data><disabled/></Data>
|
||||
</Item>
|
||||
</Replace>
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<Item>
|
||||
<Target>
|
||||
<LocURI>./Device/Vendor/MSFT/BitLocker/EncryptionMethodByDriveType</LocURI>
|
||||
</Target>
|
||||
<Meta>
|
||||
<Format xmlns="syncml:metinf">chr</Format>
|
||||
</Meta>
|
||||
<Data><disabled/></Data>
|
||||
</Item>
|
||||
</Replace>
|
||||
```
|
||||
|
||||
Data type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
|
||||
@ -111,7 +111,8 @@ Defines the certificate store that contains root, or self-signed, certificates.
|
||||
|
||||
Supported operation is Get.
|
||||
|
||||
> **Note** Root/System is case sensitive. Please use the RootCATrustedCertificates CSP moving forward for installing root certificates.
|
||||
> [!NOTE]
|
||||
> Root/System is case sensitive. Please use the RootCATrustedCertificates CSP moving forward for installing root certificates.
|
||||
|
||||
|
||||
|
||||
@ -120,7 +121,8 @@ Defines the certificate store that contains cryptographic information, including
|
||||
|
||||
Supported operation is Get.
|
||||
|
||||
> **Note** CA/System is case sensitive. Please use the RootCATrustedCertificates CSP moving forward for installing CA certificates.
|
||||
> [!NOTE]
|
||||
> CA/System is case sensitive. Please use the RootCATrustedCertificates CSP moving forward for installing CA certificates.
|
||||
|
||||
|
||||
|
||||
@ -129,7 +131,8 @@ Defines the certificate store that contains public keys for client certificates.
|
||||
|
||||
Supported operation is Get.
|
||||
|
||||
> **Note** My/User is case sensitive.
|
||||
> [!NOTE]
|
||||
> My/User is case sensitive.
|
||||
|
||||
|
||||
|
||||
@ -138,7 +141,8 @@ Defines the certificate store that contains public key for client certificate. T
|
||||
|
||||
Supported operation is Get.
|
||||
|
||||
> **Note** My/System is case sensitive.
|
||||
> [!NOTE]
|
||||
> My/System is case sensitive.
|
||||
|
||||
|
||||
|
||||
@ -182,7 +186,8 @@ Required for Simple Certificate Enrollment Protocol (SCEP) certificate enrollmen
|
||||
|
||||
Supported operation is Get.
|
||||
|
||||
> **Note** Please use the ClientCertificateInstall CSP to install SCEP certificates moving forward. All enhancements to SCEP will happen in that CSP.
|
||||
> [!NOTE]
|
||||
> Please use the ClientCertificateInstall CSP to install SCEP certificates moving forward. All enhancements to SCEP will happen in that CSP.
|
||||
|
||||
|
||||
|
||||
@ -196,7 +201,8 @@ Required for SCEP certificate enrollment. Parent node to group SCEP certificate
|
||||
|
||||
Supported operations are Add, Replace, and Delete.
|
||||
|
||||
> **Note** Though the children nodes under Install support Replace commands, after the Exec command is sent to the device, the device takes the values that are set when the Exec command is accepted. You should not expect the node value change that occurs after the Exec command is accepted to impact the current undergoing enrollment. You should check the Status node value and make sure that the device is not at an unknown stage before changing the children node values.
|
||||
> [!NOTE]
|
||||
> Though the children nodes under Install support Replace commands, after the Exec command is sent to the device, the device takes the values that are set when the Exec command is accepted. You should not expect the node value change that occurs after the Exec command is accepted to impact the current undergoing enrollment. You should check the Status node value and make sure that the device is not at an unknown stage before changing the children node values.
|
||||
|
||||
|
||||
|
||||
@ -296,7 +302,8 @@ Valid values are one of the following:
|
||||
- Months
|
||||
- Years
|
||||
|
||||
> **Note** The device only sends the MDM server expected certificate validation period (ValidPeriodUnits + ValidPeriod) of the SCEP server as part of certificate enrollment request. How this valid period is used to create the certificate depends on the MDM server.
|
||||
> [!NOTE]
|
||||
> The device only sends the MDM server expected certificate validation period (ValidPeriodUnits + ValidPeriod) of the SCEP server as part of certificate enrollment request. How this valid period is used to create the certificate depends on the MDM server.
|
||||
|
||||
|
||||
|
||||
@ -305,7 +312,8 @@ Optional. Specifies desired number of units used in validity period and subject
|
||||
|
||||
Supported operations are Get, Add, Delete, and Replace.
|
||||
|
||||
> **Note** The device only sends the MDM server expected certificate validation period (ValidPeriodUnits + ValidPeriod) of the SCEP server as part of certificate enrollment request. How this valid period is used to create the certificate depends on the MDM server.
|
||||
> [!NOTE]
|
||||
> The device only sends the MDM server expected certificate validation period (ValidPeriodUnits + ValidPeriod) of the SCEP server as part of certificate enrollment request. How this valid period is used to create the certificate depends on the MDM server.
|
||||
|
||||
|
||||
|
||||
@ -362,7 +370,8 @@ Supported operation is Get.
|
||||
<a href="" id="my-wstep-renew-serverurl"></a>**My/WSTEP/Renew/ServerURL**
|
||||
Optional. Specifies the URL of certificate renewal server. If this node does not exist, the client uses the initial certificate enrollment URL.
|
||||
|
||||
> **Note** The renewal process follows the same steps as device enrollment, which means that it starts with Discovery service, followed by Enrollment policy service, and then Enrollment web service.
|
||||
> [!NOTE]
|
||||
> The renewal process follows the same steps as device enrollment, which means that it starts with Discovery service, followed by Enrollment policy service, and then Enrollment web service.
|
||||
|
||||
|
||||
|
||||
@ -375,7 +384,8 @@ The default value is 42 and the valid values are 1 – 1000. Value type is an in
|
||||
|
||||
Supported operations are Add, Get, Delete, and Replace.
|
||||
|
||||
> **Note** When you set the renewal schedule over SyncML DM commands to ROBOSupport, RenewalPeriod, and RetryInterval, you must wrap them in Atomic commands.
|
||||
> [!NOTE]
|
||||
> When you set the renewal schedule over SyncML DM commands to ROBOSupport, RenewalPeriod, and RetryInterval, you must wrap them in Atomic commands.
|
||||
|
||||
|
||||
|
||||
@ -390,7 +400,8 @@ The default value is 7 and the valid values are 1 – 1000 AND =< RenewalPeriod,
|
||||
|
||||
Supported operations are Add, Get, Delete, and Replace.
|
||||
|
||||
> **Note** When you set the renewal schedule over SyncML DM commands to ROBOSupport, RenewalPeriod, and RetryInterval, you must wrap them in Atomic commands.
|
||||
> [!NOTE]
|
||||
> When you set the renewal schedule over SyncML DM commands to ROBOSupport, RenewalPeriod, and RetryInterval, you must wrap them in Atomic commands.
|
||||
|
||||
|
||||
|
||||
@ -401,7 +412,8 @@ ROBO is the only supported renewal method for Windows 10. This value is ignored
|
||||
|
||||
Supported operations are Add, Get, Delete, and Replace.
|
||||
|
||||
> **Note** When you set the renewal schedule over SyncML DM commands to ROBOSupport, RenewalPeriod, and RetryInterval, you must wrap them in Atomic commands.
|
||||
> [!NOTE]
|
||||
> When you set the renewal schedule over SyncML DM commands to ROBOSupport, RenewalPeriod, and RetryInterval, you must wrap them in Atomic commands.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -325,7 +325,8 @@ Valid values are:
|
||||
- Months
|
||||
- Years
|
||||
|
||||
> **Note** The device only sends the MDM server expected certificate validation period (ValidPeriodUnits + ValidPeriod) to the SCEP server as part of certificate enrollment request. Depending on the server configuration, the server defines how to use this valid period to create the certificate.
|
||||
> [!NOTE]
|
||||
> The device only sends the MDM server expected certificate validation period (ValidPeriodUnits + ValidPeriod) to the SCEP server as part of certificate enrollment request. Depending on the server configuration, the server defines how to use this valid period to create the certificate.
|
||||
|
||||
Supported operations are Add, Get, Delete, and Replace.
|
||||
|
||||
|
||||
@ -17,11 +17,11 @@ ms.date: 06/26/2017
|
||||
|
||||
The CM\_ProxyEntries configuration service provider is used to configure proxy connections on the mobile device.
|
||||
|
||||
> **Note** CM\_ProxyEntries CSP is only supported in Windows 10 Mobile.
|
||||
>
|
||||
>
|
||||
>
|
||||
> **Note** This configuration service provider requires the ID\_CAP\_CSP\_FOUNDATION and ID\_CAP\_NETWORKING\_ADMIN capabilities to be accessed from a network configuration application.
|
||||
> [!NOTE]
|
||||
> CM\_ProxyEntries CSP is only supported in Windows 10 Mobile.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This configuration service provider requires the ID\_CAP\_CSP\_FOUNDATION and ID\_CAP\_NETWORKING\_ADMIN capabilities to be accessed from a network configuration application.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -17,9 +17,8 @@ ms.date: 06/26/2017
|
||||
|
||||
The CMPolicy configuration service provider defines rules that the Connection Manager uses to identify the correct connection for a connection request.
|
||||
|
||||
> **Note**
|
||||
This configuration service provider requires the ID\_CAP\_CSP\_FOUNDATION and ID\_CAP\_NETWORKING\_ADMIN capabilities to be accessed from a network configuration application.
|
||||
|
||||
> [!NOTE]
|
||||
> This configuration service provider requires the ID\_CAP\_CSP\_FOUNDATION and ID\_CAP\_NETWORKING\_ADMIN capabilities to be accessed from a network configuration application.
|
||||
|
||||
|
||||
Each policy entry identifies one or more applications in combination with a host pattern. The policy entry is assigned a list of connection details that Connection Manager uses to satisfy connection requests matching the application and host patterns. CMPolicy configuration service provider can have multiple policies
|
||||
|
||||
@ -17,8 +17,8 @@ ms.date: 06/26/2017
|
||||
|
||||
The CMPolicyEnterprise configuration service provider is used by the enterprise to define rules that the Connection Manager uses to identify the correct connection for a connection request.
|
||||
|
||||
> **Note**
|
||||
This configuration service provider requires the ID\_CAP\_CSP\_FOUNDATION and ID\_CAP\_NETWORKING\_ADMIN capabilities to be accessed from a network configuration application.
|
||||
> [!NOTE]
|
||||
> This configuration service provider requires the ID\_CAP\_CSP\_FOUNDATION and ID\_CAP\_NETWORKING\_ADMIN capabilities to be accessed from a network configuration application.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -17,7 +17,9 @@ ms.date: 06/26/2017
|
||||
The CustomDeviceUI configuration service provider allows OEMs to implement their custom foreground application, as well as the background tasks to run on an IoT device running IoT Core. Only one foreground application is supported per device. Multiple background tasks are supported.
|
||||
The following shows the CustomDeviceUI configuration service provider in tree format as used by both the Open Mobile Alliance (OMA) Device Management (DM) and OMA Client Provisioning.
|
||||
|
||||
> **Note** This configuration service provider only applies to Windows 10 IoT Core (IoT Core).
|
||||
> [!NOTE]
|
||||
> ]This configuration service provider only applies to Windows 10 IoT Core (IoT Core).
|
||||
|
||||
```
|
||||
./Vendor/MSFT
|
||||
CustomDeviceUI
|
||||
@ -25,6 +27,7 @@ CustomDeviceUI
|
||||
----BackgroundTasksToLaunch
|
||||
--------BackgroundTaskPackageName
|
||||
```
|
||||
|
||||
<a href="" id="./Vendor/MSFT/CustomDeviceUI"></a>**./Vendor/MSFT/CustomDeviceUI**
|
||||
The root node for the CustomDeviceUI configuration service provider. The supported operation is Get.
|
||||
|
||||
|
||||
@ -17,7 +17,8 @@ ms.date: 06/26/2017
|
||||
|
||||
The DevInfo configuration service provider handles the managed object which provides device information to the OMA DM server. This device information is automatically sent to the OMA DM server at the beginning of each OMA DM session.
|
||||
|
||||
> **Note** This configuration service provider requires the ID\_CAP\_CSP\_FOUNDATION and ID\_CAP\_DEVICE\_MANAGEMENT\_ADMIN capabilities to be accessed from a network configuration application.
|
||||
> [!NOTE]
|
||||
> This configuration service provider requires the ID\_CAP\_CSP\_FOUNDATION and ID\_CAP\_DEVICE\_MANAGEMENT\_ADMIN capabilities to be accessed from a network configuration application.
|
||||
|
||||
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user