Are scheduled tasks 'additive' only via policy? Can't seem to remove.

Discussion in 'Other ESET Home Products' started by JoeyJoeJoe, Mar 9, 2010.

Thread Status:
Not open for further replies.
  1. JoeyJoeJoe

    JoeyJoeJoe Registered Member

    Joined:
    Oct 22, 2009
    Posts:
    63
    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
     
  2. Brambb

    Brambb Registered Member

    Joined:
    Sep 25, 2006
    Posts:
    411
    Location:
    The Netherlands
    My guess is to open/download a clients configuration and take a look at the scheduled tasks?
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Scheduled tasks are unequivocally identified by their respective IDs. If your goal is to remove all custom scheduled tasks, this will be a few-clicks-away task with ERA4 and 4.2 clients.
     
  4. gmiest

    gmiest Registered Member

    Joined:
    Feb 2, 2010
    Posts:
    43
    This is great news!
     
  5. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    I'm not sure if this bug finally got fixed or not, but for a while if you were using the policy builder and set the flag to delete a task, it didn't actually set the flag correctly and you had to manually edit the xml file to add the flag in. That bug sucked.
     
  6. JoeyJoeJoe

    JoeyJoeJoe Registered Member

    Joined:
    Oct 22, 2009
    Posts:
    63
    Sticky, where would I edit the .xml to add the 'delete flag'?

    Would I then have to wait for the .xml to apply, then reapply my policy with the scheduled tasks I want?

    Thanks,
    JJJ
     
  7. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    Basically I have to make the policy that said to delete an entry, which builds the xml file in Server/cache/policy as some randomy characters.tmp. Then stop the RA service, manually look through the tmp files (xml, just with a different extension), find the exclusion that I wanted to delete and manually add in the delete flag, then restart services and apply the policy to specified computers. A very annoying work-around.
     
  8. Stealth111

    Stealth111 Registered Member

    Joined:
    May 6, 2009
    Posts:
    25
    OK, so for the million dollar question.... When will ERA4 be released?
     
Thread Status:
Not open for further replies.