Forum Discussion
Exchange Online PowerShell - Invoke-Command with Select-Object inside scriptblock
Few points. First, Select-Object and select are two different things, because of the NoLanguage mode, as in - no aliases are allowed either. So you need to write it "properly":
# Invoke-Command -Session (Get-PSSession -id 19) { Get-Mailbox vasil | select PrimarySmtpAddress } The term 'select' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. + CategoryInfo : ObjectNotFound: (select:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException + PSComputerName : outlook.office365.com # Invoke-Command -Session (Get-PSSession -id 19) { Get-Mailbox vasil | Select-Object PrimarySmtpAddress } PrimarySmtpAddress PSComputerName RunspaceId ------------------ -------------- ---------- vasil@michev.info outlook.office365.com 58472f81-7f34-4e40-8ea7-486a0be474e7Next, Get-MailboxPermission in ExO returns the UPN of the user, which is "unique enough" and you can get the GUID by querying based on the UPN if needed. I'd agree the full object would be better. It does return the SID though:
# Invoke-Command -Session (Get-PSSession -id 19) { Get-MailboxPermission sharednew -User vasil | Select-Object -ExpandProperty User } -HideComputerName RunspaceId : 58472f81-7f34-4e40-8ea7-486a0be474e7 SecurityIdentifier : S-1-5-21-3675944716-2045640655-299186705-3762784 ReturnUrlTokenEncodedString : False RawIdentity : vasil@michev.infoYou can apply the same method to get the ObjectGUID for the Identity value.
The mailbox folder permission entries returning a full ADRecipient object is something I probed the PG few years back, never got a reply whether it's intentional of bug. Most of the time you can get enough properties via Invoke-Command though.
Removed / no longer relevant.
Last point. I'm not sure why but objects returned from Get-MailboxFolderPermission are different. The User property is more than just a string
( I think I can guess why on this one now: it might be because there are usually very many folder permissions, so exposing .ADRecipient is a smart move to avert further lookups.)
Get-MailboxFolderPermission <User>:\<Folder> | select @{n='TrusteeExchangeGuid';e={$_.User.ADRecipient.ExchangeGuid}}Removed comment - no longer relevant.
Few points. First, Select-Object and select are two different things, because of the NoLanguage mode, as in - no aliases are allowed either. So you need to write it "properly":
# Invoke-Command -Session (Get-PSSession -id 19) { Get-Mailbox vasil | select PrimarySmtpAddress } The term 'select' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. + CategoryInfo : ObjectNotFound: (select:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException + PSComputerName : outlook.office365.com # Invoke-Command -Session (Get-PSSession -id 19) { Get-Mailbox vasil | Select-Object PrimarySmtpAddress } PrimarySmtpAddress PSComputerName RunspaceId ------------------ -------------- ---------- vasil@michev.info outlook.office365.com 58472f81-7f34-4e40-8ea7-486a0be474e7Next, Get-MailboxPermission in ExO returns the UPN of the user, which is "unique enough" and you can get the GUID by querying based on the UPN if needed. I'd agree the full object would be better. It does return the SID though:
# Invoke-Command -Session (Get-PSSession -id 19) { Get-MailboxPermission sharednew -User vasil | Select-Object -ExpandProperty User } -HideComputerName RunspaceId : 58472f81-7f34-4e40-8ea7-486a0be474e7 SecurityIdentifier : S-1-5-21-3675944716-2045640655-299186705-3762784 ReturnUrlTokenEncodedString : False RawIdentity : vasil@michev.infoYou can apply the same method to get the ObjectGUID for the Identity value.
The mailbox folder permission entries returning a full ADRecipient object is something I probed the PG few years back, never got a reply whether it's intentional of bug. Most of the time you can get enough properties via Invoke-Command though.
- Thanks very much - I was stuck in my own way with that one!
To confirm about the user being returned as UPN. What happens when the trustee is a group?
I was / am hoping to avoid needing to do any further lookups by using those nested properties that would be included otherwise (e.g. with the snapin).
But I can do select-object and work with that! Im happy to have a solution on day 1 of my post.Well now, I'm back with a follow-on question. Having now used the proper cmdlet name Select-Object I notice I can't create custom properties.
Works in Exchange on-premises PS remoting:
>Invoke-Command -Session $exPSSession -ScriptBlock {Get-MailboxPermission Gray | Select-Object @{n='t';e={$_.User.SecurityIdentifier}}}But doesn't work in Exchange Online PS remoting:
>Invoke-Command -Session $exops -ScriptBlock {Get-MailboxPermission -Identity Ross | Select-Object -Property @{Name='MbxObjectGuid';Expression={$_.Identity.ObjectGuid}}}
The syntax is not supported by this runspace. This can occur if the runspace is in no-language
mode.
+ CategoryInfo : ParserError: (Get-MailboxPerm...ty.ObjectGuid}}:String) [], ParseExc
eption
+ FullyQualifiedErrorId : ScriptsNotAllowed
+ PSComputerName : outlook.office365.comVasilMichev do you know if this means I'd have to run Get-MailboxPermission multiple times in order to then do Select-Object -ExpandProperty against each property I'm trying to expand?