Copy about_WMI to 7.x

Author: sdwheeler

reference/7.4/Microsoft.PowerShell.Core/About/about_WMI.md

@@ -0,0 +1,110 @@
+---
+description: Windows Management Instrumentation (WMI) uses the Common Information Model (CIM) to represent systems, applications, networks, devices, and other manageable components of the modern enterprise.
+Locale: en-US
+ms.date: 01/03/2018
+online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_wmi?view=powershell-7.4&WT.mc_id=ps-gethelp
+schema: 2.0.0
+title: about_WMI
+---
+
+# about_WMI
+
+## Short description
+
+Windows Management Instrumentation (WMI) uses the Common Information Model
+(CIM) to represent systems, applications, networks, devices, and other
+manageable components of the modern enterprise.
+
+## Long description
+
+Windows Management Instrumentation (WMI) is Microsoft's implementation of
+Web-Based Enterprise Management (WBEM), the industry standard.
+
+Classic WMI uses DCOM to communicate with networked devices to manage remote
+systems. Windows PowerShell 3.0 introduces a CIM provider model that uses WinRM
+to remove the dependency on DCOM. This CIM provider model also uses new WMI
+provider APIs that enable developers to write Windows PowerShell cmdlets in
+native code (C++).
+
+Don't confuse WMI providers with Windows PowerShell providers. Many Windows
+features have an associated WMI provider that exposes their management
+capabilities. To get WMI providers, run a WMI query that gets instances of the
+**__Provider** WMI class, such as the following query.
+
+```powershell
+Get-WmiObject -Class __Provider
+```
+
+## Three components of WMI
+
+The following three components of WMI interact with Windows PowerShell:
+Namespaces, Providers, and Classes.
+
+WMI Namespaces organize WMI providers and WMI classes into groups of related
+components. In this way, they're similar to .NET Framework namespaces.
+Namespaces aren't physical locations, but are more like logical databases. All
+WMI namespaces are instances of the __Namespace system class. The default WMI
+namespace is **root/CIMV2** (since Microsoft Windows 2000). To use Windows
+PowerShell to get WMI namespaces in the current session, use a command with the
+following format.
+
+```powershell
+Get-WmiObject -Class __Namespace
+```
+
+To get WMI namespaces in other namespaces, use the Namespace parameter to
+change the location of the search. The following command finds WMI namespaces
+that reside in the **root/CIMV2/Applications** namespace.
+
+```powershell
+Get-WmiObject -Class __Namespace -Namespace root/CIMV2/Applications
+```
+
+WMI namespaces are hierarchical. Therefore, obtaining a list of all namespaces
+on a particular system requires performing a recursive query starting at the
+root namespace.
+
+WMI Providers expose information about Windows manageable objects. A provider
+retrieves data from a component, and passes that data through WMI to a
+management application, such as Windows PowerShell. Most WMI providers are
+dynamic providers, which means that they obtain the data dynamically when it's
+requested through the management application.
+
+## Finding WMI classes
+
+In a default Windows 8 installation, there are more than 1,100 WMI classes in
+**root/CIMV2**. With this many WMI classes, the challenge becomes identifying
+the appropriate WMI class to use to perform a specific task. Windows PowerShell
+3.0 provides two ways to find WMI classes that are related to a specific topic.
+
+For example, to find WMI classes in the **root/CIMV2** WMI namespace that are
+related to disks, you can use a query such as the one shown here.
+
+```powershell
+Get-WmiObject -List *Disk*
+```
+
+To find WMI classes that are related to memory, you might use a query such as
+the one shown here.
+
+```powershell
+Get-WmiObject -List *Memory*
+```
+
+The CIM cmdlets also provide the ability to discover WMI classes. To do this,
+use the `Get-CimClass` cmdlet. The command shown here lists WMI classes related
+to video.
+
+```powershell
+Get-CimClass *Video*
+```
+
+Tab expansion works when changing WMI namespaces, and therefore use of tab
+expansion makes sub-WMI namespaces easily discoverable. In the following
+example, the `Get-CimClass` cmdlet lists WMI classes related to power settings.
+To find it, type the **root/CIMV2** namespace and then press the Tab key
+several times until the **power** namespace appears. Here is the command:
+
+```powershell
+Get-CimClass *Power* -Namespace root/CIMV2/power
+```

reference/7.4/Microsoft.PowerShell.Core/About/about_WQL.md

@@ -712,10 +712,8 @@ Get-CimInstance -Query $q
 - [about_Special_Characters][02]
 - [about_Quoting_Rules][01]
 - [about_WMI][04]
