It sounds like the components for the policy are working both on the core and on the client. When you open the deployment portal it makes a call to policy.sync.exe which will contact the core and request policies. Local Scheduler is responsible for calling polciy.sync.exe on the client. By default this occurs once per day, but can be configured to occur more or less frequently based on company needs. To see if local scheduler is running and if its calling policy.sync.exe you can check your localsch.log. You should see some entries like this:
Sun, 07 Jun 2009 09:41:56 Starting process: C:\Program Files\LANDesk\LDCLient\policy.sync.exe
Sun, 07 Jun 2009 09:41:56 launched "C:\Program Files\LANDesk\LDCLient\policy.sync.exe "
If you are not seeing these then you need to look and see if something happened to the localsch tasks. You can see what tasks a machine has by looking in the inventory or from the client machine open up a command window and typing:
"C:\Program Files\LANDesk\LDclient\localsch.exe" /tasks | more
What you are looking for is something like this:
1: C:\Program Files\LANDesk\LDClient\policy.sync.exe
handle : 600
start : Thu Jun 25 07:54:13 2009
frequency : 86400
Filter 1 : [Auto delay] State=(Not ready) Min=(0) Max=(60)
NOTE: Frequency=86400 seconds (1day)
If you have made a job a required policy than it will install as soon as policy.sync runs on the system. The interval is configured in the agent under the software distribution section. I would check the machine to make sure that the local scheduler is still kicking off policy.sync on an interval.
This can be done by running the following from the ldclient dir from a command prompt:
localsch.exe \tasks |more
look for a task that is kicking off policy.sysn.exe
Hi There I reinstalled agents and all works fine now. The issues i have is that the task in the tasks window stays in pending even when the software as installed correctly.
I have test other activities and the statsu is working fine its just of software distribution.