10 Replies Latest reply: Aug 8, 2011 2:30 AM by Dataspike RSS

    Client Does not update the ldappl3.ini though changes are made available to clients

    Specialist

      I have several clients that aren't updating the ldappl3.ini file.

       

      I've deleted all of the ldappl3 files (minus .template) file and recreated them on the core.

       

      Checked the ldapplpcgi.sig and ldapplpcgi.exe files (http://community.landesk.com/support/docs/DOC-6320), they have the same date, just are 13hrs apart.

       

      Aside from reinstall, I am not sure what I can do.

       

      Anyone have any suggestions?

        • 1. Re: Client Does not update the ldappl3.ini though changes are made available to clients
          LANDeskWizrd SSMMVPGroup

          Looks like the issue here is going to be the time difference between ldapplpcgi.sig and ldapplpcgi.exe. According to that document they both have to be the same. Of course the patch mentioned on the doc is old but maybe support can provide you with the set of files that have matching dates. Do you have another core or dev core that you can copy them from?

          • 2. Re: Client Does not update the ldappl3.ini though changes are made available to clients
            LANDeskWizrd SSMMVPGroup

            I attached the files from my core in case you want to test and see if that fixes it for you.

            • 3. Re: Client Does not update the ldappl3.ini though changes are made available to clients
              mrspike SSMMVPGroup

              We have come across some of these systems that refuse to update, and in most cases if you delete the files (ldappl3*.*) in the ldclient\data folder and call an full inventory scan, they will usually download the new files.

               

               

              We created a batch file that we can push out to these using a Custom Def.

               

               

              Here is the code we use, change "yourcore" to the name of your core

               

               

              @ECHO OFF
              del "%LDMS_LOCAL_DIR%\ldappl3.*"
              "%LDMS_LOCAL_DIR%\..\LDISCN32.EXE" /NTT=yourcore:5007 /S=yourcore /I=HTTP://yourcore/ldlogon/ldappl3.ldz /F /SYNC /NOUI

               

               

              Here is the detection we use in our custom def.  You need to choose a date that is one day older than what yours is actually dated.

               

              ldapp.JPG

              • 4. Re: Client Does not update the ldappl3.ini though changes are made available to clients
                Specialist

                LANDeskWizrd wrote:

                 

                I attached the files from my core in case you want to test and see if that fixes it for you.

                Thanks... but looks like you are using LD9, I'm stuck on 8.8 still.

                • 5. Re: Client Does not update the ldappl3.ini though changes are made available to clients
                  Specialist

                  James Marriott wrote:

                   

                  We have come across some of these systems that refuse to update, and in most cases if you delete the files (ldappl3*.*) in the ldclient\data folder and call an full inventory scan, they will usually download the new files.

                   

                   

                  We created a batch file that we can push out to these using a Custom Def.

                   

                   

                  Here is the code we use, change "yourcore" to the name of your core

                   

                   

                  @ECHO OFF
                  del "%LDMS_LOCAL_DIR%\ldappl3.*"
                  "%LDMS_LOCAL_DIR%\..\LDISCN32.EXE" /NTT=yourcore:5007 /S=yourcore /I=HTTP://yourcore/ldlogon/ldappl3.ldz /F /SYNC /NOUI

                   

                   

                  Here is the detection we use in our custom def.  You need to choose a date that is one day older than what yours is actually dated.

                   

                  ldapp.JPG

                  Thanks... I can try that too.

                   

                  I guess I'd like to see the two file date/times become sync'd, but the document referes to an old patch that SP4 should've included; right?

                  • 6. Re: Client Does not update the ldappl3.ini though changes are made available to clients
                    LANDeskWizrd SSMMVPGroup

                    Ouch 8.8 lol. Yeah my files won't work unfortunately. You may have to get them from support unless someone with 8.8 can post them here.

                    • 7. Re: Client Does not update the ldappl3.ini though changes are made available to clients
                      Specialist

                      James,

                       

                      Took your suggestion and went a step further...

                       

                      Created a CD as suggested, however just tweaked it a little.  I just included a script to delete the files, rather than having to worry about downloading a patch, just in case there are some other issues.

                       

                      7-14-2011 3-37-50 PM.jpg

                       

                      7-14-2011 3-38-37 PM.jpg

                       

                      7-14-2011 3-39-30 PM.jpg

                       

                      And here's the script.  It detects both 32bit and 64bit, and will only delete the files that contain "ldappl3" in the file name.

                      Const HKEY_CLASSES_ROOT   = &H80000000
                      Const HKEY_CURRENT_USER   = &H80000001
                      Const HKEY_LOCAL_MACHINE  = &H80000002
                      Const HKEY_USERS          = &H80000003

                       

                      strComputer = "."
                      Set oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & "\root\default:StdRegProv")
                      Set objProcessor = GetObject("winmgmts:\\.\root\cimv2:Win32_Processor='cpu0'")
                      Set wshShell = CreateObject("WScript.Shell")
                      strKeyPath = "Software\LANDesk\ManagementSuite\WinClient"
                      strValueName = "Path"
                      If (objProcessor.AddressWidth = "64") Then
                         strKeyPath = "Software\Wow6432Node\LANDesk\ManagementSuite\WinClient"
                      End If

                       

                      oReg.GetStringValue HKEY_LOCAL_Machine, strKeyPath, strValueName, strLDPath
                      strInvCmd = """" & strLDPath & "\LDISCN32.EXE" & """" & " /NTT=<Core Server>:5007 /S=<Core Server> /I=HTTP://<Core Server>/ldlogon/ldappl3.ldz /F /SYNC /NOUI"

                       

                      Set fso = CreateObject("Scripting.FileSystemObject")
                      Set oFolder =  fso.GetFolder(strLDPath & "\Data")
                      For Each oFile In oFolder.Files
                      If InStr(oFile.Name, "LDAPPL3") Then
                        oFile.Delete True
                      End If
                      Next

                       

                      ReturnCode = wshShell.Run(strInvCmd)

                       

                      * Don't forget to change the <Core Server> to the name of your LD Core.

                      • 9. Re: Client Does not update the ldappl3.ini though changes are made available to clients
                        axaly Rookie

                        Hi,

                         

                        Thanks for this script !

                        But one question :

                        Why the deleting function is after the LDISCN32.exe which download the good LDAPPL3 files ?

                         

                        Download files:

                        strInvCmd = """" & strLDPath & "\LDISCN32.EXE" & """" & " /NTT=<Core Server>:5007 /S=<Core Server> /I=HTTP://<Core Server>/ldlogon/ldappl3.ldz /F /SYNC /NOUI"

                         

                        Delete Files:

                        For Each oFile In oFolder.Files
                        If InStr(oFile.Name, "LDAPPL3") Then
                          oFile.Delete True
                        End If
                        Next

                         

                        Regards,

                        Alex

                        • 10. Re: Client Does not update the ldappl3.ini though changes are made available to clients
                          Specialist

                          The "strInvCmd" variable is just declared before the command to delete.  I guess "proper" coding would put it next to the command "ReturnCode = wshShell.Run(strInvCmd)" where the actual inventory scan command is called.

                          Something like this....

                           

                          Const HKEY_CLASSES_ROOT = &H80000000
                          Const HKEY_CURRENT_USER = &H80000001
                          Const HKEY_LOCAL_MACHINE = &H80000002
                          Const HKEY_USERS = &H80000003

                           

                          strComputer = "."
                          Set oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & "\root\default:StdRegProv")
                          Set objProcessor = GetObject("winmgmts:\\.\root\cimv2:Win32_Processor='cpu0'")
                          Set wshShell = CreateObject("WScript.Shell")
                          strKeyPath = "Software\LANDesk\ManagementSuite\WinClient"
                          strValueName = "Path"
                          If (objProcessor.AddressWidth = "64") Then    
                          strKeyPath = "Software\Wow6432Node\LANDesk\ManagementSuite\WinClient"
                          End If

                           

                          Set fso = CreateObject("Scripting.FileSystemObject")
                          Set oFolder = fso.GetFolder(strLDPath & "\Data")
                          For Each oFile In oFolder.Files
                          If InStr(oFile.Name, "LDAPPL3") Then    
                            oFile.Delete True
                          End If
                          Next

                           

                          oReg.GetStringValue HKEY_LOCAL_Machine, strKeyPath, strValueName, strLDPath
                          strInvCmd = """" & strLDPath & "\LDISCN32.EXE" & """" & " /NTT=<Core Server>:5007 /S=<Core Server> /I=HTTP://<Core Server>/ldlogon/ldappl3.ldz /F /SYNC /NOUI"

                          ReturnCode = wshShell.Run(strInvCmd)