1
00:00:00,210 --> 00:00:01,120
[Autogenerated] So let's talk about the

2
00:00:01,120 --> 00:00:04,820
available SIM commands. Firstly, all SIM

3
00:00:04,820 --> 00:00:07,560
commands are available within the SIM

4
00:00:07,560 --> 00:00:10,650
cmdlet module, so that's a critical step

5
00:00:10,650 --> 00:00:12,870
here. Make sure that we have the Sim

6
00:00:12,870 --> 00:00:15,300
cmdlet module available, which if we're

7
00:00:15,300 --> 00:00:18,310
using the right versions of windows and as

8
00:00:18,310 --> 00:00:20,510
long as it's not a super super old version

9
00:00:20,510 --> 00:00:22,580
of PowerShell, then we will have the same

10
00:00:22,580 --> 00:00:26,110
cmdlet modules. Now the available SIM

11
00:00:26,110 --> 00:00:29,880
commands are kind of split up by the

12
00:00:29,880 --> 00:00:32,200
verbs. So the first verb that we would

13
00:00:32,200 --> 00:00:34,860
commonly use is the get So our first

14
00:00:34,860 --> 00:00:37,920
command here would be get sim associate ID

15
00:00:37,920 --> 00:00:40,410
instantiate. Now, this retrieves the SIM

16
00:00:40,410 --> 00:00:43,770
instances that are connected to a specific

17
00:00:43,770 --> 00:00:47,090
instance called the source instantiate. So

18
00:00:47,090 --> 00:00:49,730
in association, each Sim instance has a

19
00:00:49,730 --> 00:00:52,370
named role, and the same instance can

20
00:00:52,370 --> 00:00:55,740
participate in different types of roles.

21
00:00:55,740 --> 00:00:57,630
Then we have to get sim class, which we

22
00:00:57,630 --> 00:01:00,190
have looked at. This will retrieve a list

23
00:01:00,190 --> 00:01:03,090
of the SIM classes for a specific name

24
00:01:03,090 --> 00:01:06,390
space. If there is no class name supplied,

25
00:01:06,390 --> 00:01:08,380
then the commander will return all of the

26
00:01:08,380 --> 00:01:11,800
classes in the name space. So unlike a SIM

27
00:01:11,800 --> 00:01:15,050
instantiation, classes do not contain the

28
00:01:15,050 --> 00:01:17,650
session or computer name from where that

29
00:01:17,650 --> 00:01:20,100
information was retrieved. Now, of course,

30
00:01:20,100 --> 00:01:22,770
we have used get Sim. Instantiate is one

31
00:01:22,770 --> 00:01:25,090
we can specify either a class name or a

32
00:01:25,090 --> 00:01:27,980
query to return the class that we're

33
00:01:27,980 --> 00:01:30,390
looking for. The cmdlet returns want to

34
00:01:30,390 --> 00:01:32,930
more sim instantiate objects that

35
00:01:32,930 --> 00:01:36,270
represent a snapshot off the data from

36
00:01:36,270 --> 00:01:38,900
that SIM server or the same database

37
00:01:38,900 --> 00:01:41,480
effectively. Then, of course, by default

38
00:01:41,480 --> 00:01:44,450
we have SIM session. The cmdlet gets all

39
00:01:44,450 --> 00:01:48,170
of the SIM sessions that are created. To

40
00:01:48,170 --> 00:01:52,000
get information from PowerShell, you can

41
00:01:52,000 --> 00:01:54,360
use the parameters of Get SIM session to

42
00:01:54,360 --> 00:01:56,340
get the sessions that are for particular

43
00:01:56,340 --> 00:01:59,590
computers or identify them by the names or

44
00:01:59,590 --> 00:02:02,610
other identifies. Using that command does

45
00:02:02,610 --> 00:02:05,010
not get SIM sessions that were created

46
00:02:05,010 --> 00:02:08,240
within other PowerShell sessions or on

47
00:02:08,240 --> 00:02:10,930
other machines, so it only has access to

48
00:02:10,930 --> 00:02:13,130
the stuff that was created by the same

49
00:02:13,130 --> 00:02:16,810
session. The next verb is new, and we have

50
00:02:16,810 --> 00:02:19,760
three core commands. The first one is new

51
00:02:19,760 --> 00:02:22,130
SIM session. This will create an instance

52
00:02:22,130 --> 00:02:24,470
of the same class based on the class

53
00:02:24,470 --> 00:02:27,070
definition in either the local computer or

54
00:02:27,070 --> 00:02:29,330
the remote computer. By default, the

55
00:02:29,330 --> 00:02:32,070
commandment will create an instance on the

56
00:02:32,070 --> 00:02:35,110
local machine that you execute it the new

57
00:02:35,110 --> 00:02:37,190
SIM session, cmdlet creates a brand new

58
00:02:37,190 --> 00:02:40,060
session. The SIM session is a client side

59
00:02:40,060 --> 00:02:42,900
object that represents the connection to

60
00:02:42,900 --> 00:02:45,840
the local computer or the remote computer.

61
00:02:45,840 --> 00:02:47,290
The same session will then contain

62
00:02:47,290 --> 00:02:49,710
information about the connection, such as

63
00:02:49,710 --> 00:02:52,600
computer name, the protocol used or any

