mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-13 17:43:21 +00:00
77dc8384e3
Description: There have been repeated cases of misunderstanding the time format needed to reset the reboot date & time schedule, lately in ticket #4810. This is an attempt to shift the focus over to the fact that the Reboot CSP strictly follows the ISO 8601 standard, also when resetting the date and time for a reboot schedule. Changes proposed: - Add an extra sentence to inform the reader that the empty (null) value to reset an existing reboot schedule needs to contain zeros (0000-00-00T00:00:00). - Move the sentence "Setting a null (empty) date will delete [...]" to a line below the example to configure, as well as the addendum, to focus on this fact that a format representation is required. - Add the missing spacing in "ISO 8601" to keep its ISO name standard. - Remove redundant white space (10 lines) at the end of the document. issue ticket closure or reference: Closes #4810
58 lines
2.5 KiB
Markdown
58 lines
2.5 KiB
Markdown
---
|
||
title: Reboot CSP
|
||
description: Reboot CSP
|
||
ms.assetid: 4E3F1225-BBAD-40F5-A1AB-FF221B6BAF48
|
||
ms.reviewer:
|
||
manager: dansimp
|
||
ms.author: dansimp
|
||
ms.topic: article
|
||
ms.prod: w10
|
||
ms.technology: windows
|
||
author: manikadhiman
|
||
ms.date: 06/26/2017
|
||
---
|
||
|
||
# Reboot CSP
|
||
|
||
|
||
The Reboot configuration service provider is used to configure reboot settings.
|
||
|
||
The following diagram 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.
|
||
|
||
|
||
|
||
<a href="" id="--vendor-msft-reboot"></a>**./Vendor/MSFT/Reboot**
|
||
<p style="margin-left: 20px">The root node for the Reboot configuration service provider.</p>
|
||
|
||
<p style="margin-left: 20px">The supported operation is Get.</p>
|
||
|
||
<a href="" id="rebootnow"></a>**RebootNow**
|
||
<p style="margin-left: 20px">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>
|
||
|
||
> [!NOTE]
|
||
> If this node is set to execute during a sync session, the device will reboot at the end of the sync session.
|
||
|
||
<p style="margin-left: 20px">The supported operations are Execute and Get.</p>
|
||
|
||
<a href="" id="schedule"></a>**Schedule**
|
||
<p style="margin-left: 20px">The supported operation is Get.</p>
|
||
|
||
<a href="" id="schedule-single"></a>**Schedule/Single**
|
||
<p style="margin-left: 20px">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>
|
||
|
||
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 style="margin-left: 20px">The supported operations are Get, Add, Replace, and Delete.</p>
|
||
|
||
<a href="" id="schedule-dailyrecurrent"></a>**Schedule/DailyRecurrent**
|
||
<p style="margin-left: 20px">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 style="margin-left: 20px">The supported operations are Get, Add, Replace, and Delete.</p>
|
||
|
||
## Related topics
|
||
|
||
|
||
[Configuration service provider reference](configuration-service-provider-reference.md)
|