JoeyJoeJoe
March 9th, 2010, 09:03 AM
I had removed scheduled tasks from the policy applied to our servers without ‘marking for deletion’. I assumed if you removed it, that removal will apply to all clients who have that policy. ESET doesn’t have the most intuitive way to manage scheduled tasks via policy. Thanks for nothin', guys.
Policies for scheduled tasks appear to be additive only. That is if you remove a task from a policy and apply that policy to an ESET client, that task won’t be removed. Turns out you need to click ‘Mark for deletion’ to actually delete them from the clients.
I think I have a workaround for it though. I’m going to add a task with the same unique ID number to a policy, choose ‘Mark for deletion’ and see if that will trigger removal of the scheduled task.
How do I find the ID for the tasks on the client machines?
Thanks,
JJJ
Policies for scheduled tasks appear to be additive only. That is if you remove a task from a policy and apply that policy to an ESET client, that task won’t be removed. Turns out you need to click ‘Mark for deletion’ to actually delete them from the clients.
I think I have a workaround for it though. I’m going to add a task with the same unique ID number to a policy, choose ‘Mark for deletion’ and see if that will trigger removal of the scheduled task.
How do I find the ID for the tasks on the client machines?
Thanks,
JJJ