WEBVTT 00:00.420 --> 00:07.350 If Windows partially is unable to buy and pipeline input by you then led by well your technique it tries 00:07.350 --> 00:14.550 to use that by probit to name technique for example get serviced by its top Brosius the first command 00:14.550 --> 00:19.650 puts objects of the type service controller into the pipeline. 00:19.770 --> 00:24.240 The second command has no parameters that can accept that kind of object. 00:24.360 --> 00:31.370 The second comment also has no parameters left except a generic object or the object. 00:31.470 --> 00:38.330 Therefore there by well your technique fails the Lachelle changes to the by property name technique 00:38.520 --> 00:40.410 to predict what it will do. 00:40.410 --> 00:45.990 You must review the properties of the objects produced by the first command. 00:46.020 --> 00:50.150 And this example you would run good service by get mamber. 00:50.280 --> 00:56.240 You would also have to make a list of parameters of the second command that can accept pipelining input 00:56.280 --> 01:04.230 by use and by property name to make that list view the help for the second command help stop this process. 01:04.300 --> 01:11.850 The show window in this example the stop Russa's command has more than one parameter that accepts pipeline 01:11.940 --> 01:20.610 input by use and by robot only those parameters are maime and ID the objects already used by get service 01:20.640 --> 01:28.560 do not have an id property so their ID perimeter is not considered the object produced by get service 01:28.560 --> 01:30.360 have and name property. 01:30.420 --> 01:36.780 Therefore the contents of the name property are attached to the name parameter. 01:36.840 --> 01:44.520 Please know that by property name technique is very simplistic because the property name and the parameter 01:44.640 --> 01:53.220 name spelled Lissy and because the perimeter was programmed to accept input in this manner they connect 01:53.370 --> 01:54.390 to one another. 01:54.480 --> 02:01.410 Some votes about finding by property named parameters to see what parameters except pipeline input by 02:01.410 --> 02:06.020 use and by property name examine the full help for their command. 02:06.030 --> 02:13.960 It is possible for a perimeter to access pipeline in good by use and both by well and by property name. 02:14.040 --> 02:21.300 Remember that the shell will always try while you are fast and will use by property name only if by 02:21.310 --> 02:22.460 well-you fails. 02:22.470 --> 02:28.950 Now lets have some demonstration examples to see how by property name can be used to create new user 02:28.950 --> 02:29.640 accounts. 02:29.640 --> 02:32.380 Here are our demonstration steps. 02:32.400 --> 02:40.470 First will display the contents of a comma separated 12 or six the file that contains new user information. 02:40.470 --> 02:41.860 Let's run the following command. 02:41.880 --> 02:45.660 Import says Field users 1.6 V. 02:45.760 --> 02:52.230 Remember that Covance of this is free file become properties and feature all of this is refiled becomes 02:52.230 --> 02:53.040 an object. 02:53.040 --> 03:01.560 Now let's view the help of new There's a user command to get parameters that can accept pipeline input 03:01.740 --> 03:06.880 to do that just type help me you say the user does show window. 03:06.900 --> 03:14.180 Please know that most parameters of this command response to active directory attributes and parameters 03:14.180 --> 03:17.310 such as title deps CDR and so on. 03:17.400 --> 03:19.530 All except pipeline input. 03:19.620 --> 03:22.070 By using by property name. 03:22.120 --> 03:30.410 Now let's create new users by using the information in the CSFB file but only Phills will do that. 03:30.630 --> 03:41.070 What if parameter to do that will type in persons users 1.60 and pipe it to new user and add what if 03:41.250 --> 03:46.980 this command would have created for new users having the appropriate attributes. 03:46.980 --> 03:49.640 This is not a real world example. 03:49.710 --> 03:56.730 In a real organization this is a file that originate with a human resources or personnel department 03:56.970 --> 03:59.370 which might not provide the correct format. 03:59.370 --> 04:05.940 No that's viewas Second since we filed that represents a more real world scenario it's more realistic 04:05.940 --> 04:11.240 example that person provided this file eliminated that same account name field. 04:11.280 --> 04:18.410 That person might not have known that it was for or might have thought that it contained duplicate data. 04:18.510 --> 04:24.750 However you can no longer use the file directly because it doesn't provide the required same account 04:24.750 --> 04:25.800 name property. 04:25.920 --> 04:34.200 So let's run in Perth says the user of student service fee and part that to select object property they'll 04:34.200 --> 04:42.090 be selecting all properties and grid and you want same account name and then pipe it to new user. 04:42.180 --> 04:49.260 So select object was used to add the missing semicolon Name property copy in its value from the provided 04:49.260 --> 04:50.430 Name property. 04:50.430 --> 04:51.300 Now what's wrong. 04:51.360 --> 04:55.910 Get a user does filter asterisk for all users.