1606 including hotfixes -> Clients no longer reporting Hardware Inventory (updated 8/24/16 14:30) RRS feed

  • Question

  • Running the latest client 5.00.8412.1007 on Windows 10 Enterprise 1607 (14393.51), also confirmed on 5.00.8412.1006 on Windows 10 Enterprise 1607 (14393.51)

    This client is able to grab the machine policy, but does not report back the hardware inventory. Since our nested device collections depend on the client's HINV this is obviously an issue for me.

    Our system center environment is in DomainA, client machines are in DomainB, there's no trust whatsoever. This situation has worked for us up until the latest 2 hotfixes on SCCM 1606.

    On the client:

    Manually invoking the Hardware Inventory Action from the client.

    - CCMeval.log is ok

    - InventoryAgent.log reports no errors

    - CCMMessaging.log never shows that the MESSAGE PAYLOAD was received or sent

    On the MP:

    - MP_Hinv.log does not log my client posting anything.

    - Checked IIS logs for my client's IP: does not show up..


    Windows 2008R2SP1 / Windows 2012 / Windows 2012R2 / Windows 8.1 / Windows 10 1511 all work fine with the .1006 or .1007 client.

    So, putting together what I've found so far: Hardware Inventory runs, and is supposed to drop a msg in the queue containing the results to be send to MP. CCMMessaging reports when this message is uploaded and if successful. This happens on Windows 10 1607 deployments, using client .1006 or .1007 and maybe more.

    Looking at the BITS processes (which are ultimately responsible for getting the mssgs to the MP):

    (Run Get-BitsTransfer -AllUsers in PowerShell on the client)

    JobId                                DisplayName                                               TransferType JobState       OwnerAccount
    -----                                -----------                                               ------------ --------       ------------
    62c22ef9-adf6-4ec3-bd6a-226901529233 CCM Message Upload {B448A760-7F81-4A76-BA78-AEA09E0185CF} Upload       TransientError NT AUTHORITY\SYSTEM
    a522b095-eb50-4d74-a7cc-37bc7373e931 CCM Message Upload {665659F5-22AB-4898-9BD1-965654D1A3FF} Upload       TransientError NT AUTHORITY\SYSTEM
    ee267479-a0c6-4913-9831-e9283953098d CCM Message Upload {F855F606-22BE-48FC-BAFC-12A89240E1DA} Upload       TransientError NT AUTHORITY\SYSTEM
    b169922e-fcb3-4d76-a15e-e277863266b6 CCM Message Upload {4564E6F8-5F1F-4531-8B6E-6C445387AB87} Upload       TransientError NT AUTHORITY\SYSTEM
    58e6c128-f0d9-4765-b74f-fee82d49d693 CCM Message Upload {74BFB5C5-3122-4C10-8EC8-7DFE9FC9438E} Upload       TransientError NT AUTHORITY\SYSTEM

    Any hints into what to check / do next are appreciated.. Not much of an SCCM /BITS wizard here ;)

    There's a new blog in town:

    • Edited by Arjan Mensch Wednesday, August 24, 2016 12:17 PM more info
    Tuesday, August 23, 2016 8:13 PM

