Hello!
I am currently learning ePO 5.9.1 and i'm trying to come up with a way to recieve custom system properties from a remote client. Using Agent's custom properties to recieve system information seems like the best way, but i'm having trouble on figuring out how to send a script that recieves the last reboot info (of the client) and return it to for example custom property 1.
I'm also trying to solve this problem without the use of SIR. Any help would be appreciated.
Best Regards,
D.
Solved! Go to Solution.
simple to do with 2 ways
1. One powershell script that will read three informations into the registry and the system. (if we do it we will do it completely
- Last boot date
- Last installation date for an MS update
- Date of this last installation
the script will then use the agent 5.5 command line properties to populate the local agent custom properties.
use EEDK tool to import this script as a Mcafee package into EPO and launch it remotely on all your endpoints. Job is done as EPO will collect all informations and you'll be able to create reports on it.
2. easiest way. if you are in A.D. domain type. use the startpc script to launch the script. agent and ePO will follow. But in this case, as you'll want to optimize this script, also add a submodule into the script that will detect that the local agent is no more contacting the agent (check the agent last communication date into the registry, and also the epo that should be contacted.) and if not normal, the script will put a tag into EPO that will let you target it globally in a automated remediation process.
you can imagin almost anything based on this principle. Script + EEDK
I don't know of any way to get that info other than SIR. You might want to check on this forum since they assist sometimes with customized things like that, but I would not guarantee they can help.
https://community.mcafee.com/t5/McAfee-Open-Source/bd-p/mcafee-open-source
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
simple to do with 2 ways
1. One powershell script that will read three informations into the registry and the system. (if we do it we will do it completely
- Last boot date
- Last installation date for an MS update
- Date of this last installation
the script will then use the agent 5.5 command line properties to populate the local agent custom properties.
use EEDK tool to import this script as a Mcafee package into EPO and launch it remotely on all your endpoints. Job is done as EPO will collect all informations and you'll be able to create reports on it.
2. easiest way. if you are in A.D. domain type. use the startpc script to launch the script. agent and ePO will follow. But in this case, as you'll want to optimize this script, also add a submodule into the script that will detect that the local agent is no more contacting the agent (check the agent last communication date into the registry, and also the epo that should be contacted.) and if not normal, the script will put a tag into EPO that will let you target it globally in a automated remediation process.
you can imagin almost anything based on this principle. Script + EEDK
Will try this in my test lab, thx for sharing!
Never forget one thing. If you mixed scripts, API, EEDK tools and finally automatic response, you can automate quite a lot your epo management.
as an example you can use this in your script
.\maconfig.exe -custom -prop1 $variable1 -prop2 $variable2 ....-prop8 $variable8
feel free to PM me if more information needed but be aware that i'll be out of office starting the 20/07 until the 13/08
Best regards