WEBVTT 00:07.000 --> 00:14.690 You're going to use Windows shell to list all the name spaces on the computer and on the local computer 00:14.750 --> 00:21.090 or on a remote computer you could try running this command get w my object. 00:21.180 --> 00:23.110 There's namespace route. 00:23.210 --> 00:30.900 There's at least rigorous and pipe it to select there's a unique underscore namespace. 00:30.980 --> 00:36.380 Please know that it can take several minutes to produce a complete list of name spaces. 00:36.400 --> 00:45.500 Notice that underscore namespace case to underscore characters and is typed all capital windows powers 00:45.520 --> 00:54.640 shell also supports term completion for namespace names in this class will use only the root seem to 00:54.680 --> 01:02.320 namespace which includes all the clauses are related to the Windows operating system to your computer's 01:02.330 --> 01:03.200 hardware. 01:03.320 --> 01:09.730 The road seemed to version two namespace is the default namespace. 01:09.770 --> 01:15.620 Therefore you do not have to specify the namespace when querent instances from it. 01:15.620 --> 01:23.030 Now let's take a look at demonstration example you'll see how to list local repository namespace is 01:23.030 --> 01:25.210 by using WMI. 01:25.250 --> 01:35.040 So to use WMI to list all local namespace says Place type get WMI object does namespace root. 01:35.140 --> 01:44.180 There's at least Dessler occurs and pipe it to select thus unique to underscores namespace. 01:44.180 --> 01:53.150 Please note here the root backslash seem v to namespace and there root backslash Security Center to 01:53.450 --> 01:54.560 namespace. 01:54.660 --> 01:58.560 We all use this in the next practice activity. 01:58.700 --> 02:06.650 Now about listin classes acknowledge let the process of finding the class that you must have is difficult 02:06.860 --> 02:10.070 time consuming and error prone. 02:10.100 --> 02:16.770 Many newcomers to WMI and soon become frustrated with their guesswork. 02:16.910 --> 02:25.760 Unfortunately Gassan is currently the only technique available Varos third party like WMI Explorer 2 02:26.030 --> 02:30.810 are available that can make exploring the repository easier. 02:30.830 --> 02:37.200 This graphical tool enable you to validate guesses more quickly. 02:37.280 --> 02:45.920 An internet search for WMI Explorer will frequently return several The results so you can try these 02:45.920 --> 02:51.670 two windows for a shell can list all the classes in a particular namespace. 02:51.740 --> 02:59.240 For example to list all the classes in the root backslash seen the two namespace you could run. 02:59.300 --> 03:10.040 Either of these commands get w my object namespace root backslash symbol to the list or get the same 03:10.040 --> 03:17.810 class dush namespace a root backslash simply to please know that it can take several minutes to list 03:17.870 --> 03:22.900 all the classes in a large namespace like root seem to. 03:23.270 --> 03:31.940 Windows for supports term completion of namespace names for same commands only you can type get same 03:32.150 --> 03:43.440 tab dush name like an A M tab are double and press tab again to quickly type the second command. 03:43.460 --> 03:47.750 Glasses are not listed in any particular order. 03:47.770 --> 03:52.570 Finding a class can be easier when they are listed alphabetically. 03:52.700 --> 03:59.310 For example if you are looking for a class that represents a process but do not know the class name. 03:59.390 --> 04:07.280 You could quickly move to the beat section of a sorted list and start to look for the word process to 04:07.280 --> 04:11.370 produce an alphabetical list of classes in the root. 04:11.400 --> 04:21.030 Since the two namespace you could run either of these commands get WMI object dush namespace root backslash 04:21.170 --> 04:26.590 seem v to this list and pipe it to sort name. 04:26.630 --> 04:33.230 Or you could type Get some class namespace root in the two pipe sort. 04:33.260 --> 04:38.830 Name please know that in the root seem to seeing the two namespace. 04:38.840 --> 04:47.240 You'll see clauses whose name start with re-inserted to underscore and other clauses whose names start 04:47.240 --> 04:49.560 with same underscore. 04:49.730 --> 04:55.960 This namespace is the only one where those preferences are used. 04:55.960 --> 05:04.200 Classes starting with CM underscore are typically abstract classes classes started with when. 05:04.290 --> 05:13.520 So to underscore typically more specific versions of the abstract glosses and contain information that 05:13.520 --> 05:21.770 is specific to the Windows operating system many administrators feel that the repository can be difficult 05:21.770 --> 05:23.060 to work with. 05:23.170 --> 05:30.000 Finding the class that you must have to perform a given task is basically a guessing game. 05:30.050 --> 05:36.710 You have to guess at what the class might be named and then looks through the class list and determine 05:36.980 --> 05:38.480 whether you are right. 05:38.540 --> 05:44.510 Then you must go where is the class to determine whether the class contains the information that you 05:44.510 --> 05:45.080 need. 05:45.140 --> 05:52.510 Because many classes outside the route seem to namespace is not well documented. 05:52.520 --> 05:54.720 This is your best approach. 05:54.840 --> 06:03.410 An administrator who is good at using WMI and the same is also good to make an educated guesses. 06:03.440 --> 06:11.450 There is no central directory of repository classes the repository does not include a search system. 06:11.540 --> 06:19.400 You can use windows power shell to perform a basic keyword search of repository class names for example 06:19.400 --> 06:24.280 to find all classes in the root symbol to namespace. 06:24.370 --> 06:28.150 Have a network in the class name you could use. 06:28.160 --> 06:38.690 This gets in class does name a route seeing to and pipe it to where the same class name Desch like network 06:38.900 --> 06:40.760 and pipe it to sort. 06:40.760 --> 06:42.200 Same class name. 06:42.200 --> 06:50.210 However this technique can search Glaus descriptions because that information is not stored in the repository. 06:50.330 --> 06:58.550 Frequently an Internet search engine will provide a better way to search for possible class names. 06:58.550 --> 07:03.890 You may see some classes whose names begin with two underscore characters. 07:03.920 --> 07:11.200 These are system classes and they are used internally by WMI and see him. 07:11.210 --> 07:18.350 Now let's have a look at some demonstration example where you'll see how to list the classes in a namespace 07:18.530 --> 07:24.560 so to list the classes in the root backslash Security Center to namespace. 07:24.590 --> 07:33.670 You could type get WMI object their namespace a root Security Center to Desch least. 07:33.680 --> 07:40.320 As I said you can encounter names class names start with to underscore character. 07:40.430 --> 07:45.800 These are system classes and classes can typically be ignored. 07:45.800 --> 07:54.590 Now another example to list the classes in the root seems the name space and sort the list by name type. 07:54.670 --> 08:02.720 Get the same class the first name space would seem to version 2 and pipe it to sort. 08:02.720 --> 08:10.460 Same class name and alphabetical list can be useful when you have to validate a guess about a class 08:10.460 --> 08:11.150 name. 08:11.150 --> 08:19.430 For example if you think a class name is inserted to underscore network and it could be useful you can 08:19.430 --> 08:25.610 more easily discover whether the class exists by using an alphabetical list.