64
00:02:52,600 --> 00:02:56,140
identifies. The cmdlet will return a

65
00:02:56,140 --> 00:02:59,340
session object that can be used by all

66
00:02:59,340 --> 00:03:02,390
other Sim cmdlet is, and then lastly, we

67
00:03:02,390 --> 00:03:04,890
have the session option. This cmdlet

68
00:03:04,890 --> 00:03:07,370
creates an instance off a SIM session

69
00:03:07,370 --> 00:03:10,320
options object, which he would then pass

70
00:03:10,320 --> 00:03:13,400
to a SIM session. You use the session

71
00:03:13,400 --> 00:03:16,500
options object as an input to the session

72
00:03:16,500 --> 00:03:19,010
to specify certain things about the

73
00:03:19,010 --> 00:03:21,850
connection. So the cmdlet itself has two

74
00:03:21,850 --> 00:03:24,980
parameter sets. One for do Bs man options

75
00:03:24,980 --> 00:03:27,170
on one for D. Com. Depending on how you

76
00:03:27,170 --> 00:03:29,590
connect, depending on which parameters you

77
00:03:29,590 --> 00:03:32,030
use, the cmdlet will return either a

78
00:03:32,030 --> 00:03:38,230
decomp session or a W s man session. Now

79
00:03:38,230 --> 00:03:41,680
there is also an import on an invoke as

80
00:03:41,680 --> 00:03:45,310
well. So we have to core cmdlet. It's

81
00:03:45,310 --> 00:03:48,170
import binary, my log. So this will

82
00:03:48,170 --> 00:03:50,390
recreate saved objects based on the

83
00:03:50,390 --> 00:03:53,530
contents of an exported file. If we've ran

84
00:03:53,530 --> 00:03:56,490
the Export Command the cmdlet is similar

85
00:03:56,490 --> 00:04:00,880
to the import CLI XML, except this time

86
00:04:00,880 --> 00:04:02,700
it's just a binary object that's being

87
00:04:02,700 --> 00:04:04,570
uploaded. And then, of course, we have

88
00:04:04,570 --> 00:04:07,880
invoked SIM method. This effectively just

89
00:04:07,880 --> 00:04:10,570
invokes a method of a SIM class or a Sim

90
00:04:10,570 --> 00:04:14,080
instantiate using the key value name pairs

91
00:04:14,080 --> 00:04:16,410
that you specify within the arguments

92
00:04:16,410 --> 00:04:19,640
parameter. And then lastly, we have a few

93
00:04:19,640 --> 00:04:21,770
other ones. We have register, we have

94
00:04:21,770 --> 00:04:26,140
removes and we have sets the register. CMD

95
00:04:26,140 --> 00:04:30,270
indication event allows you to subscribe

96
00:04:30,270 --> 00:04:32,810
to indications Using a class name or a

97
00:04:32,810 --> 00:04:35,420
query expression, you we can use the

98
00:04:35,420 --> 00:04:38,090
source. Identify a parameter to get the

99
00:04:38,090 --> 00:04:40,400
name off the subscription so the cmdlet

100
00:04:40,400 --> 00:04:44,050
returns an Advent subscription object, and

101
00:04:44,050 --> 00:04:46,530
you can then use that at any point. So

102
00:04:46,530 --> 00:04:49,970
we're registering an event for something

103
00:04:49,970 --> 00:04:52,860
to happen. We then also have the remove.

104
00:04:52,860 --> 00:04:55,230
Sim instantiate is commander will remove

105
00:04:55,230 --> 00:04:57,600
the sim instantiate. You can specify the

106
00:04:57,600 --> 00:04:59,660
same instance to remove by using the

107
00:04:59,660 --> 00:05:03,610
object retrieved or a query, or by using a

108
00:05:03,610 --> 00:05:07,650
different cmdlet. We could also remove any

109
00:05:07,650 --> 00:05:10,850
SIM sessions so we can remove one or more

110
00:05:10,850 --> 00:05:12,700
from the local PowerShell session by using

111
00:05:12,700 --> 00:05:14,660
remove Sim session and then, of course,

112
00:05:14,660 --> 00:05:17,610
we can set specific properties off the

113
00:05:17,610 --> 00:05:20,060
same instance I using the set command.

114
00:05:20,060 --> 00:05:22,570
There are others, but these are the base

115
00:05:22,570 --> 00:05:25,510
ones that we would expect to utilize. Now,

116
00:05:25,510 --> 00:05:27,870
to be able to view all of the SIM commands

117
00:05:27,870 --> 00:05:30,000
we can simply use a standard PowerShell

118
00:05:30,000 --> 00:05:32,660
cmdlet called get command, specify the

119
00:05:32,660 --> 00:05:35,350
module as Sim cmdlet is and then as

120
00:05:35,350 --> 00:05:36,980
normal. Select the object and get the

121
00:05:36,980 --> 00:05:40,530
property of the name etcetera. We can also

122
00:05:40,530 --> 00:05:42,990
use the get help option as well. So we can

123
00:05:42,990 --> 00:05:45,710
say I want to get help for a specific SIM

124
00:05:45,710 --> 00:05:48,610
command. So not only can we view all of

125
00:05:48,610 --> 00:05:51,160
the commands, but we can then get help for

126
00:05:51,160 --> 00:05:54,000
those commands by using the standard get help.