Merge pull request #7355 from MicrosoftDocs/main

Publish 04/13/2022 3:30 PM PT

Author: Angela Fleischmann

memdocs/intune/apps/apps-win32-app-management.md

@@ -6,7 +6,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 03/29/2022
+ms.date: 04/13/2022
 ms.topic: overview
 ms.service: microsoft-intune
 ms.subservice: apps
@@ -31,7 +31,7 @@ Microsoft Intune allows Win32 app management capabilities. Although it's possibl
 > This app management capability supports both 32-bit and 64-bit operating system architecture for Windows applications.
 
 > [!IMPORTANT]
-> When you're deploying Win32 apps, consider using the [Intune Management Extension](../apps/intune-management-extension.md) approach exclusively, particularly when you have a multiple-file Win32 app installer. If you mix the installation of Win32 apps and line-of-business apps during AutoPilot enrollment, the app installation might fail. The Intune management extension is installed automatically when a PowerShell script or Win32 app is assigned to the user or device.
+> When you're deploying Win32 apps, consider using the [Intune Management Extension](../apps/intune-management-extension.md) approach exclusively, particularly when you have a multiple-file Win32 app installer. If you mix the installation of Win32 apps and line-of-business apps during AutoPilot enrollment, the app installation might fail. The Intune management extension is installed automatically when a PowerShell script or Win32 app is assigned to the user or device. Additionally, the Intune management extension agent checks every hour (or on service or device restart) for any new Win32 app assignments.
 
 ## Prerequisites
 

memdocs/intune/configuration/device-profile-monitor.md

@@ -7,7 +7,7 @@ keywords:
 author: MandiOhlinger
 ms.author: mandia
 manager: dougeby
-ms.date: 03/21/2022
+ms.date: 04/13/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: configuration
@@ -79,9 +79,19 @@ After you create your device profile, Intune provides graphical charts. These ch
       - **Assignments**: See the users and groups that receive policy, and see any existing [filters](../fundamentals/filters.md) in the policy. Select **Edit** to update the policy assignment, and add or remove a filter.
       - **Applicability Rules**: On your Windows devices, see the [applicability rules](device-profile-create.md#applicability-rules) used in the policy. Select **Edit** to add or remove an applicability rule.
 
-    - **Device status**: The devices assigned to the profile are listed, and it shows if the profile is successfully deployed. You can select a specific device to get even more details, including the installed apps.
-    - **User status**: Lists the user names with devices affected by this profile, and if the profile successfully deployed. You can select a specific user to get even more details.
-    - **Per-setting status**: Filters the output by showing the individual settings within the profile, and shows if the setting is successfully applied.
+    - **Device and user check-in status**: Shows the number of users or devices that checked-in with the profile. When they check-in, they receive the settings in your profile.
+
+      Select **View report** to see the following information:
+      
+      - The devices that received the profile
+      - The user names with devices that received the profile
+      - The check-in status and the last time the user/device checked in with the profile
+
+      You can also select a specific device to get more details and use the filter column to see the assignment filter options.
+
+    - **Device assignment status**: Select **Generate report** to see the latest profile assignment states for the devices that received the profile. You can also filter the assignment status to see only errors, conflicts, and more.
+
+    - **Per setting status**: Shows the individual settings in the profile, and their status.
 
 > [!TIP]
 > [Intune reports](../fundamentals/reports.md) is a great resource, and describes all the reporting features you can use.

memdocs/intune/configuration/device-profile-troubleshoot.md

@@ -58,7 +58,7 @@ If devices recently enroll, then the compliance, non-compliance, and configurati
 | Windows 10/11 PCs enrolled as devices | Every 3 minutes for 15 minutes, then every 15 minutes for 2 hours, and then around every 8 hours | 
 | Windows 8.1 | Every 5 minutes for 15 minutes, then every 15 minutes for 2 hours, and then around every 8 hours | 
 
-At any time, users can open the Company Portal app, **Settings** > **Sync** to immediately check for policy or profile updates.
+At any time, users can open the Company Portal app, **Settings** > **Sync** to immediately check for policy or profile updates. For related information about the Intune Management Extention agent or Win32 apps, see [Win32 app management in Microsoft Intune](../apps/apps-win32-app-management.md).
 
 ## What actions cause Intune to immediately send a notification to a device?
 

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

@@ -7,7 +7,7 @@ keywords:
 author: brenduns
 ms.author: brenduns
 manager: dougeby
-ms.date: 04/12/2022
+ms.date: 04/13/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: protect
@@ -360,10 +360,7 @@ Updates for the Certificate Connector for Microsoft Intune are released periodic
 New updates for the connector can take a week or more to become available for each tenant.
 
 > [!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.
- 
+> Starting April 2022, certificate connectors earlier than version **6.2101.13.0** will be deprecated and will show a status of *Error*. This status does not affect functionality. Starting June 2022, such connectors will not be able to issue certificates. 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 on July 29, 2021 were replaced by the *Certificate Connector for Microsoft Intune* (as detailed in this article).
 
 ### March 10, 2022
 

memdocs/intune/protect/certificate-connectors.md

@@ -7,7 +7,7 @@ keywords:
 author: brenduns
 ms.author: brenduns
 manager: dougeby
-ms.date: 04/12/2022
+ms.date: 04/13/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: protect
@@ -271,9 +271,7 @@ All events are tagged with a Task Category to aid in filtering.  Task categories
 Updates for the two certificate connectors are released periodically. When we update a connector, you can read about the changes here.
 
 > [!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.
+> Starting April 2022, certificate connectors earlier than version **6.2101.13.0** will be deprecated and will show a status of *Error*. This status does not affect functionality. Starting June 2022, such connectors will not be able to issue certificates. See the note at the to start of this article for details on moving to the new **Certificate Connector for Microsoft**.
 
 ### PFX Certificate Connector release history