@VMware: When can we expect cmdlets for working with scheduled tasks and alarms?
We're not planning cmdlets to deal with alarms or scheduling tasks for this release. For now you can deal with these using the extensibility cmdlets (views and entity views.)
If you have any thoughts on how you might like to use alarms in particular, that would be helpful for us. Would you like to do something like launch a long-running powershell script that waits for alarms to come in and takes actions based on them, or would you prefer to use other tools to do things like that?
Not quite sure yet, just exploring at the moment. But I think a polling powershell app would be a waste of resources, it would be better I think to install powershell on your VC server, then have alarms trigger script executions.
What I had in mind when I mentioned both alarms and events was an idea I'm playing with to be able to recreate our team's VI for other departments. The idea would be to do the ESX installs, then VC, then run a powershell script that could queue off a bunch of tasks to create alarms and events that come from my team's best practices documentation. None of which exists yet so I'm thinking ahead a little bit. I imagine services shops could use such a model to automate a large VI.