/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


Custom Inventory Rules not being applied to new devices

11/15/2017 2053 views

Recently a technician noticed that a number newly imaged devices did not have any of the custom inventory fields that we use to apply smart labels/managed installs. After parsing through the KAgent log I noticed that most of the custom inventory rules were not being processed, it was only processing two deprecated rulesets. I looked at another recently imaged device and discovered that it had all/most of the correct rulesets being applied. I understand that the custom inventory rules are created within the K1000 software library, and I see where the KAgent is sending an HTTP query to the K1000 to collect the list of rules to be processed, so what are we missing?

Each PC is imaged with Windows 10 x64 Enterprise
We are running K1000 Version: 7.0.121306

We have attempted KAgent v 6.3.306 and 7.0.763


18 Rules found

No rules found

0 Comments   [ + ] Show comments

Comments


All Answers

0
Verify that your custom rules have been updated to include the build version of Windows 10. By default new builds are not added to software titles, so you need to update your custom inventory rules when new builds become available. There is a great post on how to setup a script that will automatically enable new builds here:

Answered 11/16/2017 by: chucksteel
Red Belt

  • Thanks for the answer!

    K1000 Shows:
    10.0.10240
    10.0.10586
    10.0.14393
    10.0.15063
    10.0.16299

    The machines mentioned above are running
    10.0.10586
    and
    10.0.15063

    So it looks like we are still in the clear on that, for now.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