[Autogenerated] So let's go back into our
environment on. We'll look at how we can
view all of the SIM commands and then
we'll retrieve help for some of those
specific commands that are available.
Okay, so we're back on the workstation
now, and I want to be. Had to do is
retrieve a list of all the SIM commands.
Now, all of the SIM commands exist in the
same cmdlet is module. So if I sue, get if
I do get command and type module and then
do cmdlet is like so you'll see it
returns. May a list off the SIM commands.
Now, you may have thought there was gonna
be hundreds of these things, but actually
there's not The same is the w my object
ones. There's only a subset there needed
because, of course, you're using these
parent methods or modules or cmdlet sat
least to retrieve other values. So what we
could do? We could just say I want to
select the object, specify the property on
that. I just want to see the list of the
names. Now, some of these we've already
looked at, so gets him. Instantiate gets
him session. New instantiate news session,
etcetera So these are standard commands
that are available now. How do you know
what isn't required or what is optional on
what parameters even exist? But this is
where we can utilize standard out of the
box PowerShell commands that are not sim
specific. So, for example, let's take a
look at the get SIM session. So we can
just clear this out and I'll say, Get dash
help, which is a standard PowerShell
command on. Then I'm going to say, get
same session and I'm just gonna say show
window now What this will do is this will
go ahead and check and you'll see a little
windows popped up. We don't have to do it
this way. I sometimes like this because it
makes a bit more sense when I'm trying to
look at it. But you'll see it gives me the
basic information it will say gets him
session requires a computer name. It could
be an IDE, an instance IDE or a name, and
then comes in and tells me that computer
name is really the main parameter or the
IDE one or the instance or the name and
then some examples. Some inputs links to
the documentation and anything else. Now
if we run that same cmdlet tear again but
say, Don't show window, it will just write
it out to the same window so you can do
either or it's entirely up to you now.
What this means is, if I just clear
everything is that when it comes to
utilizing some of the sessions. So if I
say new sim session, then of course I can
get the help for that, which gives me
syntax as well as aliases and other
information. So when your first trying to
use any PowerShell commands, not even just
the SIM commands, it's always helpful to
be able to run the get help option to be
able to identify what needs to be done now
if we flick back to PowerShell is, see if
you remember we looked at the CIMB
Explorer, but we also have this option
here, which is the list of commands. Now,
if I drop down here, you'll see Sim
cmdlet. It's now, of course. What's nice
here is that even though I'm not going to
encourage you to use PowerShell, I see you
can actually view the Sim cmdlet it's
here. If I wasn't sure how to use get Sim
session. I could then click on to it and
say show details. This would refresh And
then I would see computer name instance.
IDE name set session ID. So in the left
here, I'm just going to clear this and
you'll understand why in a second, let me
make that a little bit smaller. There we
do. And of course I'm going to say Trainer
and then I could say Insert and you'll see
it injects that value into this side. I
could also then expand the common
parameters, which are not unique to this
specific cmdlet, but to everything such as
arrow, variable error, message, etcetera.
But what it does allow me to do is to kind
of scroll between them and say, Well, what
about New Sim Instance, And then you'll
see there's a whole host of different
things. So two different ways there. One.
You could do it straight in the console
and just say, Go and get me the help for
that command or to to use PowerShell I see
and then be able to retrieve values about that