/build/static/layout/Breadcrumb_cap_w.png

Best Practices Question


device model numbers.

06/18/2018 452 views
We are working on deploying  Kace SMA. For inventory management purposes we are trying to be able to sort by model and have reports telling us how many of a specific model is left in out environment and things along them lines. Problem is Kace sees 20H9000TUS, 20BE003PUS, 424049U, etc. But is there a way and if so what is pest practice for Kace to display T570, T470, T560 etc. To add more trouble to the issue. There are two to three different types of T570, so it would have two or three of the longer numbers attached and instead of using one of the long numbers, it sees all them numbers as the same T570 model. Otherwise I was thinking about assigning them (T570, T560, T47, etc)  as sub-types. Anyone else have better ideas?
1 Comment   [ + ] Show comment

Comments

  • You have two issues

    1- A custom inventory rule to pull the desired Data.

    2- A report to organize the gathered Data.

    So... First check this URL

    https://www.windows-commandline.com/get-computer-model/

    Use one of those Lenovos to see which WMIC command is able to pull the model the way you want, or NOT, if it's not, then you will need to check with Lenovo if they store the Commercial name (ThinkPad, IdeaPad, etc etc) somewhere on the registry.

    Anyways a custom inventory rule let's you pull more information from several sources (inside the device), information the agent is not pulling by default.
    (It can be a file, something on the registry, or WMIC, or powershell results)

    https://support.quest.com/technical-documents/kace-sma/8.0/administrator-guide/137#TOPIC-829259

Be the first to answer this question

 
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