All replies

  • We're experiencing the exact same issue.  Hopefully Microsoft can shade some light on this.

    Monday, August 29, 2016 4:12 PM
  • Have you ran Hardware inventory on client side ?
    Monday, August 29, 2016 6:29 PM
  • Hi,

    I have same behavior, our inventory scans dont work after servicing upgrade from 1511 to 1607. Client works correctly like DDR and Policy requests, but no inventory scans.

    Client reinstall wont help at all and inventoryAgent.log tells that scan is in queue, but nothing else.


    Thursday, September 1, 2016 5:34 AM
  • Hi All,

    The SCCM team is investigating.  Can you guys try updating some of these clients to build 14393.82 to see if it helps?  Internally we have confirmed that .82 machines are uploading HINV correctly.

    tim [MSFT]

    Thursday, September 1, 2016 3:47 PM
  • Hi Arjan,

    Can you please provide log snippets from the affected machine.Like Inventoryagent.log.

    It is worth to examining the sccm client and server side log files related HW inventory and reviewing status messages.


    Jijo Chacko

    Tuesday, September 6, 2016 12:58 AM
  • Just come off a call with Premier Support and we have a work around for this, but not entirely happy with the workaround.  At the least it will allow us to run the HW Inventory while we work out why this is happening.

    To implement this you need to change the following registry key:

    HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\EFS\EfsConfiguration - change the value from 1 to 0. Reboot the system.

    This will change the Encryption File System to enabled (yes, 0 does equal enabled).  More about this is available here:

    The big change you have is that your end users can suddenly encrypt files and folders on their system.  They'll come running when their system crashes and they can't retrieve the data as well.  I'm keeping this as a workaround at the moment so we can continue testing with Windows 10 1607 release.  Will see what else we can dig up and keep up the pressure on MS Premier Support.

    • Proposed as answer by YoungRobbo Wednesday, October 5, 2016 8:05 AM
    Wednesday, September 7, 2016 11:13 AM
  • We have 1 client at build 14393.105 that has the same inventory issue.

    We have about 9 clients at build 14393.82 All have the inventory issue accept one system.

    • Site version 5.0.8412.1000
    • Console version 5.0.8412.1003
    • Client version 5.00.8412.1007 

    I tested the registry key change shared below by YoungRobbo and it resolved the inventory issue on that system.

    Are there any new developments on this issue?

    Thank for your time!  

    Friday, September 9, 2016 4:28 PM
  • At the moment I have nothing I can report on from MS. 

    I've put an application based CI in place, with detection method of the build for 1607 in Powershell:

    if(([System.Environment]::OSVersion.Version).Build -eq 14393)
        write-host "Your Windows build is 1607 version"
    It then changes the registry key as temporary fix (reversing this when we get a fix from MS on this issue).
    Monday, September 12, 2016 11:14 AM
  • Does anyone have any progress on this?

    Is it a SCCM client or Windows 10 1607 issue?

    When can we suspect a fix?

    Friday, September 30, 2016 11:35 AM
  • The issue is in Windows 10 1607 release, not SCCM.  This occurs when it needs to send larger BITS transfers (like the HW Inventory) and the EFS is turned off.  The fix for this is due to be released to the insider build according to David James (@djammmer) on Twitter.  Hopefully we'll see the complete fix shortly this means.

    • Proposed as answer by YoungRobbo Wednesday, October 5, 2016 8:05 AM
    • Edited by YoungRobbo Wednesday, October 5, 2016 8:06 AM edit twitter user
    Wednesday, October 5, 2016 8:04 AM
  • I updated my Win10 with latest Cumulative update and now my win10 build number is 14393.222. I am not facing any inventory issues. As per inventoryagent.log,MP_hinv.log,dataldr.log and bits job, it is getting properly processed into the SCCM database.

    Please try updating the Windows 10 to mentioned build number 14393.222.

    Friday, October 7, 2016 2:15 PM
  • I installed 14393.222 this morning and my client still faces the same issue with HW Inventory without changing the EFS key.  Although MS have indicated that we will receive a fix for this in a coming update release to Win 10 1607.
    Monday, October 10, 2016 12:25 PM
  • Update 2016/10/06

    We just receive confirmation from the product group that a fix for this issue is in Windows 10 Insider build 14941+. Hopefully will be released to Windows 10 1607 later this month.


    Regarding the efs thing

    Monday, October 17, 2016 2:42 PM
  • Experiencing this issue as well.

    As of 10/26, build 14393.321 still has the issue.

    Thursday, October 27, 2016 1:44 PM
  • Fixed with

    • Proposed as answer by YoungRobbo Monday, October 31, 2016 2:28 PM
    Monday, October 31, 2016 2:28 PM
  • Hi

    I am trying to Deploy MBAM 2.5 policy, but I cant download the MBAM 2.5 SP1 Group policy templates, from the link that microsoft had to download, the link isn't working, can someone else please help me with that? This is the link that I used to download. Link:

    I am following this steps:

    How to Install MBAM 2.5 SP1 and integrate with SCCM Configmgr 2012 R2 SP1 – Part 5

    to finish the configuration of MBAM 2.5 SP1 integration with SCCM 2012 R2 SP1.

    At the same time, I don't know, why I have problem with to get a report from windows 10 Laptops, but from Windows 8.1 is wroking.


    Wednesday, March 29, 2017 5:08 PM