Merge pull request #8516 from MicrosoftDocs/main

Angela Fleischmann · web-flow · commit 9dee27cd7b92 · 2022-09-22T16:49:33.000-06:00
Publish 09/22/2022 3:30 PM PT
diff --git a/memdocs/autopilot/known-issues.md b/memdocs/autopilot/known-issues.md
@@ -1,18 +1,14 @@
 ---
 title: Windows Autopilot known issues
 description: Inform yourself about known issues that may occur during Windows Autopilot deployment.
-keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
-ms.prod: w10
-ms.mktglfcycl: deploy
+ms.prod: windows-client
+ms.technology: itpro-deploy
 ms.localizationpriority: medium
-ms.sitesec: library
-ms.pagetype: deploy
-audience: itpro
 author: aczechowski
 ms.author: aaroncz
 ms.reviewer: jubaptis
 manager: dougeby
-ms.date: 05/18/2022
+ms.date: 09/21/2022
 ms.collection: M365-modern-desktop
 ms.topic: troubleshooting
 ---
@@ -28,6 +24,14 @@ This article describes known issues that can often be resolved by configuration
 
 ## Known issues
 
+### Autopilot deployment report shows "failure" status on a successful deployment
+
+The Autopilot deployment report (preview) will show a failed status for any device that experiences an initial deployment failure. For subsequent deployment attempts, using the **Try again** or **Continue to desktop** options, it won't update the deployment state in the report. If the user resets the device, it will show as a new deployment row in the report with the previous attempt remaining as failed.
+
+### Autopilot deployment report doesn't show deployed device
+
+Autopilot deployments that take longer than one hour may display an incomplete deployment status in the deployment report. If the device successfully enrolls but doesn't complete provisioning after more than one hour, the device status may not be updated in the report.
+
 ### Autopilot profile not being applied when assigned 
 
 In Windows 10 April and some May update releases, there is an issue where the Autopilot profile may fail to apply to the device and the hardware hash may not be harvested. As a result, any settings made in the profile may not be configured for the user such as device renaming. To resolve this issue, the May (KB5015020) cumulative update needs to be applied to the device.
@@ -62,9 +66,11 @@ When you attempt an Autopilot reset, you see the following message: _Autopilot r
 
 When a device is registered in Autopilot and no profile is assigned, it will take the default Autopilot profile. This behavior is by design. It makes sure that all devices that you register with Autopilot go through the Autopilot experience. If you don't want the device to go through an Autopilot deployment, remove the Autopilot registration.
 
-### White screen during HAADJ deployment
+### White screen during hybrid Azure AD joined deployment
+
+There's a UI bug on Autopilot hybrid Azure AD joined deployments where the Enrollment Status page is displayed as a white screen. This issue is limited to the UI and shouldn't affect the deployment process.
 
-There's a UI bug on Autopilot HAADJ deployments where the Enrollment Status page is displayed as a white screen. This issue is limited to the UI and shouldn't affect the deployment process.
+This issue was resolved in September 2022.
 
 ### Virtual machine failing at "Preparing your device for mobile management"
 
diff --git a/memdocs/configmgr/mdt/known-issues.md b/memdocs/configmgr/mdt/known-issues.md
@@ -16,6 +16,44 @@ ms.collection: openauth
 
 This article provides details of any current known issues and limitations with the Microsoft Deployment Toolkit (MDT). It assumes familiarity with MDT version concepts, features, and capabilities.
 
+## HTA applications report Script error after upgrading to ADK for Windows 11, version 22H2
+After you updated your MDT boot image to [ADK for Windows 11, version 22H2](/windows-hardware/get-started/adk-install), HTA applications stop working and a message box is displayed: Script Error - An error has occurred in the script on this page.
+
+HTA applications rely on MSHTML and starting with Windows 11, version 22H2, the default legacy scripting engine was changed.
+
+To work around this issue you need to add the following registry value in WinPE: 
+ ``` 
+ reg.exe add "HKLM\Software\Microsoft\Internet Explorer\Main" /t REG_DWORD /v JscriptReplacement /d 0 /f
+ ```
+To enable this change in MDT, we recommend that you back up the following file: `C:\Program Files\Microsoft Deployment Toolkit\Templates\Unattend_PE_x64.xml` and to modify it as follows:
+ ``` <?xml version="1.0" encoding="utf-8"?>
+<unattend xmlns="urn:schemas-microsoft-com:unattend">
+    <settings pass="windowsPE">
+        <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
+            <Display>
+                <ColorDepth>32</ColorDepth>
+                <HorizontalResolution>1024</HorizontalResolution>
+                <RefreshRate>60</RefreshRate>
+                <VerticalResolution>768</VerticalResolution>
+            </Display>
+            <RunSynchronous>
+                <RunSynchronousCommand wcm:action="add">
+                    <Description>Lite Touch PE</Description>
+                    <Order>1</Order>
+                    <Path>reg.exe add "HKLM\Software\Microsoft\Internet Explorer\Main" /t REG_DWORD /v JscriptReplacement /d 0 /f</Path>
+                </RunSynchronousCommand>
+                <RunSynchronousCommand wcm:action="add">
+                    <Description>Lite Touch PE</Description>
+                    <Order>2</Order>
+                    <Path>wscript.exe X:\Deploy\Scripts\LiteTouch.wsf</Path>
+                </RunSynchronousCommand>
+            </RunSynchronous>
+        </component>
+    </settings>
+</unattend>
+  ```
+After saving the changes, you will need to completely regenerate the boot images.
+
 ## Windows Deployment Services (WDS) multicast stops working after upgrading to ADK for Windows 11
 
 <!-- 12891430 --> 
