Check the services on some of the failed systems, is the LANDesk Policy Invoker Service running?
We are seeing a number of systems where it is not and when we restart it, it will fail out.
I have found that running this script (create a Manage Script) works in most cases:
REMEXEC2=<qt/>%LDMS_CLIENT_DIR%\LDISCN32.EXE<qt/> /NTT=%server%:5007 /S="%server%" /I=HTTP://%server%/ldlogon/ldappl3.ldz /NOUI /NOCD
REMEXEC4=<qt/>%LDMS_CLIENT_DIR%\LDISCN32.EXE<qt/> /NTT=%server%:5007 /S="%server%" /I=HTTP://%server%/ldlogon/ldappl3.ldz /F /SYNC /NOUI /NOCD
The first instance of the inventory scanner being called was added as cheating way to "wait" or pause for a bit as I found that the service would try to start too soon after registering the service in line one. The second instance is to update the inventory.
Create a query looking for the status of this service by looking under OS > Drivers and Services > Services, run this on systems where it is stopped
If you are using LD9 you can use the attached query to find affected systems
An update on this....
While this script helps in many cases, some of our Techs are saying they are finding the service is still stopping on many clients, even after the script has been run on it.
LANDesk has since released the "0428" patch for SD and the readme for it list this issue as fixed in it.