4 Replies Latest reply on Dec 18, 2012 7:25 AM by darrenwilson

    Software Packages constantly being re-installed

    Rookie

      I have just installed LANDesk 9.0 SP3 and am experiencing big problems related to software packages re-installing themselves on the Windows 7 Clients, even though the end-client (and scheduled task status) reports as the tasks being completed successfully.

       

      The customer uses membership of AD security groups as targets for the software deployment policies.

       

      The idea being that you can just drop a device into the AD security group, and then the scheduler on the core server will resolve the AD query and populate the deployment policy with the relevant machine targets. (All pretty standard stuff)

       

      We have found that the only way we can get the AD queried and policy targets refreshed is by setting the scheduled task to repeat every hour. By default you have to set this to repeat on ‘All Devices’, rather than devices which did not succeed.

       

      This works fine, and whenever the AD group is altered, this is reflected in the Policy Targets.

       

      However, we have found that as soon as the scheduled task is re-started, the package is automatically re-deployed to ALL devices, regardless of whether they have reported back to the core server that they have successfully installed the package previously.

       

      This happens for both ‘Policy Push’ and ‘Policy Required’ delivery methods.

       

      So could this indicate a problem with the local LDClientDB.db3 file either not being populated correctly with the correct deployment status, or is the client itself ignoring the LDClientDB.db3 file and saying that it needs to re-install all packages?

       

      The only work around we have found is to set the scheduled task to Be advertised in the Software Deployment Portal , so the only way it is going to get re-installed is if the user selects it themselves.

      I have got a couple of calls open with Support regarding this , but was wondering if anyone else has come across this?

       

      The nearest thing I have found is this discussion , but we are not using uninstall association

      http://community.landesk.com/support/thread/20753?tstart=0

        • 1. Re: Software Packages constantly being re-installed
          MarXtar ITSMMVPGroup

          Do not set the task to be rescheduled, that is what is causing the re-installations. If you want an ongoing policy, then set it purely as a policy and target against the query. It should never need to be restarted unless you truly want to re-install.

           

          If you are finding that new machines that have never received the package do not get targeted, then log that specifically as a support issue. What you are trying to do to avoid this issue is causing a more serious issue.

           

          Mark McGinn

          MarXtar Ltd

          http://landesk.marxtar.co.uk

          LANDesk Silver ESP

           

          The One-Stop Shop for LANDesk Enhancements

          - Wake-On-WAN - Distributed Wake-On-LAN, Scheduled Power Down, and SWDist Sequencing

          - State Notifier - Real-Time Device & User State Inventory Updating & Alerting

          Update - WoW & State Notifier now integrate for even more functionality

          Update - State Notifier now detects machine and user Idle states

          • 2. Re: Software Packages constantly being re-installed
            Rookie

            Thanks Mark.

             

            So it looks like the issue is with the AD query resolver , rather than the db3 file ?

             

            Sort of makes sense as we can see that some of the job hashes are changed each time the task is re-ran , so that's why the packages are being re-deployed

             

            We believed that we should not have to re-start the scheudled task , and that once the initial AD query was assigned as the target , then we shouldn;t have to do anything apart from add devices into the AD groups.

             

            But we have found that the  only way we could get the scheduler to resolve the AD queries was by manually starting the task , and this forced an immediate refresh of the AD Targets.

            Which is why we considered  setting the task to re-start every hour , as this did start to resolve the AD queries.

             

            The schedldapresolver.exe.log isn;t really showing much in the way of errors , but there is a reference to the domian account used by the scheduler service  isn't in the console users table.

            12/09/2012 20:34:23 INFO  41872:1     RollingLog : Error: Unable to find user XXXXXXX in the ConsoleUser table.

             

            But we only got this once last week , and for the rest of the time it's showing:

             

            12/18/2012 13:08:35 WARN  45148:1     DataServices : Query <select LT.APM_POLICY_USERS_IDN, C.Computer_Idn from LD_LDAP_TARGETS LT, LDAPUserGroups C, APM_POLICY_USERS APU where (APU.APM_POLICY_USERS_IDN = LT.APM_POLICY_USERS_IDN) and (LT.LD_TASK_IDN = ?) and APU.USER_NAME = C.NAME and 0 = (SELECT COUNT(*) FROM LD_LDAP_TARGETS LDAP WHERE LDAP.LD_TASK_IDN = ? AND LDAP.APM_POLICY_USERS_IDN = APU.APM_POLICY_USERS_IDN AND LDAP.COMPUTER_IDN = C.COMPUTER_IDN) order by LT.APM_POLICY_USERS_IDN> took 4.5713274 seconds

            12/18/2012 13:08:35 WARN  45148:1     DataServices :    OleDBParm: 387

            12/18/2012 13:08:35 WARN  45148:1     DataServices :    OleDBParm: 387

            12/18/2012 13:08:44 INFO  45164:1     RollingLog : Resolving LDAP object for task 388

            12/18/2012 13:09:00 INFO  32660:1     RollingLog : Resolving LDAP object for task 540

            12/18/2012 13:09:13 INFO  36036:1     RollingLog : Resolving LDAP object for task 522

            12/18/2012 13:09:40 INFO  43296:1     RollingLog : Resolving LDAP object for task 392

            12/18/2012 13:09:45 INFO  41176:1     RollingLog : Resolving LDAP object for task 666

            12/18/2012 13:10:10 INFO  33960:1     RollingLog : Resolving LDAP object for task 533

             

             

            It never shows a completed message.

             

             

            But looking at the schedqry.log , I am seeing this:

            Tue, 18 Dec 2012 13:00:42 Failed to get group members for

            Tue, 18 Dec 2012 13:03:45 Failed to bind ADSI object in getting group members, returning (8007052E)

            Tue, 18 Dec 2012 13:03:45 Failed to bind ADSI object in getting group members, returning (80072030)

            Tue, 18 Dec 2012 13:03:45 Failed to bind ADSI object in getting query results, returning (8007052E)

            Tue, 18 Dec 2012 13:03:45 Failed to bind ADSI object in getting query results, returning (80072030)

             

             

            But when looking at the actual taks handler log for one of the deployment jobs , this is showing as successful:

            Tue, 18 Dec 2012 11:53:11 37948 27828 Task complete, status 12

            Tue, 18 Dec 2012 12:53:06 30468 29564 2 machines targeted to task

            Tue, 18 Dec 2012 12:53:11 30468 29564 Processing package

            Tue, 18 Dec 2012 12:53:11 30468 29564 Task complete, status 12

             

             

            Bit confused here, I have logged a couple of enginnering calls about this ,

            • 3. Re: Software Packages constantly being re-installed
              MarXtar ITSMMVPGroup

              Glad you've logged it; you should get some useful pointers.  I would suggest that you make sure that you have an account that can access AD with enough rights to resolve the memberships.  As a test, go into the console's Directory Manager and set the credentials to a domain admin temporarily. Always a good way to check whether rights are an issue and very safe since no other use is made of that account. The scheduler service account plays no part in resolving of LDAP groups, only the account set in Directory Manager.

               

              Mark McGinn

              MarXtar Ltd

              http://landesk.marxtar.co.uk

              LANDesk Silver ESP

               

              The One-Stop Shop for LANDesk Enhancements

              - Wake-On-WAN - Distributed Wake-On-LAN, Scheduled Power Down, and SWDist Sequencing

              - State Notifier - Real-Time Device & User State Inventory Updating & Alerting

              Update - WoW & State Notifier now integrate for even more functionality

              Update - State Notifier now detects machine and user Idle states

              • 4. Re: Software Packages constantly being re-installed
                Rookie

                Thanks Mark.

                 

                The acocunt is a domain admin one , but I'm going to change it to a different account anyway , as I do not like where this service account sits in their AD.

                 

                I'll wait and see what happens , and what engineering comes back with

                 

                Regards