... because you told the task to re-start every hour.
You're doing something that's rather pointless - You either do a scheduled task which restarts every hour OR you leave it per default and leave it as a push-once and let it turn into a policy for devices that were off at the time.
Or you do a policy / policy supported push and "leave it as is". There's not point to having it be a policy if you re-start it every hour (since it will start as a push).
What exactly are you trying to acheive - maybe let's start with that?
LANDesk EMEA Technical Lead
Thank you for your help.
But in our company, some software was not be deployed to every client at the first time. When the user need to install a softwre, he need to take a IT application vis a IT application tools, then I add the client hostname to the software task, if I don't start this task, the software isn't be deploy to the client, so I need to re-start the task every hour.
This isn't the way LANDesk is designed to work. If you really want to do this, don't set it to restart like this, instead, delete completed machines, add the new one, and then schedule the task again so that you don't re-target completed machines.
The way to do this properly is to set it as a policy, and since you are receiving a request anyway, add the machine and respond to the user asking them to now access the software deployment portal on their machine to install it whenever they are ready.
Mark Star - MarXtar LANDesk Enhancements
Home of Power State Notifier & Wake-On-WAN for LANDesk