New alerts for Windows updates in Microsoft Intune

You can now better find and troubleshoot devices that aren’t reporting Windows Update progress in Microsoft Intune reports. It may not have been obvious before, but devices that aren’t sending diagnostic data to Microsoft can’t show detailed device status during the deployment process.

Two new alerts provide better insight into these issues: DeviceDiagnosticDataNotReceived and MinimumOSBuildNotMet. You’ll see them integrated into Intune reporting, as well as Windows Update for Business reporting and Log Analytics. Let’s take a look at what these alerts mean, where to find them, and how to troubleshoot and fix the underlying issues.

Reporting problems and causes

Have you ever faced the following issues while monitoring Windows Update deployments?

• Sometimes the device shows as “offline”, which prevents the update installation process from proceeding successfully, but other times the update will proceed successfully.
• Devices that are being deployed seem to be stuck in the “Reserved” or “Ready to Deliver” state for long periods of time, sometimes even after the update has been successfully installed. That is, they do not show the correct progress, such as “Installing”, “Awaiting Restart”, etc.
• After enrollment, the device does not appear in Windows Update for Business reports. This occurs when the device has not communicated diagnostic data in the first place or has not communicated for more than 28 days.

These issues occur when the device fails to communicate client data. Some of the most common causes are device inactivity or incorrectly configured client data settings. Another possible cause is that the device is not on the minimum OS build required to be eligible for reporting. Device compliance notifications related to diagnostic data can help you measure deployment success and better monitor the overall health of your organization.

Device Compliance Notification

No matter what reporting tool you use, it’s important to see the true state of your organization’s devices. Windows diagnostic data helps you understand exactly how your devices are progressing through the deployment process and detect issues that trigger alerts. Alerts provide details on why devices aren’t updating and provide clear guidance on how to address those issues with targeted solutions. Here are some insights you can gain through two new alerts and existing alerts in Microsoft Intune:

Warning: New device diagnostic data not received

The DeviceDiagnosticDataNotReceived alert identifies devices that fail to send diagnostic data, resulting in incorrect client status in reports.

• meaning: The device is not transmitting diagnostic data. This is a common signal and the reasons for this include but are not limited to:
  • Incorrect diagnostic data configuration
  • There is no configuration to send diagnostic data
  • Blocked network endpoints
• Recommended Action: Make sure your device is properly configured to share diagnostic data. Enable Windows diagnostic data usage in Intune Please see the Troubleshooting and Fixes section below.
• Availability Reporting: Microsoft Intune (new), Windows Update for Business Report

New MinimumOSBuildNotMet warning

MinimumOSBuildNotMet identifies a subset of missing devices that are ineligible for report registration.

• meaning: The Windows Diagnostic Data Processor configuration is missing, and the device does not meet the minimum service requirements for registering reports.
• Recommended Action: Make sure your device has at least the January 2023 non-security update or the February 2023 cumulative update installed. Learn more Windows Diagnostic Processor Support.
• Availability Reporting: Microsoft Intune (new), Windows Update for Business Report (new)

Existing InsufficientUpdateConnectivity warning

A related warning you may be more familiar with is InsufficientUpdateConnectivity. It’s not new, but it adds to our understanding of the bigger picture.

• meaning: The device is inactive or diagnostic data is insufficient to verify the activity required to successfully update the device.
• Recommended Action: Make sure your device is activated and connected to the Internet.
• Availability Reporting: Microsoft Intune, Windows Update for Business report

The three alerts are mutually exclusive. The active DeviceDiagnosticDataNotReceived alert only provides a general overview of devices that are missing from the report for various unspecified reasons. Devices with known reasons, such as not meeting the OS build prerequisites, are instead identified by the active MinimumOSBuildNotMet alert. Similarly, the InsufficientUpdateConnectivity alert is more specific than the generic alert. This specific alert will not appear as active on the same device as DeviceDiagnosticDataNotReceived.

Let’s look at how to use these notifications in Microsoft Intune, similar to Windows Update for Business reports or Log Analytics.

Integration with Microsoft Intune reporting

Whether you manage a few devices or thousands of devices, Microsoft Intune helps you keep your Windows Update deployments running smoothly. Let’s say you want to monitor a group of devices associated with a specific deployment policy. You can monitor active devices that meet the prerequisites for registering for reports and continuously delivering diagnostic data. Here’s how to use new alerts to find and resolve these scenarios.

