Powershell quirks - have to use Guid instead of friendly identity names?
Posted on 2007-07-20
This may just be how powershell works and behaves, or maybe we have something wierd/wrong...
Is there a reason why we need to use the physical Guid on a lot of the PowerShell commands instead of using their friendly names?
For example if I want to get the permissions on a Storage Group with the Get-Adpermissions cmdlet, I need to first issue a get-storagegroups | fl to pluck out the Guid of my storage group. I then need to pass that guid into the Get-Adpermissions cmdlet instead of just using the identity listed..
Get-AdPermissions "ExchStore\Tier1 SG" -> returns ExchStore\Tier1 SG was not found.
Get-StorageGroup "Tier1 SG" | fl -property Guid -> Returns the guid string -> Copy to clipboard
Get-AdPermissions <paste Guid string> -> Returns expected results.
Why can I use the "Tier1 SG" on a get-storagegroup, but not on a Get-AdPermissions? I've run into this with a lot of the cmdlets for Exchange 2007 and it's been driving me batty.