-- [about_WMI_Cmdlets][03]
 
 <!-- link references -->
 [01]: about_Quoting_Rules.md
 [02]: about_Special_Characters.md
-[03]: about_WMI_Cmdlets.md
 [04]: about_WMI.md

reference/7.5/Microsoft.PowerShell.Core/About/about_WMI.md

@@ -0,0 +1,110 @@
+---
+description: Windows Management Instrumentation (WMI) uses the Common Information Model (CIM) to represent systems, applications, networks, devices, and other manageable components of the modern enterprise.
+Locale: en-US
+ms.date: 01/03/2018
+online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_wmi?view=powershell-7.5&WT.mc_id=ps-gethelp
+schema: 2.0.0
+title: about_WMI
+---
+
+# about_WMI
+
+## Short description
+
+Windows Management Instrumentation (WMI) uses the Common Information Model
+(CIM) to represent systems, applications, networks, devices, and other
+manageable components of the modern enterprise.
+
+## Long description
+
+Windows Management Instrumentation (WMI) is Microsoft's implementation of
+Web-Based Enterprise Management (WBEM), the industry standard.
+
+Classic WMI uses DCOM to communicate with networked devices to manage remote
+systems. Windows PowerShell 3.0 introduces a CIM provider model that uses WinRM
+to remove the dependency on DCOM. This CIM provider model also uses new WMI
+provider APIs that enable developers to write Windows PowerShell cmdlets in
+native code (C++).
+
+Don't confuse WMI providers with Windows PowerShell providers. Many Windows
+features have an associated WMI provider that exposes their management
+capabilities. To get WMI providers, run a WMI query that gets instances of the
+**__Provider** WMI class, such as the following query.
+
+```powershell
+Get-WmiObject -Class __Provider
+```
+
+## Three components of WMI
+
+The following three components of WMI interact with Windows PowerShell:
+Namespaces, Providers, and Classes.
+
+WMI Namespaces organize WMI providers and WMI classes into groups of related
+components. In this way, they're similar to .NET Framework namespaces.
+Namespaces aren't physical locations, but are more like logical databases. All
+WMI namespaces are instances of the __Namespace system class. The default WMI
+namespace is **root/CIMV2** (since Microsoft Windows 2000). To use Windows
+PowerShell to get WMI namespaces in the current session, use a command with the
+following format.
+
+```powershell
+Get-WmiObject -Class __Namespace
+```
+
+To get WMI namespaces in other namespaces, use the Namespace parameter to
+change the location of the search. The following command finds WMI namespaces
+that reside in the **root/CIMV2/Applications** namespace.
+
+```powershell
+Get-WmiObject -Class __Namespace -Namespace root/CIMV2/Applications
+```
+
+WMI namespaces are hierarchical. Therefore, obtaining a list of all namespaces
+on a particular system requires performing a recursive query starting at the
+root namespace.
+
+WMI Providers expose information about Windows manageable objects. A provider
+retrieves data from a component, and passes that data through WMI to a
+management application, such as Windows PowerShell. Most WMI providers are
+dynamic providers, which means that they obtain the data dynamically when it's
+requested through the management application.
+
+## Finding WMI classes
+
+In a default Windows 8 installation, there are more than 1,100 WMI classes in
+**root/CIMV2**. With this many WMI classes, the challenge becomes identifying
+the appropriate WMI class to use to perform a specific task. Windows PowerShell
+3.0 provides two ways to find WMI classes that are related to a specific topic.
+
+For example, to find WMI classes in the **root/CIMV2** WMI namespace that are
+related to disks, you can use a query such as the one shown here.
+
+```powershell
+Get-WmiObject -List *Disk*
+```
+
+To find WMI classes that are related to memory, you might use a query such as
+the one shown here.
+
+```powershell
+Get-WmiObject -List *Memory*
+```
+
+The CIM cmdlets also provide the ability to discover WMI classes. To do this,
+use the `Get-CimClass` cmdlet. The command shown here lists WMI classes related
+to video.
+
+```powershell
+Get-CimClass *Video*
+```
+
+Tab expansion works when changing WMI namespaces, and therefore use of tab
+expansion makes sub-WMI namespaces easily discoverable. In the following
+example, the `Get-CimClass` cmdlet lists WMI classes related to power settings.
+To find it, type the **root/CIMV2** namespace and then press the Tab key
+several times until the **power** namespace appears. Here is the command:
+
+```powershell
+Get-CimClass *Power* -Namespace root/CIMV2/power
+```

reference/7.5/Microsoft.PowerShell.Core/About/about_WQL.md

