There aren’t many occasions when you trip up in PowerShell because of something being case sensitive, it generally doesn’t happen since most things are typically not like that. I was working with the PowerCLI cmdlet Get-Task and in particular the ID parameter to do something like:
Get-Task -Id 'task-task-2035'
I had originally found the ID via:
Get-Task | Format-Table Name,ID -AutoSize
However, I received the error that no tasks of that ID were found :
Get-Task : 24/02/2015 20:51:57 Get-Task The identifier task-task-2035 resulted in no objects. At line:1 char:1 + Get-Task -Id task-task-2035 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (:) [Get-Task], VimException + FullyQualifiedErrorId : Client20_OutputTracker_ReportNotFoundLocators_LocatorNotProduced,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetTask
Turned out that making the task ID match the exact case worked:
Get-Task -Id 'Task-task-2035'
Apparently the IDs are case sensitive by design :-)
One to watch out for anyway…..