Like all other notifications in Intune, these notifications can be viewed in Intune’s default status and failure reports.

1. Please log in Microsoft Intune Admin Center.
2. Go to report.
3. Below Device ManagementChoose Windows Update.
4. Switch to report tag.

   Screenshot of the Reports tab in the Microsoft Intune admin center.

5. Select the report you want to open from the list of available tiles. Note: The Quick Updates report is used as an example here, but the following steps can also be applied to the Feature Updates and Driver Updates reports.
6. Choose what you want Policy Updates and Aggregated status updates.
7. Please select Generate Report Click the button to view the results.

   Screenshot of the Windows Update Status report in Microsoft Intune.

Failure reports group devices based on specific policies that have errors or warnings. To view a failure report:

1. Start from Microsoft Intune Admin Center.
2. Go to device.
3. Below Update ManagementChoose Windows Update.
4. Switch to monitor tag.
5. Select the KPI card for the desired policy to view more details.

   Screenshot of the unified view of update policies with active notifications in Microsoft Intune.

6. Select a profile from the list.

   Screenshot of a policy profile containing devices with active errors in Microsoft Intune.

7. Select a policy profile to view a list of devices with active notifications.

   Screenshot of a device with active alerts in the update failure report.

8. (Optional) Select specific notifications from: knell filter.
9. Selecting an alert message for a specific device will display a description of the error, related details, and recommendations.

   Here’s a screenshot of the full details flyout for the error device for the selected notification message.

Other reports using these notifications

Are you using Windows Update for Business reports? You can also find these notifications using Azure Workbooks or Log Analytics. Both notifications are now available in Azure Workbooks. outline tab, inside Total number of devices KPI Card. Just select it. View details Then Missing DeviceAs shown.

Screenshot of a device missing from the Windows Update for Business report. Notice the two new notifications.

To view data from a Windows Update for Business report workbook in Log Analytics, use the following query:

UCDeviceAlert
| If AlertSubtype is (“DeviceDiagnosticDataNotReceived”, “MinimumOSBuildNotMet”)
| Project DeviceName, AzureADDeviceId, AlertSubtype, StartTime, AlertData, Description, Recommendation

For detailed instructions on these reporting options, follow these instructions: Is your device missing from your Windows Update for Business report?.

Troubleshoot and fix diagnostic data issues.

Make sure the device with these notifications is enabled and properly configured to send Windows diagnostic data. To do this, make sure the following settings are properly configured:

• Default Windows diagnostic data settings. Please check Windows diagnostic data settings. In most cases, the default setting of “Required” or “Basic” is sufficient. If you have previously configured these settings to something other than the default, check to see if that configuration may have affected the diagnostic data behavior.
• Intune diagnostic data settings. Make sure you have activated it correctly Intune settings for diagnostic data.
• Group policy settings. Check the group policy settings you are deploying. If the required settings are incorrectly set through group policy, Intune will override the settings. Pay special attention to the group policies that remain on the device. To resolve conflicts, follow these instructions: Allow Diagnostic Data Group Policy.
• Co-management of configuration managers. If you use Configuration Manager co-management, make sure that: Setting up diagnostic data in System Center Operations Manager.
• OneSettings service. Make sure DisableOneSettingsDownload is enabled. The default is to not disable this configuration policy. For more information and to re-check this policy, visit: System Policy CSP.

Try new notifications in Microsoft Intune today

Collecting and utilizing diagnostic data is essential to improving the stability and efficiency of the overall system.

Get a more comprehensive view of the success of your Windows Update deployments with two new notifications: DeviceDiagnosticDataNotReceived and MinimumOSBuildNotMet. This new Microsoft Intune capability builds on existing capabilities in Windows Update for Business Reports and Log Analytics, giving you more flexibility and control over your device management strategy.

In the spirit of continuous improvement, we want to help you gain more insight into subsets of devices that were previously difficult to identify. Try these new reporting improvements and check out these additional resources:

Keep the conversation going. Find best practices. Bookmark it. Windows Tech CommunityThen follow us @MSWindowsITPro About X and on LinkedIn. Looking for support? Visit Microsoft’s Windows Q&A.