During agent-server communication, the agent sends events and properties to the server. It also retrieves policy changes and enforces the policies locally. Updates are done through tasks, not through the agent-server communication.
yes but it also checks for updates in master repository. but for Patch upgrade you should create a task
I think they may be missing a trick here, if the agent-server communication finds a new update say in the case of a new virus or 0 day notice, it would make sense for it to trigger an update to ensure the client is protected against the new threat. Am just wondering what the best thing to do if this happenend. Would it be a good idea to have a task for such situations that does a product update to all pc's and 'runs immediately', then simply do a wake up agent?
Wondering what other peoples views are on reacting to a new outbreak as quick as possible.
Hope you can help.
Many Thanks in advance.
Updates are done through tasks, not by agent-server communication alone. Agent to server communication is an exchange of events, policies and tasks.
We don't check for updates in the master repository directly during agent-server communication but task changes will be passed down from the ePO server. So if you've checked in a new dat, you kick off an update task and all selected machines will recieve and execute it on their next communication and according to the task schedule.
If you're feeling brave or the need is urgent, you'll use a global update task to do it all in one sweep.
oops you are right you should create product update task,