[Autogenerated] So let's talk about the
available SIM commands. Firstly, all SIM
commands are available within the SIM
cmdlet module, so that's a critical step
here. Make sure that we have the Sim
cmdlet module available, which if we're
using the right versions of windows and as
long as it's not a super super old version
of PowerShell, then we will have the same
cmdlet modules. Now the available SIM
commands are kind of split up by the
verbs. So the first verb that we would
commonly use is the get So our first
command here would be get sim associate ID
instantiate. Now, this retrieves the SIM
instances that are connected to a specific
instance called the source instantiate. So
in association, each Sim instance has a
named role, and the same instance can
participate in different types of roles.
Then we have to get sim class, which we
have looked at. This will retrieve a list
of the SIM classes for a specific name
space. If there is no class name supplied,
then the commander will return all of the
classes in the name space. So unlike a SIM
instantiation, classes do not contain the
session or computer name from where that
information was retrieved. Now, of course,
we have used get Sim. Instantiate is one
we can specify either a class name or a
query to return the class that we're
looking for. The cmdlet returns want to
more sim instantiate objects that
represent a snapshot off the data from
that SIM server or the same database
effectively. Then, of course, by default
we have SIM session. The cmdlet gets all
of the SIM sessions that are created. To
get information from PowerShell, you can
use the parameters of Get SIM session to
get the sessions that are for particular
computers or identify them by the names or
other identifies. Using that command does
not get SIM sessions that were created
within other PowerShell sessions or on
other machines, so it only has access to
the stuff that was created by the same
session. The next verb is new, and we have
three core commands. The first one is new
SIM session. This will create an instance
of the same class based on the class
definition in either the local computer or
the remote computer. By default, the
commandment will create an instance on the
local machine that you execute it the new
SIM session, cmdlet creates a brand new
session. The SIM session is a client side
object that represents the connection to
the local computer or the remote computer.
The same session will then contain
information about the connection, such as
computer name, the protocol used or any
identifies. The cmdlet will return a
session object that can be used by all
other Sim cmdlet is, and then lastly, we
have the session option. This cmdlet
creates an instance off a SIM session
options object, which he would then pass
to a SIM session. You use the session
options object as an input to the session
to specify certain things about the
connection. So the cmdlet itself has two
parameter sets. One for do Bs man options
on one for D. Com. Depending on how you
connect, depending on which parameters you
use, the cmdlet will return either a
decomp session or a W s man session. Now
there is also an import on an invoke as
well. So we have to core cmdlet. It's
import binary, my log. So this will
recreate saved objects based on the
contents of an exported file. If we've ran
the Export Command the cmdlet is similar
to the import CLI XML, except this time
it's just a binary object that's being
uploaded. And then, of course, we have
invoked SIM method. This effectively just
invokes a method of a SIM class or a Sim
instantiate using the key value name pairs
that you specify within the arguments
parameter. And then lastly, we have a few
other ones. We have register, we have
removes and we have sets the register. CMD
indication event allows you to subscribe
to indications Using a class name or a
query expression, you we can use the
source. Identify a parameter to get the
name off the subscription so the cmdlet
returns an Advent subscription object, and
you can then use that at any point. So
we're registering an event for something
to happen. We then also have the remove.
Sim instantiate is commander will remove
the sim instantiate. You can specify the
same instance to remove by using the
object retrieved or a query, or by using a
different cmdlet. We could also remove any
SIM sessions so we can remove one or more
from the local PowerShell session by using
remove Sim session and then, of course,
we can set specific properties off the
same instance I using the set command.
There are others, but these are the base
ones that we would expect to utilize. Now,
to be able to view all of the SIM commands
we can simply use a standard PowerShell
cmdlet called get command, specify the
module as Sim cmdlet is and then as
normal. Select the object and get the
property of the name etcetera. We can also
use the get help option as well. So we can
say I want to get help for a specific SIM
command. So not only can we view all of
the commands, but we can then get help for
those commands by using the standard get help.