Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post 'extend' operator: Failed to resolve table or column expression named 'WaaSDeploymentStatus'... #18

Open
Subhayu2016 opened this issue Oct 2, 2023 · 4 comments

Comments

@Subhayu2016
Copy link

Describe the bug
A clear and concise description of what the bug is. 'extend' operator: Failed to resolve table or column expression named 'WaaSDeploymentStatus'...

Post uploading to Intune Portal reporting getting error and Update Compliance Table not getting created

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
image

Additional context
Add any other context about the problem here.

@hanenChh
Copy link

i have the same pb

@Ioan-Popovici
Copy link

You have to actually send update data to log analytics in order for that table to be created as stated in the blog post.

Enable Windows diagnostics

@MP-feedback
Copy link

MP-feedback commented Dec 16, 2024

I have the same problem, I had created the diagnostic settings and even left them for a week, however I don't see that table in the Log Analytics Workspace:

image

image

image

Currently we only have an Update ring, and Driver update policy assigned. We also have a feature update policy that hasn't been assigned and nothing under the quality updates tab. Do we need to create a quality update/expedite update policy for this table to show up in the Intune logs or does the WaaSDeploymentStatus table come from somewhere else?

I'm asking because I don't see that log listed here https://learn.microsoft.com/en-us/mem/intune/fundamentals/review-logs-using-azure-monitor#send-logs-to-azure-monitor

@Ioan-Popovici
Copy link

Ensure the devices are correctly configured to send Windows Update reporting data to Log Analytics

  1. Go to the Microsoft Endpoint Manager Admin Center:
    • Navigate to Reports > Windows updates.
    • Verify that the reporting data collection for Windows Update for Business (WUfB) is enabled.
  2. Ensure that Update compliance settings are configured:
    • Log in to the Azure portal.
    • Go to Azure Monitor > Log Analytics Workspaces > Workspace Settings.
    • Under Agents Management, ensure devices are correctly connected to the workspace.

Ensure that Update compliance settings are configured:
• Log in to the Azure portal.
• Go to Azure Monitor > Log Analytics Workspaces > Workspace Settings.
• Under Agents Management, ensure devices are correctly connected to the workspace.

Check Intune Device Configuration Policy for Update Compliance
The Update Compliance integration requires a Custom Device Configuration profile in Intune.

  1. Go to Endpoint Manager Admin Center > Devices > Configuration Profiles.
  2. Create or verify the following:
    • OMA-URI Configuration:
    • OMA-URI Path: ./Vendor/MSFT/Policy/Config/Update/AllowWUfBCloudProcessing
    • Value: 1
    This ensures Windows Update for Business telemetry data is sent to Azure.
  3. Ensure the policy is deployed to the correct device group.

Verify Device Telemetry Settings
The WaaSDeploymentStatus data relies on telemetry. Ensure devices have the proper diagnostic data settings:

  1. Open Settings on the device:
    • Go to Privacy > Diagnostics & Feedback.
    • Ensure that Optional diagnostic data is enabled.
  2. In Intune:
    • Go to Devices > Windows > Configuration profiles.
    • Create or update a profile to set:
    • Telemetry level to Enhanced or Full.

Custom OMA-URI for Telemetry Settings
If required, deploy the following setting via a custom configuration profile:
• OMA-URI Path: ./Vendor/MSFT/Policy/Config/System/AllowTelemetry
• Value: Enhanced (2) or Full (3).

Verify Devices are Reporting to Log Analytics

  1. Go to your Log Analytics Workspace in the Azure Portal.
  2. Use the following query to check for data:
    ,,,
    UpdateCompliance
    | summarize count() by DeviceName
    ,,,

If no data is returned:
• Confirm the workspace ID and key are correct in your configuration.
• Ensure that devices can communicate with the Log Analytics endpoint.

Check for Windows Update Compliance Delay
• Windows Update reporting can take up to 24-48 hours to appear in Log Analytics.
• Devices must have internet connectivity and Telemetry Services running.

Validate Required Firewall and Network Connectivity

Devices must reach Log Analytics endpoints and Windows Update for Business (WUfB) telemetry endpoints. Allow the following URLs in your firewall/proxy:
• *.monitor.azure.com
• *.ods.opinsights.azure.com
• *.loganalytics.io
• v20.events.data.microsoft.com

Revalidate Device Enrollment
Devices must be enrolled in both Intune and correctly configured for WUfB.

Run the following commands on a client machine to validate settings:

# Check Telemetry Level
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection"

# Check Connectivity to Windows Update Service
Test-NetConnection -ComputerName settings-win.data.microsoft.com -Port 443

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants