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

reliability remoteassistance removablestorage

Browse Source
This commit is contained in:
Liz Long 2023-01-05 10:06:34 -05:00
parent 0630d0e12b
commit 0163f5f4e4
3 changed files with 2052 additions and 1656 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

386
windows/client-management/mdm/policy-csp-admx-reliability.md
View File

@ -1,237 +1,244 @@
---
title: Policy CSP - ADMX_Reliability
description: Policy CSP - ADMX_Reliability
title: ADMX_Reliability Policy CSP
description: Learn more about the ADMX_Reliability Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa
ms.date: 01/05/2023
ms.localizationpriority: medium
ms.topic: article
ms.prod: windows-client
ms.technology: itpro-manage
author: vinaypamnani-msft
ms.date: 08/13/2020
ms.reviewer:
manager: aaroncz
ms.topic: reference
---
<!-- Auto-Generated CSP Document -->
<!-- ADMX_Reliability-Begin -->
# Policy CSP - ADMX_Reliability
> [!TIP]
> These are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](../understanding-admx-backed-policies.md).
> Some of these are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
>
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](../understanding-admx-backed-policies.md#enabling-a-policy).
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
>
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
<hr/>
<!-- ADMX_Reliability-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ADMX_Reliability-Editable-End -->
<!--Policies-->
## ADMX_Reliability policies
<!-- EE_EnablePersistentTimeStamp-Begin -->
## EE_EnablePersistentTimeStamp
<dl>
<dd>
<a href="#admx-reliability-ee-enablepersistenttimestamp">ADMX_Reliability/EE_EnablePersistentTimeStamp</a>
</dd>
<dd>
<a href="#admx-reliability-pch-reportshutdownevents">ADMX_Reliability/PCH_ReportShutdownEvents</a>
</dd>
<dd>
<a href="#admx-reliability-shutdowneventtrackerstatefile">ADMX_Reliability/ShutdownEventTrackerStateFile</a>
</dd>
<dd>
<a href="#admx-reliability-shutdownreason">ADMX_Reliability/ShutdownReason</a>
</dd>
</dl>
<!-- EE_EnablePersistentTimeStamp-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- EE_EnablePersistentTimeStamp-Applicability-End -->
<!-- EE_EnablePersistentTimeStamp-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_Reliability/EE_EnablePersistentTimeStamp
```
<!-- EE_EnablePersistentTimeStamp-OmaUri-End -->
<hr/>
<!--Policy-->
<a href="" id="admx-reliability-ee-enablepersistenttimestamp"></a>**ADMX_Reliability/EE_EnablePersistentTimeStamp**
<!--SupportedSKUs-->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * Device
<hr/>
<!--/Scope-->
<!--Description-->
<!-- EE_EnablePersistentTimeStamp-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting allows the system to detect the time of unexpected shutdowns by writing the current time to disk on a schedule controlled by the Timestamp Interval.
If you enable this policy setting, you're able to specify how often the Persistent System Timestamp is refreshed and then written to the disk. You can specify the Timestamp Interval in seconds.
If you enable this policy setting, you are able to specify how often the Persistent System Timestamp is refreshed and subsequently written to the disk. You can specify the Timestamp Interval in seconds.
If you disable this policy setting, the Persistent System Timestamp is turned off and the timing of unexpected shutdowns isn't recorded.
If you disable this policy setting, the Persistent System Timestamp is turned off and the timing of unexpected shutdowns is not recorded.
If you don't configure this policy setting, the Persistent System Timestamp is refreshed according to the default, which is every 60 seconds beginning with Windows Server 2003.
If you do not configure this policy setting, the Persistent System Timestamp is refreshed according the default, which is every 60 seconds beginning with Windows Server 2003.
> [!NOTE]
> This feature might interfere with power configuration settings that turn off hard disks after a period of inactivity. These power settings may be accessed in the Power Options Control Panel.
Note: This feature might interfere with power configuration settings that turn off hard disks after a period of inactivity. These power settings may be accessed in the Power Options Control Panel.
<!-- EE_EnablePersistentTimeStamp-Description-End -->
<!--/Description-->
<!-- EE_EnablePersistentTimeStamp-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- EE_EnablePersistentTimeStamp-Editable-End -->
<!-- EE_EnablePersistentTimeStamp-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Enable Persistent Time Stamp*
- GP name: *EE_EnablePersistentTimeStamp*
- GP path: *System*
- GP ADMX file name: *Reliability.admx*
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- EE_EnablePersistentTimeStamp-DFProperties-End -->
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!-- EE_EnablePersistentTimeStamp-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<hr/>
**ADMX mapping**:
<!--Policy-->
<a href="" id="admx-reliability-pch-reportshutdownevents"></a>**ADMX_Reliability/PCH_ReportShutdownEvents**
| Name | Value |
|:--|:--|
| Name | EE_EnablePersistentTimeStamp |
| Friendly Name | Enable Persistent Time Stamp |
| Location | Computer Configuration |
| Path | System |
| Registry Key Name | Software\Policies\Microsoft\Windows NT\Reliability |
| Registry Value Name | TimeStampEnabled |
| ADMX File Name | Reliability.admx |
<!-- EE_EnablePersistentTimeStamp-AdmxBacked-End -->
<!--SupportedSKUs-->
<!-- EE_EnablePersistentTimeStamp-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- EE_EnablePersistentTimeStamp-Examples-End -->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!-- EE_EnablePersistentTimeStamp-End -->
<!--/SupportedSKUs-->
<hr/>
<!-- PCH_ReportShutdownEvents-Begin -->
## PCH_ReportShutdownEvents
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
<!-- PCH_ReportShutdownEvents-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- PCH_ReportShutdownEvents-Applicability-End -->
> [!div class = "checklist"]
> * Device
<!-- PCH_ReportShutdownEvents-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_Reliability/PCH_ReportShutdownEvents
```
<!-- PCH_ReportShutdownEvents-OmaUri-End -->
<hr/>
<!--/Scope-->
<!--Description-->
<!-- PCH_ReportShutdownEvents-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting controls whether or not unplanned shutdown events can be reported when error reporting is enabled.
If you enable this policy setting, error reporting includes unplanned shutdown events.
If you disable this policy setting, unplanned shutdown events aren't included in error reporting.
If you disable this policy setting, unplanned shutdown events are not included in error reporting.
If you don't configure this policy setting, users can adjust this setting using the control panel, which is set to "Upload unplanned shutdown events" by default.
If you do not configure this policy setting, users can adjust this setting using the control panel, which is set to "Upload unplanned shutdown events" by default.
Also see the "Configure Error Reporting" policy setting.
<!-- PCH_ReportShutdownEvents-Description-End -->
<!--/Description-->
<!-- PCH_ReportShutdownEvents-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- PCH_ReportShutdownEvents-Editable-End -->
<!-- PCH_ReportShutdownEvents-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Report unplanned shutdown events*
- GP name: *PCH_ReportShutdownEvents*
- GP path: *Windows Components\Windows Error Reporting\Advanced Error Reporting Settings*
- GP ADMX file name: *Reliability.admx*
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- PCH_ReportShutdownEvents-DFProperties-End -->
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!-- PCH_ReportShutdownEvents-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<hr/>
**ADMX mapping**:
<!--Policy-->
<a href="" id="admx-reliability-shutdowneventtrackerstatefile"></a>**ADMX_Reliability/ShutdownEventTrackerStateFile**
| Name | Value |
|:--|:--|
| Name | PCH_ReportShutdownEvents |
| Friendly Name | Report unplanned shutdown events |
| Location | Computer Configuration |
| Path | CAT_WindowsErrorReporting > Advanced Error Reporting Settings |
| Registry Key Name | Software\Policies\Microsoft\PCHealth\ErrorReporting |
| Registry Value Name | IncludeShutdownErrs |
| ADMX File Name | Reliability.admx |
<!-- PCH_ReportShutdownEvents-AdmxBacked-End -->
<!--SupportedSKUs-->
<!-- PCH_ReportShutdownEvents-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- PCH_ReportShutdownEvents-Examples-End -->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!-- PCH_ReportShutdownEvents-End -->
<!--/SupportedSKUs-->
<hr/>
<!-- ShutdownEventTrackerStateFile-Begin -->
## ShutdownEventTrackerStateFile
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
<!-- ShutdownEventTrackerStateFile-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- ShutdownEventTrackerStateFile-Applicability-End -->
> [!div class = "checklist"]
> * Device
<!-- ShutdownEventTrackerStateFile-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_Reliability/ShutdownEventTrackerStateFile
```
<!-- ShutdownEventTrackerStateFile-OmaUri-End -->
<hr/>
<!--/Scope-->
<!--Description-->
<!-- ShutdownEventTrackerStateFile-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting defines when the Shutdown Event Tracker System State Data feature is activated.
The system state data file contains information about the basic system state and the state of all running processes.
The system state data file contains information about the basic system state as well as the state of all running processes.
If you enable this policy setting, the System State Data feature is activated when the user indicates that the shutdown or restart is unplanned.
If you disable this policy setting, the System State Data feature is never activated.
If you don't configure this policy setting, the default behavior for the System State Data feature occurs.
If you do not configure this policy setting, the default behavior for the System State Data feature occurs.
Note: By default, the System State Data feature is always enabled on Windows Server 2003. See "Supported on" for all supported versions.
<!-- ShutdownEventTrackerStateFile-Description-End -->
<!--/Description-->
<!-- ShutdownEventTrackerStateFile-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ShutdownEventTrackerStateFile-Editable-End -->
<!-- ShutdownEventTrackerStateFile-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Activate Shutdown Event Tracker System State Data feature*
- GP name: *ShutdownEventTrackerStateFile*
- GP path: *System*
- GP ADMX file name: *Reliability.admx*
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- ShutdownEventTrackerStateFile-DFProperties-End -->
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!-- ShutdownEventTrackerStateFile-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<hr/>
**ADMX mapping**:
<!--Policy-->
<a href="" id="admx-reliability-shutdownreason"></a>**ADMX_Reliability/ShutdownReason**
| Name | Value |
|:--|:--|
| Name | ShutdownEventTrackerStateFile |
| Friendly Name | Activate Shutdown Event Tracker System State Data feature |
| Location | Computer Configuration |
| Path | System |
| Registry Key Name | Software\Policies\Microsoft\Windows NT\Reliability |
| Registry Value Name | SnapShot |
| ADMX File Name | Reliability.admx |
<!-- ShutdownEventTrackerStateFile-AdmxBacked-End -->
<!--SupportedSKUs-->
<!-- ShutdownEventTrackerStateFile-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- ShutdownEventTrackerStateFile-Examples-End -->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!-- ShutdownEventTrackerStateFile-End -->
<!--/SupportedSKUs-->
<hr/>
<!-- ShutdownReason-Begin -->
## ShutdownReason
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
<!-- ShutdownReason-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- ShutdownReason-Applicability-End -->
> [!div class = "checklist"]
> * Device
<!-- ShutdownReason-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_Reliability/ShutdownReason
```
<!-- ShutdownReason-OmaUri-End -->
<hr/>
<!--/Scope-->
<!--Description-->
The Shutdown Event Tracker can be displayed when you shut down a workstation or server. This tracker is an extra set of questions that is displayed when you invoke a shutdown to collect information related to why you're shutting down the computer.
<!-- ShutdownReason-Description-Begin -->
<!-- Description-Source-ADMX -->
The Shutdown Event Tracker can be displayed when you shut down a workstation or server. This is an extra set of questions that is displayed when you invoke a shutdown to collect information related to why you are shutting down the computer.
If you enable this setting and choose "Always" from the drop-down menu list, the Shutdown Event Tracker is displayed when the computer shuts down.
@ -239,28 +246,55 @@ If you enable this policy setting and choose "Server Only" from the drop-down me
If you enable this policy setting and choose "Workstation Only" from the drop-down menu list, the Shutdown Event Tracker is displayed when you shut down a computer running a client version of Windows. (See "Supported on" for supported versions.)
If you disable this policy setting, the Shutdown Event Tracker isn't displayed when you shut down the computer.
If you disable this policy setting, the Shutdown Event Tracker is not displayed when you shut down the computer.
If you don't configure this policy setting, the default behavior for the Shutdown Event Tracker occurs.
If you do not configure this policy setting, the default behavior for the Shutdown Event Tracker occurs.
> [!NOTE]
> By default, the Shutdown Event Tracker is only displayed on computers running Windows Server.
Note: By default, the Shutdown Event Tracker is only displayed on computers running Windows Server.
<!-- ShutdownReason-Description-End -->
<!--/Description-->
<!-- ShutdownReason-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ShutdownReason-Editable-End -->
<!-- ShutdownReason-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Display Shutdown Event Tracker*
- GP name: *ShutdownReason*
- GP path: *System*
- GP ADMX file name: *Reliability.admx*
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- ShutdownReason-DFProperties-End -->
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!-- ShutdownReason-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
**ADMX mapping**:
| Name | Value |
|:--|:--|
| Name | ShutdownReason |
| Friendly Name | Display Shutdown Event Tracker |
| Location | Computer Configuration |
| Path | System |
| Registry Key Name | Software\Policies\Microsoft\Windows NT\Reliability |
| Registry Value Name | ShutdownReasonOn |
| ADMX File Name | Reliability.admx |
<!-- ShutdownReason-AdmxBacked-End -->
<!--/Policies-->
<!-- ShutdownReason-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- ShutdownReason-Examples-End -->
<!-- ShutdownReason-End -->
<!-- ADMX_Reliability-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ADMX_Reliability-CspMoreInfo-End -->
<!-- ADMX_Reliability-End -->
## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md)

211
windows/client-management/mdm/policy-csp-admx-remoteassistance.md
View File

@ -1,118 +1,111 @@
---
title: Policy CSP - ADMX_RemoteAssistance
description: Learn about Policy CSP - ADMX_RemoteAssistance.
title: ADMX_RemoteAssistance Policy CSP
description: Learn more about the ADMX_RemoteAssistance Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa
ms.date: 01/05/2023
ms.localizationpriority: medium
ms.topic: article
ms.prod: windows-client
ms.technology: itpro-manage
author: vinaypamnani-msft
ms.date: 12/14/2020
ms.reviewer:
manager: aaroncz
ms.topic: reference
---
<!-- Auto-Generated CSP Document -->
<!-- ADMX_RemoteAssistance-Begin -->
# Policy CSP - ADMX_RemoteAssistance
> [!TIP]
> These are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](../understanding-admx-backed-policies.md).
> Some of these are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
>
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](../understanding-admx-backed-policies.md#enabling-a-policy).
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
>
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
<hr/>
<!-- ADMX_RemoteAssistance-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ADMX_RemoteAssistance-Editable-End -->
<!--Policies-->
## ADMX_RemoteAssistance policies
<!-- RA_EncryptedTicketOnly-Begin -->
## RA_EncryptedTicketOnly
<dl>
<dd>
<a href="#admx-remoteassistance-ra-encryptedticketonly">ADMX_RemoteAssistance/RA_EncryptedTicketOnly</a>
</dd>
<dd>
<a href="#admx-remoteassistance-ra-optimize-bandwidth">ADMX_RemoteAssistance/RA_Optimize_Bandwidth</a>
</dd>
</dl>
<!-- RA_EncryptedTicketOnly-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- RA_EncryptedTicketOnly-Applicability-End -->
<!-- RA_EncryptedTicketOnly-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_RemoteAssistance/RA_EncryptedTicketOnly
```
<!-- RA_EncryptedTicketOnly-OmaUri-End -->
<hr/>
<!--Policy-->
<a href="" id="admx-remoteassistance-ra-encryptedticketonly"></a>**ADMX_RemoteAssistance/RA_EncryptedTicketOnly**
<!--SupportedSKUs-->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * Device
<hr/>
<!--/Scope-->
<!--Description-->
This policy setting enables Remote Assistance invitations to be generated with improved encryption so that only computers running this version (or later versions) of the operating system can connect. This policy setting doesn't affect Remote Assistance connections that are initiated by instant messaging contacts or the unsolicited Offer Remote Assistance.
<!-- RA_EncryptedTicketOnly-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting enables Remote Assistance invitations to be generated with improved encryption so that only computers running this version (or later versions) of the operating system can connect. This policy setting does not affect Remote Assistance connections that are initiated by instant messaging contacts or the unsolicited Offer Remote Assistance.
If you enable this policy setting, only computers running this version (or later versions) of the operating system can connect to this computer.
If you disable this policy setting, computers running this version and a previous version of the operating system can connect to this computer.
If you don't configure this policy setting, users can configure this setting in System Properties in the Control Panel.
If you do not configure this policy setting, users can configure the setting in System Properties in the Control Panel.
<!-- RA_EncryptedTicketOnly-Description-End -->
<!--/Description-->
<!-- RA_EncryptedTicketOnly-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- RA_EncryptedTicketOnly-Editable-End -->
<!-- RA_EncryptedTicketOnly-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Allow only Windows Vista or later connections*
- GP name: *RA_EncryptedTicketOnly*
- GP path: *System\Remote Assistance*
- GP ADMX file name: *RemoteAssistance.admx*
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- RA_EncryptedTicketOnly-DFProperties-End -->
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!-- RA_EncryptedTicketOnly-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--Policy-->
<a href="" id="admx-remoteassistance-ra-optimize-bandwidth"></a>**ADMX_RemoteAssistance/RA_Optimize_Bandwidth**
**ADMX mapping**:
<!--SupportedSKUs-->
| Name | Value |
|:--|:--|
| Name | RA_EncryptedTicketOnly |
| Friendly Name | Allow only Windows Vista or later connections |
| Location | Computer Configuration |
| Path | System > Remote Assistance |
| Registry Key Name | Software\policies\Microsoft\Windows NT\Terminal Services |
| Registry Value Name | CreateEncryptedOnlyTickets |
| ADMX File Name | RemoteAssistance.admx |
<!-- RA_EncryptedTicketOnly-AdmxBacked-End -->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!-- RA_EncryptedTicketOnly-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- RA_EncryptedTicketOnly-Examples-End -->
<!--/SupportedSKUs-->
<hr/>
<!-- RA_EncryptedTicketOnly-End -->
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
<!-- RA_Optimize_Bandwidth-Begin -->
## RA_Optimize_Bandwidth
> [!div class = "checklist"]
> * Device
<!-- RA_Optimize_Bandwidth-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- RA_Optimize_Bandwidth-Applicability-End -->
<hr/>
<!-- RA_Optimize_Bandwidth-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_RemoteAssistance/RA_Optimize_Bandwidth
```
<!-- RA_Optimize_Bandwidth-OmaUri-End -->
<!--/Scope-->
<!--Description-->
<!-- RA_Optimize_Bandwidth-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting allows you to improve performance in low bandwidth scenarios.
This setting is incrementally scaled from "No optimization" to "Full optimization". Each incremental setting includes the previous optimization setting.
@ -120,12 +113,10 @@ This setting is incrementally scaled from "No optimization" to "Full optimizatio
For example:
"Turn off background" will include the following optimizations:
-No full window drag
-Turn off background
"Full optimization" will include the following optimizations:
-Use 16-bit color (8-bit color in Windows Vista)
-Turn off font smoothing (not supported in Windows Vista)
-No full window drag
@ -135,25 +126,51 @@ If you enable this policy setting, bandwidth optimization occurs at the level sp
If you disable this policy setting, application-based settings are used.
If you don't configure this policy setting, application-based settings are used.
If you do not configure this policy setting, application-based settings are used.
<!-- RA_Optimize_Bandwidth-Description-End -->
<!--/Description-->
<!-- RA_Optimize_Bandwidth-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- RA_Optimize_Bandwidth-Editable-End -->
<!-- RA_Optimize_Bandwidth-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Turn on bandwidth optimization*
- GP name: *RA_Optimize_Bandwidth*
- GP path: *System\Remote Assistance*
- GP ADMX file name: *RemoteAssistance.admx*
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- RA_Optimize_Bandwidth-DFProperties-End -->
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!-- RA_Optimize_Bandwidth-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
**ADMX mapping**:
<!--/Policies-->
| Name | Value |
|:--|:--|
| Name | RA_Optimize_Bandwidth |
| Friendly Name | Turn on bandwidth optimization |
| Location | Computer Configuration |
| Path | System > Remote Assistance |
| Registry Key Name | Software\policies\Microsoft\Windows NT\Terminal Services |
| Registry Value Name | UseBandwidthOptimization |
| ADMX File Name | RemoteAssistance.admx |
<!-- RA_Optimize_Bandwidth-AdmxBacked-End -->
## Related topics
<!-- RA_Optimize_Bandwidth-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- RA_Optimize_Bandwidth-Examples-End -->
[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md)
<!-- RA_Optimize_Bandwidth-End -->
<!-- ADMX_RemoteAssistance-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ADMX_RemoteAssistance-CspMoreInfo-End -->
<!-- ADMX_RemoteAssistance-End -->
## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md)

3085
windows/client-management/mdm/policy-csp-admx-removablestorage.md
View File

File diff suppressed because it is too large Load Diff