which Task type did you selected? (Policy-supported push, policy, push)
If you choose "policy-supported push" you have to start the task once. All offline machines will be as failed,
but if they are go in online mode, they check their policies and will start the installation automatically.
If you really want that the task runs every hour you have to change this also in "task settings - Frequency"
just a side note, we have a ticket open currently due to issues with tasks not being deployed due to the agent not being found, these devices are on and should be receiving the task. The task will do a discovery which uses UDP so make sure nothing is blocking that. Good luck cause so far we have not resolved this issue for us. Ill update if we do find a resolution though.
What i really want, is to distribute a package to some devices, knowing that the package will be installed on all the devices sooner or later. The failed devices needs to retry again and again until the package is successful.
Right now, we have to push "start now:>Devices that did not succeed" over and over again until all is successful which is a solution that aren't working for us at all.
If you have the solotion to our problem, it would be nice if you could tell me the step by step clicks for making it work.
We only use push to stop our IT-ers from manual installation. For deployment with a big number of devices we use policy based distribution as computers won't fail when turned off.
If you have the task set as policy-push then the push will run but fail for those offline, when those check in on their policy sync they should get the task policy, I don't think you even need to set it to reschedule but you could to be sure. You could also set a task to do a policy sync and repeat that task every hour, this is under manage scripts, basically you would run a task to tell the agent to check in for a policy, its supposed to run a little different than normal push task. For my issue I was on with support yesterday and found that a bunch of my agents appear to be broken. You may want to check this in your environment as well.
We are distributing packages to remote sites very often and there cannot know if the devices are online or offline, so we need to be 100% sure that the package gets installed.
Frequency: Run once
Repeat every Hour
Devices that did not succeed
Will these options guarantee packages keep trying to install until they are successful?
Yes, policy-push will ensure those not online will get the task as a policy when they check in. The other thing we do is use the "policy sync" script, and schedule that as task on a repeated schedule as well. target the same group of machine. If you go to distribution, manage scripts, look in the all scripts list for "policy sync", schedule that one as well, it basically goes out finds the devices and tells them to check for new policies. This is good if the device is online but for some reason will not accept a push task. We have had a lot of broken agents lately though so you need to be sure this is causing a problem as well.
i thought it was built in but maybe we added it, the script just contains this, you can create a new custom script and add this line under the [Machines] header
[MACHINES] (this is the header this line needs to go under)
REMEXEC100=cmd /c "%LDMS_CLIENT_DIR%\PolicySync.exe"
I'm working on a Change Request for activating Policy Sync at login. I guess that should solve the problem?
I will return when I have some feedback