WEBVTT 00:04.430 --> 00:13.100 Start an Exchange 2007 and continuing to race through the subsequent exchange Roshan's address lists 00:13.310 --> 00:21.430 dynamic distribution groups and email address boluses and global address lists can be customized with 00:21.460 --> 00:26.620 recipient filters that you're there or pass filter and. 00:26.780 --> 00:35.150 Lewis replaces the legacy elder filtering syntax that was used in our live versions of exchange. 00:35.150 --> 00:43.850 We can also perform search site searches using filters which can greatly speed up our Virk and this 00:43.850 --> 00:51.440 lesson you'll learn how to work with these filters and they change management shall we can filter the 00:51.440 --> 00:54.030 results from the recipient. 00:54.370 --> 00:55.700 Get this. 00:55.790 --> 00:59.100 C'mon let's use the filter parameter. 00:59.180 --> 01:03.300 For example get mailbox dust filter. 01:03.320 --> 01:05.450 Office equals sales. 01:05.450 --> 01:13.850 In addition we can to use attribute filters to create distribution groups email address policies and 01:13.940 --> 01:18.790 address lists using the recipient filter parameter. 01:18.830 --> 01:20.770 You could type the following command. 01:20.780 --> 01:28.850 New Dynamic distribution group name distribution list account in recipient filter which will make the 01:28.850 --> 01:30.860 following parameter. 01:30.950 --> 01:35.660 Department accountant and recipient type user mailbox. 01:35.690 --> 01:44.840 So in our first example you can see that you've used the get mailbox command to retrieve only the users 01:45.200 --> 01:48.570 that have the office properties set to that. 01:48.620 --> 01:55.550 Well your sales list is more efficient than performing the following command which would return the 01:55.550 --> 01:56.680 same result. 01:56.810 --> 02:05.680 Get mailbox pipe where object BSR makes Rose sales this command to use in the where object command let 02:05.910 --> 02:06.380 use them. 02:06.410 --> 02:14.750 The question mark LS to retrieve only the mailboxes with their office property set to sales. 02:14.750 --> 02:20.830 We get back the same results but it's less efficient than our original example. 02:20.960 --> 02:29.510 When filtering a where object every mailbox in the organization must be retrieved and evaluated before 02:29.750 --> 02:32.060 any results are returned. 02:32.090 --> 02:39.680 The benefit of the filter parameter with the get mailbox command left is that the filtering is done 02:39.680 --> 02:43.940 on the server and not our client machines. 02:43.970 --> 02:48.950 The filter method is pre-filter and Vergon in large environments. 02:48.950 --> 02:53.320 There are a number of them and lots that support this parameter. 02:53.330 --> 03:02.390 You can get an entire list with a simple one line or get the X command and pipe it to where object request 03:02.630 --> 03:06.600 asking for parameters which are equal to filter. 03:06.620 --> 03:14.090 This uses the shell function get the X command to retrieve a list of exchange management shell come 03:14.090 --> 03:17.700 on lads that support the filter parameter. 03:17.840 --> 03:24.980 If you are writing scripts or functions that need to carry a large number of recipients you'll want 03:24.980 --> 03:29.870 to try to use server side filtering whenever possible. 03:29.870 --> 03:37.160 Unfortunately there are only a certain set of properties that can be filtered for instance where we 03:37.160 --> 03:45.130 are able to filter use of the office property can you the get mailbox command land based on that. 03:45.140 --> 03:53.000 You may assume since organizational unit is a property of a mailbox object that you can filter that 03:53.060 --> 03:57.320 as well but that is not the case. 03:57.350 --> 04:04.760 The get mailbox command glad for why it's an organizational unit parameter that can be used to accomplish 04:04.820 --> 04:05.890 that task. 04:05.940 --> 04:13.280 So it's not always safe to assume that a particular robotic can be used within a filter. 04:13.370 --> 04:21.130 So in our second example we use then you dynamic distribution group command left to create a square 04:21.140 --> 04:22.460 root based group. 04:22.510 --> 04:30.920 The membership of this group is determined to you than the Opas filter defiantly the recipient filter 04:30.920 --> 04:32.010 parameter. 04:32.060 --> 04:39.760 The syntax is similar around the same power show operators can be used based on the service used to 04:39.760 --> 04:41.230 resolve or filter. 04:41.330 --> 04:49.090 When we created the distribution list account group only mailboxes were they are department attributes 04:49.090 --> 04:58.340 that to add content will be included all the recipient types such as Malcolm X and Moul users will not 04:58.340 --> 05:06.960 be included in the group even though they may be in the account department dynamic distribution groups 05:06.960 --> 05:14.430 or dress lists down to mail address policies can be configured to raise these filters again to get the 05:14.430 --> 05:18.170 list of command letters that support this functionality. 05:18.210 --> 05:27.200 Use get the X command shell variable you could type a command like this get a x command pipe it to where 05:27.300 --> 05:33.060 object and the parameter is equal in recipient field to these command. 05:33.060 --> 05:41.580 Let's also have a limited number of filter both properties that can be used instead of using the recipient 05:41.580 --> 05:43.030 filter parameter. 05:43.080 --> 05:47.220 You have the option of using Bricktown filters. 05:47.310 --> 05:54.880 In some cases this may be easier as it allows you to simplify the process. 05:54.900 --> 06:02.170 You can just use a set of parameters sound values as opposed to an open field or the following command 06:02.220 --> 06:10.610 would create our distribution list counter in distribution list group or the same members in the pre-canned 06:10.620 --> 06:12.330 filter parameters. 06:12.330 --> 06:14.290 You could type the following command. 06:14.430 --> 06:17.490 New Dynamic distribution group name. 06:17.490 --> 06:27.540 DL underscore accountant included recipient's mailbox users and conditional Department accountant. 06:27.600 --> 06:34.100 As you can see this is a little easier to read and probably easier to type into the shell. 06:34.100 --> 06:42.990 However there are only a few recount parameters available and they may not be always used depending 06:42.990 --> 06:50.370 on what you are type drying to do but it helps to be aware of this functionality you can to use. 06:50.370 --> 06:58.200 Get help to view the entire list of available parameters for each come and let that supports the recipient 06:58.200 --> 06:59.110 filters. 06:59.160 --> 07:07.620 One of the issues you may run into one Gerken with a shell is the expansion of variables used within 07:07.620 --> 07:08.470 a filter. 07:08.550 --> 07:14.980 For example this syntax is completely wellat but will not currently work correctly. 07:14.990 --> 07:22.140 The Exchange management shell you might get some results from this command but they will not probably 07:22.470 --> 07:24.510 be what you are expecting. 07:24.510 --> 07:31.500 This is because when running the get mailbox command let the will of the office where Abodh will not 07:31.500 --> 07:38.700 be expanded prior to the command being performed through the remote shell. 07:38.700 --> 07:47.380 What you end up with is instead either filter or check in for a new value in order to fix this. 07:47.400 --> 07:51.120 You need to use syntax similar to the following. 07:51.120 --> 07:59.280 This syntax will forth and variables scienter then the filter parameter to be expanded before Sanden 07:59.520 --> 08:06.140 the command through the remote session and you should get back the correct results.