diff --git a/memdocs/intune/protect/antivirus-microsoft-defender-settings-macos.md b/memdocs/intune/protect/antivirus-microsoft-defender-settings-macos.md
@@ -22,7 +22,7 @@ search.appverid: MET150
 #ms.tgt_pltfrm:
 ms.custom: intune-azure
 ms.collection: M365-identity-device-management
-ms.reviewer: laarrizz
+ms.reviewer: laarrizz        
 
 ---
 
diff --git a/memdocs/intune/protect/endpoint-protection-configure.md b/memdocs/intune/protect/endpoint-protection-configure.md
@@ -24,7 +24,7 @@ search.appverid: MET150
 #ms.tgt_pltfrm:
 ms.custom: intune-azure
 ms.collection: M365-identity-device-management
-mr.reviewer: karthib
+ms.reviewer: mattcall
 ---
 
 # Add Endpoint protection settings in Intune
diff --git a/memdocs/intune/protect/endpoint-protection-macos.md b/memdocs/intune/protect/endpoint-protection-macos.md
@@ -19,6 +19,7 @@ ms.technology:
 #ROBOTS:
 #audience:
 
+ms.reviewer: mattcall
 ms.suite: ems
 search.appverid: MET150
 #ms.tgt_pltfrm:
diff --git a/memdocs/intune/protect/tutorial-protect-email-on-enrolled-devices.md b/memdocs/intune/protect/tutorial-protect-email-on-enrolled-devices.md
@@ -21,7 +21,7 @@ ms.assetid:
 #ROBOTS:
 #audience:
 
-ms.reviewer:
+ms.reviewer: demerson
 ms.suite: ems
 search.appverid: MET150
 #ms.tgt_pltfrm:
diff --git a/memdocs/intune/protect/tutorial-protect-email-on-unmanaged-devices.md b/memdocs/intune/protect/tutorial-protect-email-on-unmanaged-devices.md
@@ -21,7 +21,7 @@ ms.assetid:
 #ROBOTS:
 #audience:
 
-ms.reviewer:
+ms.reviewer: demerson
 ms.suite: ems
 #ms.tgt_pltfrm:
 ms.custom: intune-azure
diff --git a/memdocs/intune/remote-actions/remote-help.md b/memdocs/intune/remote-actions/remote-help.md
@@ -77,7 +77,7 @@ The Remote help app supports the following capabilities:
 > [!NOTE]
 > Remote help has the following limitations:  
 >
-> - Remote help is not supported on GCC, GCC High or DoD Tenants.
+> - Remote help is not supported on GCC High or DoD Tenants.
 > - You cannot establish a remote help session from one tenant to a different tenant.
 > - May not be available in all markets or localizations.
 
@@ -376,4 +376,4 @@ Version 4.0.0.0 - GA release
 ## Next steps
 
 [Get support in Microsoft Endpoint Manager admin center](../../get-support.md)
