Post navigation

2 comments

Thank you but we had to remove the UMCallRouterSettings manually. The script did not work at this point with Exchange 2016 lates CU. Everything else worked. Thank you.

The input object cannot be bound to any parameters for the command either because the command does not take pipeline input or the input and its properties do not match any of the parameters that take pipeline input.
+ CategoryInfo : InvalidArgument: (XXX\UMCallRouterSettings:PSObject) [Set-UMCallRouterSettings], ParameterBindingException
+ FullyQualifiedErrorId : InputObjectNotBound,Set-UMCallRouterSettings
+ PSComputerName : XXX.XXX

I’m interested to know how the output of this command looked like if you still had that info:
Get-UMService | Get-UMCallRouterSettings | where {$_.DialPlans -contains $UMDialPlan} | FL Identity, DialPLans