Share via

Nothing appears in update compliance solution

Moataz Shaaban 1 Reputation point
2020-06-29T07:09:05.303+00:00

I am trying to use update compliance and I installed the MMA client on windows machines and the machines send logs to my log analytics workspace normally but till now after 5 days nothing appear in the update compliance ,I run configuration script and also tried manual way , here is the result for the script

2020-06-28T16:29:56 : Start : Starting Update Compliance Configuration Script
2020-06-28T16:29:57 : Info :
2020-06-28T16:29:57 : Info : ******************************** Update Compliance ******************************************
2020-06-28T16:29:57 : Info : UTC DateTime: 2020-06-28T14:29:57Z
2020-06-28T16:29:57 : Info : Script Version: 1.0.0 - 03.06.2020
2020-06-28T16:29:57 : Info : OS Version: 10.0.17134
2020-06-28T16:29:57 : Info : RunMode: Pilot
2020-06-28T16:29:57 : Info : LogPath: d:\logs
2020-06-28T16:29:57 : Info : CommercialIdInput: 97a2521c-2380-45a3-8244-8f7cb201a093
2020-06-28T16:29:57 : Info : LogMode: 1
2020-06-28T16:29:57 : Info : Verbose: True
2020-06-28T16:29:57 : Info : ClientProxy: Direct
2020-06-28T16:29:57 : Info : DeviceNameOptIn: true
2020-06-28T16:29:57 : Info : Architecture: AMD64
2020-06-28T16:29:57 : Info : Machine Sqm Id: s:8BFCDCD6-8EB2-4F21-81DC-7CF15A4B3D8F
2020-06-28T16:29:57 : Info : Machine Name: MOATAZ-PC
2020-06-28T16:29:57 : Info : *********************************************************************************************
2020-06-28T16:29:57 : Info :
2020-06-28T16:29:57 : Info : Powershell Execution Policies:
2020-06-28T16:29:57 : Info : @{Scope=MachinePolicy; ExecutionPolicy=Undefined}
2020-06-28T16:29:57 : Info : @{Scope=UserPolicy; ExecutionPolicy=Undefined}
2020-06-28T16:29:57 : Info : @{Scope=Process; ExecutionPolicy=Bypass}
2020-06-28T16:29:57 : Info : @{Scope=CurrentUser; ExecutionPolicy=Undefined}
2020-06-28T16:29:57 : Info : @{Scope=LocalMachine; ExecutionPolicy=Unrestricted}
2020-06-28T16:29:57 : Info :
2020-06-28T16:29:57 : Info : Start: CheckCommercialId
2020-06-28T16:29:57 : Info : Passed: CheckCommercialId
2020-06-28T16:29:57 : Info : Start: SetupCommercialId
2020-06-28T16:29:57 : Info : Commercial Id already set to the same value as provided in the script parameters.
2020-06-28T16:29:57 : Info : Passed: SetupCommercialId
2020-06-28T16:29:57 : Info : Start: CheckTelemetryOptIn
2020-06-28T16:29:57 : Info : AllowTelemetry property value at registry key path HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection : 1
2020-06-28T16:29:57 : Info : AllowTelemetry property value at registry key path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection : 1
2020-06-28T16:29:57 : Info : Start: CheckProxySettings
2020-06-28T16:29:57 : Info : WinHTTP Proxy settings:
2020-06-28T16:29:57 : Info :
2020-06-28T16:29:57 : Info : Current WinHTTP proxy settings:
2020-06-28T16:29:57 : Info :
2020-06-28T16:29:57 : Info : Direct access (no proxy server).
2020-06-28T16:29:57 : Info :
2020-06-28T16:29:57 : Info : WinINET Proxy settings:
2020-06-28T16:29:57 : Info : Proxy properties at path HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings :
2020-06-28T16:29:57 : Info : ProxyEnable: 0
2020-06-28T16:29:57 : Info : Proxy properties at path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings :
2020-06-28T16:29:57 : Info : ProxyEnable: 0
2020-06-28T16:29:57 : Info : Passed: CheckProxySettings
2020-06-28T16:29:57 : Info : Start: CheckUserProxy
2020-06-28T16:29:57 : Info : DisableEnterpriseAuthProxy property value at registry key path: HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection : 0
2020-06-28T16:29:57 : Info : Passed: CheckUserProxy
2020-06-28T16:29:57 : Info : Start: CheckVortexConnectivity
2020-06-28T16:29:58 : Info : Impersonating a user for authenticated proxy.

