WEBVTT 00:00.450 --> 00:07.410 As soon as you find the command that you must have for a particular task you can use its help file to 00:07.410 --> 00:08.950 learn how to use it. 00:09.090 --> 00:16.260 Although the examples are obviously a great way to do that learning to interpret the help files syntax 00:16.410 --> 00:23.280 can enable you quickly find to commands capabilities so that you can run it more easily. 00:23.280 --> 00:31.980 You can use their help for go out there and look as an example that command features two parameter sets. 00:31.980 --> 00:36.600 Each feature represents one way in which the command can be run. 00:36.600 --> 00:44.400 Notice that each parameter set has many parameters and several parameters in common. 00:44.430 --> 00:47.990 You can make sound merge parameters between sets. 00:48.000 --> 00:57.270 That is if you decide to use the list parameter you cannot also use the shlock name because those two 00:57.270 --> 01:02.850 do not appear together in the same perimeter set in the first perimeter set. 01:02.880 --> 01:06.260 The log name perimeter is mandatory. 01:06.300 --> 01:12.660 This is indicated by the whole parameter not be an enclosed in square brackets. 01:12.750 --> 01:22.620 Help also shows that the perimeter accepts Drian Well yes men in strings of letters numbers or other 01:22.680 --> 01:23.690 characters. 01:23.730 --> 01:32.070 The actual log name parameter name is listed in square brackets meaning it is a positional perimeter 01:32.260 --> 01:40.400 that command cannot be around without a lot name but you do not have to actually type shlock name parameter 01:40.410 --> 01:41.100 name. 01:41.100 --> 01:48.420 You have to pass the log names Korean in the first position because that is the position in the Help 01:48.420 --> 01:55.680 file where the log name parameter appears there for the following two commands are functionally equal 01:55.680 --> 01:58.070 and get their share around lock. 01:58.090 --> 02:00.900 There's a log name application. 02:01.050 --> 02:10.560 And the second command get Desch event lock application again because log name parameter is the positional 02:10.560 --> 02:11.280 parameter. 02:11.280 --> 02:12.650 We can skip it. 02:12.660 --> 02:20.330 We don't have to type it to note here that more information about each parameter can be found by viewing 02:20.370 --> 02:22.320 the commands for help. 02:22.410 --> 02:31.300 For example around help get Desha won't lock dush fool to see the full Calpol forgat event log. 02:31.440 --> 02:38.850 And notice the additional information display you can for example confirm that the log name parameter 02:39.090 --> 02:40.200 is mandatory. 02:40.230 --> 02:43.120 And it appears in the first position. 02:43.120 --> 02:46.710 Be cautious when a meeting parameter names. 02:46.710 --> 02:51.940 One reason for caution is that you cannot do so with every parameter. 02:52.020 --> 02:54.620 The first computer name parameter. 02:54.690 --> 02:59.000 As one example can not have the parameter name emitted. 02:59.040 --> 03:06.450 Another reason for caution is that you can quickly lose track of what goes where when you provide perimeter 03:06.450 --> 03:10.760 names and parameters can come in any order. 03:10.800 --> 03:21.150 So try type and get to and lock computer name or example Leptis it to a log name application Midwest 03:21.350 --> 03:31.400 town that'll get to the nearest town records for application log for computer lab DC to how many are 03:31.560 --> 03:37.760 made to parameter name you become responsible for everything in the correct order. 03:37.920 --> 03:44.940 As for example get around to lock Desch computer name will have to sit to application. 03:44.940 --> 03:51.940 This command will not work because the log name is being parsed in the wrong position. 03:51.990 --> 04:00.060 So the best practice for you that if you are just getting started with Windows powers shell try to provide 04:00.060 --> 04:08.520 full parameter names instead of pass and parameter well used by position for parameter names make commands 04:08.610 --> 04:11.470 easier to read and troubleshoot. 04:11.640 --> 04:19.200 And they make it easier to see when you are typing the command incorrectly some votes about fool help 04:19.380 --> 04:26.370 although the brief syntax section of the help file can be used as a quick reminder. 04:26.370 --> 04:34.080 It doesn't provide a higher level of detail about each parameter read and it commands full help provides 04:34.140 --> 04:35.940 much deeper detail. 04:35.940 --> 04:44.500 For example around get help get service full and see how much additional information you receive. 04:44.550 --> 04:51.840 Some additional information includes the following description of each parameter whether each parameter 04:51.840 --> 04:52.850 has a default. 04:52.860 --> 05:01.060 Well you know whether a parameter is mandatory whether a parameter can accept failure and is tific position 05:01.270 --> 05:11.770 and whether a perimeter accepts pipeline input and if this is the case how so for help also includes 05:11.950 --> 05:15.840 extended command descriptions and examples.