We are in the process of moving from an old LANDesk Core Server (v8.6) to a new LANDesk Core Server (v8.7 SP3). This is not a migration of an old machine, but a new machine is installed along the old one.
We move the machines by deploying a LANDesk Agent from the new LD8.7 Core server. This works fine, but when it comes to the deploying of the software, all software is being redeployed. While most sofware does not really care of being redeployed, some software gets damaged. This is really a big pain for us.
We make use of Policy based pull distribution of software. LDAP Queries are being used to target machines and the software is being deployed using the AMCLIENT.EXE /APM command. We have chosen not to migrate the distribution packages and scheduled tasks from the old environment but to completely define new distribution packages and scheduled tasks. But although the definitions are new, why are MSI / SWD packages being redeployed? Why isn't there a check performed by LANDesk?
How can we prevent that MSI packages are being redeployed? The LANDesk distribution mechanism should be smart enough to detect if software is already installed before attempting to deploy software. We had the same problem when we moved from LD8.5 to LD8.6 a year earlier and we hoped it would be solved by now...