mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge branch 'main' into patch-5
This commit is contained in:
Stephanie Savell
GitHub
commit
24507b6aac
@ -2,6 +2,14 @@
|
||||
|
||||
|
||||
|
||||
## Week of August 15, 2022
|
||||
|
||||
|
||||
| Published On |Topic title | Change |
|
||||
|------|------------|--------|
|
||||
| 8/17/2022 | [For IT administrators get Minecraft Education Edition](/education/windows/school-get-minecraft) | modified |
|
||||
|
||||
|
||||
## Week of August 08, 2022
|
||||
|
||||
|
||||
|
||||
@ -83,6 +83,9 @@ The table below lists the supported configurations for remotely connecting to an
|
||||
> [!NOTE]
|
||||
> If the RDP client is running Windows Server 2016 or Windows Server 2019, to be able to connect to Azure Active Directory-joined PCs, it must [allow Public Key Cryptography Based User-to-User (PKU2U) authentication requests to use online identities](/windows/security/threat-protection/security-policy-settings/network-security-allow-pku2u-authentication-requests-to-this-computer-to-use-online-identities).
|
||||
|
||||
> [!NOTE]
|
||||
> When an Azure Active Directory group is added to the Remote Desktop Users group on a Windows device, it isn't honoured when the user that belongs to the Azure AD group logs in through Remote Desktop Protocol (they can't sign in using Remote Desktop Connection). In this scenario, Network Level Authentication should be disabled to run the connection.
|
||||
|
||||
## Related topics
|
||||
|
||||
[How to use Remote Desktop](https://support.microsoft.com/windows/how-to-use-remote-desktop-5fe128d5-8fb1-7a23-3b8a-41e636865e8c)
|
||||
|
||||
@ -14,7 +14,7 @@ ms.collection: highpri
|
||||
|
||||
# Diagnose MDM failures in Windows 10
|
||||
|
||||
To help diagnose enrollment or device management issues in Windows 10 devices managed by an MDM server, you can examine the MDM logs collected from the desktop. The following sections describe the procedures for collecting MDM logs.
|
||||
To help diagnose enrollment or device management issues in Windows 10 devices managed by an MDM server, you can examine the MDM logs collected from the desktop. The following sections describe the procedures for collecting MDM logs.
|
||||
|
||||
## Download the MDM Diagnostic Information log from Windows 10 PCs
|
||||
|
||||
@ -30,32 +30,34 @@ To help diagnose enrollment or device management issues in Windows 10 devices m
|
||||
|
||||
1. In File Explorer, navigate to c:\Users\Public\Documents\MDMDiagnostics to see the report.
|
||||
|
||||
## Use command to collect logs directly from Windows 10 PCs
|
||||
## Use command to collect logs directly from Windows 10 PCs
|
||||
|
||||
You can also collect the MDM Diagnostic Information logs using the following command:
|
||||
|
||||
```xml
|
||||
mdmdiagnosticstool.exe -area DeviceEnrollment;DeviceProvisioning;Autopilot -zip c:\users\public\documents\MDMDiagReport.zip
|
||||
mdmdiagnosticstool.exe -area "DeviceEnrollment;DeviceProvisioning;Autopilot" -zip "c:\users\public\documents\MDMDiagReport.zip"
|
||||
```
|
||||
- In File Explorer, navigate to c:\Users\Public\Documents\MDMDiagnostics to see the report.
|
||||
|
||||
- In File Explorer, navigate to c:\Users\Public\Documents\MDMDiagnostics to see the report.
|
||||
|
||||
### Understanding zip structure
|
||||
|
||||
The zip file will have logs according to the areas that were used in the command. This explanation is based on DeviceEnrollment, DeviceProvisioning and Autopilot areas. It applies to the zip files collected via command line or Feedback Hub
|
||||
|
||||
- DiagnosticLogCSP_Collector_Autopilot_*: Autopilot etls
|
||||
- DiagnosticLogCSP_Collector_DeviceProvisioning_*: Provisioning etls (Microsoft-Windows-Provisioning-Diagnostics-Provider)
|
||||
- MDMDiagHtmlReport.html: Summary snapshot of MDM space configurations and policies. Includes, management url, MDM server device ID, certificates, policies.
|
||||
- MdmDiagLogMetadata, json: mdmdiagnosticstool metadata file, contains command-line arguments used to run the tool
|
||||
- MDMDiagReport.xml: contains a more detail view into the MDM space configurations, e.g enrollment variables
|
||||
- MdmDiagReport_RegistryDump.reg: contains dumps from common MDM registry locations
|
||||
- MdmLogCollectorFootPrint.txt: mdmdiagnosticslog tool logs from running the command
|
||||
- *.evtx: Common event viewer logs microsoft-windows-devicemanagement-enterprise-diagnostics-provider-admin.evtx main one that contains MDM events.
|
||||
- DiagnosticLogCSP_Collector_Autopilot_*: Autopilot etls
|
||||
- DiagnosticLogCSP_Collector_DeviceProvisioning_*: Provisioning etls (Microsoft-Windows-Provisioning-Diagnostics-Provider)
|
||||
- MDMDiagHtmlReport.html: Summary snapshot of MDM space configurations and policies. Includes, management url, MDM server device ID, certificates, policies.
|
||||
- MdmDiagLogMetadata, json: mdmdiagnosticstool metadata file, contains command-line arguments used to run the tool
|
||||
- MDMDiagReport.xml: contains a more detail view into the MDM space configurations, e.g enrollment variables
|
||||
- MdmDiagReport_RegistryDump.reg: contains dumps from common MDM registry locations
|
||||
- MdmLogCollectorFootPrint.txt: mdmdiagnosticslog tool logs from running the command
|
||||
- *.evtx: Common event viewer logs microsoft-windows-devicemanagement-enterprise-diagnostics-provider-admin.evtx main one that contains MDM events.
|
||||
|
||||
## Collect logs directly from Windows 10 PCs
|
||||
## Collect logs directly from Windows 10 PCs
|
||||
|
||||
Starting with the Windows 10, version 1511, MDM logs are captured in the Event Viewer in the following location:
|
||||
Starting with the Windows 10, version 1511, MDM logs are captured in the Event Viewer in the following location:
|
||||
|
||||
- Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostic-Provider
|
||||
- Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostic-Provider
|
||||
|
||||
Here's a screenshot:
|
||||
|
||||
@ -63,34 +65,34 @@ Here's a screenshot:
|
||||
|
||||
In this location, the **Admin** channel logs events by default. However, if you need more details logs you can enable **Debug** logs by choosing **Show Analytic and Debug** logs option in **View** menu in Event Viewer.
|
||||
|
||||
**To collect Admin logs**
|
||||
### Collect admin logs
|
||||
|
||||
1. Right click on the **Admin** node.
|
||||
2. Select **Save all events as**.
|
||||
3. Choose a location and enter a filename.
|
||||
4. Click **Save**.
|
||||
5. Choose **Display information for these languages** and then select **English**.
|
||||
6. Click **Ok**.
|
||||
1. Right click on the **Admin** node.
|
||||
2. Select **Save all events as**.
|
||||
3. Choose a location and enter a filename.
|
||||
4. Click **Save**.
|
||||
5. Choose **Display information for these languages** and then select **English**.
|
||||
6. Click **Ok**.
|
||||
|
||||
For more detailed logging, you can enable **Debug** logs. Right click on the **Debug** node and then click **Enable Log**.
|
||||
|
||||
**To collect Debug logs**
|
||||
### Collect debug logs
|
||||
|
||||
1. Right click on the **Debug** node.
|
||||
2. Select **Save all events as**.
|
||||
3. Choose a location and enter a filename.
|
||||
4. Click **Save**.
|
||||
5. Choose **Display information for these languages** and then select **English**.
|
||||
6. Click **Ok**.
|
||||
1. Right click on the **Debug** node.
|
||||
2. Select **Save all events as**.
|
||||
3. Choose a location and enter a filename.
|
||||
4. Click **Save**.
|
||||
5. Choose **Display information for these languages** and then select **English**.
|
||||
6. Click **Ok**.
|
||||
|
||||
You can open the log files (.evtx files) in the Event Viewer on a Windows 10 PC running the November 2015 update.
|
||||
You can open the log files (.evtx files) in the Event Viewer on a Windows 10 PC running the November 2015 update.
|
||||
|
||||
## Collect logs remotely from Windows 10 PCs
|
||||
## Collect logs remotely from Windows 10 PCs
|
||||
|
||||
When the PC is already enrolled in MDM, you can remotely collect logs from the PC through the MDM channel if your MDM server supports this facility. The [DiagnosticLog CSP](diagnosticlog-csp.md) can be used to enable an event viewer channel by full name. Here are the Event Viewer names for the Admin and Debug channels:
|
||||
|
||||
- Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%2FAdmin
|
||||
- Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%2FDebug
|
||||
- Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%2FAdmin
|
||||
- Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%2FDebug
|
||||
|
||||
Example: Enable the Debug channel logging
|
||||
|
||||
@ -235,27 +237,27 @@ After the logs are collected on the device, you can retrieve the files through t
|
||||
|
||||
For best results, ensure that the PC or VM on which you're viewing logs matches the build of the OS from which the logs were collected.
|
||||
|
||||
1. Open eventvwr.msc.
|
||||
2. Right-click on **Event Viewer(Local)** and select **Open Saved Log**.
|
||||
1. Open eventvwr.msc.
|
||||
2. Right-click on **Event Viewer(Local)** and select **Open Saved Log**.
|
||||
|
||||
|
||||
|
||||
3. Navigate to the etl file that you got from the device and then open the file.
|
||||
4. Click **Yes** when prompted to save it to the new log format.
|
||||
3. Navigate to the etl file that you got from the device and then open the file.
|
||||
4. Click **Yes** when prompted to save it to the new log format.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
5. The new view contains traces from the channel. Click on **Filter Current Log** from the **Actions** menu.
|
||||
5. The new view contains traces from the channel. Click on **Filter Current Log** from the **Actions** menu.
|
||||
|
||||
|
||||
|
||||
6. Add a filter to Event sources by selecting **DeviceManagement-EnterpriseDiagnostics-Provider** and click **OK**.
|
||||
6. Add a filter to Event sources by selecting **DeviceManagement-EnterpriseDiagnostics-Provider** and click **OK**.
|
||||
|
||||
|
||||
|
||||
7. Now you're ready to start reviewing the logs.
|
||||
7. Now you're ready to start reviewing the logs.
|
||||
|
||||
|
||||
|
||||
@ -283,5 +285,3 @@ Here's an example of how to collect current MDM device state data using the [Dia
|
||||
</SyncBody>
|
||||
</SyncML>
|
||||
```
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: vinaypamnani-msft
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 06/06/2022
|
||||
ms.date: 08/01/2022
|
||||
---
|
||||
|
||||
# Policies in Policy CSP supported by HoloLens 2
|
||||
@ -52,12 +52,18 @@ ms.date: 06/06/2022
|
||||
- [Experience/AllowManualMDMUnenrollment](policy-csp-experience.md#experience-allowmanualmdmunenrollment)
|
||||
- [MixedReality/AADGroupMembershipCacheValidityInDays](policy-csp-mixedreality.md#mixedreality-aadgroupmembershipcachevalidityindays)
|
||||
- [MixedReality/AADGroupMembershipCacheValidityInDays](./policy-csp-mixedreality.md#mixedreality-aadgroupmembershipcachevalidityindays) <sup>9</sup>
|
||||
- [MixedReality/AllowCaptivePortalBeforeSignIn](./policy-csp-mixedreality.md#mixedreality-allowcaptiveportalpeforesignin) <sup>Insider</sup>
|
||||
- [MixedReality/AllowLaunchUriInSingleAppKiosk](./policy-csp-mixedreality.md#mixedreality-allowlaunchuriinsingleappkiosk)<sup>10</sup>
|
||||
- [MixedReality/AutoLogonUser](./policy-csp-mixedreality.md#mixedreality-autologonuser) <sup>11</sup>
|
||||
- [MixedReality/BrightnessButtonDisabled](./policy-csp-mixedreality.md#mixedreality-brightnessbuttondisabled) <sup>9</sup>
|
||||
- [MixedReality/ConfigureMovingPlatform](policy-csp-mixedreality.md#mixedreality-configuremovingplatform) <sup>*[Feb. 2022 Servicing release](/hololens/hololens-release-notes#windows-holographic-version-21h2---february-2022-update)</sup>
|
||||
- [MixedReality/DisallowNetworkConnectivityPassivePolling](./policy-csp-mixedreality.md#mixedreality-disablesisallownetworkconnectivitypassivepolling) <sup>Insider</sup>
|
||||
- [MixedReality/FallbackDiagnostics](./policy-csp-mixedreality.md#mixedreality-fallbackdiagnostics) <sup>9</sup>
|
||||
- [MixedReality/HeadTrackingMode](policy-csp-mixedreality.md#mixedreality-headtrackingmode) <sup>9</sup>
|
||||
- [MixedReality/ManualDownDirectionDisabled](policy-csp-mixedreality.md#mixedreality-manualdowndirectiondisabled) <sup>*[Feb. 2022 Servicing release](/hololens/hololens-release-notes#windows-holographic-version-21h2---february-2022-update)</sup>
|
||||
- [MixedReality/MicrophoneDisabled](./policy-csp-mixedreality.md#mixedreality-microphonedisabled) <sup>9</sup>
|
||||
- [MixedReality/SkipCalibrationDuringSetup](./policy-csp-mixedreality.md#mixedreality-skipcalibrationduringsetup) <sup>Insider</sup>
|
||||
- [MixedReality/SkipTrainingDuringSetup](./policy-csp-mixedreality.md#mixedreality-skiptrainingduringsetup) <sup>Insider</sup>
|
||||
- [MixedReality/VisitorAutoLogon](policy-csp-mixedreality.md#mixedreality-visitorautologon) <sup>10</sup>
|
||||
- [MixedReality/VolumeButtonDisabled](./policy-csp-mixedreality.md#mixedreality-volumebuttondisabled) <sup>9</sup>
|
||||
- [Power/DisplayOffTimeoutOnBattery](./policy-csp-power.md#power-displayofftimeoutonbattery) <sup>9</sup>
|
||||
@ -67,6 +73,7 @@ ms.date: 06/06/2022
|
||||
- [Power/StandbyTimeoutOnBattery](./policy-csp-power.md#power-standbytimeoutonbattery) <sup>9</sup>
|
||||
- [Power/StandbyTimeoutPluggedIn](./policy-csp-power.md#power-standbytimeoutpluggedin) <sup>9</sup>
|
||||
- [Privacy/AllowInputPersonalization](policy-csp-privacy.md#privacy-allowinputpersonalization)
|
||||
- [Privacy/DisablePrivacyExperience](./policy-csp-privacy.md#privacy-disableprivacyexperience) <sup>Insider</sup>
|
||||
- [Privacy/LetAppsAccessAccountInfo](policy-csp-privacy.md#privacy-letappsaccessaccountinfo)
|
||||
- [Privacy/LetAppsAccessAccountInfo_ForceAllowTheseApps](policy-csp-privacy.md#privacy-letappsaccessaccountinfo-forceallowtheseapps)
|
||||
- [Privacy/LetAppsAccessAccountInfo_ForceDenyTheseApps](policy-csp-privacy.md#privacy-letappsaccessaccountinfo-forcedenytheseapps)
|
||||
@ -96,6 +103,11 @@ ms.date: 06/06/2022
|
||||
- [Settings/AllowVPN](policy-csp-settings.md#settings-allowvpn)
|
||||
- [Settings/PageVisibilityList](./policy-csp-settings.md#settings-pagevisibilitylist) <sup>9</sup>
|
||||
- [Speech/AllowSpeechModelUpdate](policy-csp-speech.md#speech-allowspeechmodelupdate)
|
||||
- [Storage/AllowStorageSenseGlobal](policy-csp-storage.md#storage-allowstoragesenseglobal) <sup>Insider</sup>
|
||||
- [Storage/AllowStorageSenseTemporaryFilesCleanup](policy-csp-storage.md#storage-allowstoragesensetemporaryfilescleanup) <sup>Insider</sup>
|
||||
- [Storage/ConfigStorageSenseCloudContentDehydrationThreshold](policy-csp-storage.md#storage-configstoragesensecloudcontentdehydrationthreshold) <sup>Insider</sup>
|
||||
- [Storage/ConfigStorageSenseDownloadsCleanupThreshold](policy-csp-storage.md#storage-configstoragesensedownloadscleanupthreshold) <sup>Insider</sup>
|
||||
- [Storage/ConfigStorageSenseGlobalCadence](policy-csp-storage.md#storage-configstoragesenseglobalcadence) <sup>Insider</sup>
|
||||
- [System/AllowCommercialDataPipeline](policy-csp-system.md#system-allowcommercialdatapipeline)
|
||||
- [System/AllowLocation](policy-csp-system.md#system-allowlocation)
|
||||
- [System/AllowStorageCard](policy-csp-system.md#system-allowstoragecard)
|
||||
@ -140,6 +152,7 @@ Footnotes:
|
||||
- 9 - Available in [Windows Holographic, version 20H2](/hololens/hololens-release-notes-2004#windows-holographic-version-20h2)
|
||||
- 10 - Available in [Windows Holographic, version 21H1](/hololens/hololens-release-notes#windows-holographic-version-21h1)
|
||||
- 11 - Available in [Windows Holographic, version 21H2](/hololens/hololens-release-notes#windows-holographic-version-21h2)
|
||||
- Insider - Available in our current [HoloLens Insider builds](/hololens/hololens-insider).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: vinaypamnani-msft
|
||||
ms.date: 01/03/2022
|
||||
ms.date: 08/19/2022
|
||||
ms.reviewer:
|
||||
manager: aaroncz
|
||||
---
|
||||
@ -3757,7 +3757,7 @@ ADMX Info:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy setting allows you to define the number of days that must pass before spyware security intelligence is considered out of date. If security intelligence is determined to be out of date, this state may trigger several other actions, including falling back to an alternative update source or displaying a warning icon in the user interface. By default, this value is set to 14 days.
|
||||
This policy setting allows you to define the number of days that must pass before spyware security intelligence is considered out of date. If security intelligence is determined to be out of date, this state may trigger several other actions, including falling back to an alternative update source or displaying a warning icon in the user interface. By default, this value is set to 7 days.
|
||||
|
||||
We don't recommend setting the value to less than 2 days to prevent machines from going out of date.
|
||||
|
||||
@ -4797,4 +4797,4 @@ ADMX Info:
|
||||
|
||||
## Related topics
|
||||
|
||||
[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md)
|
||||
[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md)
|
||||
|
||||
@ -22,6 +22,12 @@ manager: aaroncz
|
||||
<dd>
|
||||
<a href="#mixedreality-aadgroupmembershipcachevalidityindays">MixedReality/AADGroupMembershipCacheValidityInDays</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#mixedreality-allowcaptiveportalpeforesignin">MixedReality/AllowCaptivePortalBeforeSignIn</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#mixedreality-allowlaunchuriinsingleappkiosk">MixedReality/AllowLaunchUriInSingleAppKiosk</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#mixedreality-autologonuser">MixedReality/AutoLogonUser</a>
|
||||
</dd>
|
||||
@ -31,15 +37,27 @@ manager: aaroncz
|
||||
<dd>
|
||||
<a href="#mixedreality-configuremovingplatform">MixedReality/ConfigureMovingPlatform</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#mixedreality-disablesisallownetworkconnectivitypassivepolling">MixedReality/DisallowNetworkConnectivityPassivePolling</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#mixedreality-fallbackdiagnostics">MixedReality/FallbackDiagnostics</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#mixedreality-headtrackingmode">MixedReality/HeadTrackingMode</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#mixedreality-manualdowndirectiondisabled">MixedReality/ManualDownDirectionDisabled</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#mixedreality-microphonedisabled">MixedReality/MicrophoneDisabled</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#mixedreality-skipcalibrationduringsetup">MixedReality/SkipCalibrationDuringSetup</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#mixedreality-skiptrainingduringsetup">MixedReality/SkipTrainingDuringSetup</a>
|
||||
</dd>
|
||||
<dd>
|
||||
<a href="#mixedreality-visitorautologon">MixedReality/VisitorAutoLogon</a>
|
||||
</dd>
|
||||
@ -79,7 +97,74 @@ Steps to use this policy correctly:
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="mixedreality-autologonuser"></a>**MixedReality/AutoLogonUser**
|
||||
<a href="" id="mixedreality-allowcaptiveportalpeforesignin"></a>**MixedReality/AllowCaptivePortalBeforeSignIn**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
|
||||
|Windows Edition|Supported|
|
||||
|--- |--- |
|
||||
|HoloLens (first gen) Development Edition|No|
|
||||
|HoloLens (first gen) Commercial Suite|No|
|
||||
|HoloLens 2|Yes|
|
||||
|
||||
> [!NOTE]
|
||||
> This feature is currently only available in [HoloLens Insider](/hololens/hololens-insider) builds.
|
||||
|
||||
<!--Scope-->
|
||||
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||
|
||||
> [!div class = "checklist"]
|
||||
> * Device
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Description-->
|
||||
This new feature is an opt-in policy that IT Admins can enable to help with the setup of new devices in new areas or new users. When this policy is turned on it allows a captive portal on the sign-in screen, which allows a user to enter credentials to connect to the Wi-Fi access point. If enabled, sign in will implement similar logic as OOBE to display captive portal if necessary.
|
||||
|
||||
MixedReality/AllowCaptivePortalBeforeSignIn
|
||||
|
||||
The OMA-URI of new policy: `./Device/Vendor/MSFT/Policy/Config/MixedReality/AllowCaptivePortalBeforeSignIn`
|
||||
|
||||
Bool value
|
||||
|
||||
<!--/Description-->
|
||||
|
||||
<!--/SupportedSKUs-->
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="mixedreality-allowlaunchuriinsingleappkiosk"></a>**MixedReality/AllowLaunchUriInSingleAppKiosk**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
|
||||
|Windows Edition|Supported|
|
||||
|--- |--- |
|
||||
|HoloLens (first gen) Development Edition|No|
|
||||
|HoloLens (first gen) Commercial Suite|No|
|
||||
|HoloLens 2|Yes|
|
||||
|
||||
<!--Scope-->
|
||||
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||
|
||||
> [!div class = "checklist"]
|
||||
> * Device
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Description-->
|
||||
This can be enabled to allow for other apps to be launched with in a single app Kiosk, which may be useful, for example, if you want to launch the Settings app to calibrate your device or change your Wi-fi.
|
||||
|
||||
By default, launching applications via Launcher API (Launcher Class (Windows.System) - Windows UWP applications) is disabled in single app kiosk mode. To enable applications to launch in single app kiosk mode on HoloLens devices, set the policy value to true.
|
||||
|
||||
The OMA-URI of policy: `./Device/Vendor/MSFT/Policy/Config/MixedReality/AllowLaunchUriInSingleAppKiosk`
|
||||
|
||||
Bool value
|
||||
|
||||
<!--/Description-->
|
||||
|
||||
<!--/SupportedSKUs-->
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="mixedreality-autologonuser"></a>**MixedReality/AutoLogonUser**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
|
||||
@ -90,7 +175,7 @@ Steps to use this policy correctly:
|
||||
|HoloLens 2|Yes|
|
||||
|
||||
<!--/Description-->
|
||||
This new AutoLogonUser policy controls whether a user will be automatically signed in. Some customers want to set up devices that are tied to an identity but don't want any sign-in experience. Imagine picking up a device and using remote assist immediately. Or have a benefit of being able to rapidly distribute HoloLens devices and enable their end users to speed up sign in.
|
||||
This new AutoLogonUser policy controls whether a user will be automatically signed in. Some customers want to set up devices that are tied to an identity but don't want any sign-in experience. Imagine picking up a device and using remote assist immediately. Or have a benefit of being able to rapidly distribute HoloLens devices and enable their end users to speed up sign-in.
|
||||
|
||||
When the policy is set to a non-empty value, it specifies the email address of the auto log-on user. The specified user must sign in to the device at least once to enable autologon.
|
||||
|
||||
@ -101,7 +186,7 @@ Supported value is String.
|
||||
|
||||
- User with the same email address will have autologon enabled.
|
||||
|
||||
On a device where this policy is configured, the user specified in the policy will need to sign in at least once. Subsequent reboots of the device after the first sign in will have the specified user automatically signed in. Only a single autologon user is supported. Once enabled, the automatically signed-in user won't be able to sign out manually. To sign in as a different user, the policy must first be disabled.
|
||||
On a device where this policy is configured, the user specified in the policy will need to sign in at least once. Subsequent reboots of the device after the first sign-in will have the specified user automatically signed in. Only a single autologon user is supported. Once enabled, the automatically signed-in user won't be able to sign out manually. To sign in as a different user, the policy must first be disabled.
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
@ -204,7 +289,7 @@ The following list shows the supported values:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
This policy controls the behavior of moving platform feature on Hololens 2, that is, whether it's turned off / on, or it can be toggled by a user. It should only be used by customers who intend to use Hololens 2 in moving environments with low dynamic motion. For background information, see [HoloLens 2 Moving Platform Mode | Microsoft Docs](/hololens/hololens2-moving-platform#:~:text=Why%20Moving%20Platform%20Mode%20is%20Necessary%20HoloLens%20needs%2csimilar%20pieces%20of%20information%20from%20two%20separate%20sources:).
|
||||
This policy controls the behavior of moving platform feature on HoloLens 2, that is, whether it's turned off / on, or it can be toggled by a user. It should only be used by customers who intend to use HoloLens 2 in moving environments with low dynamic motion. For background information, see [HoloLens 2 Moving Platform Mode | Microsoft Docs](/hololens/hololens2-moving-platform#:~:text=Why%20Moving%20Platform%20Mode%20is%20Necessary%20HoloLens%20needs%2csimilar%20pieces%20of%20information%20from%20two%20separate%20sources:).
|
||||
|
||||
<!--/Description-->
|
||||
|
||||
@ -222,6 +307,42 @@ Supported value is Integer.
|
||||
<!--/Policy-->
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="mixedreality-disablesisallownetworkconnectivitypassivepolling"></a>**MixedReality/DisallowNetworkConnectivityPassivePolling**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
|
||||
|Windows Edition|Supported|
|
||||
|--- |--- |
|
||||
|HoloLens (first gen) Development Edition|No|
|
||||
|HoloLens (first gen) Commercial Suite|No|
|
||||
|HoloLens 2|Yes|
|
||||
|
||||
<!--/SupportedSKUs-->
|
||||
|
||||
> [!NOTE]
|
||||
> This feature is currently only available in [HoloLens Insider](/hololens/hololens-insider) builds.
|
||||
|
||||
<!--Scope-->
|
||||
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||
|
||||
> [!div class = "checklist"]
|
||||
> * Device
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Description-->
|
||||
Windows Network Connectivity Status Indicator may get false positive Internet capable signal from passive polling. That may result in unexpected Wi-Fi adapter reset when device connects to an intranet only access point. Enabling this policy would avoid unexpected network interruptions caused by false positive NCSI passive polling.
|
||||
|
||||
The OMA-URI of new policy: `./Device/Vendor/MSFT/Policy/Config/MixedReality/DisallowNetworkConnectivityPassivePolling`
|
||||
|
||||
- Bool value
|
||||
|
||||
<!--/Description-->
|
||||
|
||||
<!--/Policy-->
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="mixedreality-fallbackdiagnostics"></a>**MixedReality/FallbackDiagnostics**
|
||||
|
||||
@ -309,6 +430,46 @@ The following list shows the supported values:
|
||||
<!--/Policy-->
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="mixedreality-manualdowndirectiondisabled"></a>**MixedReality/ManualDownDirectionDisabled**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
|
||||
|Windows Edition|Supported|
|
||||
|--- |--- |
|
||||
|HoloLens (first gen) Development Edition|No|
|
||||
|HoloLens (first gen) Commercial Suite|No|
|
||||
|HoloLens 2|Yes|
|
||||
|
||||
<!--/SupportedSKUs-->
|
||||
<hr/>
|
||||
|
||||
<!--Scope-->
|
||||
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||
|
||||
> [!div class = "checklist"]
|
||||
> * Device
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
|
||||
This policy controls whether the user can change down direction manually or not. If no down direction is set by the user, then an automatically calculated down direction is used by the system. This policy has no dependency on ConfigureMovingPlatform policy and they can be set independently.
|
||||
|
||||
The OMA-URI of new policy: `./Device/Vendor/MSFT/Policy/Config/MixedReality/ManualDownDirectionDisabled`
|
||||
|
||||
<!--/Description-->
|
||||
|
||||
<!--SupportedValues-->
|
||||
|
||||
Supported values:
|
||||
|
||||
- **False (Default)** - User can manually change down direction if they desire, otherwise down direction will be determined automatically based on the measured gravity vector.
|
||||
- **True** - User can’t manually change down direction and down direction will be always determined automatically based on the measured gravity vector.
|
||||
|
||||
<!--/SupportedValues-->
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="mixedreality-microphonedisabled"></a>**MixedReality/MicrophoneDisabled**
|
||||
|
||||
@ -352,6 +513,78 @@ The following list shows the supported values:
|
||||
<!--/Policy-->
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="mixedreality-skipcalibrationduringsetup"></a>**MixedReality/SkipCalibrationDuringSetup**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
|
||||
|Windows Edition|Supported|
|
||||
|--- |--- |
|
||||
|HoloLens (first gen) Development Edition|No|
|
||||
|HoloLens (first gen) Commercial Suite|No|
|
||||
|HoloLens 2|Yes|
|
||||
|
||||
<!--/SupportedSKUs-->
|
||||
|
||||
> [!NOTE]
|
||||
> This feature is currently only available in [HoloLens Insider](/hololens/hololens-insider) builds.
|
||||
|
||||
<!--Scope-->
|
||||
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||
|
||||
> [!div class = "checklist"]
|
||||
> * Device
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Description-->
|
||||
Skips the calibration experience on HoloLens 2 devices when setting up a new user in the Out of Box Experience (OOBE) or when adding a new user to the device. The user will still be able to calibrate their device from the Settings app.
|
||||
|
||||
The OMA-URI of new policy: `./Device/Vendor/MSFT/Policy/Config/MixedReality/SkipCalibrationDuringSetup`
|
||||
|
||||
- Bool value
|
||||
|
||||
<!--/Description-->
|
||||
|
||||
<!--/Policy-->
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="mixedreality-skiptrainingduringsetup"></a>**MixedReality/SkipTrainingDuringSetup**
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
|
||||
|Windows Edition|Supported|
|
||||
|--- |--- |
|
||||
|HoloLens (first gen) Development Edition|No|
|
||||
|HoloLens (first gen) Commercial Suite|No|
|
||||
|HoloLens 2|Yes|
|
||||
|
||||
<!--/SupportedSKUs-->
|
||||
|
||||
> [!NOTE]
|
||||
> This feature is currently only available in [HoloLens Insider](/hololens/hololens-insider) builds.
|
||||
|
||||
<!--Scope-->
|
||||
[Scope](./policy-configuration-service-provider.md#policy-scope):
|
||||
|
||||
> [!div class = "checklist"]
|
||||
> * Device
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Description-->
|
||||
On HoloLens 2 devices, skips the training experience of interactions with the humming bird and start menu training when setting up a new user in the Out of Box Experience (OOBE) or when adding a new user to the device. The user will still be able to learn these movement controls from the Tips app.
|
||||
|
||||
The OMA-URI of new policy: `./Device/Vendor/MSFT/Policy/Config/MixedReality/SkipTrainingDuringSetup`
|
||||
|
||||
- Bool value
|
||||
|
||||
<!--/Description-->
|
||||
|
||||
<!--/Policy-->
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="mixedreality-volumebuttondisabled"></a>**MixedReality/VolumeButtonDisabled**
|
||||
|
||||
@ -442,4 +675,4 @@ The following list shows the supported values:
|
||||
|
||||
## Related topics
|
||||
|
||||
[Policy configuration service provider](policy-configuration-service-provider.md)
|
||||
[Policy configuration service provider](policy-configuration-service-provider.md)
|
||||
|
||||
@ -108,7 +108,7 @@ If you don’t sign up for any of these enterprise services, Microsoft will act
|
||||
|
||||
### Rollout plan for this change
|
||||
|
||||
This change will roll out initially to Windows devices enrolled in the [Dev Channel](/windows-insider/flighting#dev-channel) of the Windows Insider program no earlier than July 2022. Once the rollout is initiated, devices in the Dev Channel that are joined to an Azure AD tenant with a billing address in the EU or EFTA will be automatically enabled for the processor configuration option.
|
||||
This change will rollout in phases, starting with Windows devices enrolled in the [Dev Channel](/windows-insider/flighting#dev-channel) of the Windows Insider program. Starting in build 25169, devices in the Dev Channel that are joined to an Azure AD tenant with a billing address in the EU or EFTA will be automatically enabled for the processor configuration option.
|
||||
|
||||
During this initial rollout, the following conditions apply to devices in the Dev Channel that are joined to an Azure AD tenant with a billing address outside of the EU or EFTA:
|
||||
|
||||
@ -129,4 +129,4 @@ As part of this change, the following policies will no longer be supported to co
|
||||
- Allow Desktop Analytics Processing
|
||||
- Allow Update Compliance Processing
|
||||
- Allow WUfB Cloud Processing
|
||||
- Configure the Commercial ID
|
||||
- Configure the Commercial ID
|
||||
|
||||
@ -497,7 +497,7 @@ You can reset the recovery password in two ways:
|
||||
> [!NOTE]
|
||||
> To manage a remote computer, you can specify the remote computer name rather than the local computer name.
|
||||
|
||||
You can use the following sample script to create a VBScript file to reset the recovery passwords:
|
||||
You can use the following sample VBScript to reset the recovery passwords:
|
||||
|
||||
```vb
|
||||
' Target drive letter
|
||||
|
||||
@ -8,7 +8,7 @@ ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: denisebmsft
|
||||
ms.author: deniseb
|
||||
ms.date: 03/10/2022
|
||||
ms.date: 08/22/2022
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.custom: sasr
|
||||
@ -30,6 +30,9 @@ Application Guard uses both network isolation and application-specific settings.
|
||||
|
||||
These settings, located at `Computer Configuration\Administrative Templates\Network\Network Isolation`, help you define and manage your organization's network boundaries. Application Guard uses this information to automatically transfer any requests to access the non-corporate resources into the Application Guard container.
|
||||
|
||||
> [!NOTE]
|
||||
> For Windows 10, if you have KB5014666 installed, and for Windows 11, if you have KB5014668 installed, you don't need to configure network isolation policy to enable Application Guard for Microsoft Edge.
|
||||
|
||||
> [!NOTE]
|
||||
> You must configure either the Enterprise resource domains hosted in the cloud or Private network ranges for apps settings on your employee devices to successfully turn on Application Guard using enterprise mode. Proxy servers must be a neutral resource listed in the **Domains categorized as both work and personal** policy.
|
||||
|
||||
@ -55,9 +58,8 @@ These settings, located at `Computer Configuration\Administrative Templates\Wind
|
||||
|-----------|------------------|-----------|-------|
|
||||
|Configure Microsoft Defender Application Guard clipboard settings|Windows 10 Enterprise, 1709 or higher<p>Windows 10 Pro, 1803 or higher<p>Windows 11|Determines whether Application Guard can use the clipboard functionality.|**Enabled.** Turns On the clipboard functionality and lets you choose whether to additionally:<br/>- Disable the clipboard functionality completely when Virtualization Security is enabled.<br/>- Enable copying of certain content from Application Guard into Microsoft Edge.<br/>- Enable copying of certain content from Microsoft Edge into Application Guard. **Important:** Allowing copied content to go from Microsoft Edge into Application Guard can cause potential security risks and isn't recommended.<p>**Disabled or not configured.** Completely turns Off the clipboard functionality for Application Guard.|
|
||||
|Configure Microsoft Defender Application Guard print settings|Windows 10 Enterprise, 1709 or higher<p>Windows 10 Pro, 1803 or higher<p>Windows 11|Determines whether Application Guard can use the print functionality.|**Enabled.** Turns On the print functionality and lets you choose whether to additionally:<br/>- Enable Application Guard to print into the XPS format.<br/>- Enable Application Guard to print into the PDF format.<br/>- Enable Application Guard to print to locally attached printers.<br/>- Enable Application Guard to print from previously connected network printers. Employees can't search for other printers.<br/><br/>**Disabled or not configured.** Completely turns Off the print functionality for Application Guard.|
|
||||
|Prevent enterprise websites from loading non-enterprise content in Microsoft Edge and Internet Explorer|Windows 10 Enterprise, 1709 or higher<p>Windows 11|Determines whether to allow Internet access for apps not included on the **Allowed Apps** list.|**Enabled.** Prevents network traffic from both Internet Explorer and Microsoft Edge to non-enterprise sites that can't render in the Application Guard container. <p>**NOTE**: This action might also block assets cached by CDNs and references to analytics sites. Add them to the trusted enterprise resources to avoid broken pages.<p>**Disabled or not configured.** Prevents Microsoft Edge to render network traffic to non-enterprise sites that can't render in Application Guard. |
|
||||
|Allow Persistence|Windows 10 Enterprise, 1709 or higher<br><br>Windows 10 Pro, 1803 or higher<p>Windows 11|Determines whether data persists across different sessions in Microsoft Defender Application Guard.|**Enabled.** Application Guard saves user-downloaded files and other items (such as, cookies, Favorites, and so on) for use in future Application Guard sessions.<p>**Disabled or not configured.** All user data within Application Guard is reset between sessions.<p>**NOTE**: If you later decide to stop supporting data persistence for your employees, you can use our Windows-provided utility to reset the container and to discard any personal data.<p>**To reset the container:**<br/>1. Open a command-line program and navigate to `Windows/System32`.<br/>2. Type `wdagtool.exe cleanup`. The container environment is reset, retaining only the employee-generated data.<br/>3. Type `wdagtool.exe cleanup RESET_PERSISTENCE_LAYER`. The container environment is reset, including discarding all employee-generated data.|
|
||||
|Turn on Microsoft Defender Application Guard in Managed Mode|Windows 10 Enterprise, 1809 or higher<p>Windows 11|Determines whether to turn on Application Guard for Microsoft Edge and Microsoft Office.|**Enabled.** Turns on Application Guard for Microsoft Edge and/or Microsoft Office, honoring the network isolation settings, rendering non-enterprise domains in the Application Guard container. Application Guard won't actually be turned on unless the required prerequisites and network isolation settings are already set on the device. Available options:<br/>- Enable Microsoft Defender Application Guard only for Microsoft Edge<br/>- Enable Microsoft Defender Application Guard only for Microsoft Office<br/>- Enable Microsoft Defender Application Guard for both Microsoft Edge and Microsoft Office<br/><br/>**Disabled.** Turns off Application Guard, allowing all apps to run in Microsoft Edge and Microsoft Office.|
|
||||
|Turn on Microsoft Defender Application Guard in Managed Mode|Windows 10 Enterprise, 1809 or higher<p>Windows 11|Determines whether to turn on Application Guard for Microsoft Edge and Microsoft Office.|**Enabled.** Turns on Application Guard for Microsoft Edge and/or Microsoft Office, honoring the network isolation settings, rendering untrusted content in the Application Guard container. Application Guard won't actually be turned on unless the required prerequisites and network isolation settings are already set on the device. Available options:<br/>- Enable Microsoft Defender Application Guard only for Microsoft Edge<br/>- Enable Microsoft Defender Application Guard only for Microsoft Office<br/>- Enable Microsoft Defender Application Guard for both Microsoft Edge and Microsoft Office<br/><br/>**Disabled.** Turns off Application Guard, allowing all apps to run in Microsoft Edge and Microsoft Office. <br/><br/>**Note:** For Windows 10, if you have KB5014666 installed, and for Windows 11, if you have KB5014668 installed, you are no longer required to configure network isolation policy to enable Application Guard for Edge.|
|
||||
|Allow files to download to host operating system|Windows 10 Enterprise, 1803 or higher<p>Windows 11|Determines whether to save downloaded files to the host operating system from the Microsoft Defender Application Guard container.|**Enabled.** Allows users to save downloaded files from the Microsoft Defender Application Guard container to the host operating system. This action creates a share between the host and container that also allows for uploads from the host to the Application Guard container.<p>**Disabled or not configured.** Users aren't able to save downloaded files from Application Guard to the host operating system.|
|
||||
|Allow hardware-accelerated rendering for Microsoft Defender Application Guard|Windows 10 Enterprise, 1803 or higher<br><br>Windows 10 Pro, 1803 or higher<p>Windows 11|Determines whether Microsoft Defender Application Guard renders graphics using hardware or software acceleration.|**Enabled.** Microsoft Defender Application Guard uses Hyper-V to access supported, high-security rendering graphics hardware (GPUs). These GPUs improve rendering performance and battery life while using Microsoft Defender Application Guard, particularly for video playback and other graphics-intensive use cases. If this setting is enabled without connecting any high-security rendering graphics hardware, Microsoft Defender Application Guard will automatically revert to software-based (CPU) rendering. **Important:** Enabling this setting with potentially compromised graphics devices or drivers might pose a risk to the host device.<br><br>**Disabled or not configured.** Microsoft Defender Application Guard uses software-based (CPU) rendering and won’t load any third-party graphics drivers or interact with any connected graphics hardware.|
|
||||
|Allow camera and microphone access in Microsoft Defender Application Guard|Windows 10 Enterprise, 1809 or higher<br><br>Windows 10 Pro, 1809 or higher<p>Windows 11|Determines whether to allow camera and microphone access inside Microsoft Defender Application Guard.|**Enabled.** Applications inside Microsoft Defender Application Guard are able to access the camera and microphone on the user's device. **Important:** Enabling this policy with a potentially compromised container could bypass camera and microphone permissions and access the camera and microphone without the user's knowledge.<p>**Disabled or not configured.** Applications inside Microsoft Defender Application Guard are unable to access the camera and microphone on the user's device.|
|
||||
|
||||
@ -19,8 +19,8 @@ ms.technology: windows-sec
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
- Windows 10 Education, Enterprise, and Professional
|
||||
- Windows 11 Education, Enterprise, and Professional
|
||||
|
||||
The threat landscape is continually evolving. While hackers are busy developing new techniques to breach enterprise networks by compromising workstations, phishing schemes remain one of the top ways to lure employees into social engineering attacks. Microsoft Defender Application Guard is designed to help prevent old, and newly emerging attacks, to help keep employees productive.
|
||||
|
||||
@ -45,6 +45,6 @@ Your environment must have the following hardware to run Microsoft Defender Appl
|
||||
|
||||
| Software | Description |
|
||||
|--------|-----------|
|
||||
| Operating system | Windows 10 Enterprise edition, version 1809 or higher <br/> Windows 10 Professional edition, version 1809 or higher <br/> Windows 10 Professional for Workstations edition, version 1809 or higher <br/> Windows 10 Professional Education edition, version 1809 or higher <br/> Windows 10 Education edition, version 1809 or higher <br/> Professional editions are only supported for non-managed devices; Intune or any other third-party mobile device management (MDM) solutions aren't supported with MDAG for Professional editions. <br/> Windows 11 |
|
||||
| Operating system | Windows 10 Enterprise edition, version 1809 or higher <br/> Windows 10 Professional edition, version 1809 or higher <br/> Windows 10 Professional for Workstations edition, version 1809 or higher <br/> Windows 10 Professional Education edition, version 1809 or higher <br/> Windows 10 Education edition, version 1809 or higher <br/> Professional editions are only supported for non-managed devices; Intune or any other third-party mobile device management (MDM) solutions aren't supported with MDAG for Professional editions. <br/> Windows 11 Education, Enterprise, and Professional |
|
||||
| Browser | Microsoft Edge |
|
||||
| Management system <br> (only for managed devices)| [Microsoft Intune](/intune/) <p> **OR** <p> [Microsoft Endpoint Configuration Manager](/configmgr/) <p> **OR** <p> [Group Policy](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc753298(v=ws.11)) <p> **OR** <p>Your current, company-wide, non-Microsoft mobile device management (MDM) solution. For info about non-Mirosoft MDM solutions, see the documentation that came with your product. |
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user