mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 05:47:23 +00:00
Merge pull request #6083 from MicrosoftDocs/master
Publish 12/10/2021, 3:30 PM
This commit is contained in:
commit
9071794e9a
@ -8359,6 +8359,12 @@ dfsdiscoverdc">ADMX_DFS/DFSDiscoverDC</a>
|
||||
<dd>
|
||||
<a href="./policy-csp-system.md#system-feedbackhubalwayssavediagnosticslocally" id="system-feedbackhubalwayssavediagnosticslocally">System/FeedbackHubAlwaysSaveDiagnosticsLocally</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="./policy-csp-system.md#system-limitdiagnosticlogcollection" id="system-limitdiagnosticlogcollection">System/LimitDiagnosticLogCollection</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="./policy-csp-system.md#system-limitdumpcollection" id="system-limitdumpcollection">System/LimitDumpCollection</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="./policy-csp-system.md#system-limitenhanceddiagnosticdatawindowsanalytics" id="system-limitenhanceddiagnosticdatawindowsanalytics">System/LimitEnhancedDiagnosticDataWindowsAnalytics</a>
|
||||
</dd>
|
||||
@ -8992,6 +8998,9 @@ dfsdiscoverdc">ADMX_DFS/DFSDiscoverDC</a>
|
||||
<dd>
|
||||
<a href="./policy-csp-wirelessdisplay.md#wirelessdisplay-allowmdnsdiscovery" id="wirelessdisplay-allowmdnsdiscovery">WirelessDisplay/AllowMdnsDiscovery</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="./policy-csp-wirelessdisplay.md#wirelessdisplay-allowmovementdetectiononinfrastructure" id="wirelessdisplay-allowmovementdetectiononinfrastructure">WirelessDisplay/AllowMovementDetectionOnInfrastructure</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="./policy-csp-wirelessdisplay.md#wirelessdisplay-allowprojectionfrompc" id="wirelessdisplay-allowprojectionfrompc">WirelessDisplay/AllowProjectionFromPC</a>
|
||||
</dd>
|
||||
|
@ -94,6 +94,12 @@ manager: dansimp
|
||||
<dd>
|
||||
<a href="#system-feedbackhubalwayssavediagnosticslocally">System/FeedbackHubAlwaysSaveDiagnosticsLocally</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#system-limitdiagnosticlogcollection">System/LimitDiagnosticLogCollection</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#system-limitdumpcollection">System/LimitDumpCollection</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#system-limitenhanceddiagnosticdatawindowsanalytics">System/LimitEnhancedDiagnosticDataWindowsAnalytics</a>
|
||||
</dd>
|
||||
@ -1295,6 +1301,105 @@ The following list shows the supported values:
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="system-limitdiagnosticlogcollection"></a>**System/LimitDiagnosticLogCollection**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|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 specifies whether diagnostic log data can be collected when more information is needed to troubleshoot a problem. It is sent only if we have permission to collect optional diagnostic data, and only if the device meets the criteria for additional data collection.
|
||||
|
||||
If you disable or do not configure this policy setting, we may occasionally collect advanced diagnostic data if the user has opted to send optional diagnostic data.
|
||||
|
||||
<!--/Description-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
- GP Friendly name: *Limit Diagnostic Log Collection*
|
||||
- GP name: *LimitDiagnosticLogCollection*
|
||||
- GP path: *Data Collection and Preview Builds*
|
||||
- GP ADMX file name: *DataCollection.admx*
|
||||
|
||||
<!--/ADMXMapped-->
|
||||
<!--SupportedValues-->
|
||||
The following list shows the supported values:
|
||||
|
||||
- 0 – Disabled
|
||||
- 1 – Enabled
|
||||
|
||||
<!--/SupportedValues-->
|
||||
<!--/Policy-->
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="system-limitdumpcollection"></a>**System/LimitDumpCollection**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|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 limits the type of dumps that can be collected when more information is needed to troubleshoot a problem. These dumps are not sent unless we have permission to collect optional diagnostic data.
|
||||
|
||||
By enabling this policy setting, Windows Error Reporting is limited to sending kernel mini dumps and user mode triage dumps only.
|
||||
|
||||
If you disable or do not configure this policy setting, we may occasionally collect full or heap dumps if the user has opted to send optional diagnostic data.
|
||||
|
||||
<!--/Description-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
- GP Friendly name: *Limit Dump Collection*
|
||||
- GP name: *LimitDumpCollection*
|
||||
- GP path: *Data Collection and Preview Builds*
|
||||
- GP ADMX file name: *DataCollection.admx*
|
||||
|
||||
<!--/ADMXMapped-->
|
||||
<!--SupportedValues-->
|
||||
The following list shows the supported values:
|
||||
|
||||
- 0 – Disabled
|
||||
- 1 – Enabled
|
||||
<!--/SupportedValues-->
|
||||
<!--/Policy-->
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="system-limitenhanceddiagnosticdatawindowsanalytics"></a>**System/LimitEnhancedDiagnosticDataWindowsAnalytics**
|
||||
|
||||
|
@ -26,6 +26,9 @@ manager: dansimp
|
||||
<dd>
|
||||
<a href="#wirelessdisplay-allowmdnsdiscovery">WirelessDisplay/AllowMdnsDiscovery</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#wirelessdisplay-allowmovementdetectiononinfrastructure">WirelessDisplay/AllowMovementDetectionOnInfrastructure</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#wirelessdisplay-allowprojectionfrompc">WirelessDisplay/AllowProjectionFromPC</a>
|
||||
</dd>
|
||||
@ -129,6 +132,53 @@ The following list shows the supported values:
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="wirelessdisplay-allowmovementdetectiononinfrastructure"></a>**WirelessDisplay/AllowMovementDetectionOnInfrastructure**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
|
||||
|Edition|Windows 10|Windows 11|
|
||||
|--- |--- |--- |
|
||||
|Home|No|No|
|
||||
|Pro|Yes|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 allows you to disable the infrastructure movement detection feature.
|
||||
|
||||
If you set it to 0, your PC may stay connected and continue to project if you walk away from a Wireless Display receiver to which you are projecting over infrastructure.
|
||||
|
||||
If you set it to 1, your PC will detect that you have moved and will automatically disconnect your infrastructure Wireless Display session.
|
||||
|
||||
The default value is 1.
|
||||
|
||||
<!--/Description-->
|
||||
<!--SupportedValues-->
|
||||
|
||||
The following list shows the supported values:
|
||||
|
||||
- 0 - Do not allow
|
||||
- 1 (Default) - Allow
|
||||
|
||||
<!--/SupportedValues-->
|
||||
<!--/Policy-->
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="wirelessdisplay-allowprojectionfrompc"></a>**WirelessDisplay/AllowProjectionFromPC**
|
||||
|
||||
|
@ -39,6 +39,7 @@ Windows Hello for Business provisioning enables a user to enroll a new, strong,
|
||||
|
||||
## Azure AD joined provisioning in a Managed environment
|
||||

