1
00:00:00,340 --> 00:00:01,450
[Autogenerated] So let's go back into our

2
00:00:01,450 --> 00:00:03,230
environment on. We'll look at how we can

3
00:00:03,230 --> 00:00:06,140
view all of the SIM commands and then

4
00:00:06,140 --> 00:00:08,120
we'll retrieve help for some of those

5
00:00:08,120 --> 00:00:10,440
specific commands that are available.

6
00:00:10,440 --> 00:00:12,370
Okay, so we're back on the workstation

7
00:00:12,370 --> 00:00:14,280
now, and I want to be. Had to do is

8
00:00:14,280 --> 00:00:17,370
retrieve a list of all the SIM commands.

9
00:00:17,370 --> 00:00:20,220
Now, all of the SIM commands exist in the

10
00:00:20,220 --> 00:00:23,960
same cmdlet is module. So if I sue, get if

11
00:00:23,960 --> 00:00:29,140
I do get command and type module and then

12
00:00:29,140 --> 00:00:33,120
do cmdlet is like so you'll see it

13
00:00:33,120 --> 00:00:35,880
returns. May a list off the SIM commands.

14
00:00:35,880 --> 00:00:37,710
Now, you may have thought there was gonna

15
00:00:37,710 --> 00:00:39,400
be hundreds of these things, but actually

16
00:00:39,400 --> 00:00:42,380
there's not The same is the w my object

17
00:00:42,380 --> 00:00:44,860
ones. There's only a subset there needed

18
00:00:44,860 --> 00:00:46,550
because, of course, you're using these

19
00:00:46,550 --> 00:00:49,880
parent methods or modules or cmdlet sat

20
00:00:49,880 --> 00:00:53,120
least to retrieve other values. So what we

21
00:00:53,120 --> 00:00:56,260
could do? We could just say I want to

22
00:00:56,260 --> 00:00:59,940
select the object, specify the property on

23
00:00:59,940 --> 00:01:01,660
that. I just want to see the list of the

24
00:01:01,660 --> 00:01:03,600
names. Now, some of these we've already

25
00:01:03,600 --> 00:01:05,910
looked at, so gets him. Instantiate gets

26
00:01:05,910 --> 00:01:08,420
him session. New instantiate news session,

27
00:01:08,420 --> 00:01:11,080
etcetera So these are standard commands

28
00:01:11,080 --> 00:01:13,960
that are available now. How do you know

29
00:01:13,960 --> 00:01:17,910
what isn't required or what is optional on

30
00:01:17,910 --> 00:01:20,370
what parameters even exist? But this is

31
00:01:20,370 --> 00:01:23,010
where we can utilize standard out of the

32
00:01:23,010 --> 00:01:26,060
box PowerShell commands that are not sim

33
00:01:26,060 --> 00:01:28,410
specific. So, for example, let's take a

34
00:01:28,410 --> 00:01:31,570
look at the get SIM session. So we can

35
00:01:31,570 --> 00:01:34,700
just clear this out and I'll say, Get dash

36
00:01:34,700 --> 00:01:37,090
help, which is a standard PowerShell

37
00:01:37,090 --> 00:01:40,340
command on. Then I'm going to say, get

38
00:01:40,340 --> 00:01:45,460
same session and I'm just gonna say show

39
00:01:45,460 --> 00:01:48,810
window now What this will do is this will

40
00:01:48,810 --> 00:01:50,850
go ahead and check and you'll see a little

41
00:01:50,850 --> 00:01:53,040
windows popped up. We don't have to do it

42
00:01:53,040 --> 00:01:54,920
this way. I sometimes like this because it

43
00:01:54,920 --> 00:01:56,400
makes a bit more sense when I'm trying to

44
00:01:56,400 --> 00:01:59,360
look at it. But you'll see it gives me the

45
00:01:59,360 --> 00:02:01,770
basic information it will say gets him

46
00:02:01,770 --> 00:02:04,620
session requires a computer name. It could

47
00:02:04,620 --> 00:02:08,180
be an IDE, an instance IDE or a name, and

48
00:02:08,180 --> 00:02:09,820
then comes in and tells me that computer

49
00:02:09,820 --> 00:02:12,760
name is really the main parameter or the

50
00:02:12,760 --> 00:02:15,380
IDE one or the instance or the name and

