This content has been marked as final. Show 4 replies
But you WANT the inheritance to be broken
If you dont break the inheritance at that machine level (after it has inherited the task from top level first obv) then how can you enable the task at that point.....
I dont see the problem?
I'm obviously missing something fundamental here sad - this is the way (I guess) most folk use ePO - define most standard settting at the directory or site level and the create your sites and groups etc. - break the inheritance at the site level and then tailor each sites specific tasks and policy setting accordingly - everything created below the site level now has all the "customised" settings and tasks active as desired ?
That is true. Howerver, when I create the task at the parent level and say disable this. I then enable the task at the child level. So the inheritance will be broken, because we want this to be enabled at the child level. However, the task that is set to run, does not run, for example deploy the HIPS module, agent, or to remove a particular module.
So even though the inheritance is broken at the child level, the machines in that group, or individually are not getting the task, even after performing wake-up call. Task is set to run immediately.
sounds good to me. In my experience though ''Run Immediately'' is not as immediate as you think. Leave it for 10-15 minutes and see if the task as invoked on the client machine. Open thw EPO Agent status monitor to see if it kicks off (Right click on the epo agent icon taskbar and click status, or , run cmdagent.exe /show from the commandline (located in the Common Framework directory)