Desktop Analytics

Question

Can anyone help with desktop analytics , in my environment half of the machines shows unable to enroll due to diagtrack version, half of the machines are properly enrolled…
All machines are patched up do date still half machines are showing unable to enroll

solved 0
Ankit Shukla 2020-05-24T10:49:58+05:30 7 Answers 658 views Admin
0

Answers ( 7 )

  2. Ankit Shukla
    0
    2020-05-24T14:21:51+05:30
    Reply

    Have found the reason why machines are not showing as ‘Unable to enroll’ seems to be a miss from MS Side, need to open the advisory with them.

    Till February 2020 , if we check the file version of diagtrack.dll in the rollup (KB4537820) it is 10.0.10586.10007 which is minimum required by desktop Analytics.

    But post Feb 2020, checking file version of diagtrack.dll in March,April and May 2020 Rollup i.e. KB4540688,KB4556836 and KB4550964 the version is downgraded to 10.0.10240.18485 which is not meeting prereq criteria by desktop Analytics.

    So in my environment machines which have rebooted post feb 2020 shows ‘Unable to Enroll’ .

    Best answer
  4. Anoop C Nair
    0
    2020-05-24T12:24:02+05:30
    Reply

    Are you trying to use desktop analytics for windows 7 devices. Only those devices having problem or it’s a mix of both win7 and 10

    Most of the time we forget about SCCM client version

    DA should have version 1902 with update rollup (4500571) or later

  6. Anoop C Nair
    0
    2020-05-24T11:30:30+05:30
    Reply

    I could see

    Not a 1903 client and the DisableTelemetry is enabled M365AHandler

    Do you think telemetry is not enabled ?

    • Ankit Shukla
      0
      2020-05-24T11:44:21+05:30
      Reply

      The logs are from Windows 7 SP1 client, thats the reason it shows as not 1903 client.
      My current environment is at 1906 with all clients at latest version.All other component in Desktop Analytics dashboard shows ‘Successful’ only it shows error that Diagtrack version is not up to date which cam be seen in logs as well on ‘unable to enroll’ machines.

      MS article prereq for diagtrack is to have machine patch with latest montjly rollup which it is.

      I think is there any KB which is missing on clients? Currently comparing the installed KB’s from ‘properly enrolled’ and ‘Unable to enroll’ machines.

  8. Ankit Shukla
    0
    2020-05-24T11:25:52+05:30
    Reply

    M365Handler.log

    CompatTelRunner path: C:\windows\system32\CompatTelRunner.exe M365AHandler 24/05/2020 00:01:50 5752 (0x1678)
    CensusToRun M365AHandler 24/05/2020 00:01:50 5752 (0x1678)
    no need to run M365AHandler 24/05/2020 00:01:50 5752 (0x1678)
    DA Enabled = 1 M365AHandler 24/05/2020 00:01:50 5752 (0x1678)
    CompatTelRunner path: C:\windows\system32\CompatTelRunner.exe not found or the feature is not enabled or the schedual interval is not current M365AHandler 24/05/2020 00:01:50 5752 (0x1678)
    DetailedAppInfo ran less than 2 weeks ago. M365AHandler 24/05/2020 00:01:50 5752 (0x1678)
    CompatTelRunner path: C:\windows\system32\CompatTelRunner.exe M365AHandler 24/05/2020 12:01:50 2356 (0x0934)
    CensusToRun M365AHandler 24/05/2020 12:01:50 2356 (0x0934)
    no need to run M365AHandler 24/05/2020 12:01:50 2356 (0x0934)
    DA Enabled = 1 M365AHandler 24/05/2020 12:01:50 2356 (0x0934)
    CompatTelRunner path: C:\windows\system32\CompatTelRunner.exe not found or the feature is not enabled or the schedual interval is not current M365AHandler 24/05/2020 12:01:50 2356 (0x0934)
    DetailedAppInfo ran less than 2 weeks ago. M365AHandler 24/05/2020 12:01:50 2356 (0x0934)
    Setting = M365ASettings_AllowComputerNameOptIn, Value = True M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Not a Windows 10 1803. M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    cistate: 1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Setting = M365ASettings_AllowWin8andEarlierTelemetry, Value = True M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    CheckTelemetryOptIn/CommercialOptInLevel: Enforcement is not enabled M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    CheckTelemetryOptIn/CommercialOptInLevel: match between dword values in existing setting M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Error Code: 0 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    cistate: 1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Setting = M365ASettings_UserProxyEnabled, Value = False M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Start: CheckUserProxy M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    g_GPOALLOWTELEMETRY: -1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    g_GPOALLOWDEVICENAME: -1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    g_GPOENTERPRISEAUTHPROXY: -1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    g_GPOLIMITEDENHANCED: -1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    UserProxy is not enabled M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Error Code: 0 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    cistate: 1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    g_GPOALLOWTELEMETRY: -1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    g_GPOALLOWDEVICENAME: -1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    g_GPOENTERPRISEAUTHPROXY: -1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    g_GPOLIMITEDENHANCED: -1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    WA CommercialID is not changed. M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Error Code: 0 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    cistate: 1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Setting = M365ASettings_Win10TelemetryLevels, Value = 3 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    cistate: 1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    start checking implicit settings M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Checking Appraiser KB M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Retrieved dll path C:\windows\System32\appraiser.dll M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    retrieved versions 10018362 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Error Code: 0 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    cistate: 1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Checking All Appraiser Versions M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    SetRequestAllAppraiserVersions Set dword at (SOFTWARE\Policies\Microsoft\Windows\DataCollection) M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    SetRequestAllAppraiserVersions Set dword at (SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection) M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Error Code: 0 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    cistate: 1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Checking Diagtrack Service M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Retrieved dll path C:\windows\System32\diagtrack.dll M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Diagtrack version needs to be updated M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    cistate: 2 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Checking MSA Service M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    not windows 10 10240 or above M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Error Code: 0 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    cistate: 1 M365AHandler 24/05/2020 12:19:11 6496 (0x1960)
    Checking CheckConnectivityDiagnosis M365AHandler 24/05/2020 12:19:12 6496 (0x1960)
    C:\windows\CCM\SettingsPlugins\ConnectivityDiagnosis.exe is Microsoft trusted. M365AHandler 24/05/2020 12:19:13 6496 (0x1960)
    Running: C:\windows\CCM\SettingsPlugins\ConnectivityDiagnosis.exe M365AHandler 24/05/2020 12:19:13 6496 (0x1960)
    Passed: CheckConnectivityDiagnosis M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    Error Code: 0 M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    cistate: 1 M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    Checking CheckUserDisableTelemetry M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    CheckUserDisableTelemetry – compliant: there is no User telemetry at SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection\USERS M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    Error Code: 0 M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    cistate: 1 M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    Checking CheckOfficeTelemetryLevel M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    Not a 1903 client and the DisableTelemetry is enabled M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    Error Code: 0 M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    cistate: 1 M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    finished check implicit settings M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    Sending M365A state message M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    Last Hash: C7C2181D2341810C7E6A63254606FF125CB9BE76 M365AHandler 24/05/2020 12:19:19 6496 (0x1960)
    Message Hash is not changed. no need to send. M365AHandler 24/05/2020 12:19:19 6496 (0x1960)

  10. Anoop C Nair
    0
    2020-05-24T11:10:18+05:30
    Reply

    Hello – Can you share the snippets of M365AHandler.log to get the information about the Desktop Analytics settings policy from Client

    Also, collect the logs to analyze Desktop Analytics issues https://docs.microsoft.com/en-us/mem/configmgr/desktop-analytics/log-collector

Leave an answer

Sorry, you do not have permission to answer to this question .