Merge branch 'main' into release-win365-gcc

v-alje · v-alje · commit 1915aed05e7d · 2022-09-22T17:32:51.000-07:00
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/configuration/settings-catalog-printer-provisioning.md b/memdocs/intune/configuration/settings-catalog-printer-provisioning.md
@@ -7,7 +7,7 @@ keywords:
 author: MandiOhlinger
 ms.author: mandia
 manager: dougeby
-ms.date: 07/21/2022
+ms.date: 09/22/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: configuration
@@ -38,7 +38,7 @@ Using the settings catalog in Intune, you can create a printer policy, and deplo
 This feature applies to:
 
 - Windows 11
-- Windows 10 and later
+- Windows 10 21H2 with [July 2022 update](https://support.microsoft.com/topic/july-12-2022-kb5015807-os-builds-19042-1826-19043-1826-and-19044-1826-8c8ea8fe-ec83-467d-86fb-a2f48a85eb41) and later
 
 This article shows you how to create a Universal Print policy in Microsoft Intune. To learn more about Universal Print and onboarding, go to [What is Universal Print](/universal-print/fundamentals/universal-print-whatis) and [Set up Universal Print](/universal-print/fundamentals/universal-print-getting-started).
 
diff --git a/memdocs/intune/fundamentals/deployment-guide-enrollment-android.md b/memdocs/intune/fundamentals/deployment-guide-enrollment-android.md
@@ -294,7 +294,7 @@ There are some situations when you must use Device Administrator enrollment:
 - Android Enterprise requires access to Google services. Google services may not be available because of geography, or because of the device manufacturer. For example:
 
   - There are places where Google services aren’t available, like China. In this situation, use Android device administrator enrollment.  
-  - Some devices are based on Android, but don't have access to Google Services, such as Amazon Fire tablets. In this situation, use Android device administrator enrollment.
+  - Some devices are based on Android, but don't have access to Google Services, such as Microsoft Teams Android devices and Amazon Fire tablets. In this situation, use Android device administrator enrollment.
 
 - Android OS versions older than 5.0 must use Android device administrator enrollment. Android Enterprise enrollment isn't an option.
 
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/toc.yml b/memdocs/intune/protect/toc.yml
@@ -237,6 +237,11 @@ items:
         items:
         - name: Symantec and Intune integration
           href: skycure-mtd-connector-integration.md
+      - name: Set up Trend Micro Mobile Security as a Service
+        href: trend-micro-mobile-threat-defense-connector.md
+        items:
+        - name: Trend Micro Mobile Security as a Service and Intune integration
+          href: trend-micro-mtd-connector-integration.md 
       - name: Set up Wandera
         href: wandera-mtd-connector.md
         items:
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).
