13 Replies Latest reply on Jul 11, 2017 10:39 AM by carlos

    Custom Data: Registry Search

    carlos Expert

      LDMS 9.6 SP2

      CSA

       

      Hello trying to retrieve Some registry data from my clients, but I haven't been able to get the results under the inventory report, this is what I have done so far.

      1. Create the Custom Data definitions as described here: Custom Data Registry Scan Not Working: How To Pull Registry Information Using The Manage Software List

      2. After clicking the "Make Available to Clients" Button I ran an Inventory Scan on the client: LDISCN32.EXE /V /F

      3. Check the unknown Items as describe here: Custom Data is not Entered - Using the Unknown Items Inventory Tool

      (No Unknown Items were found)

       

      Nothing

       

      I can see the machine on my CSA and on my core just fine.

       

      Any help is appreciated.

      Best.

       

      These are the 3 Registry entries I'm trying to get:

        • 1. Re: Custom Data: Registry Search
          rdavidson SupportEmployee

          Try running another inventory scan. It often takes 2 full scans for the scanner to pick up newly added custom data.

           

          Also, I'd recommend using LDISCN32.EXE /V /F /SYNC as your command. Custom Data takes place as part of the hardware scan, and your command will only force a Software scan, not a Full Sync Scan.

          • 2. Re: Custom Data: Registry Search
            carlos Expert

            Replaced my command to "C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE" /V /F /SYNC

            Ran it twice, I also opened the Portal Manager and clicked the refresh button a few times, but I got the same results.

            This is what is listed on the inventory under Custom Data, Shouldn't I be seeing other default entries like Custom Data - Internet Explorer - Version as well?

             

             

            -CS

            • 3. Re: Custom Data: Registry Search
              rdavidson SupportEmployee

              Try checking for the ldappl3.ini file in both locations:

               

              C:\Program Files (x86)\LANDesk\LDClient\Data on the Client

               

              %ldms_home%ldlogon on the Core

               

              You can edit them and check for a Registry Info section, where you should see your registry key and specified inventory path.

               

               

              Also, use "C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE" /V /F /SYNC /O="test.scn" to write the scan file to C:\Program Files (x86)\LANDesk\LDClient\test.scn, and then open it to see if the scan has those entries.

               

              Below are the most likely scenarios and general next steps, based on that info:

               

              • If your ldappl3.ini on the client has the custom data entries, but the scan doesn't have those attributes, then that generally means the inventory scanner is failing to access the key.
                • Usually running a Procmon capture will identify the reason why. Often permissions.

               

              • If your ldappl3.ini on the client doesn't have the custom data entries, but the one on your core does, then the client isn't updating its ldappl3.ini, and may not even be configured to.
                • Check your agent config's Inventory Settings and ensure "auto update lappl3" is checked.
                • Check your agent's proxyhost.log under C:\Program Files (x86)\LANDesk\Shared Files to see what kind of error is returned calling LDDownloader, if any

               

              • If your ldappl3.ini on the core doesn't have the custom data entries, then the core has failed to rebuild the file.
                • Head to %ldms_home%ldlogon and delete all files with "ldappl3" in the name, except for ldappl3.template. Then hit "Make available to clients" again to rebuild the file.
              • 4. Re: Custom Data: Registry Search
                carlos Expert

                rdavidson

                I checked both ldappl3.ini files in the core and client, and both of them have the registry entries as follows:

                I ran this as well: "C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE" /V /F /SYNC /O="test.scn"

                NOTE: This only works (the log) if I run it via cmd (I was using a shortcut, that runs the scan but does not writes the log, even running it as admin)

                The registry entries seem to be found in the log:

                ...

                AMT Information - AMT SCS Information - Wireless Link Status = 0

                AMT Information - AMT SCS Information - Wireless MAC Address = 0

                Custom Data - Image - Image Time Stamp =Fri Jun 30 18:11:00 2017

                Custom Data - MDAC - Version =6.3.9600.16384

                Custom Data - Internet Explorer - Version =9.11.9600.18698

                Asset TAG =654321

                Custom Data: Customer ID =123456

                Customer Name =AzureCustomer01

                Scan Type =Delta

                Type =Virtual Server

                Device Name =NewCustomer01

                Network - TCPIP - Address =010.000.000.004

                Network - TCPIP - Subnet Mask =255.255.255.000

                Network - TCPIP - Subnet Broadcast Address =010.000.000.255

                ....

                 

                And the Proxyhost doesn't seem to have any errors either:

                 

                2017-07-11 14:57:26(2780-2940) proxyhost.exe:FIPS mode = 1

                2017-07-11 14:57:29(2780-2940) proxyhost.exe:Call UpdateCSAROIFile() with numberofDirectConnectSuccess = 0 numberofDirectConnectFailure = 1  csaName =  bSuccess = 1

                2017-07-11 14:57:29(2780-2940) proxyhost.exe:127.0.0.1:50251 Unable to start session with PS-Mycore-US:80 internal.proxyhost.directfailed sessionrc=3

                2017-07-11 14:57:29(2780-2940) proxyhost.exe:Made direct (non-proxy) connection to mycsa.com

                2017-07-11 14:57:29(2780-2940) proxyhost.exe:Call UpdateCSAROIFile() with numberofDirectConnectSuccess = 0 numberofDirectConnectFailure = 0  csaName = mycsa.com bSuccess = 1

                2017-07-11 14:57:29(2780-2940) proxyhost.exe:

                Connect to CSA successfully with host = mycsa.com and IP = 1xx.1xx.xx.xx1

                2017-07-11 14:57:29(2780-2940) proxyhost.exe:127.0.0.1:50251 Connection close 0 0 0 0

                2017-07-11 14:57:29(2780-2940) proxyhost.exe:127.0.0.1:50251 - - [11/Jul/2017:14:57:29 0000] "HEAD HTTP://PS-mycore-US/ldlogon/ldappl3.INI HTTP/1.1" 200 117 416

                2017-07-11 14:57:29(2780-2940) proxyhost.exe:127.0.0.1:50251 EOS on request

                2017-07-11 14:57:29(3080-2144) proxyhost.exe:FIPS mode = 1

                2017-07-11 14:57:31(3080-2144) proxyhost.exe:Call UpdateCSAROIFile() with numberofDirectConnectSuccess = 0 numberofDirectConnectFailure = 1  csaName =  bSuccess = 1

                2017-07-11 14:57:31(3080-2144) proxyhost.exe:127.0.0.1:50253 Unable to start session with PS-mycore-US:5007 internal.proxyhost.directfailed sessionrc=3

                2017-07-11 14:57:31(3080-2144) proxyhost.exe:Made direct (non-proxy) connection to mycsa.com

                2017-07-11 14:57:31(3080-2144) proxyhost.exe:Call UpdateCSAROIFile() with numberofDirectConnectSuccess = 0 numberofDirectConnectFailure = 0  csaName = mycsa.com bSuccess = 1

                2017-07-11 14:57:31(3080-2144) proxyhost.exe:

                Connect to CSA successfully with host = mycsa.com and IP = 1xx.1xx.xx.xx1

                2017-07-11 14:57:33(3080-2144) proxyhost.exe:127.0.0.1:50253 - - [11/Jul/2017:14:57:33 0000] "CONNECT PS-mycore-US:5007 HTTP/1.1" 0 47 282

                2017-07-11 14:57:50(3704-3792) proxyhost.exe:FIPS mode = 1

                2017-07-11 14:57:53(3704-3792) proxyhost.exe:Call UpdateCSAROIFile() with numberofDirectConnectSuccess = 0 numberofDirectConnectFailure = 1  csaName =  bSuccess = 1

                2017-07-11 14:57:53(3704-3792) proxyhost.exe:127.0.0.1:50255 Unable to start session with PS-mycore-US:5007 internal.proxyhost.directfailed sessionrc=3

                2017-07-11 14:57:53(3704-3792) proxyhost.exe:Made direct (non-proxy) connection to mycsa.com

                2017-07-11 14:57:53(3704-3792) proxyhost.exe:Call UpdateCSAROIFile() with numberofDirectConnectSuccess = 0 numberofDirectConnectFailure = 0  csaName = mycsa.com bSuccess = 1

                2017-07-11 14:57:53(3704-3792) proxyhost.exe:

                Connect to CSA successfully with host = mycsa.com and IP = 1xx.1xx.xx.xx1

                2017-07-11 14:57:54(3704-3792) proxyhost.exe:127.0.0.1:50255 - - [11/Jul/2017:14:57:54 0000] "CONNECT PS-mycore-US:5007 HTTP/1.1" 1 172443 282

                 

                My inventory settings seems correct as well:

                 

                 

                -CS

                • 5. Re: Custom Data: Registry Search
                  rdavidson SupportEmployee

                  With the scan containing that data, the issue is Core side at this point.

                   

                  Can you check the inventory of that device and look at the "Last updated by inventory server" value?

                   

                  Screenshot_96.png

                  • 6. Re: Custom Data: Registry Search
                    carlos Expert

                    This is at the core:

                    • 7. Re: Custom Data: Registry Search
                      rdavidson SupportEmployee

                      Are you seeing any errors in the event viewer on the Core around 8:55 AM? They'd be under Windows Logs > Application and be logged by the Landesk Inventory Server.

                      • 8. Re: Custom Data: Registry Search
                        carlos Expert

                        Nothing around that time:

                         

                        • 9. Re: Custom Data: Registry Search
                          amagi Expert

                          Hi Carlos, did you restart Inventory service?

                          1 of 1 people found this helpful
                          • 10. Re: Custom Data: Registry Search
                            rdavidson SupportEmployee

                            I just looked back and your custom data entry looks odd.

                             

                            The format is Attribute Name - Child Attribute

                             

                            Like Custom Data - Customer ID

                             

                            Your config isn't using that format. I took your scan contents and built a scan file with it, then enabled some extra logging and that attribute never gets looked at for custom data.

                             

                            I'd change the attribute to match the expected format, then make available again and re-run a few scans.

                             

                            You can also edit your scan file so the entries are as follows:

                             

                            Custom Data - Asset TAG =654321

                            Custom Data - Customer ID =123456

                            Custom Data - Customer Name =AzureCustomer01

                             

                            And then try re-processing that scan by dropping it into the %ldms_home%ldscan folder.

                             

                            With your current format you should see those attributes under Computer, similar to the Last Updated by Inventory Server attribute.

                            • 11. Re: Custom Data: Registry Search
                              carlos Expert

                              amagi yes I did restart the inventory server, then I ran the scan and checked again. same results:

                              • 12. Re: Custom Data: Registry Search
                                carlos Expert

                                rdavidson I'm a in a meeting now,  but I'll report back asap.

                                • 13. Re: Custom Data: Registry Search
                                  carlos Expert

                                  rdavidson I added "Custom Data - " to the beginning of the Attribute Name on 2 of the keys that had it missing, ran the scan and the tags showed up on the core.

                                  The documentation says Custom Data Registry Scan Not Working: How To Pull Registry Information Using The Manage Software List :

                                  "...This path can be named however you would like. We recommend keeping the attribute name Custom Data as the top of the tree just for organizational purposes..."

                                  But looks like the "Custom Data -" IS required.

                                  After running more tests, IF I remove the Custom Data the entry is not returned, if I add the Custom Data it is. This happens in any of the registry entries.

                                   

                                  Thank you for your help! (and amagi as well)

                                   

                                  SOLUTION: Include "Custom Data - " as part of the Name attribute in the registry Scan attribute.