Start an Exchange 2007 and continuing to race through the subsequent exchange Roshan's address lists
dynamic distribution groups and email address boluses and global address lists can be customized with
recipient filters that you're there or pass filter and.
Lewis replaces the legacy elder filtering syntax that was used in our live versions of exchange.
We can also perform search site searches using filters which can greatly speed up our Virk and this
lesson you'll learn how to work with these filters and they change management shall we can filter the
results from the recipient.
Get this.
C'mon let's use the filter parameter.
For example get mailbox dust filter.
Office equals sales.
In addition we can to use attribute filters to create distribution groups email address policies and
address lists using the recipient filter parameter.
You could type the following command.
New Dynamic distribution group name distribution list account in recipient filter which will make the
following parameter.
Department accountant and recipient type user mailbox.
So in our first example you can see that you've used the get mailbox command to retrieve only the users
that have the office properties set to that.
Well your sales list is more efficient than performing the following command which would return the
same result.
Get mailbox pipe where object BSR makes Rose sales this command to use in the where object command let
use them.
The question mark LS to retrieve only the mailboxes with their office property set to sales.
We get back the same results but it's less efficient than our original example.
When filtering a where object every mailbox in the organization must be retrieved and evaluated before
any results are returned.
The benefit of the filter parameter with the get mailbox command left is that the filtering is done
on the server and not our client machines.
The filter method is pre-filter and Vergon in large environments.
There are a number of them and lots that support this parameter.
You can get an entire list with a simple one line or get the X command and pipe it to where object request
asking for parameters which are equal to filter.
This uses the shell function get the X command to retrieve a list of exchange management shell come
on lads that support the filter parameter.
If you are writing scripts or functions that need to carry a large number of recipients you'll want
to try to use server side filtering whenever possible.
Unfortunately there are only a certain set of properties that can be filtered for instance where we
are able to filter use of the office property can you the get mailbox command land based on that.
You may assume since organizational unit is a property of a mailbox object that you can filter that
as well but that is not the case.
The get mailbox command glad for why it's an organizational unit parameter that can be used to accomplish
that task.
So it's not always safe to assume that a particular robotic can be used within a filter.
So in our second example we use then you dynamic distribution group command left to create a square
root based group.
The membership of this group is determined to you than the Opas filter defiantly the recipient filter
parameter.
The syntax is similar around the same power show operators can be used based on the service used to
resolve or filter.
When we created the distribution list account group only mailboxes were they are department attributes
that to add content will be included all the recipient types such as Malcolm X and Moul users will not
be included in the group even though they may be in the account department dynamic distribution groups
or dress lists down to mail address policies can be configured to raise these filters again to get the
list of command letters that support this functionality.
Use get the X command shell variable you could type a command like this get a x command pipe it to where
object and the parameter is equal in recipient field to these command.
Let's also have a limited number of filter both properties that can be used instead of using the recipient
filter parameter.
You have the option of using Bricktown filters.
In some cases this may be easier as it allows you to simplify the process.
You can just use a set of parameters sound values as opposed to an open field or the following command
would create our distribution list counter in distribution list group or the same members in the pre-canned
filter parameters.
You could type the following command.
New Dynamic distribution group name.
DL underscore accountant included recipient's mailbox users and conditional Department accountant.
As you can see this is a little easier to read and probably easier to type into the shell.
However there are only a few recount parameters available and they may not be always used depending
on what you are type drying to do but it helps to be aware of this functionality you can to use.
Get help to view the entire list of available parameters for each come and let that supports the recipient
filters.
One of the issues you may run into one Gerken with a shell is the expansion of variables used within
a filter.
For example this syntax is completely wellat but will not currently work correctly.
The Exchange management shell you might get some results from this command but they will not probably
be what you are expecting.
This is because when running the get mailbox command let the will of the office where Abodh will not
be expanded prior to the command being performed through the remote shell.
What you end up with is instead either filter or check in for a new value in order to fix this.
You need to use syntax similar to the following.
This syntax will forth and variables scienter then the filter parameter to be expanded before Sanden
the command through the remote session and you should get back the correct results.