-  
+  
diff --git a/windows-365/enterprise/health-checks-connectivity.md b/windows-365/enterprise/health-checks-connectivity.md
@@ -0,0 +1,104 @@
+---
+# required metadata
+title: Connectivity health checks in Windows 365
+titleSuffix:
+description: Learn about connectivity health checks.
+keywords:
+author: ErikjeMS
+ms.author: erikje
+manager: dougeby
+ms.date: 09/22/2022
+ms.topic: how-to
+ms.service: cloudpc
+ms.subservice:
+ms.localizationpriority: high
+ms.technology:
+ms.assetid: 
+
+# optional metadata
+
+#ROBOTS:
+#audience:
+
+ms.reviewer: abpineda
+ms.suite: ems
+search.appverid: MET150
+#ms.tgt_pltfrm:
+ms.custom: intune-azure; get-started
+ms.collection: M365-identity-device-management
+---
+
+# Connectivity health checks
+
+Connectivity health checks are run on individual Cloud PCs and give information on the state of the Cloud PC's connection. These checks are constantly run by the Windows 365 service in the backend. When any of these checks fail, the end user won’t be able to connect to their Cloud PC.
+
+You can review any connectivity errors and use the **Troubleshoot this connection** button to troubleshoot.
+
+## View Cloud PC connectivity status
+
+1. Sign in to [windows365.microsoft.com](https://windows365.microsoft.com) > **Devices** > **Windows 365** > **All Cloud PCs**.
+2. Select a connection in the list > **Overview** > **Connectivity and usage (preview)**.
+
+If the Cloud PC is connected, the status will show as **Available**.
+
+If there is a problem with the Cloud PC's connection, the status will show as **Unavailable**. Details appear on the right. Select **Troubleshoot this connection** to troubleshoot the issue.
+
+## Connectivity errors
+
+When a connectivity check fails, you'll see one of the following errors. Review the status pane to see more details. You can use the **Troubleshoot this connection** button to troubleshoot.
+
+- **Azure Resource Availability Check**: Azure resources are not up and running.
+- **DomainJoin**: This Cloud PC isn't joined to a domain.
+- **omainReachable**: This Cloud PC can't connect to the domain.
+- **DomainTrust**: The domain doesn't trust this Cloud PC.
+- **SxSStackListener**: The side-by-side stack installed on the Cloud PC is malfunctioning or blocked. 
+- **Unknown**: This Cloud PC might not be running or the network isn't connected to the public Internet.
+- **UrlsAccesible**: This Cloud PC is blocking traffic to [these URLs](requirements.md).
+- **VM Power Status Check**: This Cloud PC is powered off and an issue is preventing it from turning back on.
+
+
+<!--
+Possible different view of this data:
+
+| Check | Failure description | Troubleshooting |
+| --- | --- | --- |
+| Azure Resource Availability Check | Azure resources are not up and running. | If this persists, contact Microsoft support. |
+| DomainJoin | This Cloud PC isn't joined to a domain. | Try reprovisioning the Cloud PC or join it to a domain. |
+| DomainReachable | This Cloud PC can't connect to the domain. | Check for an issue with your virtual network configuration by reviewing your [Azure network connection checks](troubleshoot-azure-network-connection.md). |
+| DomainTrust | The domain doesn't trust this Cloud PC. | Make sure that the local device password matches the device password in the domain. |
+| SxSStackListener | The side-by-side stack installed on the Cloud PC is malfunctioning or blocked. | Run the troubleshooting tool to fix this issue. |
+| Unknown | This Cloud PC might not be running or the network isn't connected to the public Internet. | Run the troubleshooting tool to get more information. |
+| UrlsAccesible | This Cloud PC is blocking traffic to [these URLs](requirements.md). | Unblock the URLs this Cloud PC uses to connect to Windows 365. |
+| VM Power Status Check | This Cloud PC is powered off and an issue is preventing it from turning back on. |  If this persists, contact Microsoft support. |
+
+
+-->
+If any of these issues persist, contact Microsoft support.
+
+Connectivity errors can occur even when all connectivity health checks have successfully passed.
+
+## User connectivity history report
+
+The user connectivity history report shows when a user started a connection and when the connection finished. There are different ways a connection can start/finish and these are logged as activities in the report.
+
+### View Connectivity history report
+
+1. Sign in to [windows365.microsoft.com](https://windows365.microsoft.com) > **Devices** > **Windows 365** > **All Cloud PCs**.
+2. Select a connection in the list > **Overview** > **Connectivity and usage (preview)** > **View connectivity history**.
+
+### Activities
+
+The report shows of the following activities:
+
+| Activity | Description |
+| --- | --- | --- |
+| Connection started | The user successfully connected to their Cloud PC. |
+| Connection finished | The user signs out of their Cloud PC or finishes their work session. If the connection fails because of an unexpected network connectivity error, it's listed as a **Connection finished** with a **Failure** status.|
+| Connectivity check | If the connection fails because of a failed connectivity check, the failed check is listed. |
+
+Select any activity to get more information about the event.
+
+<!-- ########################## -->
+## Next steps
+
+[Learn more about Azure network connections](azure-network-connections.md).
