Windows management instrumentation WMI and common information Modell's see them are related technologies
both are based on industry standards defined by the distributed management task force so the MTF which
defines independent management standards that can be implemented across different platforms or vendor
enterprise environments WMI is Microsoft implementation of the web based enterprise management or VB.
M. standart antes an earlier technology that is based on preliminary standards and proprietary technology.
Same is in your technology and is based on open cross-platform standards WMI has been available on Windows
operating system since Windows enty for most technologies provide a way to connect to common information
repository also known as the WMI repository.
This repository holds management information that can be WHERRETT and manipulated reenters Power Shell
supports both technologies.
Earlier versions of Windows poleward shell supported on a WMI in windows power shell or flater level
3 dogs 0 version 2 Berle's sets of commands lets you perform tasks by using either WMI or see him soome
commands provide many different Glaus cross platform and cross version capabilities.
This supports three kinds of connections connections to the local computer which has always use decorum
at home.
Connections to remote computer which all of us use web services for management or W-S man protocol.
This protocol is based on HTP and session based connections to remote computer which can use either
D-Conn. or W-S man brought Tiko decorum connections are typical and to the windows management instrumentations
service that is part of the Windows operating system.
We as many connections are made to Windows Remote management.
When our ram service which is the same server that enables windows power shell the modem will talk about
Irmo return a bit later in some other course in more detail.
No RAM is part of the windows management framework and is included in vendors management framework version
2 and newer versions.
When aroma is installed by default on computers that are running Windows 7 Windows 8 and so on.
Although installed by default on all those operating systems you can use SIM commands in two ways.
The first is the remote computer to have RAM installed and enabled that will typically require the windows
management framework version 3 be installed that Windows polls show a remote and is unable.
The second way to use suum commands is to tell the command to use the WMI technology that is the same
technology used by w my commands and it does not require that Windows management framework be installed
on the remote computer.
Now to WMI commands WMI commands use the same repositories same commands.
The only difference is in how the WMI commands connect to a remote computer WMI commands do not support
session based connections.
The commands support only ad hoc connections over decorum whether used by WMI or ACM commands.
Decorum can be difficult to use on some networks DICOM uses the remote pre-surgical or our PC protocol
that protocol requires specific firewall exceptions to work correctly WMI commands communicate with
the WMI service.
They do not require any version of Windows management framework on a remote computer and they do not
require that Windows Porcello remote be enabled is a remote computer.
Hell the Windows Firewall feature enabled WMI commands require that the remote administration exception
be enabled all the remote computer use the remote computer has a different local firewall enabled and
equal an exception must be created and enabled because commands can also use decorum WMI commands are
typically necessary only when you have to make an ad hoc connection to a computer that does not have
windows power shell or remote enabled.
So should you use WMI or assume most of the time you should you see him come on let's instead of that
older or w Mike and let's see him come on let's use D-Conn. one Crerand the local computer sim C'mon
let's use w else man for Redhawk connections to remote computer and see him come on let's can we use
decrement Duggal yes man for session based connections to remote computers they are WMI C'MON LET'S
can be used to when you must make an ad hoc connection to a computer that does not have Windows management
framework version 2 or newer version install or to a computer that has windows management framework
installed.
But that doesn't have windows power shell or remote enabled.
However this same command lads can connect to a computer that doesn't have windows management framework
installed and two computers that do not have Windows partial the remote enabled.
You must use the same session to connect to those computers.
You'll learn about Sim sessions a bit later in this course.
Please note Microsoft considers their WMI commands to read them windows for Shell to be deprecated although
the underlying WMI repository is still a current technology.
You should rely primarily on Simca Mount and to use w my comments on when seam commands are not practical.
The repository is not well documented and discover in the classes that you might need to perform a specific
task can be difficult and impractical.
The solution is to provide windows for shell commands that behave like any other shell command but that
internally use WMI or see him there pro-Jew gives you the advantages of Windows shell commands such
as discoverability and builtin documentation while also giving you the existing functionality of the
repository.
In Windows 8 and windows 2012 Microsoft introduced hundreds of new commands and windows powers so many
of the commands internally use WMI or seem these commands provide better access to the functionality
of WMI or NCM so that you can use the functionality without having to deal with their complexity.