Once you get used to Powershell, you will want to do more and more with it.\u00a0 One of the keys to leveraging the power of PowerShell is filters.
\nPowerShell commandlets all support filters (well, most of them anyway).\u00a0 This means you can drill down to resulting data subsets.
\nIf you run into commandlets that don\u2019t support the native -filter you can always pipe to where-object (aka \u201cwhere\u201d).<\/p>\n
In other words you can do this: get-service | Where {$_.Status -eq \u201cRunning\u201d}<\/em> You can also pipe the service name into the get-service commandlet: \u201cW32Time\u201d | get-service<\/em><\/p>\n Here\u2019s a great chart I found on the MSDN Blogs<\/a> that describes what each filter operator does:<\/p>\n Using filters is extremely helpful is narrowing down the scope to fine-tune the data you need to work with and this chart is one I frequently reference.<\/p>\n","protected":false},"excerpt":{"rendered":" Once you get used to Powershell, you will want to do more and more with it.\u00a0 One of the keys to leveraging the power of PowerShell is filters. PowerShell commandlets all support filters (well, most of them anyway).\u00a0 This means you can drill down to resulting data subsets. If you run into commandlets that don\u2019t … <\/p>\n
\nThis takes the results of a generic get-service request which returns a full list of system services and pares it down to only the running services.
\nChange \u201cRunning\u201d to \u201cStopped\u201d and you get, obviously a list of services that are stopped.<\/p>\n\n\n
\n Logical Operator<\/strong><\/td>\n Description<\/strong><\/td>\n Equivalent LDAP operator\/<\/strong>expression<\/strong><\/td>\n<\/tr>\n \n -eq<\/td>\n Equal to. This will not<\/strong> support wild card search.<\/td>\n =<\/td>\n<\/tr>\n \n -ne<\/td>\n Not equal to. This will not<\/strong> support wild card search.<\/td>\n ! x = y<\/td>\n<\/tr>\n \n -like<\/td>\n Similar to -eq and supports wildcard comparison. The only wildcard character supported is: *<\/strong><\/td>\n =<\/td>\n<\/tr>\n \n -notlike<\/td>\n Not like. Supports wild card comparison.<\/td>\n ! x = y<\/td>\n<\/tr>\n \n -approx<\/td>\n Approximately equal to<\/td>\n ~=<\/td>\n<\/tr>\n \n -le<\/td>\n Lexicographically less than or equal to<\/td>\n <=<\/td>\n<\/tr>\n \n -lt<\/td>\n Lexicographically less than<\/td>\n ! x >= y<\/td>\n<\/tr>\n \n -ge<\/td>\n Lexicographically greater than or equal to<\/td>\n >=<\/td>\n<\/tr>\n \n -gt<\/td>\n Lexicographically greater than<\/td>\n ! x <= y<\/td>\n<\/tr>\n \n -and<\/td>\n AND<\/td>\n &<\/td>\n<\/tr>\n \n -or<\/td>\n OR<\/td>\n |<\/td>\n<\/tr>\n \n -not<\/td>\n NOT<\/td>\n !<\/td>\n<\/tr>\n \n -bor<\/td>\n Bitwise OR<\/td>\n :1.2.840.113556.1.4.804:=<\/td>\n<\/tr>\n \n -band<\/td>\n Bitwise AND<\/td>\n :1.2.840.113556.1.4.803:=<\/td>\n<\/tr>\n \n -recursivematch<\/td>\n Uses LDAP_MATCHING_RULE_IN_CHAIN (Win2k3 SP2 and above)<\/td>\n :1.2.840.113556.1.4.1941:=<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n