10 Replies Latest reply on Sep 21, 2011 4:17 AM by Catalysttgj

    Incorrect display of Physical Memory

    Rookie

      Hi,

       

      I was wondering, how can I have the real amount of physical memory installed in my computers, because if I choose the report Physical Memory it shows me only what Windows operational system can detect. For example I have 4 memory slots, two are not filled and the others have 2Gb each, so instead of report 4Gb, it only reports what Windows Operational System says.

       

      Another way, was to use Queries choosing: Computer/ Memory / Slots / Memory Slot / Installed Size, but the result is exactly the same from that report.

       

      How can I have a hardware inventory showing me in a collum the real ammount of physical memory installed?

       

       

      Best regards,

      Michel

        • 1. Re: Incorrect display of Physical Memory
          Catalysttgj Expert

          Okay, this is gonna get ugly. Here's what you're encountering, as I just reproduced it on our core. Basically, when you build a query to look at the memory slots and the "installed size" of memory for each slot, you'll need to qualify a column for each slot that can possibly exist. Slots will be numbered starting with 0 to the total count of slots that are possible - 1. You'll need to add EACH individual slot as a "qualified" column, and you'll need to label each one slot + its number, so like Slot 0 through 7 for example, but you may need to go higher if you're working with servers that could have a lot more slots than 8 total. At any rate, this worked for me. I was only able to see only 2 memory slots before qualifying them all, and when you don't qualify a column that should be, you get duplicate line items per device in the results instead of just one line item, so its really best to qualify the columns just for the sake of making it look more logical. Once you get it started, it will go pretty smooth, and you'll be done before you know it, and when you run your query you'll end up with each slot column with either a 0 or the size of the ram module that is has in it. I was able to see all 4 modules in our core server that has a total of 8 slots after doing this.

           

          Hope that all made sense, or it might be easier to just use the attached exported query that i slapped together.

           

          Good luck either way!

          1 of 1 people found this helpful
          • 2. Re: Incorrect display of Physical Memory
            klevitan Specialist

            Very cool!   I'll have to remember this technique.

            - Kurt

            • 3. Re: Incorrect display of Physical Memory
              Catalysttgj Expert

              Yeah, I'm sure you're going to run into the same scenario again with something else.

               

              Could you mark this thread answered? Would much appreciate it! :-)

              • 4. Re: Incorrect display of Physical Memory
                Rookie

                Tomorrow I'm going to run your query

                After, I'll be sending the result.

                 

                Kind regards,

                Michel

                • 5. Re: Incorrect display of Physical Memory
                  Catalysttgj Expert

                  Cool. I hear ya on the excel bit. Excel is so 1980's, can we just move along already?! :-) At any rate, how crazy can you get with your DB? or rather, how crazy do you feel about coding an SQL query instead of using the LDMS query method. This would be an alternative, but it will be more work. In theory at least, you could write an SQL query to get all the same data out of the DB, and then sum up all the memory slot elements into one column instead of individual columns for each. Let me know if this might interest you, and i can look at it a bit, and maybe figure it out, but you'd have to go to the effort of learning how to attach the SQL query in a LANDesk report, or at least have good access to your DB to run the SQL query through it directly, if that's an option for ya.

                  • 6. Re: Incorrect display of Physical Memory
                    Rookie

                    Hi,

                     

                    I think I don't have enough rights, because I couldn't find where can I import your query to my Landesk.

                    Can you give me the directions?

                     

                     

                    Tks,

                    Michel

                    • 7. Re: Incorrect display of Physical Memory
                      Catalysttgj Expert

                      You should be able to just open up the folder in the console for queries in the upper left section of the console and then once you're in either the public or the my queries section, try right-clicking in there and you should see a choice for import. Should be that easy.

                      • 8. Re: Incorrect display of Physical Memory
                        Rookie

                        Nop! No access, I just can't send the script file to the LD server (Terminal server blocks copy/paste and no shared folder to put the file, so I think the only way is to manually create the script.

                         

                         

                        Best regards,

                        Michel

                        • 9. Re: Incorrect display of Physical Memory
                          Catalysttgj Expert

                          Well, if you can run a landesk console from a box that you have more access. This would be the simplest way to get the query imported.

                          • 10. Re: Incorrect display of Physical Memory
                            Catalysttgj Expert

                            I finally got around to putting together an SQL query that can get some interesting data on memory and slots. Check out this other thread where its discussed and posted: http://community.landesk.com/support/message/67802#67802

                             

                            This would require either directly accessing your DB, so this might not be of any use to you. There is a way to incorporate an SQL statement into a report as well, so you could maybe go that route if you're familiar with that process.

                             

                            Anyways, good luck!