@@ -712,10 +712,8 @@ Get-CimInstance -Query $q
 - [about_Special_Characters][02]
 - [about_Quoting_Rules][01]
 - [about_WMI][04]
-- [about_WMI_Cmdlets][03]
 
 <!-- link references -->
 [01]: about_Quoting_Rules.md
 [02]: about_Special_Characters.md
-[03]: about_WMI_Cmdlets.md
 [04]: about_WMI.md

reference/7.6/Microsoft.PowerShell.Core/About/about_WMI.md

@@ -0,0 +1,110 @@
+---
+description: Windows Management Instrumentation (WMI) uses the Common Information Model (CIM) to represent systems, applications, networks, devices, and other manageable components of the modern enterprise.
+Locale: en-US
+ms.date: 01/03/2018
+online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_wmi?view=powershell-7.6&WT.mc_id=ps-gethelp
+schema: 2.0.0
+title: about_WMI
+---
+
+# about_WMI
+
+## Short description
+
+Windows Management Instrumentation (WMI) uses the Common Information Model
+(CIM) to represent systems, applications, networks, devices, and other
+manageable components of the modern enterprise.
+
+## Long description
+
+Windows Management Instrumentation (WMI) is Microsoft's implementation of
+Web-Based Enterprise Management (WBEM), the industry standard.
+
+Classic WMI uses DCOM to communicate with networked devices to manage remote
+systems. Windows PowerShell 3.0 introduces a CIM provider model that uses WinRM
+to remove the dependency on DCOM. This CIM provider model also uses new WMI
+provider APIs that enable developers to write Windows PowerShell cmdlets in
+native code (C++).
+
+Don't confuse WMI providers with Windows PowerShell providers. Many Windows
+features have an associated WMI provider that exposes their management
+capabilities. To get WMI providers, run a WMI query that gets instances of the
+**__Provider** WMI class, such as the following query.
+
+```powershell
+Get-WmiObject -Class __Provider
+```
+
+## Three components of WMI
+
+The following three components of WMI interact with Windows PowerShell:
+Namespaces, Providers, and Classes.
+
+WMI Namespaces organize WMI providers and WMI classes into groups of related
+components. In this way, they're similar to .NET Framework namespaces.
+Namespaces aren't physical locations, but are more like logical databases. All
+WMI namespaces are instances of the __Namespace system class. The default WMI
+namespace is **root/CIMV2** (since Microsoft Windows 2000). To use Windows
+PowerShell to get WMI namespaces in the current session, use a command with the
+following format.
+
+```powershell
+Get-WmiObject -Class __Namespace
+```
+
+To get WMI namespaces in other namespaces, use the Namespace parameter to
+change the location of the search. The following command finds WMI namespaces
+that reside in the **root/CIMV2/Applications** namespace.
+
+```powershell
+Get-WmiObject -Class __Namespace -Namespace root/CIMV2/Applications
+```
+
+WMI namespaces are hierarchical. Therefore, obtaining a list of all namespaces
+on a particular system requires performing a recursive query starting at the
+root namespace.
+
+WMI Providers expose information about Windows manageable objects. A provider
+retrieves data from a component, and passes that data through WMI to a
+management application, such as Windows PowerShell. Most WMI providers are
+dynamic providers, which means that they obtain the data dynamically when it's
+requested through the management application.
+
+## Finding WMI classes
+
+In a default Windows 8 installation, there are more than 1,100 WMI classes in
+**root/CIMV2**. With this many WMI classes, the challenge becomes identifying
+the appropriate WMI class to use to perform a specific task. Windows PowerShell
+3.0 provides two ways to find WMI classes that are related to a specific topic.
+
+For example, to find WMI classes in the **root/CIMV2** WMI namespace that are
+related to disks, you can use a query such as the one shown here.
+
+```powershell
+Get-WmiObject -List *Disk*
+```
+
+To find WMI classes that are related to memory, you might use a query such as
+the one shown here.
+
+```powershell
+Get-WmiObject -List *Memory*
+```
+
+The CIM cmdlets also provide the ability to discover WMI classes. To do this,
+use the `Get-CimClass` cmdlet. The command shown here lists WMI classes related
+to video.
+
+```powershell
+Get-CimClass *Video*
+```
+
+Tab expansion works when changing WMI namespaces, and therefore use of tab
+expansion makes sub-WMI namespaces easily discoverable. In the following
+example, the `Get-CimClass` cmdlet lists WMI classes related to power settings.
+To find it, type the **root/CIMV2** namespace and then press the Tab key
+several times until the **power** namespace appears. Here is the command:
+
+```powershell
+Get-CimClass *Power* -Namespace root/CIMV2/power
+```