Checking for Vortex connectivity.

AccountUsedToConnect: Moataz-PC\Moataz

Proxy settings:

ProxyType: 0 (default proxy)

ProxyList: (null)

ProxyBypass: (null)

OS version 10.0.17134

DiagTrack version 10.0.17134.48

Connecting to https://v10.events.data.microsoft.com/ping

Connected to https://v10.events.data.microsoft.com/ping.

Service returned HttpStatus: 200.

2020-06-28T16:29:58 : Info : Passed: CheckVortexConnectivity
2020-06-28T16:29:58 : Info : Start: CheckRebootRequired
2020-06-28T16:29:58 : Info : Checking if there is a pending reboot
2020-06-28T16:29:58 : Info : Passed: CheckRebootRequired. Reboot is not needed.
2020-06-28T16:29:58 : Info : Start: CheckDiagtrackService
2020-06-28T16:29:58 : Info : Diagtrack.dll version: 10017134
2020-06-28T16:29:58 : Info : Diagtrack.dll full version: 10.0.17134.48
2020-06-28T16:29:58 : warning : CheckUTCKB The Diagnostics and Telemetry tracking service (diagtrack.dll version 10.0.17134.48) is old. 10.0.17134.320 enables faster processing of insights and reduces overall latency for devices enrolled in analytics. Learn more at https://go.microsoft.com/fwlink/?linkid=2011593&clcid=0x409
2020-06-28T16:29:58 : Info : Diagtrack Service Status: Running
2020-06-28T16:29:58 : Info : Passed: CheckDiagtrackService
2020-06-28T16:29:58 : Info : Start: CheckMSAService
2020-06-28T16:29:58 : Info : Microsoft Account Sign In Assistant Service State: Stopped, StartMode: Manual
2020-06-28T16:29:58 : Info : Microsoft Account Sign In Assistant Service is Manual(Triggered Start).
2020-06-28T16:29:58 : Info : Passed: CheckMSAService
2020-06-28T16:29:58 : Info : Start: SetDeviceNameOptIn
2020-06-28T16:29:58 : Info : Passed: SetDeviceNameOptIn
2020-06-28T16:29:58 : Info : Start: CleanupOneSettings
2020-06-28T16:29:58 : Info : Registry Key details for HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Diagnostics\Diagtrack\SettingsRequests are: @{LastDownloadTime=132378278221314662; LastTelSettingsRingId=2; LastTelSettingsRingName=Retail; PSPath=Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Diagnostics\Diagtrack\SettingsRequests; PSParentPath=Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Diagnostics\Diagtrack; PSChildName=SettingsRequests; PSDrive=HKLM; PSProvider=Microsoft.PowerShell.Core\Registry}
2020-06-28T16:29:59 : Info : Passed: CleanupOneSettings
2020-06-28T16:29:59 : Info : Start: RunCensus
2020-06-28T16:29:59 : Info : Setting property: FullSync to value 1 at registry key path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Census to turn on Census FullSync mode
2020-06-28T16:29:59 : Info : Running C:\WINDOWS\system32\devicecensus.exe
2020-06-28T16:30:06 : Info : Passed: RunCensus
2020-06-28T16:30:06 : Info : Resetting property: FullSync to value 0 at registry key path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Census to turn off Census FullSync mode
2020-06-28T16:30:06 : Info : Running diagnose_internal.cmd
2020-06-28T16:30:10 : Success : Script succeeded

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
3,231 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. SwathiDhanwada-MSFT 18,756 Reputation points
    2020-07-01T08:37:39.65+00:00

    @MoatazShaaban-9684 Thanks for reaching out !! From the logs, I could see that you have configured windows device through the Update Compliance Configuration Script recently. Normally, it can take up to 72 hours before devices are visible in the solution. Until then, Update Compliance will indicate it is still assessing devices.

    I would suggest you to check again after 24 hours and revert if you are still facing the issue.

    1 person found this answer helpful.
  2. Moataz Shaaban 1 Reputation point
    2020-07-02T12:22:14.36+00:00

    A machine started to appear just today ,thanks

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.