Using comparison operators on parameters of Powershell cmdlets

Question

I'm trying to use the Get-BrokerDesktop cmdlet,

Like any other Powershell cmdlets I can pass it parameters to filter out the results to my needs. So, I could do something like,

Get-brokerdesktop  -RegistrationState Unregistered

Which would return an object that only has Unregistered as its RegistrationState.

How would I go about having the ones that are not Unregistered?

I tried,

Get-brokerdesktop  -RegistrationState -ne Unregistered

Which is invalid syntax.

scharette · Answer 1 · 2018-07-18T19:43:31.397

1

Actually, I just noticed an example at the bottom of the linked documentation...

The trick here is to use -Filter like so,

Get-BrokerDesktop -Filter { RegistrationState -ne 'Unregistered' }

Or even better in this case, as proposed by @TheIncorrigible1,

-Filter 'RegistrationState -ne "Unregistered"'

edited Jul 18 '18 at 19:43

answered Jul 18 '18 at 18:55

scharette

1

Do not use scriptblocks for filters unless the type of the parameter is a scriptblock.. It just gets converted to a string and can cause annoying bugs. – Maximilian Burszley Jul 18 '18 at 19:37
How can I alternatively run it then ? – scharette Jul 18 '18 at 19:38
`-Filter 'RegistrationState -ne "Unregistered"'` – Maximilian Burszley Jul 18 '18 at 19:39
1

Also: `This cmdlet is now deprecated, please use Get-BrokerMachine.` – Maximilian Burszley Jul 18 '18 at 19:39
1

@scharette: To add a little backstory: The misguided use of script blocks as `-Filter` arguments is as unfortunate as it is misguided, and cmdlet publishers using it in their own doc examples is even more so. If you want the details on why script blocks should be avoided: https://stackoverflow.com/a/44184818/45375 – mklement0 Jul 19 '18 at 01:04
1

@mklement0 Thank you for link really interesting, – scharette Jul 19 '18 at 01:19

1 Answers1