This happened to me as well. It was caused by the Landesk Policy Invoker service not running. I don't know what caused it, but I started the service and the computer is fine now. I'll have to keep an eye on it to see if this is a bigger problem.
This is happening to me as well, but I am not finding a LANDesk Policy Invoker service in Server Manager. I am finding a LANDesk Policy Server service, though, but it appears to be running fine.
Ah, nevermind, the service is on the client, not the server. Is there any way to tell clients to start the LANDesk Policy Invoker service from the core?