Updated articles with grammar, headings, bullets, and lists.

This commit is contained in:
Shesh 2022-04-01 17:53:38 +05:30
parent eb80578ef9
commit 5a3c2be122
8 changed files with 34 additions and 38 deletions

View File

@ -14,10 +14,10 @@ ms.date: 06/26/2017
# Reboot CSP
The Reboot configuration service provider is used to configure reboot settings.
The following shows the Reboot configuration service provider management objects in tree format as used by Open Mobile Alliance Device Management (OMA DM), OMA Client Provisioning, and Enterprise DM.
```
./Device/Vendor/MSFT
Reboot
@ -26,41 +26,44 @@ Reboot
--------Single
--------DailyRecurrent
```
<a href="" id="--vendor-msft-reboot"></a>**./Vendor/MSFT/Reboot**
<p>The root node for the Reboot configuration service provider.</p>
<p>The supported operation is Get.</p>
<a href="" id="--vendor-msft-reboot"></a>**./Vendor/MSFT/Reboot**
The root node for the Reboot configuration service provider.
The supported operation is Get.
<a href="" id="rebootnow"></a>**RebootNow**
<p>This node executes a reboot of the device. RebootNow triggers a reboot within 5 minutes to allow the user to wrap up any active work.</p>
This node executes a reboot of the device. RebootNow triggers a reboot within 5 minutes to allow the user to wrap up any active work.
> [!NOTE]
> If this node is set to execute during a sync session, the device will reboot at the end of the sync session.
<p>The supported operations are Execute and Get.</p>
The supported operations are Execute and Get.
<a href="" id="schedule"></a>**Schedule**
<p>The supported operation is Get.</p>
The supported operation is Get.
<a href="" id="schedule-single"></a>**Schedule/Single**
<p>This node will execute a reboot at a scheduled date and time. The date and time value is **ISO 8601**, and both the date and time are required. </br>
Example to configure: 2018-10-25T18:00:00</p>
This node will execute a reboot at a scheduled date and time. The date and time value is **ISO 8601**, and both the date and time are required.
Example to configure: 2018-10-25T18:00:00
Setting a null (empty) date will delete the existing schedule. In accordance with the ISO 8601 format, the date and time representation needs to be 0000-00-00T00:00:00.
<p>The supported operations are Get, Add, Replace, and Delete.</p>
<p>The supported data type is "String".</p>
- The supported operations are Get, Add, Replace, and Delete.
- The supported data type is "String".
<a href="" id="schedule-dailyrecurrent"></a>**Schedule/DailyRecurrent**
<p>This node will execute a reboot each day at a scheduled time starting at the configured starting time and date. Setting a null (empty) date will delete the existing schedule. The date and time value is ISO8601, and both the date and time are required. The CSP will return the date time in the following format: 2018-06-29T10:00:00+01:00. </br>
Example to configure: 2018-10-25T18:00:00</p>
<p>The supported operations are Get, Add, Replace, and Delete.</p>
This node will execute a reboot each day at a scheduled time starting at the configured starting time and date. Setting a null (empty) date will delete the existing schedule. The date and time value is ISO8601, and both the date and time are required. The CSP will return the date time in the following format: 2018-06-29T10:00:00+01:00.
Example to configure: 2018-10-25T18:00:00
<p>The supported data type is "String".</p>
- The supported operations are Get, Add, Replace, and Delete.
- The supported data type is "String".
## Related topics
[Configuration service provider reference](configuration-service-provider-reference.md)

View File

@ -14,7 +14,6 @@ ms.date: 12/05/2017
# Reboot DDF file
This topic shows the OMA DM device description framework (DDF) for the **Reboot** configuration service provider. DDF files are used only with OMA DM provisioning XML.
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
@ -147,7 +146,6 @@ The XML below is the current version for this CSP.
## Related topics
[Reboot configuration service provider](reboot-csp.md)
 

View File

@ -14,7 +14,6 @@ ms.date: 06/26/2017
# RemoteFind CSP
The RemoteFind configuration service provider retrieves the location information for a particular device.
The following shows the RemoteFind configuration service provider management object in tree format as used by OMA Client Provisioning.
@ -37,21 +36,24 @@ Optional. The node accepts the requested radius value in meters. Valid values fo
The default value is 50. Replacing this value only replaces it for the current session. The value is not retained.
Supported operations are Replace and Get. The Add command is not supported.
- Supported operations are Replace and Get.
- The Add command is not supported.
<a href="" id="timeout"></a>**Timeout**
Optional. Value is DWORD in seconds.
The default value is 7, and the range is 0 to 1800 seconds. Replacing this value only replaces it for the current session. The value is not retained.
Supported operations are Replace and Get. The Add command is not supported.
- Supported operations are Replace and Get.
- The Add command is not supported.
<a href="" id="maximumage"></a>**MaximumAge**
Optional. The value represents the desired time window in minutes that the server will accept a successful location retrieval. The node enables the server to set the requested age value in 100 nanoseconds. Valid values for accuracy include any integer value between 0 and 1440 minutes.
The default value is 60. Replacing this value only replaces it for the current session. The value is not retained.
Supported operations are Replace and Get. The Add command is not supported.
- Supported operations are Replace and Get.
- The Add command is not supported.
<a href="" id="location"></a>**Location**
Required. Nodes under this path must be queried atomically in order to succeed. This is to prevent servers from querying incomplete sets of data.
@ -102,7 +104,7 @@ The default value is 0.
Supported operation is Get.
<a href="" id="age"></a>**Age**
Required. Provides the age in 100 nanoseconds for current location data.
Required. Provides the age in 100 nanoseconds for the current location data.
The value returned is an integer.
@ -176,7 +178,6 @@ Supported operation is Get.
## Related topics
[Configuration service provider reference](configuration-service-provider-reference.md)
 

