So during provisioning I install a landesk agent; I've verified that the agent gets installed and everything seems fine as far as that goes. However I have a problem after provisioning whereby that agent gets removed from the system or otherwised messed up due to a conflict with a group policy agent install. I need help resolving the conflict.
Again, the provisioning process installs a working agent. If I keep a newly provisioned computer in an active directory container which doesn't see group policy then it continues to work as normal. As soon as it updates with group policy it loses its agent. The files for LDClient are still there but the agent doesn't run and I can't manage the device from the LDMS console.
My group policy says to push the Advance Agent MSI package down to any machine which doesn't have it. The thought is that I want to capture all of my machines because not all have been provisioned by landesk yet, and I want to make sure that all of them have the most recent agent settings.
Previously I feel that there was no conflict with this scenario, however something as recent as the past 6 weeks has changed things and now this conflict exists on any machine provisioned during this period.
Any ideas on where I should begin to resolve this conflict?