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

Formatting fixes

Browse Source
This commit is contained in:
Vinay Pamnani (from Dev Box) 2025-02-14 11:01:00 -07:00
parent 80cc10b7ed
commit d63a451036
9 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
windows/client-management/mdm/declaredconfiguration-csp.md
View File

@ -1,7 +1,7 @@
---
title: DeclaredConfiguration CSP
description: Learn more about the DeclaredConfiguration CSP.
ms.date: 02/13/2025
ms.date: 02/14/2025
ms.topic: generated-reference
---
@ -226,7 +226,7 @@ Uniquely identifies the configuration document. No other document can have this
<!-- Device-Host-Complete-Documents-{DocID}-Document-Description-Begin -->
<!-- Description-Source-DDF -->
The Document node's value is an XML based document containing a collection of settings and values to configure the specified scenario. The Declared Configuration stack verifies the syntax of the document, the stack marks the document to be processed asynchronously by the client. The stack then returns control back to the OMA-DM service. The stack, in turn, asynchronously processes the request. Below is an example of a specified desired state configuration using the Declared Configuration URI ./Device/Vendor/MSFT/DeclaredConfiguration/Host/Complete/Documents/27FEA311-68. B9-4320-9. FC4-296. F6FDFAFE2/Document.
The Document node's value is an XML based document containing a collection of settings and values to configure the specified scenario. The Declared Configuration stack verifies the syntax of the document, the stack marks the document to be processed asynchronously by the client. The stack then returns control back to the OMA-DM service. The stack, in turn, asynchronously processes the request. Below is an example of a specified desired state configuration using the Declared Configuration URI ./Device/Vendor/MSFT/DeclaredConfiguration/Host/Complete/Documents/27FEA311-68B9-4320-9FC4-296F6FDFAFE2/Document.
<!-- Device-Host-Complete-Documents-{DocID}-Document-Description-End -->
<!-- Device-Host-Complete-Documents-{DocID}-Document-Editable-Begin -->
@ -591,7 +591,7 @@ Uniquely identifies the inventory document. No other document can have this id.
<!-- Device-Host-Inventory-Documents-{DocID}-Document-Description-Begin -->
<!-- Description-Source-DDF -->
The Document node's value is an XML based document containing a collection of settings that will be used to retrieve their values. The Declared Configuration stack verifies the syntax of the document, the stack marks the document to be processed asynchronously by the client. The stack then returns control back to the OMA-DM service. The stack, in turn, asynchronously processes the request. Below is an example of a specified desired state configuration using the Declared Configuration URI ./Device/Vendor/MSFT/DeclaredConfiguration/Host/Inventory/Documents/27FEA311-68. B9-4320-9. FC4-296. F6FDFAFE2/Document.
The Document node's value is an XML based document containing a collection of settings that will be used to retrieve their values. The Declared Configuration stack verifies the syntax of the document, the stack marks the document to be processed asynchronously by the client. The stack then returns control back to the OMA-DM service. The stack, in turn, asynchronously processes the request. Below is an example of a specified desired state configuration using the Declared Configuration URI ./Device/Vendor/MSFT/DeclaredConfiguration/Host/Inventory/Documents/27FEA311-68B9-4320-9FC4-296F6FDFAFE2/Document.
<!-- Device-Host-Inventory-Documents-{DocID}-Document-Description-End -->
<!-- Device-Host-Inventory-Documents-{DocID}-Document-Editable-Begin -->

4
windows/client-management/mdm/devdetail-csp.md
View File

@ -1,7 +1,7 @@
---
title: DevDetail CSP
description: Learn more about the DevDetail CSP.
ms.date: 02/13/2025
ms.date: 02/14/2025
ms.topic: generated-reference
---
@ -400,7 +400,7 @@ Total free storage in MB from first internal drive on the device.
<!-- Device-Ext-Microsoft-LocalTime-Description-Begin -->
<!-- Description-Source-DDF -->
Returns the client local time in ISO 8601 format. Example: 2003-06-16. T18:37:44Z.
Returns the client local time in ISO 8601 format. Example: 2003-06-16T18:37:44Z.
<!-- Device-Ext-Microsoft-LocalTime-Description-End -->
<!-- Device-Ext-Microsoft-LocalTime-Editable-Begin -->

4
windows/client-management/mdm/policy-csp-appvirtualization.md
View File

