Merge pull request #7347 from MicrosoftDocs/main

Publish 04/12/2022 3:30 PM PT

Author: Angela Fleischmann

memdocs/intune/apps/vpp-apps-ios.md

@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 12/16/2021
+ms.date: 04/12/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
@@ -124,7 +124,9 @@ Migrate existing purchased VPP content and tokens to Apps and Books in Apple Bus
    - **Automatic app updates** - Choose from **Yes** or **No** to enable automatic updates. When enabled, Intune detects the VPP app updates inside the app store and automatically pushes them to the device when the device checks in.
 
         > [!NOTE]
-        > Automatic app updates for Apple VPP apps will automatically update for both **Required** and **Available** install intents. For apps deployed with **Available** install intent, the automatic update generates a status message for the IT admin informing that a new version of the app is available. This status message is viewable by selecting the app, selecting Device Install Status, and checking the Status Details.  
+        > Automatic app updates for Apple VPP apps will automatically update for both **Required** and **Available** install intents. For apps deployed with **Available** install intent, the automatic update generates a status message for the IT admin informing that a new version of the app is available. This status message is viewable by selecting the app, selecting Device Install Status, and checking the Status Details. 
+        >
+        > When updating a VPP app, it can take up to 24 hours for the device to receive the updated VPP app. The device must be unlocked and available to install the update successfully.
 
     - **I grant Microsoft permission to send both user and device information to Apple.** - You must select **I agree** to proceed. To review what data Microsoft sends to Apple, see [Data Intune sends to Apple](../protect/data-intune-sends-to-apple.md).
 7. Click **Next** to display the **Scope tags** page.

memdocs/intune/fundamentals/whats-new.md

@@ -62,6 +62,18 @@ You can use RSS to be notified when this page is updated. For more information,
 
 ## Week of April, 11, 2022
 
+### Device Management
+
+#### Updating the device diagnostics folder structure<!-- 8504019 -->
+
+Intune now exports [Windows Device Diagnostic data](../remote-actions/collect-diagnostics.md) in an updated format. With the updated format, the logs collected are named to match the data collected, and when multiple files are collected a folder is created. With the earlier format, the zip file used a flat structure of numbered folders that did not identify their contents.
+
+To take advantage of this diagnostic logging update, devices must install one of the following updates:
+- **Windows 11** - KB5011563
+- **Windows 10** - KB5011543
+
+These updates are available through the Windows Updates on April 12, 2022.
+
 ### App management
 
 #### Uninstall DMG-type applications on managed macOS devices (Public preview)<!-- 13155022 -->

memdocs/intune/protect/certificate-connector-overview.md

@@ -7,7 +7,7 @@ keywords:
 author: brenduns
 ms.author: brenduns
 manager: dougeby