|
||||
[Full size image](images/howitworks/prov-aadj-managed.png)
|
||||
|
||||
| Phase | Description |
|
||||
| :----: | :----------- |
|
||||
@ -50,6 +51,7 @@ Windows Hello for Business provisioning enables a user to enroll a new, strong,
|
||||
[Return to top](#windows-hello-for-business-provisioning)
|
||||
## Azure AD joined provisioning in a Federated environment
|
||||

|
||||
[Full size image](images/howitworks/prov-aadj-federated.png)
|
||||
|
||||
| Phase | Description |
|
||||
| :----: | :----------- |
|
||||
@ -60,7 +62,7 @@ Windows Hello for Business provisioning enables a user to enroll a new, strong,
|
||||
[Return to top](#windows-hello-for-business-provisioning)
|
||||
## Hybrid Azure AD joined provisioning in a Key Trust deployment in a Managed environment
|
||||

|
||||
|
||||
[Full size image](images/howitworks/prov-haadj-keytrust-managed.png)
|
||||
|
||||
| Phase | Description |
|
||||
|:-----:|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
@ -78,7 +80,7 @@ Windows Hello for Business provisioning enables a user to enroll a new, strong,
|
||||
[Return to top](#windows-hello-for-business-provisioning)
|
||||
## Hybrid Azure AD joined provisioning in a synchronous Certificate Trust deployment in a Federated environment
|
||||

|
||||
|
||||
[Full size image](images/howitworks/prov-haadj-instant-certtrust-federated.png)
|
||||
|
||||
| Phase | Description |
|
||||
|:-----:|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
@ -96,6 +98,7 @@ Windows Hello for Business provisioning enables a user to enroll a new, strong,
|
||||
[Return to top](#windows-hello-for-business-provisioning)
|
||||
## Domain joined provisioning in an On-premises Key Trust deployment
|
||||

|
||||
[Full size image](images/howitworks/prov-onprem-keytrust.png)
|
||||
|
||||
| Phase | Description |
|
||||
| :----: | :----------- |
|
||||
@ -107,6 +110,7 @@ Windows Hello for Business provisioning enables a user to enroll a new, strong,
|
||||
[Return to top](#windows-hello-for-business-provisioning)
|
||||
## Domain joined provisioning in an On-premises Certificate Trust deployment
|
||||

|
||||
[Full size image](images/howitworks/prov-onprem-certtrust.png)
|
||||
|
||||
| Phase | Description |
|
||||
| :----: | :----------- |
|
||||
|
@ -59,7 +59,7 @@ The following table lists the Group Policy settings that you can configure for W
|
||||
|Minimum PIN length|Computer|<p><b>Not configured</b>: PIN length must be greater than or equal to 4.<p><b>Enabled</b>: PIN length must be greater than or equal to the number you specify.<p><b>Disabled</b>: PIN length must be greater than or equal to 4.|
|
||||
|Expiration|Computer|<p><b>Not configured</b>: PIN does not expire.<p><b>Enabled</b>: PIN can be set to expire after any number of days between 1 and 730, or PIN can be set to never expire by setting policy to 0.<p><b>Disabled</b>: PIN does not expire.|
|
||||
|History|Computer|<p><b>Not configured</b>: Previous PINs are not stored.<p><b>Enabled</b>: Specify the number of previous PINs that can be associated to a user account that can't be reused.<p><b>Disabled</b>: Previous PINs are not stored.<div class="alert"><b>Note</b> Current PIN is included in PIN history.</div>|
|
||||
|Require special characters|Computer|<p><b>Not configured</b>: Users cannot include a special character in their PIN<p><b>Enabled</b>: Users must include at least one special character in their PIN.<p><b>Disabled</b>: Users cannot include a special character in their PIN.|
|
||||
|Require special characters|Computer|<p><b>Not configured</b>: Windows allows, but does not require, special characters in the PIN.<p><b>Enabled</b>: Windows requires the user to include at least one special character in their PIN.<p><b>Disabled</b>: Windows does not allow the user to include special characters in their PIN.|
|
||||
|Require uppercase letters|Computer|<p><b>Not configured</b>: Users cannot include an uppercase letter in their PIN.<p><b>Enabled</b>: Users must include at least one uppercase letter in their PIN.<p><b>Disabled</b>: Users cannot include an uppercase letter in their PIN.|
|
||||
|
||||
### Phone Sign-in
|
||||
@ -168,4 +168,4 @@ If you want to use Windows Hello for Business with certificates, you'll need a d
|
||||
- [Windows Hello and password changes](hello-and-password-changes.md)
|
||||
- [Windows Hello errors during PIN creation](hello-errors-during-pin-creation.md)
|
||||
- [Event ID 300 - Windows Hello successfully created](hello-event-300.md)
|
||||
- [Windows Hello biometrics in the enterprise](hello-biometrics-in-enterprise.md)
|
||||
- [Windows Hello biometrics in the enterprise](hello-biometrics-in-enterprise.md)
|
||||
|
Loading…
x
Reference in New Issue
Block a user