Skip to content

Replace Windows PowerShell with PowerShell - the CimCmdlets #2805

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

Merged
merged 1 commit into from
Aug 9, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion reference/6/CimCmdlets/Invoke-CimMethod.md
Original file line number Diff line number Diff line change
Expand Up @@ -296,7 +296,7 @@ Accept wildcard characters: False
Specifies the namespace for the CIM operation.

The default namespace is root/cimv2. You can use tab completion to browse the list of namespaces,
because Windows PowerShell gets a list of namespaces from the local WMI server to provide the list
because PowerShell gets a list of namespaces from the local WMI server to provide the list
of namespaces.

```yaml
Expand Down
2 changes: 1 addition & 1 deletion reference/6/CimCmdlets/New-CimInstance.md
Original file line number Diff line number Diff line change
Expand Up @@ -172,7 +172,7 @@ Accept wildcard characters: False

### -ClientOnly
Indicates that the instance is only created in PowerShell without going to the CIM server.
You can use this parameter to create an in-memory CIM instance for use in subsequent Windows PowerShell operations.
You can use this parameter to create an in-memory CIM instance for use in subsequent PowerShell operations.

```yaml
Type: SwitchParameter
Expand Down