1
00:00:00,420 --> 00:00:07,860
Administrators can use their w my infrastructure technology to monitor and control managed objects in

2
00:00:07,860 --> 00:00:09,300
a network w.

3
00:00:09,310 --> 00:00:16,860
My query is capable of filtering systems based on characteristics including random access memory processor

4
00:00:16,860 --> 00:00:24,590
speed just capacity IP address operating system version service pack level installed applications and

5
00:00:24,600 --> 00:00:32,790
router printer properties because w my exposures almost every property of every object within a computer.

6
00:00:32,790 --> 00:00:36,390
The list of attributes that you can use in a W.

7
00:00:36,390 --> 00:00:39,420
My query is virtually unlimited.

8
00:00:39,510 --> 00:00:48,780
W my queries are written by using W and my query language or w q l You can use a W in my query to create

9
00:00:48,940 --> 00:00:53,770
a W and my filter which you can use to filter a Jabil.

10
00:00:53,880 --> 00:00:58,700
You can use group policy to deploy software applications and service packs.

11
00:00:58,770 --> 00:01:06,030
You might create a GPO to deploy an application and then use a W on my filter to specify that the policies

12
00:01:06,030 --> 00:01:12,810
should apply only to computers with a certain operating system and service pack their W on my query

13
00:01:12,810 --> 00:01:15,160
to identify such system.

14
00:01:15,180 --> 00:01:22,110
For example could be select aphorism from Minnesota to underscore operating system where their version

15
00:01:22,110 --> 00:01:30,620
like turned out the query above returns true for computers later Iran and windows turn and Windows Server

16
00:01:30,730 --> 00:01:38,910
2016 when the group policy clan source evaluates GPO shows that it has downloaded to determine which

17
00:01:38,970 --> 00:01:46,080
should be handled off to client side extensions for processing it performs the query against the local

18
00:01:46,080 --> 00:01:46,890
system.

19
00:01:46,910 --> 00:01:53,760
If the system meets the criteria of the query the query result is a logical Drew and the client side

20
00:01:53,760 --> 00:02:02,070
extensions process that GPO w my exposures namespace spaces within reach are classes that can be queried

21
00:02:02,280 --> 00:02:09,540
many useful classes including mincer to to underscore operating system are found in a namespace called

22
00:02:09,720 --> 00:02:19,590
Root backslash Sim V2 to create a W am I filter right click the w my filters node in the JPM C console

23
00:02:19,620 --> 00:02:26,640
3 and then click New Type A name my own description for the filter and then click Add in the namespace

24
00:02:26,730 --> 00:02:34,420
text box type the namespace for your query or write or sorry Click Browse to select from available name

25
00:02:34,420 --> 00:02:38,810
spaces in the query text box type the query and then click Okay.

26
00:02:38,940 --> 00:02:42,070
Learn to filter a GPO over the W on my filter.

27
00:02:42,150 --> 00:02:52,530
Select the GPO or GPO link in the GP M.S. consult 3 click the scope tab in a w my dropdown list select

28
00:02:52,710 --> 00:03:00,450
W on my filter you can filter a g go was only a single W and my filter but you can create a W on my

29
00:03:00,450 --> 00:03:08,550
filter with a complex query that uses multiple criteria you can link a single W on my filter to one

30
00:03:08,550 --> 00:03:15,960
or more GP shows the general tap although w are my filter displays the GP is that to use the w on my

31
00:03:15,960 --> 00:03:25,240
filter there are two significant caveats regarding w my filters first the w q l syntax of W Mike where

32
00:03:25,250 --> 00:03:31,690
it can be challenging to master you often can find examples on the Internet where you search for but

33
00:03:31,710 --> 00:03:38,460
by using the keywords w in my field to around w on my query with a description of the query that you

34
00:03:38,460 --> 00:03:45,900
want to create second w am I filter those can negatively impact group policy process and performance

35
00:03:46,050 --> 00:03:53,010
because the group policy client service must perform the W make where it at each policy process an interval

36
00:03:53,250 --> 00:04:00,930
there is a slight impact on system performance every 90 to 120 minutes with the performance of today's

37
00:04:00,930 --> 00:04:08,820
computers the impact might or might not be noticeable however you should test the effects of a W on

38
00:04:08,820 --> 00:04:13,740
my filter prior to deploying it widely in your production environment.

39
00:04:13,800 --> 00:04:21,720
Also some w are my queries are more expansive in terms of process and performance querying for available

40
00:04:21,720 --> 00:04:26,520
disk space might take more time than querying for operating system versions.