-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Add about_CimSession.md. #2373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add about_CimSession.md. #2373
Conversation
|
@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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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).
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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).
There was a problem hiding this comment.
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.
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| reference/3.0/Microsoft.PowerShell.Core/About/about_CimSession.md | Details | ||
| reference/4.0/Microsoft.PowerShell.Core/About/about_CimSession.md | Details | ||
| reference/5.0/Microsoft.PowerShell.Core/About/about_CimSession.md | Details | ||
| reference/5.1/Microsoft.PowerShell.Core/About/about_CimSession.md | Details | ||
| reference/6/Microsoft.PowerShell.Core/About/about_CimSession.md | 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.
Version(s) of document impacted