Exchange 2010 PowerShell: Cannot bind argument

Question

I'm trying to remove orphaned user objects from all mailboxes in our Exchange server.

When I execute this command:

get-mailboxpermission * | where {$_.User -like "S-1-5-21*"} | foreach {$_.Identity.Name}

It correctly returns a list with all the mailboxes that still have orphaned user account permissions set on them.

However, when I try to remove them by doing this:

get-mailboxpermission * | where {$_.User -like "S-1-5-21*"} | remove-mailboxpermission -identity $_.Identity.Name -user $_.User -accessrights $_.AccessRights -deny:$_.Deny

It returns this error:

Cannot bind argument to parameter 'Identity' because it is null.
+ CategoryInfo          : InvalidData: (:) [Remove-MailboxPermission], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Remove-MailboxPermission

What am I doing wrong?

Thanks for any help.

Mathias R. Jessen · Accepted Answer · 2015-11-17 16:17:37Z

3

$_ doesn't work like that, you need to wrap the Remove-MailboxPermission statement in ForEach-Object {}:

Get-MailboxPermission * | Where-Object {$_.User -like "S-1-5-21*"} | ForEach-Object {
  Remove-MailboxPermission -Identity $_.Identity.Name -User $_.User -AccessRights $_.AccessRights -Deny:$_.Deny
}

Since Exchange doesn't seem to like nested pipelines very much, you could simply to away with the parameter arguments altogether (Remove-MailboxPermission will automatically bind the permissions from the pipeline):

Get-MailboxPermission * | Where-Object {$_.User -like "S-1-5-21*"} | Remove-MailboxPermission

edited Nov 17, 2015 at 16:17

answered Nov 17, 2015 at 13:48

Mathias R. Jessen

178k13 gold badges175 silver badges234 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

mariu5 Over a year ago

I've already tried this and got the error Pipelines cannot be executed concurrently. Get-MailboxPermission and Remove-MailboxPermission are designed to take pipeline input from each other so there's no need to use ForEach. see this link

Mathias R. Jessen Over a year ago

@mariu5 My bad. Is there a reason you specify all those parameters with Remove-MailboxPermission? Get-MailboxPermission|Remove-MailboxPermission should suffice

mariu5 Over a year ago

That did the trick! I thought you would have to specify the exact permission in order to remove it but apparently, that isn't necessary. Thanks for your help. If you edit your answer, I could mark it as a solution if you like.

Collectives™ on Stack Overflow

Exchange 2010 PowerShell: Cannot bind argument

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related