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