Start filtering you'll need a way to tell Windows those shall we show objects that you want to keep
and which objects you want to remove from the pipeline.
You do this by specifying criteria for objects that you want to keep.
And most of the time you will do so by using one of the shelves comparison operators you will ask Lachelle
to compare some property of an object to somewhere else.
That is pretty fine.
And if the comparison is true the object is kept is if comparison is false.
The object is removed.
The basic comparison operator is includes the following.
Equal in two not equal to greater than less them less than or equal to and greater than or equal to
be aware of that first string comparisons.
This operators are all case insensitive men and they are not sensitive to case a case sensitive version
of each is available if it is necessary such as dash C.
You will be case sensitive version of equal to Q Or C D C and C not equal to.
Again case sensitive version.
This also contains the dash like operator and its case sensitive comparer companion does.
See like the dust like a barometer resembles dush IQ but supports the use of the question mark and asterisk
wildcard characters in string comparisons.
There are additional more advanced operators that will not be covered at this point.
This includes the following dash in and does contains newsman's just to see whether an object exists
in a collection and thus a test to see whether an object if a particular type and match and does C maj
compare a string to a regular expression literal also contains many operators that reverse the logic
of comparison such as does not like and does not mean comparisons can be made directly as a command
line performed.
For example turn does duty are greater than 1.
True so it will be true.
Hello in quotes is equal to hello in quotes.
All uppercase.
True but hello in quotes case sensitive equal to Hello all Borges is false.
This technique makes it easy to test comparison before you use them in a command.
Let's move on to basic filter and syntax live where the object command and it's early elsewhere has
two syntax forms.
Least two forms are created by having carefully designed parameter sets.
This enables an easy to read syntax for example to display a list of only running services Richert type
get service by their status.
There's Eik you run them.
So we are looking just for services which are our equal status in these basic syntax starts with the
areas where you could also specify the form common name where object followed by the property that you
want windows power shell to compare.
When you specify a comparison operator and the value that you want the shell to compare to every object
that has a specified well specified property will be capped.
If you misspell the property name or if you provide the name of a non-existent property then those partial
vision will not generate an error.
Instead your command drill will not generate any output for example.
Good service by where strt this EAC around him.
This command produces no output because no service object has a state property that contains the well
you're running.
Actually none of the service objects have stirred up their dough.
This is why the comparison returns FALSE For every object.
Please know that because of the complex parameters that's needed to make the basic syntax functional
the help file for where object is very long and difficult to read.
Consider steepen the initial syntax section and go directly to the description or examples.
If you need help with this command there are some limitations of the basic syntax.
The basic syntax can be used to resolve a single comparison.
You could not for example display a list of services that were stopped and had a start mode of murder
because that would require two comparisons.
The basic syntax cannot be used with complex expressions.
For example the name property of a service object in a string of characters windows partial shell uses
a system that stree an object to contain that string of characters and that system docstring object
has a lens property.
The foreign command will not Rocha's a basic filter and text get service by where named dot lands is
equal to 5.
The intent is to display all services that have a name longer than five characters.
However this command will never produce output as soon as you exceed the capabilities.
So the basic syntax you'll have to move to the advanced filtering syntax.