View File

@ -14,7 +14,6 @@ ms.date: 12/05/2017
# RemoteFind DDF file
This topic shows the OMA DM device description framework (DDF) for the **RemoteFind** configuration service provider. DDF files are used only with OMA DM provisioning XML.
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).

View File

@ -14,7 +14,6 @@ ms.date: 06/26/2017
# RemoteRing CSP
You can use the RemoteRing configuration service provider to remotely trigger a device to produce an audible ringing sound, regardless of the volume that is set on the device.
The following DDF format shows the RemoteRing configuration service provider in tree format.
@ -40,7 +39,6 @@ The supported operation is Exec.
## Examples
The following sample shows how to initiate a remote ring on the device.
```xml

View File

@ -14,7 +14,6 @@ ms.date: 12/05/2017
# RemoteRing DDF file
This topic shows the OMA DM device description framework (DDF) for the **RemoteRing** configuration service provider. DDF files are used only with OMA DM provisioning XML.
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
@ -54,7 +53,7 @@ The XML below is the current version for this CSP.
<AccessType>
<Get />
</AccessType>
<Description>Required. The node accepts requests to ring the device. The supported operation is Exec</Description>
<Description>Required. The node accepts requests to ring the device. The supported operation is Exec.</Description>
<DFFormat>
<null />
</DFFormat>

View File

@ -14,7 +14,6 @@ ms.date: 08/13/2018
# RemoteWipe CSP
The RemoteWipe configuration service provider can be used by mobile operators DM server or enterprise management server to remotely wipe a device. The RemoteWipe configuration service provider can make the data stored in memory and hard disks difficult to recover if the device is remotely wiped after being lost or stolen.
The following shows the RemoteWipe configuration service provider management object in tree format as used by both OMA DM and OMA Client Provisioning. Enterprise IT Professionals can update these settings by using the Exchange Server.
@ -40,10 +39,10 @@ Supported operation is Exec.
<a href="" id="dowipepersistprovisioneddata"></a>**doWipePersistProvisionedData**
Specifies that provisioning data should be backed up to a persistent location, and then a remote wipe of the device should be performed.
Supported operation is Exec.
When used with OMA Client Provisioning, a dummy value of "1" should be included for this element.
Supported operation is Exec.
The information that was backed up will be restored and applied to the device when it resumes. The return status code shows whether the device accepted the Exec command.
<a href="" id="doWipeProtected"></a>**doWipeProtected**
@ -54,13 +53,13 @@ The doWipeProtected is functionally similar to doWipe. But unlike doWipe, which
Supported operation is Exec.
<a href="" id="doWipePersistUserData"></a>**doWipePersistUserData**
Added in Windows 10, version 1709. Exec on this node will perform a remote reset on the device and persist user accounts and data. The return status code shows whether the device accepted the Exec command.
Added in Windows 10, version 1709. Exec on this node will perform a remote reset on the device, and persist user accounts and data. The return status code shows whether the device accepted the Exec command.
<a href="" id="automaticredeployment"></a>**AutomaticRedeployment**
Added in Windows 10, version 1809. Node for the Autopilot Reset operation.
<a href="" id="doautomaticredeployment"></a>**AutomaticRedeployment/doAutomaticRedeployment**
Added in Windows 10, version 1809. Exec on this node triggers Autopilot Reset operation. This works like PC Reset, similar to other existing nodes in this RemoteWipe CSP, except that it keeps the device enrolled in Azure AD and MDM, keeps Wi-Fi profiles, and a few other settings like region, language, keyboard.
Added in Windows 10, version 1809. Exec on this node triggers Autopilot Reset operation. This works like PC Reset, similar to other existing nodes in RemoteWipe CSP, except that it keeps the device enrolled in Azure AD and MDM, keeps Wi-Fi profiles, and a few other settings like region, language, keyboard.
<a href="" id="lasterror"></a>**AutomaticRedeployment/LastError**
Added in Windows 10, version 1809. Error value, if any, associated with Autopilot Reset operation (typically an HRESULT).
@ -71,7 +70,7 @@ Added in Windows 10, version 1809. Status value indicating current state of an A
Supported values:
- 0: Never run (not started). The default state.
- 1: Complete.
- 1: Complete
- 10: Reset has been scheduled.
- 20: Reset is scheduled and waiting for a reboot.
- 30: Failed during CSP Execute ("Exec" in SyncML).

View File

@ -14,7 +14,6 @@ ms.date: 08/13/2018
# RemoteWipe DDF file
This topic shows the OMA DM device description framework (DDF) for the **RemoteWipe** configuration service provider. DDF files are used only with OMA DM provisioning XML.
Looking for the DDF XML files? See [CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download).
@ -109,7 +108,7 @@ The XML below is the DDF for Windows 10, version 1809.
<DFType>
<MIME>text/plain</MIME>
</DFType>
<Description>Exec on this node will perform a remote wipe on the device and fully clean the internal drive. In some device configurations, this command may leave the device unable to boot. The return status code shows whether the device accepted the Exec command.</Description>
<Description>Exec on this node will perform a remote wipe on the device, and fully clean the internal drive. In some device configurations, this command may leave the device unable to boot. The return status code shows whether the device accepted the Exec command.</Description>
</DFProperties>
</Node>
<Node>