51
00:02:15,380 --> 00:02:17,850
then some examples. Some inputs links to

52
00:02:17,850 --> 00:02:20,210
the documentation and anything else. Now

53
00:02:20,210 --> 00:02:23,190
if we run that same cmdlet tear again but

54
00:02:23,190 --> 00:02:25,940
say, Don't show window, it will just write

55
00:02:25,940 --> 00:02:27,770
it out to the same window so you can do

56
00:02:27,770 --> 00:02:30,250
either or it's entirely up to you now.

57
00:02:30,250 --> 00:02:32,350
What this means is, if I just clear

58
00:02:32,350 --> 00:02:34,470
everything is that when it comes to

59
00:02:34,470 --> 00:02:37,210
utilizing some of the sessions. So if I

60
00:02:37,210 --> 00:02:40,060
say new sim session, then of course I can

61
00:02:40,060 --> 00:02:42,440
get the help for that, which gives me

62
00:02:42,440 --> 00:02:45,340
syntax as well as aliases and other

63
00:02:45,340 --> 00:02:47,830
information. So when your first trying to

64
00:02:47,830 --> 00:02:50,760
use any PowerShell commands, not even just

65
00:02:50,760 --> 00:02:53,230
the SIM commands, it's always helpful to

66
00:02:53,230 --> 00:02:56,170
be able to run the get help option to be

67
00:02:56,170 --> 00:02:59,250
able to identify what needs to be done now

68
00:02:59,250 --> 00:03:02,180
if we flick back to PowerShell is, see if

69
00:03:02,180 --> 00:03:03,670
you remember we looked at the CIMB

70
00:03:03,670 --> 00:03:06,950
Explorer, but we also have this option

71
00:03:06,950 --> 00:03:09,190
here, which is the list of commands. Now,

72
00:03:09,190 --> 00:03:12,230
if I drop down here, you'll see Sim

73
00:03:12,230 --> 00:03:14,780
cmdlet. It's now, of course. What's nice

74
00:03:14,780 --> 00:03:17,470
here is that even though I'm not going to

75
00:03:17,470 --> 00:03:20,020
encourage you to use PowerShell, I see you

76
00:03:20,020 --> 00:03:22,570
can actually view the Sim cmdlet it's

77
00:03:22,570 --> 00:03:25,510
here. If I wasn't sure how to use get Sim

78
00:03:25,510 --> 00:03:27,700
session. I could then click on to it and

79
00:03:27,700 --> 00:03:30,810
say show details. This would refresh And

80
00:03:30,810 --> 00:03:33,000
then I would see computer name instance.

81
00:03:33,000 --> 00:03:36,110
IDE name set session ID. So in the left

82
00:03:36,110 --> 00:03:37,900
here, I'm just going to clear this and

83
00:03:37,900 --> 00:03:39,760
you'll understand why in a second, let me

84
00:03:39,760 --> 00:03:42,130
make that a little bit smaller. There we

85
00:03:42,130 --> 00:03:45,600
do. And of course I'm going to say Trainer

86
00:03:45,600 --> 00:03:48,050
and then I could say Insert and you'll see

87
00:03:48,050 --> 00:03:51,440
it injects that value into this side. I

88
00:03:51,440 --> 00:03:53,560
could also then expand the common

89
00:03:53,560 --> 00:03:56,130
parameters, which are not unique to this

90
00:03:56,130 --> 00:03:59,140
specific cmdlet, but to everything such as

91
00:03:59,140 --> 00:04:01,940
arrow, variable error, message, etcetera.

92
00:04:01,940 --> 00:04:04,160
But what it does allow me to do is to kind

93
00:04:04,160 --> 00:04:06,850
of scroll between them and say, Well, what

94
00:04:06,850 --> 00:04:08,990
about New Sim Instance, And then you'll

95
00:04:08,990 --> 00:04:10,400
see there's a whole host of different

96
00:04:10,400 --> 00:04:13,290
things. So two different ways there. One.

97
00:04:13,290 --> 00:04:14,940
You could do it straight in the console

98
00:04:14,940 --> 00:04:17,220
and just say, Go and get me the help for

99
00:04:17,220 --> 00:04:20,460
that command or to to use PowerShell I see

100
00:04:20,460 --> 00:04:24,000
and then be able to retrieve values about that