@ -1,7 +1,7 @@
---
title: AppVirtualization Policy CSP
description: Learn more about the AppVirtualization Area in Policy CSP.
ms.date: 02/13/2025
ms.date: 02/14/2025
ms.topic: generated-reference
---
@ -313,7 +313,7 @@ Enables a UX to display to the user when a publishing refresh is performed on th
<!-- Description-Source-ADMX -->
Reporting Server URL: Displays the URL of reporting server.
Reporting Time: When the client data should be reported to the server. Acceptable range is 0~23, corresponding to the 24 hours in a day. A good practice is, don't set this time to a busy hour, e.g. 9. AM.
Reporting Time: When the client data should be reported to the server. Acceptable range is 0~23, corresponding to the 24 hours in a day. A good practice is, don't set this time to a busy hour, e.g. 9AM.
Delay reporting for the random minutes: The maximum minutes of random delay on top of the reporting time. For a busy system, the random delay will help reduce the server load.

4
windows/client-management/mdm/policy-csp-bluetooth.md
View File

@ -1,7 +1,7 @@
---
title: Bluetooth Policy CSP
description: Learn more about the Bluetooth Area in Policy CSP.
ms.date: 02/13/2025
ms.date: 02/14/2025
ms.topic: generated-reference
---
@ -266,7 +266,7 @@ Sets the local Bluetooth device name. If this is set, the value that it's set to
<!-- ServicesAllowedList-Description-Begin -->
<!-- Description-Source-DDF -->
Set a list of allowable services and profiles. String hex formatted array of Bluetooth service UUIDs in canonical format, delimited by semicolons. For example, {782AFCFC-7. CAA-436. C-8. BF0-78. CD0FFBD4AF}. The default value is an empty string. For more information, see ServicesAllowedList usage guide.
Set a list of allowable services and profiles. String hex formatted array of Bluetooth service UUIDs in canonical format, delimited by semicolons. For example, {782AFCFC-7CAA-436C-8BF0-78CD0FFBD4AF}. The default value is an empty string. For more information, see ServicesAllowedList usage guide.
<!-- ServicesAllowedList-Description-End -->
<!-- ServicesAllowedList-Editable-Begin -->

4
windows/client-management/mdm/policy-csp-connectivity.md
View File

@ -1,7 +1,7 @@
---
title: Connectivity Policy CSP
description: Learn more about the Connectivity Area in Policy CSP.
ms.date: 02/13/2025
ms.date: 02/14/2025
ms.topic: generated-reference
---
@ -702,7 +702,7 @@ This policy makes all configurable settings in the 'Cellular' Settings page read
<!-- DisableCrossDeviceResume-Description-Begin -->
<!-- Description-Source-DDF -->
This policy allows IT admins to turn off CrossDeviceResume feature to continue tasks, such as browsing file, continue using 1. P/ 3. P apps that require linking between Phone and PC.
This policy allows IT admins to turn off CrossDeviceResume feature to continue tasks, such as browsing file, continue using 1P/ 3P apps that require linking between Phone and PC.
- If you enable this policy setting, the Windows device won't receive any CrossDeviceResume notification.

4
windows/client-management/mdm/policy-csp-devicehealthmonitoring.md
View File

@ -1,7 +1,7 @@
---
title: DeviceHealthMonitoring Policy CSP
description: Learn more about the DeviceHealthMonitoring Area in Policy CSP.
ms.date: 02/13/2025
ms.date: 02/14/2025
ms.topic: generated-reference
---
@ -31,7 +31,7 @@ ms.topic: generated-reference
<!-- AllowDeviceHealthMonitoring-Description-Begin -->
<!-- Description-Source-DDF -->
Enable/disable 4. Nines device health monitoring on devices.
Enable/disable device health monitoring on devices.
<!-- AllowDeviceHealthMonitoring-Description-End -->
<!-- AllowDeviceHealthMonitoring-Editable-Begin -->

4
windows/client-management/mdm/policy-csp-eap.md
View File

@ -1,7 +1,7 @@
---
title: Eap Policy CSP
description: Learn more about the Eap Area in Policy CSP.
ms.date: 02/13/2025
ms.date: 02/14/2025
ms.topic: generated-reference
---
@ -31,7 +31,7 @@ ms.topic: generated-reference
<!-- AllowTLS1_3-Description-Begin -->
<!-- Description-Source-DDF -->
Added in Windows 10, version 21. H1. Allow or disallow use of TLS 1.3 during EAP client authentication.
Added in Windows 10, version 21H1. Allow or disallow use of TLS 1.3 during EAP client authentication.
<!-- AllowTLS1_3-Description-End -->
<!-- AllowTLS1_3-Editable-Begin -->

