From e743916b0e2680d45163b08f8130c1e9d21b6f1d Mon Sep 17 00:00:00 2001 From: sethvs Date: Sat, 28 Apr 2018 12:49:26 +0300 Subject: [PATCH 1/2] Add about_CimSession.md. --- .../About/about_CimSession.md | 65 +++++++++++++++++++ .../About/about_CimSession.md | 65 +++++++++++++++++++ .../About/about_CimSession.md | 65 +++++++++++++++++++ .../About/about_CimSession.md | 65 +++++++++++++++++++ .../About/about_CimSession.md | 65 +++++++++++++++++++ 5 files changed, 325 insertions(+) create mode 100644 reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md create mode 100644 reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md create mode 100644 reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md create mode 100644 reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md create mode 100644 reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md new file mode 100644 index 000000000000..bb9e91ddb1cd --- /dev/null +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md @@ -0,0 +1,65 @@ +--- +ms.date: 04/28/2018 +schema: 2.0.0 +locale: en-us +keywords: powershell,cmdlet +title: about_CimSession +--- + +# About CimSession + +## SHORT DESCRIPTION + +Describes a CimSession object and the difference between CIM sessions and +Windows PowerShell sessions. + +## LONG DESCRIPTION + +A Common Information Model (CIM) session is a client-side object that +represents a connection to a local computer or a remote computer. You can +use CIM sessions as an alternative to Windows PowerShell sessions +(PSSessions). Both approaches have advantages. + +You can use the New-CimSession cmdlet to create a CIM session that contains +information about a connection, such as computer name, the protocol used +for the connection, session ID, and instance ID. + +After you create a CimSession object that specifies information required to +establish a connection, Windows PowerShell does not establish the +connection immediately. When a cmdlet uses the CIM session, +Windows PowerShell connects to the specified computer, and then, when the +cmdlet finishes, Windows PowerShell terminates the connection. + +If you create a PSSession instead of using a CIM session, +Windows PowerShell validates connection settings, and then establishes and +maintains the connection. If you use CIM sessions, Windows PowerShell +does not open a network connection until needed. For more information about +Windows PowerShell sessions, see [about_PSSessions](about_PSSessions.md). + +### When to Use a CIM Session + +Only cmdlets that work with a Windows Management Infrastructure (WMI) +provider accept CIM sessions. For other cmdlets, use PSSessions. + +When you use a CIM session, Windows PowerShell runs the cmdlet on the +local client. It connects to the WMI provider by using the CIM session. +The target computer does not require Windows PowerShell, or even any +version of the Windows operating system. + +In contrast, a cmdlet run by using a PSSession runs on the target +computer. It requires Windows PowerShell on the target system. +Furthermore, the cmdlet sends data back to the local computer. +Windows PowerShell manages the data sent over the connection, and keeps +the size within the limits set by Windows Remote Management (WinRM). CIM +sessions do not impose the WinRM limits. + +PSSessions only work with WinRM. CimSessions can use DCOM. + +CIM-based Cmdlet Definition XML (CDXML) cmdlets can be written to use any +WMI Provider. All WMI providers use CimSession objects. + +## SEE ALSO + +New-CimSession + +[about_PSSessions](about_PSSessions.md) \ No newline at end of file diff --git a/reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md b/reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md new file mode 100644 index 000000000000..bb9e91ddb1cd --- /dev/null +++ b/reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md @@ -0,0 +1,65 @@ +--- +ms.date: 04/28/2018 +schema: 2.0.0 +locale: en-us +keywords: powershell,cmdlet +title: about_CimSession +--- + +# About CimSession + +## SHORT DESCRIPTION + +Describes a CimSession object and the difference between CIM sessions and +Windows PowerShell sessions. + +## LONG DESCRIPTION + +A Common Information Model (CIM) session is a client-side object that +represents a connection to a local computer or a remote computer. You can +use CIM sessions as an alternative to Windows PowerShell sessions +(PSSessions). Both approaches have advantages. + +You can use the New-CimSession cmdlet to create a CIM session that contains +information about a connection, such as computer name, the protocol used +for the connection, session ID, and instance ID. + +After you create a CimSession object that specifies information required to +establish a connection, Windows PowerShell does not establish the +connection immediately. When a cmdlet uses the CIM session, +Windows PowerShell connects to the specified computer, and then, when the +cmdlet finishes, Windows PowerShell terminates the connection. + +If you create a PSSession instead of using a CIM session, +Windows PowerShell validates connection settings, and then establishes and +maintains the connection. If you use CIM sessions, Windows PowerShell +does not open a network connection until needed. For more information about +Windows PowerShell sessions, see [about_PSSessions](about_PSSessions.md). + +### When to Use a CIM Session + +Only cmdlets that work with a Windows Management Infrastructure (WMI) +provider accept CIM sessions. For other cmdlets, use PSSessions. + +When you use a CIM session, Windows PowerShell runs the cmdlet on the +local client. It connects to the WMI provider by using the CIM session. +The target computer does not require Windows PowerShell, or even any +version of the Windows operating system. + +In contrast, a cmdlet run by using a PSSession runs on the target +computer. It requires Windows PowerShell on the target system. +Furthermore, the cmdlet sends data back to the local computer. +Windows PowerShell manages the data sent over the connection, and keeps +the size within the limits set by Windows Remote Management (WinRM). CIM +sessions do not impose the WinRM limits. + +PSSessions only work with WinRM. CimSessions can use DCOM. + +CIM-based Cmdlet Definition XML (CDXML) cmdlets can be written to use any +WMI Provider. All WMI providers use CimSession objects. + +## SEE ALSO + +New-CimSession + +[about_PSSessions](about_PSSessions.md) \ No newline at end of file diff --git a/reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md b/reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md new file mode 100644 index 000000000000..bb9e91ddb1cd --- /dev/null +++ b/reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md @@ -0,0 +1,65 @@ +--- +ms.date: 04/28/2018 +schema: 2.0.0 +locale: en-us +keywords: powershell,cmdlet +title: about_CimSession +--- + +# About CimSession + +## SHORT DESCRIPTION + +Describes a CimSession object and the difference between CIM sessions and +Windows PowerShell sessions. + +## LONG DESCRIPTION + +A Common Information Model (CIM) session is a client-side object that +represents a connection to a local computer or a remote computer. You can +use CIM sessions as an alternative to Windows PowerShell sessions +(PSSessions). Both approaches have advantages. + +You can use the New-CimSession cmdlet to create a CIM session that contains +information about a connection, such as computer name, the protocol used +for the connection, session ID, and instance ID. + +After you create a CimSession object that specifies information required to +establish a connection, Windows PowerShell does not establish the +connection immediately. When a cmdlet uses the CIM session, +Windows PowerShell connects to the specified computer, and then, when the +cmdlet finishes, Windows PowerShell terminates the connection. + +If you create a PSSession instead of using a CIM session, +Windows PowerShell validates connection settings, and then establishes and +maintains the connection. If you use CIM sessions, Windows PowerShell +does not open a network connection until needed. For more information about +Windows PowerShell sessions, see [about_PSSessions](about_PSSessions.md). + +### When to Use a CIM Session + +Only cmdlets that work with a Windows Management Infrastructure (WMI) +provider accept CIM sessions. For other cmdlets, use PSSessions. + +When you use a CIM session, Windows PowerShell runs the cmdlet on the +local client. It connects to the WMI provider by using the CIM session. +The target computer does not require Windows PowerShell, or even any +version of the Windows operating system. + +In contrast, a cmdlet run by using a PSSession runs on the target +computer. It requires Windows PowerShell on the target system. +Furthermore, the cmdlet sends data back to the local computer. +Windows PowerShell manages the data sent over the connection, and keeps +the size within the limits set by Windows Remote Management (WinRM). CIM +sessions do not impose the WinRM limits. + +PSSessions only work with WinRM. CimSessions can use DCOM. + +CIM-based Cmdlet Definition XML (CDXML) cmdlets can be written to use any +WMI Provider. All WMI providers use CimSession objects. + +## SEE ALSO + +New-CimSession + +[about_PSSessions](about_PSSessions.md) \ No newline at end of file diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md new file mode 100644 index 000000000000..bb9e91ddb1cd --- /dev/null +++ b/reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md @@ -0,0 +1,65 @@ +--- +ms.date: 04/28/2018 +schema: 2.0.0 +locale: en-us +keywords: powershell,cmdlet +title: about_CimSession +--- + +# About CimSession + +## SHORT DESCRIPTION + +Describes a CimSession object and the difference between CIM sessions and +Windows PowerShell sessions. + +## LONG DESCRIPTION + +A Common Information Model (CIM) session is a client-side object that +represents a connection to a local computer or a remote computer. You can +use CIM sessions as an alternative to Windows PowerShell sessions +(PSSessions). Both approaches have advantages. + +You can use the New-CimSession cmdlet to create a CIM session that contains +information about a connection, such as computer name, the protocol used +for the connection, session ID, and instance ID. + +After you create a CimSession object that specifies information required to +establish a connection, Windows PowerShell does not establish the +connection immediately. When a cmdlet uses the CIM session, +Windows PowerShell connects to the specified computer, and then, when the +cmdlet finishes, Windows PowerShell terminates the connection. + +If you create a PSSession instead of using a CIM session, +Windows PowerShell validates connection settings, and then establishes and +maintains the connection. If you use CIM sessions, Windows PowerShell +does not open a network connection until needed. For more information about +Windows PowerShell sessions, see [about_PSSessions](about_PSSessions.md). + +### When to Use a CIM Session + +Only cmdlets that work with a Windows Management Infrastructure (WMI) +provider accept CIM sessions. For other cmdlets, use PSSessions. + +When you use a CIM session, Windows PowerShell runs the cmdlet on the +local client. It connects to the WMI provider by using the CIM session. +The target computer does not require Windows PowerShell, or even any +version of the Windows operating system. + +In contrast, a cmdlet run by using a PSSession runs on the target +computer. It requires Windows PowerShell on the target system. +Furthermore, the cmdlet sends data back to the local computer. +Windows PowerShell manages the data sent over the connection, and keeps +the size within the limits set by Windows Remote Management (WinRM). CIM +sessions do not impose the WinRM limits. + +PSSessions only work with WinRM. CimSessions can use DCOM. + +CIM-based Cmdlet Definition XML (CDXML) cmdlets can be written to use any +WMI Provider. All WMI providers use CimSession objects. + +## SEE ALSO + +New-CimSession + +[about_PSSessions](about_PSSessions.md) \ No newline at end of file diff --git a/reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md b/reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md new file mode 100644 index 000000000000..d74ad7229a25 --- /dev/null +++ b/reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md @@ -0,0 +1,65 @@ +--- +ms.date: 04/28/2018 +schema: 2.0.0 +locale: en-us +keywords: powershell,cmdlet +title: about_CimSession +--- + +# About CimSession + +## SHORT DESCRIPTION + +Describes a CimSession object and the difference between CIM sessions and +Windows PowerShell sessions. + +## LONG DESCRIPTION + +A Common Information Model (CIM) session is a client-side object that +represents a connection to a local computer or a remote computer. You can +use CIM sessions as an alternative to Windows PowerShell sessions +(PSSessions). Both approaches have advantages. + +You can use the [New-CimSession](../../CimCmdlets/New-CimSession.md) cmdlet to create a CIM session that contains +information about a connection, such as computer name, the protocol used +for the connection, session ID, and instance ID. + +After you create a CimSession object that specifies information required to +establish a connection, Windows PowerShell does not establish the +connection immediately. When a cmdlet uses the CIM session, +Windows PowerShell connects to the specified computer, and then, when the +cmdlet finishes, Windows PowerShell terminates the connection. + +If you create a PSSession instead of using a CIM session, +Windows PowerShell validates connection settings, and then establishes and +maintains the connection. If you use CIM sessions, Windows PowerShell +does not open a network connection until needed. For more information about +Windows PowerShell sessions, see [about_PSSessions](about_PSSessions.md). + +### When to Use a CIM Session + +Only cmdlets that work with a Windows Management Infrastructure (WMI) +provider accept CIM sessions. For other cmdlets, use PSSessions. + +When you use a CIM session, Windows PowerShell runs the cmdlet on the +local client. It connects to the WMI provider by using the CIM session. +The target computer does not require Windows PowerShell, or even any +version of the Windows operating system. + +In contrast, a cmdlet run by using a PSSession runs on the target +computer. It requires Windows PowerShell on the target system. +Furthermore, the cmdlet sends data back to the local computer. +Windows PowerShell manages the data sent over the connection, and keeps +the size within the limits set by Windows Remote Management (WinRM). CIM +sessions do not impose the WinRM limits. + +PSSessions only work with WinRM. CimSessions can use DCOM. + +CIM-based Cmdlet Definition XML (CDXML) cmdlets can be written to use any +WMI Provider. All WMI providers use CimSession objects. + +## SEE ALSO + +[New-CimSession](../../CimCmdlets/New-CimSession.md) + +[about_PSSessions](about_PSSessions.md) \ No newline at end of file From 3b26d723bcffc6f84ee0912132cf8c5de76ede1e Mon Sep 17 00:00:00 2001 From: sethvs Date: Tue, 1 May 2018 14:32:59 +0300 Subject: [PATCH 2/2] Implement requested changes. --- .../About/about_CimSession.md | 31 +++++++++---------- .../About/about_CimSession.md | 31 +++++++++---------- .../About/about_CimSession.md | 31 +++++++++---------- .../About/about_CimSession.md | 31 +++++++++---------- .../About/about_CimSession.md | 31 +++++++++---------- 5 files changed, 75 insertions(+), 80 deletions(-) diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md index bb9e91ddb1cd..e2c14bd72198 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md @@ -11,13 +11,13 @@ title: about_CimSession ## SHORT DESCRIPTION Describes a CimSession object and the difference between CIM sessions and -Windows PowerShell sessions. +PowerShell sessions. ## LONG DESCRIPTION A Common Information Model (CIM) session is a client-side object that represents a connection to a local computer or a remote computer. You can -use CIM sessions as an alternative to Windows PowerShell sessions +use CIM sessions as an alternative to PowerShell sessions (PSSessions). Both approaches have advantages. You can use the New-CimSession cmdlet to create a CIM session that contains @@ -25,36 +25,35 @@ information about a connection, such as computer name, the protocol used for the connection, session ID, and instance ID. After you create a CimSession object that specifies information required to -establish a connection, Windows PowerShell does not establish the +establish a connection, PowerShell does not establish the connection immediately. When a cmdlet uses the CIM session, -Windows PowerShell connects to the specified computer, and then, when the -cmdlet finishes, Windows PowerShell terminates the connection. +PowerShell connects to the specified computer, and then, when the +cmdlet finishes, PowerShell terminates the connection. If you create a PSSession instead of using a CIM session, -Windows PowerShell validates connection settings, and then establishes and -maintains the connection. If you use CIM sessions, Windows PowerShell +PowerShell validates connection settings, and then establishes and +maintains the connection. If you use CIM sessions, PowerShell does not open a network connection until needed. For more information about -Windows PowerShell sessions, see [about_PSSessions](about_PSSessions.md). +PowerShell sessions, see [about_PSSessions](about_PSSessions.md). ### When to Use a CIM Session -Only cmdlets that work with a Windows Management Infrastructure (WMI) -provider accept CIM sessions. For other cmdlets, use PSSessions. +Only cmdlets that work with a Windows Management Instrumentation (WMI) +provider or CIM over WS-Man accept CIM sessions. +For other cmdlets, use PSSessions. -When you use a CIM session, Windows PowerShell runs the cmdlet on the +When you use a CIM session, PowerShell runs the cmdlet on the local client. It connects to the WMI provider by using the CIM session. -The target computer does not require Windows PowerShell, or even any +The target computer does not require PowerShell, or even any version of the Windows operating system. In contrast, a cmdlet run by using a PSSession runs on the target -computer. It requires Windows PowerShell on the target system. +computer. It requires PowerShell on the target system. Furthermore, the cmdlet sends data back to the local computer. -Windows PowerShell manages the data sent over the connection, and keeps +PowerShell manages the data sent over the connection, and keeps the size within the limits set by Windows Remote Management (WinRM). CIM sessions do not impose the WinRM limits. -PSSessions only work with WinRM. CimSessions can use DCOM. - CIM-based Cmdlet Definition XML (CDXML) cmdlets can be written to use any WMI Provider. All WMI providers use CimSession objects. diff --git a/reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md b/reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md index bb9e91ddb1cd..e2c14bd72198 100644 --- a/reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md +++ b/reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md @@ -11,13 +11,13 @@ title: about_CimSession ## SHORT DESCRIPTION Describes a CimSession object and the difference between CIM sessions and -Windows PowerShell sessions. +PowerShell sessions. ## LONG DESCRIPTION A Common Information Model (CIM) session is a client-side object that represents a connection to a local computer or a remote computer. You can -use CIM sessions as an alternative to Windows PowerShell sessions +use CIM sessions as an alternative to PowerShell sessions (PSSessions). Both approaches have advantages. You can use the New-CimSession cmdlet to create a CIM session that contains @@ -25,36 +25,35 @@ information about a connection, such as computer name, the protocol used for the connection, session ID, and instance ID. After you create a CimSession object that specifies information required to -establish a connection, Windows PowerShell does not establish the +establish a connection, PowerShell does not establish the connection immediately. When a cmdlet uses the CIM session, -Windows PowerShell connects to the specified computer, and then, when the -cmdlet finishes, Windows PowerShell terminates the connection. +PowerShell connects to the specified computer, and then, when the +cmdlet finishes, PowerShell terminates the connection. If you create a PSSession instead of using a CIM session, -Windows PowerShell validates connection settings, and then establishes and -maintains the connection. If you use CIM sessions, Windows PowerShell +PowerShell validates connection settings, and then establishes and +maintains the connection. If you use CIM sessions, PowerShell does not open a network connection until needed. For more information about -Windows PowerShell sessions, see [about_PSSessions](about_PSSessions.md). +PowerShell sessions, see [about_PSSessions](about_PSSessions.md). ### When to Use a CIM Session -Only cmdlets that work with a Windows Management Infrastructure (WMI) -provider accept CIM sessions. For other cmdlets, use PSSessions. +Only cmdlets that work with a Windows Management Instrumentation (WMI) +provider or CIM over WS-Man accept CIM sessions. +For other cmdlets, use PSSessions. -When you use a CIM session, Windows PowerShell runs the cmdlet on the +When you use a CIM session, PowerShell runs the cmdlet on the local client. It connects to the WMI provider by using the CIM session. -The target computer does not require Windows PowerShell, or even any +The target computer does not require PowerShell, or even any version of the Windows operating system. In contrast, a cmdlet run by using a PSSession runs on the target -computer. It requires Windows PowerShell on the target system. +computer. It requires PowerShell on the target system. Furthermore, the cmdlet sends data back to the local computer. -Windows PowerShell manages the data sent over the connection, and keeps +PowerShell manages the data sent over the connection, and keeps the size within the limits set by Windows Remote Management (WinRM). CIM sessions do not impose the WinRM limits. -PSSessions only work with WinRM. CimSessions can use DCOM. - CIM-based Cmdlet Definition XML (CDXML) cmdlets can be written to use any WMI Provider. All WMI providers use CimSession objects. diff --git a/reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md b/reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md index bb9e91ddb1cd..e2c14bd72198 100644 --- a/reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md +++ b/reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md @@ -11,13 +11,13 @@ title: about_CimSession ## SHORT DESCRIPTION Describes a CimSession object and the difference between CIM sessions and -Windows PowerShell sessions. +PowerShell sessions. ## LONG DESCRIPTION A Common Information Model (CIM) session is a client-side object that represents a connection to a local computer or a remote computer. You can -use CIM sessions as an alternative to Windows PowerShell sessions +use CIM sessions as an alternative to PowerShell sessions (PSSessions). Both approaches have advantages. You can use the New-CimSession cmdlet to create a CIM session that contains @@ -25,36 +25,35 @@ information about a connection, such as computer name, the protocol used for the connection, session ID, and instance ID. After you create a CimSession object that specifies information required to -establish a connection, Windows PowerShell does not establish the +establish a connection, PowerShell does not establish the connection immediately. When a cmdlet uses the CIM session, -Windows PowerShell connects to the specified computer, and then, when the -cmdlet finishes, Windows PowerShell terminates the connection. +PowerShell connects to the specified computer, and then, when the +cmdlet finishes, PowerShell terminates the connection. If you create a PSSession instead of using a CIM session, -Windows PowerShell validates connection settings, and then establishes and -maintains the connection. If you use CIM sessions, Windows PowerShell +PowerShell validates connection settings, and then establishes and +maintains the connection. If you use CIM sessions, PowerShell does not open a network connection until needed. For more information about -Windows PowerShell sessions, see [about_PSSessions](about_PSSessions.md). +PowerShell sessions, see [about_PSSessions](about_PSSessions.md). ### When to Use a CIM Session -Only cmdlets that work with a Windows Management Infrastructure (WMI) -provider accept CIM sessions. For other cmdlets, use PSSessions. +Only cmdlets that work with a Windows Management Instrumentation (WMI) +provider or CIM over WS-Man accept CIM sessions. +For other cmdlets, use PSSessions. -When you use a CIM session, Windows PowerShell runs the cmdlet on the +When you use a CIM session, PowerShell runs the cmdlet on the local client. It connects to the WMI provider by using the CIM session. -The target computer does not require Windows PowerShell, or even any +The target computer does not require PowerShell, or even any version of the Windows operating system. In contrast, a cmdlet run by using a PSSession runs on the target -computer. It requires Windows PowerShell on the target system. +computer. It requires PowerShell on the target system. Furthermore, the cmdlet sends data back to the local computer. -Windows PowerShell manages the data sent over the connection, and keeps +PowerShell manages the data sent over the connection, and keeps the size within the limits set by Windows Remote Management (WinRM). CIM sessions do not impose the WinRM limits. -PSSessions only work with WinRM. CimSessions can use DCOM. - CIM-based Cmdlet Definition XML (CDXML) cmdlets can be written to use any WMI Provider. All WMI providers use CimSession objects. diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md index bb9e91ddb1cd..e2c14bd72198 100644 --- a/reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md +++ b/reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md @@ -11,13 +11,13 @@ title: about_CimSession ## SHORT DESCRIPTION Describes a CimSession object and the difference between CIM sessions and -Windows PowerShell sessions. +PowerShell sessions. ## LONG DESCRIPTION A Common Information Model (CIM) session is a client-side object that represents a connection to a local computer or a remote computer. You can -use CIM sessions as an alternative to Windows PowerShell sessions +use CIM sessions as an alternative to PowerShell sessions (PSSessions). Both approaches have advantages. You can use the New-CimSession cmdlet to create a CIM session that contains @@ -25,36 +25,35 @@ information about a connection, such as computer name, the protocol used for the connection, session ID, and instance ID. After you create a CimSession object that specifies information required to -establish a connection, Windows PowerShell does not establish the +establish a connection, PowerShell does not establish the connection immediately. When a cmdlet uses the CIM session, -Windows PowerShell connects to the specified computer, and then, when the -cmdlet finishes, Windows PowerShell terminates the connection. +PowerShell connects to the specified computer, and then, when the +cmdlet finishes, PowerShell terminates the connection. If you create a PSSession instead of using a CIM session, -Windows PowerShell validates connection settings, and then establishes and -maintains the connection. If you use CIM sessions, Windows PowerShell +PowerShell validates connection settings, and then establishes and +maintains the connection. If you use CIM sessions, PowerShell does not open a network connection until needed. For more information about -Windows PowerShell sessions, see [about_PSSessions](about_PSSessions.md). +PowerShell sessions, see [about_PSSessions](about_PSSessions.md). ### When to Use a CIM Session -Only cmdlets that work with a Windows Management Infrastructure (WMI) -provider accept CIM sessions. For other cmdlets, use PSSessions. +Only cmdlets that work with a Windows Management Instrumentation (WMI) +provider or CIM over WS-Man accept CIM sessions. +For other cmdlets, use PSSessions. -When you use a CIM session, Windows PowerShell runs the cmdlet on the +When you use a CIM session, PowerShell runs the cmdlet on the local client. It connects to the WMI provider by using the CIM session. -The target computer does not require Windows PowerShell, or even any +The target computer does not require PowerShell, or even any version of the Windows operating system. In contrast, a cmdlet run by using a PSSession runs on the target -computer. It requires Windows PowerShell on the target system. +computer. It requires PowerShell on the target system. Furthermore, the cmdlet sends data back to the local computer. -Windows PowerShell manages the data sent over the connection, and keeps +PowerShell manages the data sent over the connection, and keeps the size within the limits set by Windows Remote Management (WinRM). CIM sessions do not impose the WinRM limits. -PSSessions only work with WinRM. CimSessions can use DCOM. - CIM-based Cmdlet Definition XML (CDXML) cmdlets can be written to use any WMI Provider. All WMI providers use CimSession objects. diff --git a/reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md b/reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md index d74ad7229a25..3f472f3b9ce5 100644 --- a/reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md +++ b/reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md @@ -11,13 +11,13 @@ title: about_CimSession ## SHORT DESCRIPTION Describes a CimSession object and the difference between CIM sessions and -Windows PowerShell sessions. +PowerShell sessions. ## LONG DESCRIPTION A Common Information Model (CIM) session is a client-side object that represents a connection to a local computer or a remote computer. You can -use CIM sessions as an alternative to Windows PowerShell sessions +use CIM sessions as an alternative to PowerShell sessions (PSSessions). Both approaches have advantages. You can use the [New-CimSession](../../CimCmdlets/New-CimSession.md) cmdlet to create a CIM session that contains @@ -25,36 +25,35 @@ information about a connection, such as computer name, the protocol used for the connection, session ID, and instance ID. After you create a CimSession object that specifies information required to -establish a connection, Windows PowerShell does not establish the +establish a connection, PowerShell does not establish the connection immediately. When a cmdlet uses the CIM session, -Windows PowerShell connects to the specified computer, and then, when the -cmdlet finishes, Windows PowerShell terminates the connection. +PowerShell connects to the specified computer, and then, when the +cmdlet finishes, PowerShell terminates the connection. If you create a PSSession instead of using a CIM session, -Windows PowerShell validates connection settings, and then establishes and -maintains the connection. If you use CIM sessions, Windows PowerShell +PowerShell validates connection settings, and then establishes and +maintains the connection. If you use CIM sessions, PowerShell does not open a network connection until needed. For more information about -Windows PowerShell sessions, see [about_PSSessions](about_PSSessions.md). +PowerShell sessions, see [about_PSSessions](about_PSSessions.md). ### When to Use a CIM Session -Only cmdlets that work with a Windows Management Infrastructure (WMI) -provider accept CIM sessions. For other cmdlets, use PSSessions. +Only cmdlets that work with a Windows Management Instrumentation (WMI) +provider or CIM over WS-Man accept CIM sessions. +For other cmdlets, use PSSessions. -When you use a CIM session, Windows PowerShell runs the cmdlet on the +When you use a CIM session, PowerShell runs the cmdlet on the local client. It connects to the WMI provider by using the CIM session. -The target computer does not require Windows PowerShell, or even any +The target computer does not require PowerShell, or even any version of the Windows operating system. In contrast, a cmdlet run by using a PSSession runs on the target -computer. It requires Windows PowerShell on the target system. +computer. It requires PowerShell on the target system. Furthermore, the cmdlet sends data back to the local computer. -Windows PowerShell manages the data sent over the connection, and keeps +PowerShell manages the data sent over the connection, and keeps the size within the limits set by Windows Remote Management (WinRM). CIM sessions do not impose the WinRM limits. -PSSessions only work with WinRM. CimSessions can use DCOM. - CIM-based Cmdlet Definition XML (CDXML) cmdlets can be written to use any WMI Provider. All WMI providers use CimSession objects.