-ms.date: 03/31/2022
+ms.date: 04/12/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: protect
@@ -361,6 +361,8 @@ New updates for the connector can take a week or more to become available for ea
 
 > [!IMPORTANT]  
 > On June 1, 2022, Intune certificate connectors earlier than version **6.2101.13.0** will no longer allow you to issue certificates to users and devices. This includes both the [PFX Certificate Connector for Microsoft Intune](../protect/certificate-connectors.md#pfx-certificate-connector-release-history) and  [Microsoft Intune Connector](../protect/certificate-connectors.md#microsoft-intune-connector-release-history), which were replaced by the *Certificate Connector for Microsoft Intune* (as detailed in this article) on July 29, 2021.
+> 
+> Starting in April 2022, deprecated connectors will show a status of *Error*. This status does not affect their functionality.
  
 
 ### March 10, 2022

memdocs/intune/protect/certificate-connectors.md

@@ -7,7 +7,7 @@ keywords:
 author: brenduns
 ms.author: brenduns
 manager: dougeby
-ms.date: 02/28/2022
+ms.date: 04/12/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: protect
@@ -272,6 +272,8 @@ Updates for the two certificate connectors are released periodically. When we up
 
 > [!IMPORTANT]
 > On June 1, 2022, Intune certificate connectors earlier than version 6.2101.13.0 will no longer allow you to issue certificates to users and devices. See the note at the to start of this article for detail on moving to the new **Certificate Connector for Microsoft**.
+> 
+> Starting in April 2022, deprecated connectors will show a status of *Error*. This status does not affect their functionality.
 
 ### PFX Certificate Connector release history
 

memdocs/intune/remote-actions/collect-diagnostics.md

@@ -61,7 +61,9 @@ To use the *Collect diagnostics* action:
 
 ## Data collected
 
-No personal information is collected. This list below is the same order as the diagnostic zip.  Each collection contains the following data:
+No personal information is collected. If you've installed KB5011543 on Windows 10 or KB5011563 on Windows 11, the format of the zip file will be simpler, including a flattened structure where the logs collected are named to match the data collected, and when multiple files are collected a folder is created.  
+
+This list below is the same order as the diagnostic zip.  Each collection contains the following data:
 
 Registry Keys:
 

memdocs/intune/remote-actions/remote-help.md

@@ -67,7 +67,7 @@ The Remote help app supports the following capabilities:
 ## Prerequisites
 
 - [Intune subscription](../fundamentals/licenses.md)
-- Remote help add-on license for all IT support workers (helpers) and users or active trial licenses(https://aka.ms/PremiumAddOnsDocs). 
+- Remote help add-on license for all IT support workers (helpers) and users (https://aka.ms/PremiumAddOnsDocs)
 - Windows 10/11
 - The remote help app for Windows. See [Install and update remote help](#install-and-update-remote-help)
 

windows-365/business/in-development.md

@@ -8,7 +8,7 @@ keywords:
 author: ErikjeMS 
 ms.author: erikje
 manager: dougeby
-ms.date: 03/09/2022
+ms.date: 04/12/2022
 ms.topic: reference
 ms.service: cloudpc
 ms.subservice: 
@@ -53,8 +53,11 @@ To help in your readiness and planning, this page lists Windows 365 Business upd
 -->
 
 <!-- ***********************************************-->
-<!--## Device management
--->
+## Device management
+
+### Set default languages/regions for Cloud PCs (preview)<!--38649676 -->
+
+You’ll be able to set the default languages for your newly created Cloud PCs. Thirty-eight languages/regions will be available.
 
 <!-- ***********************************************-->
 ## Monitor and troubleshoot

windows-365/enterprise/in-development.md

@@ -8,7 +8,7 @@ keywords:
 author: ErikjeMS 
 ms.author: erikje
 manager: dougeby
-ms.date: 03/09/2022
+ms.date: 04/12/2022
 ms.topic: reference
 ms.service: cloudpc
 ms.subservice: 
@@ -49,14 +49,30 @@ To help in your readiness and planning, this page lists Windows 365 updates and
 ## Monitor and troubleshoot
 ## Role-based access control
 ## Security
+## End-user experience
 
 -->
 
 <!-- ***********************************************-->
 <!--## App management-->
 
 <!-- ***********************************************-->
-<!--## Device management-->
+## Device management
+
+### Change Cloud PC time zone<!--38902639 -->
+
+Non-admin users will be able to change their Cloud PC’s time zone.
+
+### On-premises network connection getting renamed to Azure network connection<!--38457869 -->
+
+The term **on-premises network connection** will be renamed to **Azure network connection** in all user interfaces, documentation, and communications.
+
+<!-- ***********************************************-->
+## Device provisioning
+
+### Provision Cloud PCs with Secure Boot<!--38012584-->
+
+You'll be able to create Cloud PCs that use [Secure boot](/windows-hardware/design/device-experiences/oem-secure-boot) functionality.
 
 <!-- ***********************************************-->
 ## Monitor and troubleshoot
@@ -80,6 +96,10 @@ The device history report will have new information to help you evaluate Cloud P
 - Top 5 processes impacting CPU spike times
 - Top 5 processes impacting RAM spike times
 
+### Forensic auditing of Cloud PCs<!--38726407-->
+
+You’ll be able to place a Cloud PC under review. This action initiates a process to create a secure snapshot of a Cloud PC. You’ll be able to analyze the snapshot using electronic discovery solutions.
+
 <!-- ***********************************************-->
 <!-- ## Provisioning -->
 

windows-365/enterprise/provide-localized-windows-experience.md

@@ -57,104 +57,6 @@ For both the provisioning policy and custom image options to set up the display
   - FOD: https://software-download.microsoft.com/download/pr/18362.1.190318-1202.19h1_release_amd64fre_FOD-PACKAGES_OEM_PT1_amd64fre_MULTI.iso
   - InboxApps: https://software-download.microsoft.com/download/pr/18362.1.190318-1202.19h1_release_amd64fre_InboxApps.iso
 
-## Create a custom device image with languages already installed
-
-To create a custom device image that gives users a localized Windows experience, follow these steps:
-
-1. [Create a custom device image with the languages installed](#create-a-custom-image-with-the-languages-installed).
-2. [Configure the default language using Group Policy](#configure-the-default-language-using-group-policy).
-
-Cloud PCs provisioned from this image will be fully configured to work in any of the installed languages, without any user action. When the user signs in to the Cloud PC, Group Policy will evaluate the device and set the appropriate pre-installed language as the user's preferred language for Windows.
-
-## Create a custom image with the languages installed
-
-Creating a custom image with the languages installed is the best way to make sure that the desired languages are available on the Cloud PC when the user signs in.
-
-Before starting the custom image process, check if your language is supported by the [Windows 365 Language Installer](https://www.powershellgallery.com/packages/Windows365LanguagesInstaller) script. If:
-
-- The language you want to provide for your users is supported by the PowerShell script, follow the steps to [Add languages to Windows using a script and capture the image](#add-languages-to-windows-using-a-script-and-capture-the-image). Windows 10 custom images only.
-- The language you want to provide for your users isn't supported by the PowerShell script, follow the steps to [Add languages to Windows manually and capture the image](#add-languages-to-windows-manually-and-capture-the-image).
-
-### Add languages to Windows using a script and capture the image
-
-To add a language using the [Windows 365 Language Installer](https://www.powershellgallery.com/packages/Windows365LanguagesInstaller/1.0.0.0) script:
-
-1. Sign in to the virtual machine you're customizing for use as the custom image.
-2. Complete one of the **Installation Options** described for the [Windows 365 Language Installer](https://www.powershellgallery.com/packages/Windows365LanguagesInstaller/1.0.0.0) script.
-3. Run the script and enter the number corresponding to the language you'd like to install on the custom image.
-
-> [!NOTE]
-> You can use the script to install as many languages as you'd like on the custom image. To do so, run the script one time for each language.
-
-After you're done adding the desired languages and are ready to capture the image, follow the steps to [finish customizing your image](/azure/virtual-desktop/language-packs#finish-customizing-your-image).
-
-### Add languages to Windows manually and capture the image
-
-To manually install the desired languages to your Windows 10/11 Enterprise custom image, follow the steps in [Add language packs to a Windows 10/11 multi-session image](/azure/virtual-desktop/language-packs) up to and including [finish customizing your image](/azure/virtual-desktop/language-packs#finish-customizing-your-image).
-
-> [!NOTE]
-> Though these instructions are written specifically for Windows 10/11 Enterprise multi-session, these same steps apply to Windows 10/11 Enterprise.
-
-### Upload the custom image
-
-To upload the custom image to the Windows 365 service, after you've captured the image as an Azure managed image, follow the steps in [Add or delete device images](add-device-images.md).
-
-## Configure the default language using Group Policy
-
-Now that the languages are installed on the image that users will receive, you must create a Group Policy to apply the correct pre-installed language as the default for your users.
-
-The following steps configure [Group Policy Preferences](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn581922(v=ws.11)) to set the PreferredUILanguages Registry value and the Windows Regional Options. These options are then [targeted by security group](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn581922(v=ws.11)#item-level-targeting) to sets of users. Each security group and Group Policy object configures a single language as the default for those users. To cater for users with different language default requirements, you can use a single image with multiple languages and different Group Policy objects targeted to different groups of users.
-
-1. Create a security group in your Active Directory domain that will map a specific language to a specific set of users in that group.
-2. Add all Cloud PC users who should receive that language to this new security group.
-3. In Server Manager, open **Group Policy Management** and create a new Group Policy object linked to the Organization Unit (OU) or domain that will contain the Cloud PCs for those users.
-4. Right-click the new Group Policy object, and select **Edit...**
-5. Navigate to **User Configuration** > **Preferences** > **Windows Settings**, right-click **Registry**, and select **New** > **Registry Item**.
-6. Enter the following details in the **General** tab. Here's an example that shows Spanish (Spain) with language code es-ES:
-    - Action: Replace
-    - Hive: HKEY_CURRENT_USER
-    - Key Path: Control Panel\Desktop
-    - Value name: PreferredUILanguages
-    - Value type: REG_SZ
-    - Value data: [Language/region tag]. For example, **ar-SA** for Arabic (Saudi Arabia).
-    > [!Note]
-    > To find the language code for your desired language and region combination, see the [language pack list](/windows-hardware/manufacture/desktop/available-language-packs-for-windows#language-packs).
-7. Switch to the **Common** tab and check the following three options:
-    - **Run in logged-on user's security context (user policy option)**
-    - **Apply once and do not reapply**
-    > [!Note]
-    > This setting makes sure that users can change language options themselves later.
-    - **Item-level targeting**
-8. Select **Targeting...**, **New Item**, and **Security Group**.
-9. Select **...** next to the Group, search for the new security group, select the new security group, and hit **OK**.
-10. Select **User in group**, then select **OK** and **OK** to complete the new registry process.
-11. In the "Group Policy Management Editor", navigate to **User Configuration** > **Preferences** > **Control Panel Settings**, right-click **Regional Options**, and select **New** > **Regional Options**.
-12. Under **User Locale**, select the language and region combination that matches the registry key you created in a previous step.
-13. After selecting your desired language and region combination from the dropdown, the dropdown menu may be underlined in red. This indicates that the selection isn't confirmed. Press the **F5** function key on your keyboard to confirm the selection, resulting in a green underlined dropdown menu.
-
-    Before hitting **F5**:
-
-    ![An example of the "User Locale" dropdown menu with a red underline, indicating that the selected language choice hasn't been confirmed.](media/provide-localized-windows-experience/regional-option-selected-red-underline.png)
-
-    After hitting **F5**
-
-    ![An example of the "User Locale" dropdown menu with a red underline, indicating that the selected language choice has been confirmed. ](media/provide-localized-windows-experience/regional-option-selected-green-underline.png)
-
-14. Switch to the **Common** tab and check the following three options:
-    - **Run in logged-on user's security context (user policy option).**
-    - **Apply once and do not reapply.**
-    > [!Note]
-    > This setting makes sure that users can change language options themselves later.
-    - **Item-level targeting.**
-15. Select **Targeting..**, **New Item**, and **Security Group**.
-16. Select **...** next to the Group, search for the new security group, select the new security group, and select **OK**.
-17. Select **User in group**, then select **OK** and **OK** to complete the new registry process.
-
-You can perform these steps for each language you need to provide as the default language for users. If your users have both Cloud PCs and physical devices, you may want to apply [Group Policy loopback](/troubleshoot/windows-server/group-policy/loopback-processing-of-group-policy) so these settings only affect users when they sign in to their Cloud PC.
-
-> [!NOTE]
-> Step 6 above uses the "Replace" command, setting the user's preferred language to just the one language defined in the registry item. If you create multiple Group Policy objects to assign different languages to users, make sure each user is only a member of a single security group that is being targeted.
-
 ## Next steps
 
-[Create a provisioning policy](create-provisioning-policy.md)
+[Use a provisioning policy](use-provisioning-policy-default-display-language.md) or [create a custom device image](create-custom-image-languages.md) to set up the display language.

windows-365/enterprise/whats-new.md

@@ -317,7 +317,7 @@ Windows 11 Cloud PCs require Generation 2 (Gen2) virtual machines. For informati
 
 #### New PowerShell script for installing languages on custom device images<!--35726116-->
 
-The [Windows365LanguagesInstaller PowerShell script]( https://www.powershellgallery.com/packages/Windows365LanguagesInstaller) can install 38 additional languages on your custom device images. For more information, see [Provide a localized Windows experience](provide-localized-windows-experience.md#add-languages-to-windows-using-a-script-and-capture-the-image).
+The [Windows365LanguagesInstaller PowerShell script](https://www.powershellgallery.com/packages/Windows365LanguagesInstaller) can install 38 additional languages on your custom device images. For more information, see [Provide a localized Windows experience](create-custom-image-languages.md#add-languages-to-windows-using-a-script-and-capture-the-image).
 
 <!-- ########################## -->
 ## Week of September 6, 2021 (Service release 2108)