4
windows/client-management/mdm/policy-csp-remotemanagement.md
View File

@ -1,7 +1,7 @@
---
title: RemoteManagement Policy CSP
description: Learn more about the RemoteManagement Area in Policy CSP.
ms.date: 02/13/2025
ms.date: 02/14/2025
ms.topic: generated-reference
---
@ -286,7 +286,7 @@ For example, if you want the service to listen only on IPv4 addresses, leave the
Ranges are specified using the syntax IP1-IP2. Multiple ranges are separated using "," (comma) as the delimiter.
Example IPv4 filters:\n2.0.0.1-2.0.0.20, 24.0.0.1-24.0.0.22
Example IPv6 filters:\n3FFE:FFFF:7654:FEDA:1245:BA98:0000:0000-3. FFE:FFFF:7654:FEDA:1245:BA98:3210:4562.
Example IPv6 filters:\n3FFE:FFFF:7654:FEDA:1245:BA98:0000:0000-3FFE:FFFF:7654:FEDA:1245:BA98:3210:4562.
<!-- AllowRemoteServerManagement-Description-End -->
<!-- AllowRemoteServerManagement-Editable-Begin -->

8
windows/client-management/mdm/reboot-csp.md
View File

@ -1,7 +1,7 @@
---
title: Reboot CSP
description: Learn more about the Reboot CSP.
ms.date: 02/13/2025
ms.date: 02/14/2025
ms.topic: generated-reference
---
@ -121,7 +121,7 @@ The supported operation is Get.
<!-- Device-Schedule-DailyRecurrent-Description-Begin -->
<!-- Description-Source-DDF -->
Value in ISO8601 date and time format (such as 2025-10-07. T10:35:00) is required. While it's supported to set either DailyRecurrent or WeeklyRecurrent schedules, it isn't supported to enable both settings simultaneously. A reboot will be scheduled to occur every day at the configured time starting at the specified date and time. Setting a null (empty) date will delete the existing schedule.
Value in ISO8601 date and time format (such as 2025-10-07T10:35:00) is required. While it's supported to set either DailyRecurrent or WeeklyRecurrent schedules, it isn't supported to enable both settings simultaneously. A reboot will be scheduled to occur every day at the configured time starting at the specified date and time. Setting a null (empty) date will delete the existing schedule.
<!-- Device-Schedule-DailyRecurrent-Description-End -->
<!-- Device-Schedule-DailyRecurrent-Editable-Begin -->
@ -160,7 +160,7 @@ Value in ISO8601 date and time format (such as 2025-10-07. T10:35:00) is require
<!-- Device-Schedule-Single-Description-Begin -->
<!-- Description-Source-DDF -->
Value in ISO8601 date and time format (such as 2025-10-07. T10:35:00) is required. Both the date and time are required. A reboot will be scheduled to occur at the specified date and time. Setting a null (empty) date will delete the existing schedule.
Value in ISO8601 date and time format (such as 2025-10-07T10:35:00) is required. Both the date and time are required. A reboot will be scheduled to occur at the specified date and time. Setting a null (empty) date will delete the existing schedule.
<!-- Device-Schedule-Single-Description-End -->
<!-- Device-Schedule-Single-Editable-Begin -->
@ -199,7 +199,7 @@ Value in ISO8601 date and time format (such as 2025-10-07. T10:35:00) is require
<!-- Device-Schedule-WeeklyRecurrent-Description-Begin -->
<!-- Description-Source-DDF -->
Value in ISO8601 date and time format (such as 2025-10-07. T10:35:00) is required. While it's supported to set either DailyRecurrent or WeeklyRecurrent schedules, it isn't supported to enable both settings simultaneously. A reboot will be scheduled to occur every week at the configured day and time starting at the specified date and time. Setting a null (empty) date will delete the existing schedule.
Value in ISO8601 date and time format (such as 2025-10-07T10:35:00) is required. While it's supported to set either DailyRecurrent or WeeklyRecurrent schedules, it isn't supported to enable both settings simultaneously. A reboot will be scheduled to occur every week at the configured day and time starting at the specified date and time. Setting a null (empty) date will delete the existing schedule.
<!-- Device-Schedule-WeeklyRecurrent-Description-End -->
<!-- Device-Schedule-WeeklyRecurrent-Editable-Begin -->