1 of 1 people found this helpful
This task is being called from the clients database (.db3) and is not being cleared after being run. You can rebuild that clientside .db3 file which will force it to re-sync with the core as to what policies are actively being broadcast from the core so it cleans up any rogue tasks that didn't clear properly. Here is the process we run to rebuild the .db3 file on the client. If you take this and copy it into a managed script under the [MACHINES_NT] section you can use sofware distribution to deliver the script to your clients and it will rebuild the .db3 or you can do these steps manually on a client to rebuild the .db3 file.
REMEXEC1=cmd /c del /f /q "%LDMS_CLIENT_DIR%\sdclient.tasks.xml"
REMEXEC2=cmd /c del /f /q "%LDMS_CLIENT_DIR%\..\Shared Files\cbaroot\alert\queue\internal*.xml"
REMEXEC3=cmd /c net stop "LANDesk Policy Invoker"
REMEXEC4=cmd /c del /f /q "c:\Documents and Settings\All Users\Application Data\LANDesk\ManagementSuite\Database\*.db3*"
REMEXEC5=cmd /c del /f /q "c:\programdata\LANDesk\ManagementSuite\*.db3*"
REMEXEC6=cmd /c "%LDMS_CLIENT_DIR%\clientdbutil.exe" /create
REMEXEC7=cmd /c net start "LANDesk Policy Invoker"