Months ago I started writing a Powershell Module for the ePO Web API, named "ePOwerShell". My goal was to implement the few CMDLets I had in mind, but unfortunately I was not able to finish the code and publish the module. Today I dug up the source code and I'm thinking of continuing the project. I use Powershell alost daily and I use this module to apply tags to systems I get from our asset database. It's still in pre-alpha stage, but if the community is interested I might consider publishing it.
The few CMDLets I have implemented:
Connect to the McAfee ePO server and cache the connection object for later use.
Find systems in the ePO tree by name, IP address, MAC address, user name, agent GUID or tag. This Cmdlet impleme the "system.find" web api call.
Get tags available in ePO or tags assigned to system. This Cmdlet implements the "system.findTag" web api call.
Apply one or more tags to a system. This Cmdlet implements the "system.applyTag" web api call.
Clear one or more tags from a system. This Cmdlet implements the "system.clearTag" web api call.
Get all available queries from ePO. This Cmdlet implements the "core.listQueries" web api call.
Execute an ePO query. This Cmdlet implements the "core.executeQuery" web api call.
And this is what it looks like in Powershell:
The following CMDLets were/are on the list to be implemented:
- New-EpoUser (accept input from Get-ADUser)
- Update-EpoUser (accept input from Get-EpoPermissionSet)
What I want to know from the community is:
- Would you be interested in such a module?
- What functions are missing?
- What functions would be "nice to have"?
All feedback is appreciated!
Message was edited by: mischaboender on 8/25/12 3:55:36 PM CDT