I am moderately new to EPO and ENS. Usually to perform an action on a PC or group of PCs, I select them, then run a client task such as installing new software or updating existing software. I've seen where you can assign a client task to a subgroup in the system tree. Say I assign a McAfee Agent task to update ENS components to 10.6.1.1103 and .1169. I take it the PCs in the group will check in with EPO periodically and eventually see that task. It will perform that task and be upgraded to the latest ENS components (in my example). Once a system has performed the client task in question, does the EPO server keep telling the machine to re-perform the task or does it somehow know not to run it since it's been completed already. I just am trying to avoid unnecessary network traffic and PC activity.
Thanks!
Solved! Go to Solution.
I would like to help you with your question. Understanding Client Tasks in ENS is pretty easy.
1. A client task can be assigned to an individual system or a group depending upon your requirement.
2. If a client task is assigned, you have the option to schedule it to run (Example, you can schedule the task to run daily, hourly, weekly, monthly etc).
3. If you are running the client task on a single machine you will also get the option to run immediately. (This will run only once).
4. In general, the update tasks run periodically like daily, hourly etc based on your assignment and schedule interval.
5. If an update task is scheduled to update ENS (Example 10.6.1.1103 to the next available patch level like1169), the task will update the ENS.
6. To answer your question, if the task runs for the next time and checks the product and the DAT level if they are not up to date, the task will run and update the patch level and DAT to the latest. If they are already up to date, nothing happens.
I would like you to go thru this article for better understanding:
Do reply in case of any further questions. If this information is helpful, please accept this as solution.
Regards,
I would like to help you with your question. Understanding Client Tasks in ENS is pretty easy.
1. A client task can be assigned to an individual system or a group depending upon your requirement.
2. If a client task is assigned, you have the option to schedule it to run (Example, you can schedule the task to run daily, hourly, weekly, monthly etc).
3. If you are running the client task on a single machine you will also get the option to run immediately. (This will run only once).
4. In general, the update tasks run periodically like daily, hourly etc based on your assignment and schedule interval.
5. If an update task is scheduled to update ENS (Example 10.6.1.1103 to the next available patch level like1169), the task will update the ENS.
6. To answer your question, if the task runs for the next time and checks the product and the DAT level if they are not up to date, the task will run and update the patch level and DAT to the latest. If they are already up to date, nothing happens.
I would like you to go thru this article for better understanding:
Do reply in case of any further questions. If this information is helpful, please accept this as solution.
Regards,
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: