Could you specify which version of LANDesk you use and your patch level?
It's possible that I've got another sighting of this in Europe ... not sure (hence the request for the info) ... certainly if there's 2 sightings of this then this would make it more likely that there's a genuine defect.
Have you any idea about "when" this happens most likely? I.e. - if the Core / Database-server is under particular strain, is it more likely to happen? Does it also happen during "quiet" periods I/O wise (so not necessarily a performance / bottleneck problem)?
Any regularities that have been observed would help...
- Paul Hoffmann
LANDesk EMEA Technical Lead
LDMS 184.108.40.206 SP3
There isn't any time that this really happens most likely. I set it up yesterday and our server was not under any unusual load. Today I have see three systems that started to get the policy a second time since the original policy distribution hasn't reported back as successfully completed.
LDMS 9 SP1. Machines stuck in active status, but do have the software installed. Usually happens when more then one policy is queued up to the machine.