[Autogenerated] So what is W. M. I. You
may have seen these three letters. They
normally when you do a search in
PowerShell, it may come up. So what does
it actually mean? What w. M. I stands for?
Windows management instrumentation. It is
Microsoft's implementation off the Web
based Enterprise Management Protocol or W
B M, allowing access to data from specific
machines that you might be accessing. So
what could w I be used for? Well, it could
be used to set security settings on a
specific device a Windows machine, for
example. You can also do the opposite and
collect that security information or other
details about those devices. We could also
set and change user permissions if needed,
as well as configure system properties,
which are normally things stored in the
registry or key value pairs of data that
you wish to store. We can also use it for
scheduling. Process is to actually run on
either local machines or even remote
machines if needed. We can also manage
code execution, so configure when things
would run and when they wouldn't run.
We can also manage error logging. So
we can make adjustments to that, utilizing
the W. M. I And then, of course, we can
manage drives on the machines themselves.
So how much storage space, what type of
disc They are etcetera. Now it's important
to understand what the W. M. I
architectures is actually made up off. So
when we look at this, it's kind of broken
down into a series of components. Are
first one is obviously the W M I kind of
API or the Windows Management API, which
is where we would make the connection from
within the PowerShell cmdlet that will
then talk to a .NET or the .NET Framework
rapper, which then communicates to the
devices. So let's take a Windows 10 device
here, where we would utilize either D com
or win RM. And then you'll see we've got
another acronym here called SIM, which
we'll talk about a little bit later. But
basically decomp will allow me to create a
specific type of connection that goes to
the device. And on the d calm side, we can
actually use W. M I, which we're talking
about, as well as Sim, which we'll talk
about in the future. And then, of course,
when RM is the SIM version of that
connection underneath all of This is
what's called the SIM Object manager and
then the same database. I want you to
imagine that as every component and every
setting and every piece of hardware
attached or part of that Windows 10 device
is stored in a large database, and we're
going to utilize PowerShell to be able to
retrieve that information outwards. So
what are the W? My components were the
first one is the W. My service, which is
an implementation of the Windows W my
system. So this is the process that runs,
and it has the display name of Windows
management instrumentation. It acts as the
intermediary between the W, my providers,
the repository and any applications it
will automatically run at startup next
other managed objects. These are any
logical or physical component or service
that can be managed via W. M. I. This
includes a vast array of components
because essentially any parameter or
object that can be accessed by other
Windows tools, for example, like
performance monitor can also be accessed
via dubbed me. There's also W I providers,
which are objects that monitor events and
data from specific objects in the OS.
There are many different types of
providers. Some are general, some are
device specific, and Windows comes with
numerous built in W. My providers. Next
are the classes. These are used by the W
my provider to pass data to the W my
services. They contain events and
properties that allow for the actual
capture and setting of data. W My classes
are pre defined, and they will start with
a double underscore at the beginning of
the name and then Leslie. We have our
methods. These are attached to particular
classes and allow actions to be performed
based on data included in them. For
instance, methods could be used to start
and stop processes on a remote machine.
Methods could be accessed via scripting
application or or via the network
management application. Next is our W my
repository, which is a database that
stores all of the static data that relate
to the W M E components. Then, of course,
we have the same object manager, which is
a system that sits between the management
application and the providers. Then we
have the API, which provides a way for the
applications to access the infrastructure
that's connected. And then, of course, we
have a consumer, which is the entity that
sends the queries to the objects via the
object manager. So I suppose if you're
looking at the consumer, it could be, for
example, the PowerShell would be the
consumer off that where we execute the
command and it retrieves the information.
Now from a W. My perspective. What's the
kind of structure here? So, first off, we
have name spaces, and the name spaces are
in the file system structure that
organizes the objects into functions. Then
we have class instances, which are the
objects that is stored within the name
spaces themselves. And then we have things
such as operating system and applications.
Specific data is then exposed via those
class instances, so you could almost
imagine it is like a folder structure
Unnamed spaces, a folder class instances
are sub folders, and then operating system
and application data is kind of files in
there. You have access to each of those
components, and you can instantiate a name
space to be able to see the class
instances and then go into the class instances to get the data on the methods