Skip to content

Conversation

@sethvs
Copy link
Contributor

@sethvs sethvs commented Apr 28, 2018

Version(s) of document impacted

  • Impacts 6.1 document
  • Impacts 6.0 document
  • Impacts 5.1 document
  • Impacts 5.0 document
  • Impacts 4.0 document
  • Impacts 3.0 document

@zjalexander
Copy link
Contributor

⚠️ Validation status: warnings

File Status Preview URL Details
reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md ⚠️Warning Details
reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md ⚠️Warning Details
reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md ⚠️Warning Details
reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md ⚠️Warning Details
reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md ⚠️Warning Details

reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md

  • [Warning] Ignore metadata: locale. They are generated by open publish.

reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md

  • [Warning] Ignore metadata: locale. They are generated by open publish.

reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md

  • [Warning] Ignore metadata: locale. They are generated by open publish.

reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md

  • [Warning] Ignore metadata: locale. They are generated by open publish.

reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md

  • [Warning] Ignore metadata: locale. They are generated by open publish.

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@sdwheeler sdwheeler requested a review from SteveL-MSFT April 30, 2018 14:06
@sdwheeler
Copy link
Collaborator

@SteveL-MSFT Please review

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PSSessions also work with SSH (with PSCore6), PowerShell Direct (VMBus to containers/VMs), named pipes locally. Might be better to exclude this line.

Copy link
Contributor Author

@sethvs sethvs May 1, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed.

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless something is "Windows PowerShell" specific, we should just use "PowerShell" (applies throughout the doc).

Copy link
Contributor Author

@sethvs sethvs May 1, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.
Should we remove 'Windows' from 'Windows PowerShell sessions' as well?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

er - yes?!!

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WMI actually stands for Windows Management Instrumentation, although this statement isn't complete. You can use CIM sessions against any CIM over WS-Man endpoint (Dell iDrac, HP iLO, are examples).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added CIM over WS-Man.

@zjalexander
Copy link
Contributor

⚠️ Validation status: warnings

File Status Preview URL Details
reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md ⚠️Warning Details
reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md ⚠️Warning Details
reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md ⚠️Warning Details
reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md ⚠️Warning Details
reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md ⚠️Warning Details

reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md

  • [Warning] Ignore metadata: locale. They are generated by open publish.

reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md

  • [Warning] Ignore metadata: locale. They are generated by open publish.

reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md

  • [Warning] Ignore metadata: locale. They are generated by open publish.

reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md

  • [Warning] Ignore metadata: locale. They are generated by open publish.

reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md

  • [Warning] Ignore metadata: locale. They are generated by open publish.

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@sdwheeler sdwheeler merged commit 1b0b1c4 into MicrosoftDocs:staging May 2, 2018
@sethvs sethvs deleted the aboutCimSession branch May 2, 2018 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants