5 Replies Latest reply on Aug 22, 2014 3:35 PM by mrspike

    LANDesk management suite inventory scanner settings questions

    Rookie

      Hi all,

       

      I'm busy making reports on queries in the LANDesk management console on software usage and versions.

      And found a whole lot of historical information is kept in the database.

      From what I found on the web this ties in with the 'days to keep inventory scans' settings on the inventory service on the core.

      So I've set this value back from 0 (forever) to 90 days which seems more appropriate.

       

      My question is, why would anyone be interested in historical inventory scans?

      From a reporting perspective I am only interested in the most recent information. I want to know the state of my machines as they are now.

      Is it possible to have the client machines only run full scans and tell the core to keep only the last scan in it's DB or something?

       

      If you can share any insights you have on this with me that would be much appreciated.

      Thanks.

        • 1. Re: LANDesk management suite inventory scanner settings questions
          LANDeskWizrd SSMMVPGroup

          What database table are you seeing this historical information in?

           

          The "days to keep inventory scans" really pertains to how long you want a client to stay in the database without having it send in a scan. Having it at 0 is probably not a good thing unless it's a development server or the need is there. You really want to set it to a specific number, like you just did, so that the inventory service cleans old/stale records that haven't responded in X amount of time.

           

          If you go under Configure - Inventory History on the console's menu bar, what, if anything, do you have set? This might explain what you are seeing.

           

          Also, there are options to keep patch historical data as well as scheduled task history for certain amount of days. What are these set to?

           

          To try and answer your question, for me, historical data is critical in our reporting of patch/software distribution as well as remote control usage. We have certain metrics we need to provide and all have an element of time and that is only gathered if you have historical data. A single inventory scan doesn't always provide information on what happened in the past. The database needs to be able to store information for these types of metrics.

          • 2. Re: LANDesk management suite inventory scanner settings questions
            Rookie

            OK I think I'm shooting myself in the foot here.

            My query uses the computer\software\package name field and it is returning multiple records and versions per name, which I did not expect.

            So I went to devices, and a device inventory also shows many entries for a package name with different version numbers list for the same package name.

            I thought that this was historical data in the database because the right page when clicking on a package name shows details about file sizes, dates and folders appears to be indentical.

            But when I increase the column width of the value field in this pane to fit all 200 characters in there I can see that there are a few differences in the automatically generated folder names.

            So these additional entries are from past upgrades and installs but they are still present on the client's file system.

            Historical and current at the same time..hmm nice.

             

            By now you are probably wondering why I'm using the package section for software reporting in the first place.

            That's because I've noticed that some of the setups of the software products we use, (namely stuff made by Avaya), does not consistenly register itself under add/remove programs or products.

            So queries for reporting or selecting target devices for upgrade wouldn't pick up on those because of this.

            This is why I started looking into the packages section for reporting because it does not rely on the installer of the software manufacturer do it's job properly.

            • 3. Re: LANDesk management suite inventory scanner settings questions
              LANDeskWizrd SSMMVPGroup

              Ah yes, I have ran across this as well. We also have users that use some Avaya software and we have to query based on "Package" also. As you discovered, you will get more than one return if the exe name is present in multiple folders due to updates/backups and other factors. I am not sure how you get around this unless you add another condition like "Path" of the file. On one of my clients, I see Avaya listed under Computer\Software\Product but not sure if that will help you or not. That section in inventory is directly related to what SLM discovers.

              • 4. Re: LANDesk management suite inventory scanner settings questions
                Rookie

                OK thank you very much for your help!

                • 5. Re: LANDesk management suite inventory scanner settings questions
                  mrspike SSMMVPGroup

                  To clarify, if you change the setting in 'days to keep inventory scans' settings on the inventory service on the core, that system will be deleted from the core if it has not sent in an inventory in 'x' number of days.

                   

                  We have ours at 90 days, you do not want it set too soon, especially if you have laptops that are offsite and use a Gateway / CSA since they have to be listed on the core in order to come in via the Gateway.  90 days is a good compromise.