troubleshooting Question

Powershell quirks - have to use Guid instead of friendly identity names?

Avatar of qsnow
qsnow asked on
ExchangeWindows Server 2003
5 Comments1 Solution737 ViewsLast Modified:
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..

Example chain..

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.
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 5 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros