diff --git a/reference/3.0/CimCmdlets/Get-CimAssociatedInstance.md b/reference/3.0/CimCmdlets/Get-CimAssociatedInstance.md index 37635e01bcf1..c50b6d990ba9 100644 --- a/reference/3.0/CimCmdlets/Get-CimAssociatedInstance.md +++ b/reference/3.0/CimCmdlets/Get-CimAssociatedInstance.md @@ -27,14 +27,20 @@ Get-CimAssociatedInstance [[-Association] ] [-ResultClassName ] ``` ## DESCRIPTION -The Get-CimAssociatedInstance cmdlet retrieves the CIM instances connected to a specific CIM instance, called the source instance, by an association. +The Get-CimAssociatedInstance cmdlet retrieves the CIM instances connected to a specific CIM +instance, called the source instance, by an association. -In an association, each CIM instance has a named role and the same CIM instance can participate in an association in different roles. +In an association, each CIM instance has a named role and the same CIM instance can participate in +an association in different roles. -If the InputObject parameter is not specified, the cmdlet works in one of the following ways: +If the InputObject parameter is not specified, the cmdlet works in one of the following ways: ---If neither the ComputerName parameter nor the CimSession parameter is specified, then this cmdlet works on local Windows Management Instrumentation (WMI) using a Component Object Model (COM) session. ---If either the ComputerName parameter or the CimSession parameter is specified, then this cmdlet works against the CIM server specified by either the ComputerName parameter or the CimSession parameter. +- If neither the ComputerName parameter nor the CimSession parameter is specified, then this cmdlet + works on local Windows Management Instrumentation (WMI) using a Component Object Model (COM) + session. +- If either the ComputerName parameter or the CimSession parameter is specified, then this cmdlet + works against the CIM server specified by either the ComputerName parameter or the CimSession + parameter. ## EXAMPLES @@ -42,64 +48,58 @@ If the InputObject parameter is not specified, the cmdlet works in one of the fo ``` PS C:\>$disk = Get-CimInstance -ClassName Win32_LogicalDisk -KeyOnly - PS C:\>Get-CimAssociatedInstance -InputObject $disk[1] ``` -This set of commands retrieves the instances of the class named Win32_LogicalDisk and stores the information in a variable named $disk using the Get-CimInstance cmdlet. -The first logical disk instance in the variable is then used as the input object for the Get-CimAssociatedInstance cmdlet to get all the associated CIM instances of the specified CIM instance. +This set of commands retrieves the instances of the class named Win32_LogicalDisk and stores the +information in a variable named $disk using the Get-CimInstance cmdlet. The first logical disk +instance in the variable is then used as the input object for the Get-CimAssociatedInstance cmdlet +to get all the associated CIM instances of the specified CIM instance. ### Example 2: Get all the associated instances of a specific type ``` PS C:\>$disk = Get-CimInstance -ClassName Win32_LogicalDisk -KeyOnly - PS C:\>Get-CimAssociatedInstance -InputObject $disk[1] -ResultClass Win32_DiskPartition ``` -This set of commands retrieves all of the instances of the class named Win32_LogicalDisk and stores them in a variable named $disk. -The first logical disk instance in the variable is then used as the input object for the Get-CimAssociatedInstance cmdlet to get all the associated instances that are associated through the specified association class Win32_DiskPartition. +This set of commands retrieves all of the instances of the class named Win32_LogicalDisk and stores +them in a variable named $disk. The first logical disk instance in the variable is then used as the +input object for the Get-CimAssociatedInstance cmdlet to get all the associated instances that are +associated through the specified association class Win32_DiskPartition. ### Example 3: Get all the associated instances through qualifier of a specific class ``` -PS C:\>$s = Get-CimInstance -Query "Select * from Win32_Service where name like ꞌWinmgmtꞌ" - - +PS C:\>$s = Get-CimInstance -Query "Select * from Win32_Service where name like 'Winmgmt'" PS C:\>Get-CimClass -ClassName *Service* -Qualifier "Association" - - PS C:\>$c.CimClasName Win32_LoadOrderGroupServiceDependencies - - Win32_DependentService - - Win32_SystemServices - - Win32_LoadOrderGroupServiceMembers - - Win32_ServiceSpecificationService - PS C:\>Get-CimAssociatedInstance -InputObject $s -Association Win32_DependentService ``` -This set of commands retrieves the services that depend on Windows Management Instrumentation (WMI) service and stores them in a variable named $s. -The association class name for the Win32_DependentService is retrieved using the Get-CimClass cmdlet by specifying Association as the qualifier and is then passed with $s to the Get-CimAssociatedInstance cmdlet to get all the associated instances of the retrieved association class. +This set of commands retrieves the services that depend on Windows Management Instrumentation (WMI) +service and stores them in a variable named $s. The association class name for the +Win32_DependentService is retrieved using the Get-CimClass cmdlet by specifying Association as the +qualifier and is then passed with $s to the Get-CimAssociatedInstance cmdlet to get all the +associated instances of the retrieved association class. ## PARAMETERS ### -Association Specifies the name of the association class. -If you do not specify this parameter, the cmdlet returns all existing association objects irrespective of their type. +If you do not specify this parameter, the cmdlet returns all existing association objects +irrespective of their type. -For example, if class A is associated with class B through two associations, AB1 and AB2, then this parameter can be used to specify the type of association, either AB1 or AB2. +For example, if class A is associated with class B through two associations, AB1 and AB2, then this +parameter can be used to specify the type of association, either AB1 or AB2. ```yaml Type: String @@ -114,9 +114,9 @@ Accept wildcard characters: False ``` ### -CimSession -Runs the command using the specified CIM session. -Enter a variable that contains the CIM session, or a command that creates or gets the CIM session, such as New-CimSession or Get-CimSession. -For more information, see about_CimSessions. +Runs the command using the specified CIM session. Enter a variable that contains the CIM session, or +a command that creates or gets the CIM session, such as New-CimSession or Get-CimSession. For more +information, see about_CimSessions. ```yaml Type: CimSession[] @@ -134,11 +134,14 @@ Accept wildcard characters: False Specifies the name of the computer on which you want to run the CIM operation. You can specify a fully qualified domain name (FQDN) or a NetBIOS name. -If you specify this parameter, the cmdlet creates a temporary session to the specified computer using the WsMan protocol. +If you specify this parameter, the cmdlet creates a temporary session to the specified computer +using the WsMan protocol. -If you do not specify this parameter, the cmdlet performs the operation on the local computer using Component Object Model (COM). +If you do not specify this parameter, the cmdlet performs the operation on the local computer using +Component Object Model (COM). -If multiple operations are being performed on the same computer, connecting using a CIM session gives better performance. +If multiple operations are being performed on the same computer, connecting using a CIM session +gives better performance. ```yaml Type: String[] @@ -189,7 +192,10 @@ Accept wildcard characters: False Specifies the namespace for the CIM operation. The default namespace is root/cimv2. -NOTE: 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 of namespaces. + +> [!NOTE] +> 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 of namespaces. ```yaml Type: String @@ -206,9 +212,12 @@ Accept wildcard characters: False ### -OperationTimeoutSec Specifies the amount of time that the cmdlet waits for a response from the computer. -By default, the value of this parameter is 0, which means that the cmdlet uses the default timeout value for the server. +By default, the value of this parameter is 0, which means that the cmdlet uses the default timeout +value for the server. -If the OperationTimeoutSec parameter is set to a value less than the robust connection retry timeout of 3 minutes, network failures that last more than the value of the OperationTimeoutSec parameter are not recoverable, because the operation on the server times out before the client can reconnect. +If the OperationTimeoutSec parameter is set to a value less than the robust connection retry timeout +of 3 minutes, network failures that last more than the value of the OperationTimeoutSec parameter +are not recoverable, because the operation on the server times out before the client can reconnect. ```yaml Type: UInt32 @@ -223,21 +232,26 @@ Accept wildcard characters: False ``` ### -ResourceUri -Specifies the resource uniform resource identifier (URI) of the resource class or instance. -The URI is used to identify a specific type of resource, such as disks or processes, on a computer. +Specifies the resource uniform resource identifier (URI) of the resource class or instance. The URI +is used to identify a specific type of resource, such as disks or processes, on a computer. A URI consists of a prefix and a path to a resource. For example: -http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_LogicalDisk -http://intel.com/wbem/wscim/1/amt-schema/1/AMT_GeneralSettings +- `http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_LogicalDisk` +- `http://intel.com/wbem/wscim/1/amt-schema/1/AMT_GeneralSettings` -By default, if you do not specify this parameter, the DMTF standard resource URI http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/ is used and the class name is appended to it. +By default, if you do not specify this parameter, the DMTF standard resource URI +`http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/` is used and the class name is appended to it. -ResourceURI can only be used with CIM sessions created using the WSMan protocol, or when specifying the ComputerName parameter, which creates a CIM session using WSMan. -If you specify this parameter without specifying the ComputerName parameter, or if you specify a CIM session created using DCOM protocol, you will get an error, because the DCOM protocol does not support the ResourceURI parameter. +ResourceURI can only be used with CIM sessions created using the WSMan protocol, or when specifying +the ComputerName parameter, which creates a CIM session using WSMan. If you specify this parameter +without specifying the ComputerName parameter, or if you specify a CIM session created using DCOM +protocol, you will get an error, because the DCOM protocol does not support the ResourceURI +parameter. -If both the ResourceUri parameter and the Filter parameter are specified, the Filter parameter is ignored. +If both the ResourceUri parameter and the Filter parameter are specified, the Filter parameter is +ignored. ```yaml Type: Uri @@ -276,8 +290,9 @@ Accept wildcard characters: False ``` ### CommonParameters -This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. -For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216). +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, +-InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, +-WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216). ## INPUTS diff --git a/reference/3.0/CimCmdlets/Get-CimSession.md b/reference/3.0/CimCmdlets/Get-CimSession.md index b92f714c7395..b8b34f3be90f 100644 --- a/reference/3.0/CimCmdlets/Get-CimSession.md +++ b/reference/3.0/CimCmdlets/Get-CimSession.md @@ -33,7 +33,7 @@ Get-CimSession -Name [] ``` ## DESCRIPTION -The Get-CimSession cmdlet gets the CIM session objects created in the current Windows PowerShell® session. +The Get-CimSession cmdlet gets the CIM session objects created in the current Windows PowerShell session. If used without any parameters, the cmdlet gets all of the CIM sessions created in the current Windows PowerShell session. You can use the parameters of Get-CimSession to get the sessions that are for particular computers, or you can identify sessions by their names, IDs, or instance IDs. diff --git a/reference/3.0/CimCmdlets/Invoke-CimMethod.md b/reference/3.0/CimCmdlets/Invoke-CimMethod.md index 1f937685928f..ad183a68c5df 100644 --- a/reference/3.0/CimCmdlets/Invoke-CimMethod.md +++ b/reference/3.0/CimCmdlets/Invoke-CimMethod.md @@ -104,19 +104,20 @@ If the InputObject parameter is specified, the cmdlet works in one of the follow ## EXAMPLES -### Example 1: Invoke a method +### Example 1: Invoke a method> [!NOTE] +> Information the user should notice even if skimming ```powershell -PS C:\>Invoke-CimMethod -Query ꞌselect * from Win32_Process where name like "notepad%"ꞌ -MethodName "Terminate" +PS C:\>Invoke-CimMethod -Query 'select * from Win32_Process where name like "notepad%"' -MethodName "Terminate" ``` This command invokes the method named Terminate on the CIM class named Win32_Process. The CIM class -is retrieved by the query "Select * from Win32_Process where name like ꞌnotepad%ꞌ". +is retrieved by the query "Select * from Win32_Process where name like 'notepad%'". ### Example 2: Invoke a method using CIM instance object ```powershell -PS C:\>$x = Get-CimInstance -Query ꞌSelect * from Win32_Process where name like "notepad%"ꞌ +PS C:\>$x = Get-CimInstance -Query 'Select * from Win32_Process where name like "notepad%"' PS C:\>Invoke-CimMethod -InputObject $x -MethodName GetOwner ``` @@ -135,7 +136,7 @@ This command invokes the static method Create on the class named Win32_Process, ### Example 4: Invoke a method using arguments ```powershell -PS C:\>Invoke-CimMethod -ClassName Win32_Process -MethodName "Create" -Arguments @{ CommandLine = ꞌnotepad.exeꞌ; CurrentDirectory = "C:\windows\system32" } +PS C:\>Invoke-CimMethod -ClassName Win32_Process -MethodName "Create" -Arguments @{ CommandLine = 'notepad.exe'; CurrentDirectory = "C:\windows\system32" } ``` This command invokes the method named Create by using the Arguments parameter. @@ -144,7 +145,7 @@ This command invokes the method named Create by using the Arguments parameter. ```powershell PS C:\>$c = Get-CimClass -ClassName Win32_Process -PS C:\>Invoke-CimMethod -CimClass $c -MethodName "xyz" -Arguments @{ CommandLine = ꞌnotepad.exeꞌ } +PS C:\>Invoke-CimMethod -CimClass $c -MethodName "xyz" -Arguments @{ CommandLine = 'notepad.exe' } ``` This set of commands performs client-side validation for the method named xyz by passing a CimClass diff --git a/reference/3.0/CimCmdlets/Remove-CimInstance.md b/reference/3.0/CimCmdlets/Remove-CimInstance.md index e27b87259a32..f6d47387392a 100644 --- a/reference/3.0/CimCmdlets/Remove-CimInstance.md +++ b/reference/3.0/CimCmdlets/Remove-CimInstance.md @@ -41,16 +41,16 @@ The Remove-CimInstance cmdlet removes a CIM instance from a CIM server. You can specify the CIM instance to remove by using either a CIM instance object retrieved by the Get-CimInstance cmdlet, or by specifying a query. -If the InputObject parameter is not specified, the cmdlet works in one of the following ways: +If the InputObject parameter is not specified, the cmdlet works in one of the following ways: ---If neither the ComputerName parameter nor the CimSession parameter is specified, then this cmdlet works on local Windows Management Instrumentation (WMI) using a Component Object Model (COM) session. +--If neither the ComputerName parameter nor the CimSession parameter is specified, then this cmdlet works on local Windows Management Instrumentation (WMI) using a Component Object Model (COM) session. --If either the ComputerName parameter or the CimSession parameter is specified, then this cmdlet works against the CIM server specified by either the ComputerName parameter or the CimSession parameter. ## EXAMPLES ### Example 1: Remove the CIM instance ``` -PS C:\>Remove-CimInstance -Query 'Select * from Win32_Environment where name LIKE "testvar%"ꞌ +PS C:\>Remove-CimInstance -Query 'Select * from Win32_Environment where name LIKE "testvar%"' ``` This command removes the CIM instances that start with the character string testvar from the class named Win32_Environment using the Query parameter. @@ -125,7 +125,7 @@ Accept wildcard characters: False ``` ### -InputObject -Specifies a CIM instance object to be removed from the CIM server. +Specifies a CIM instance object to be removed from the CIM server. Note: The input object passed to the cmdlet is not changed, only the instance in the CIM server is removed. ```yaml @@ -143,7 +143,7 @@ Accept wildcard characters: False ### -Namespace Specifies the namespace for the CIM operation. -The default namespace is root/cimv2. +The default namespace is root/cimv2. NOTE: You can use tab completion to browse the list of namespaces, because PowerShell gets a list of namespaces from the local WMI server to provide the list of namespaces. ```yaml @@ -220,13 +220,13 @@ Specifies the resource uniform resource identifier (URI) of the resource class o The URI is used to identify a specific type of resource, such as disks or processes, on a computer. A URI consists of a prefix and a path to a resource. -For example: +For example: http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_LogicalDisk http://intel.com/wbem/wscim/1/amt-schema/1/AMT_GeneralSettings - + By default, if you do not specify this parameter, the DMTF standard resource URI http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/ is used and the class name is appended to it. ResourceURI can only be used with CIM sessions created using the WSMan protocol, or when specifying the ComputerName parameter, which creates a CIM session using WSMan. diff --git a/reference/3.0/ISE/ISE.md b/reference/3.0/ISE/ISE.md index 881605a3a8ba..59eb597441bb 100644 --- a/reference/3.0/ISE/ISE.md +++ b/reference/3.0/ISE/ISE.md @@ -13,7 +13,7 @@ Module Name: ISE ## Description -This section contains the help topics for the cmdlets that are installed with the Windows PowerShell® Integrated Scripting Environment (ISE) module. +This section contains the help topics for the cmdlets that are installed with the Windows PowerShell Integrated Scripting Environment (ISE) module. The Windows PowerShell ISE module contains cmdlets that add features to Windows PowerShell ISE. ## ISE Cmdlets diff --git a/reference/3.0/ISE/Import-IseSnippet.md b/reference/3.0/ISE/Import-IseSnippet.md index 7a2e1434501b..90b64d85daf9 100644 --- a/reference/3.0/ISE/Import-IseSnippet.md +++ b/reference/3.0/ISE/Import-IseSnippet.md @@ -30,7 +30,7 @@ Import-IseSnippet [-Recurse] -Module [-ListAvailable] [=\; \=\; …}* +`@{\=\; \=\; ...}*` ## SPLATTING WITH ARRAYS @@ -271,7 +271,7 @@ FileVersionInfo : File: C:\Windows\System32\WindowsPowerShell OriginalFilename: PowerShell.EXE.MUI FileVersion: 10.0.14393.0 (rs1_release.160715-1616 FileDescription: Windows PowerShell - Product: Microsoft® Windows® Operating System + Product: Microsoft Windows Operating System ProductVersion: 10.0.14393.0 Debug: False Patched: False diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_WMI.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_WMI.md index 62aaab7126de..9471be55aa4b 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_WMI.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_WMI.md @@ -16,11 +16,11 @@ manageable components of the modern enterprise. ## LONG DESCRIPTION -Windows Management Instrumentation (WMI) is Microsoft’s implementation of +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 +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\+\+). diff --git a/reference/3.0/Microsoft.PowerShell.Core/About/about_Windows_RT.md b/reference/3.0/Microsoft.PowerShell.Core/About/about_Windows_RT.md index df3e64972b07..cf046396aa0d 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/About/about_Windows_RT.md +++ b/reference/3.0/Microsoft.PowerShell.Core/About/about_Windows_RT.md @@ -10,7 +10,7 @@ title: about_Windows_RT ## SHORT DESCRIPTION -Explains limitations of Windows PowerShell® 4.0 on Windows RT 8.1. +Explains limitations of Windows PowerShell 4.0 on Windows RT 8.1. ## LONG DESCRIPTION @@ -37,9 +37,9 @@ devices. The following list explains the differences. While remoting is disabled, you can use Windows PowerShell remoting to run commands on other computers, but other computers cannot run commands on the - Windows RT device. Also, implicit remoting—that is, remoting that is built in - to a cmdlet or script, and not explicitly requested with added parameters—does - not work in Windows PowerShell running on Windows RT 8.1. + Windows RT device. Also, implicit remoting - that is, remoting that is built + in to a cmdlet or script, and not explicitly requested with added parameters + - does not work in Windows PowerShell running on Windows RT 8.1. - Domain-joined computing and Kerberos authentication are not supported on Windows RT 8.1. You cannot use Windows PowerShell to add or manage these diff --git a/reference/3.0/Microsoft.PowerShell.Core/Enable-PSRemoting.md b/reference/3.0/Microsoft.PowerShell.Core/Enable-PSRemoting.md index 4ed2ff705189..9892db34ba91 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/Enable-PSRemoting.md +++ b/reference/3.0/Microsoft.PowerShell.Core/Enable-PSRemoting.md @@ -24,7 +24,7 @@ Enable-PSRemoting [-Force] [-SkipNetworkProfileCheck] [-WhatIf] [-Confirm] [ Get-Content $m.Path GUID = "{8FA5064B-8479-4c5c-86EA-0D311FE48875}" Author = "Microsoft Corporation" CompanyName = "Microsoft Corporation" - Copyright = "© Microsoft Corporation. All rights reserved." + Copyright = "Microsoft Corporation. All rights reserved." ModuleVersion = "1.0.0.0" Description = "Windows PowerShell File Transfer Module" PowerShellVersion = "2.0" diff --git a/reference/3.0/Microsoft.PowerShell.Core/Invoke-Command.md b/reference/3.0/Microsoft.PowerShell.Core/Invoke-Command.md index 64159ce3c43f..ae184e7f9193 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/Invoke-Command.md +++ b/reference/3.0/Microsoft.PowerShell.Core/Invoke-Command.md @@ -381,7 +381,7 @@ As a result, if the remote computer specified by the **ConnectionURI** parameter ### Example 14 ``` -PS> $so = New-PSSessionOption -SkipCACheck -SkipCNCheck –SkipRevocationCheck +PS> $so = New-PSSessionOption -SkipCACheck -SkipCNCheck -SkipRevocationCheck PS> Invoke-Command -ComputerName server01 -UseSSL -ScriptBlock { Get-Hotfix } -SessionOption $so -Credential server01\user01 ``` diff --git a/reference/3.0/Microsoft.PowerShell.Core/New-ModuleManifest.md b/reference/3.0/Microsoft.PowerShell.Core/New-ModuleManifest.md index 8df8c400795e..d539fe941884 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/New-ModuleManifest.md +++ b/reference/3.0/Microsoft.PowerShell.Core/New-ModuleManifest.md @@ -240,7 +240,7 @@ Author : Microsoft Corporation AccessMode : ReadWrite ClrVersion : 4.0 CompanyName : Microsoft Corporation -Copyright : © Microsoft Corporation. All rights reserved. +Copyright : Microsoft Corporation. All rights reserved. DotNetFrameworkVersion : ExportedFunctions : {} ExportedCmdlets : {[Get-WinEvent, Get-WinEvent], [Get-Counter, Get-Counter], [Import-Counter, diff --git a/reference/3.0/Microsoft.PowerShell.Core/Receive-PSSession.md b/reference/3.0/Microsoft.PowerShell.Core/Receive-PSSession.md index 31a5587e410b..a9554dbf6cd7 100644 --- a/reference/3.0/Microsoft.PowerShell.Core/Receive-PSSession.md +++ b/reference/3.0/Microsoft.PowerShell.Core/Receive-PSSession.md @@ -150,7 +150,7 @@ Id Name ComputerName State ConfigurationName Availability The third command uses the Invoke-Command cmdlet to run a script in the session in the $s variable.The script begins to run and return data, but a network outage occurs that interrupts the session. The user has to exit the session and restart the local computer. PS> Invoke-Command -Session $s -FilePath \\Server12\Scripts\SharedScripts\New-ADResolve.ps1 - Running "New-ADResolve.ps1" ….exit + Running "New-ADResolve.ps1" # Network outage # Restart local computer @@ -216,7 +216,7 @@ Bug Report - Domain 01 ---------------------- ComputerName BugCount LastUpdated -------------- --------- ------------ -Server01 121 Friday, December 30, 2011 5:03:34 PM… +Server01 121 Friday, December 30, 2011 5:03:34 PM ``` This example uses the **Receive-PSSession** cmdlet to reconnect to sessions that were intentionally disconnected and get the results of jobs that were running in the sessions. @@ -259,7 +259,7 @@ PS> $j2 = Receive-PSSession -ComputerName Server01 -Name Test PS> Receive-Job $j Return 3 -Return 4… +Return 4 ``` This example shows what happens to a job that is running in a disconnected session. diff --git a/reference/3.0/Microsoft.PowerShell.Management/Get-WmiObject.md b/reference/3.0/Microsoft.PowerShell.Management/Get-WmiObject.md index 52dd404d048a..4ab9a13f6973 100644 --- a/reference/3.0/Microsoft.PowerShell.Management/Get-WmiObject.md +++ b/reference/3.0/Microsoft.PowerShell.Management/Get-WmiObject.md @@ -89,37 +89,23 @@ This command gets the WMI classes in the root or default namespace of the local ### Example 4 ``` PS C:\> Get-WmiObject -Query "select * from win32_service where name='WinRM'" -ComputerName Server01, Server02 | Format-List -Property PSComputerName, Name, ExitCode, Name, ProcessID, StartMode, State, Status -PSComputerName : SERVER01 +PSComputerName : SERVER01 Name : WinRM - ExitCode : 0 - Name : WinRM - ProcessID : 844 - StartMode : Auto - State : Running - Status : OK - PSComputerName : SERVER02 - Name : WinRM - ExitCode : 0 - Name : WinRM - ProcessID : 932 - StartMode : Auto - State : Running - Status : OK ``` @@ -145,94 +131,50 @@ This command is an alternative to using the Stop-Service cmdlet. PS C:\> Get-WmiObject -Class Win32_Bios | Format-List -Property Status : OK - Name : Phoenix ROM BIOS PLUS Version 1.10 A05 - Caption : Phoenix ROM BIOS PLUS Version 1.10 A05 - SMBIOSPresent : True - __GENUS : 2 - __CLASS : Win32_BIOS - __SUPERCLASS : CIM_BIOSElement - __DYNASTY : CIM_ManagedSystemElement - -__RELPATH : Win32_BIOS.Name="Phoenix ROM BIOS PLUS Version 1.10 … - +__RELPATH : Win32_BIOS.Name="Phoenix ROM BIOS PLUS Version 1.10 __PROPERTY_COUNT : 27 - -__DERIVATION : {CIM_BIOSElement, CIM_SoftwareElement, CIM_LogicalElement,… - +__DERIVATION : {CIM_BIOSElement, CIM_SoftwareElement, CIM_LogicalElement, __SERVER : Server01 - __NAMESPACE : root\cimv2 - __PATH : \\SERVER01\root\cimv2:Win32_BIOS.Name="Phoenix ROM BIOS - BiosCharacteristics : {7, 9, 10, 11...} - BIOSVersion : {DELL - 15, Phoenix ROM BIOS PLUS Version 1.10 A05} - BuildNumber : - CodeSet : - CurrentLanguage : en|US|iso8859-1 - Description : Phoenix ROM BIOS PLUS Version 1.10 A05 - IdentificationCode : - InstallableLanguages : 1 - InstallDate : - LanguageEdition : - ListOfLanguages : {en|US|iso8859-1} - Manufacturer : Dell Inc. - OtherTargetOS : - PrimaryBIOS : True - ReleaseDate : 20101103000000.000000+000 - SerialNumber : 8VDM9P1 - SMBIOSBIOSVersion : A05 - SMBIOSMajorVersion : 2 - SMBIOSMinorVersion : 6 SoftwareElementID : Phoenix ROM BIOS PLUS Version 1.10 A05 - SoftwareElementState : 3 - TargetOperatingSystem : 0 - Version : DELL - 15 - Scope : System.Management.ManagementScope - Path : \\SERVER01\root\cimv2:Win32_BIOS.Name="Phoenix ROM BIOS - Options : System.Management.ObjectGetOptions - ClassPath : \\JUNE-PC\root\cimv2:Win32_BIOS - Properties : {BiosCharacteristics, BIOSVersion, BuildNumber, Caption...} - SystemProperties : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...} - Qualifiers : {dynamic, Locale, provider, UUID} - Site : - Container : ``` @@ -297,21 +239,14 @@ Accept wildcard characters: False Specifies the authentication level to be used with the WMI connection. Valid values are: --1: Unchanged - -0: Default - -1: None (No authentication in performed.) - -2: Connect (Authentication is performed only when the client establishes a relationship with the application.) - -3: Call (Authentication is performed only at the beginning of each call when the application receives the request.) - -4: Packet (Authentication is performed on all the data that is received from the client.) - -5: PacketIntegrity (All the data that is transferred between the client and the application is authenticated and verified.) - -6: PacketPrivacy (The properties of the other authentication levels are used, and all the data is encrypted.) +- -1: Unchanged +- 0: Default +- 1: None (No authentication in performed.) +- 2: Connect (Authentication is performed only when the client establishes a relationship with the application.) +- 3: Call (Authentication is performed only at the beginning of each call when the application receives the request.) +- 4: Packet (Authentication is performed on all the data that is received from the client.) +- 5: PacketIntegrity (All the data that is transferred between the client and the application is authenticated and verified.) +- 6: PacketPrivacy (The properties of the other authentication levels are used, and all the data is encrypted.) ```yaml Type: AuthenticationLevel diff --git a/reference/3.0/Microsoft.PowerShell.Security/Set-Acl.md b/reference/3.0/Microsoft.PowerShell.Security/Set-Acl.md index 317d433a8079..46efa4774a7c 100644 --- a/reference/3.0/Microsoft.PowerShell.Security/Set-Acl.md +++ b/reference/3.0/Microsoft.PowerShell.Security/Set-Acl.md @@ -225,7 +225,7 @@ Accept wildcard characters: True Establishes or changes the central access policy of the item. Enter the CAP ID or friendly name of a central access policy on the computer. -Beginning in Windows Server® 2012, administrators can use Active Directory and Group Policy to set central access policies for users and groups. +Beginning in Windows Server 2012, administrators can use Active Directory and Group Policy to set central access policies for users and groups. For more information, see [Dynamic Access Control: Scenario Overview](/windows-server/identity/solution-guides/dynamic-access-control--scenario-overview). This parameter is introduced in Windows PowerShell 3.0. @@ -246,7 +246,7 @@ Accept wildcard characters: False Removes the central access policy from the specified item. -Beginning in Windows Server® 2012, administrators can use Active Directory and Group Policy to set central access policies for users and groups. +Beginning in Windows Server 2012, administrators can use Active Directory and Group Policy to set central access policies for users and groups. For more information, see [Dynamic Access Control: Scenario Overview](/windows-server/identity/solution-guides/dynamic-access-control--scenario-overview). This parameter is introduced in Windows PowerShell 3.0. diff --git a/reference/3.0/Microsoft.PowerShell.Utility/Get-Alias.md b/reference/3.0/Microsoft.PowerShell.Utility/Get-Alias.md index 28e91507132c..803f3b684ca7 100644 --- a/reference/3.0/Microsoft.PowerShell.Utility/Get-Alias.md +++ b/reference/3.0/Microsoft.PowerShell.Utility/Get-Alias.md @@ -45,29 +45,19 @@ Beginning in Windows PowerShell 3.0, Get-Alias displays non-hyphenated alias nam ``` PS C:\> Get-Alias -CommandType Name +CommandType Name ----------- ---- - Alias % -> ForEach-Object - Alias ? -> Where-Object - Alias ac -> Add-Content - Alias asnp -> Add-PSSnapin - Alias cat -> Get-Content - Alias cd -> Set-Location - Alias chdir -> Set-Location - Alias clc -> Clear-Content - Alias clear -> Clear-Host - -Alias clhy -> Clear-History … +Alias clhy -> Clear-History ``` This command gets all aliases in the current session. diff --git a/reference/3.0/Microsoft.PowerShell.Utility/Select-Object.md b/reference/3.0/Microsoft.PowerShell.Utility/Select-Object.md index a0db01bedeff..ce05e59e6ef6 100644 --- a/reference/3.0/Microsoft.PowerShell.Utility/Select-Object.md +++ b/reference/3.0/Microsoft.PowerShell.Utility/Select-Object.md @@ -71,7 +71,7 @@ InternalName: explorer OriginalFilename: EXPLORER.EXE.MUI FileVersion: 10.0.17134.1 (WinBuild.160101.0800) FileDescription: Windows Explorer -Product: Microsoft® Windows® Operating System +Product: Microsoft Windows Operating System ProductVersion: 10.0.17134.1 ... ``` diff --git a/reference/3.0/PSWorkflow/About/about_ActivityCommonParameters.md b/reference/3.0/PSWorkflow/About/about_ActivityCommonParameters.md index 3b657a380be5..45ed501a777a 100644 --- a/reference/3.0/PSWorkflow/About/about_ActivityCommonParameters.md +++ b/reference/3.0/PSWorkflow/About/about_ActivityCommonParameters.md @@ -348,7 +348,7 @@ saved when a checkpoint is taken. Applies the equivalent of the PSDisableSerialization parameter to the entire workflow, not just the activity. Adding this parameter is generally not -recommended, because a workflow that doesn’t serialize its objects cannot be +recommended, because a workflow that doesn't serialize its objects cannot be resumed or persisted. Valid values: @@ -357,7 +357,7 @@ Valid values: PSDisableSerialization parameter to an activity, objects are serialized. - `$True`. Directs all activities within a workflow to return - "live" (not serialized) objects. The resulting objects have methods, as well + "live" (not serialized) objects. The resulting objects have methods, as well as properties, but they cannot be saved when a checkpoint is taken. - `$False`. Workflow objects are serialized. @@ -406,10 +406,10 @@ Valid values: added. Checkpoints are taken based on the settings for the workflow. - `$True`. Takes a checkpoint after the activity completes. - This checkpoint is in addition to any checkpoints that are specified in + This checkpoint is in addition to any checkpoints that are specified in the workflow. -- `$False`. No checkpoints are added. Checkpoints are taken only when +- `$False`. No checkpoints are added. Checkpoints are taken only when specified in the workflow. #### PSPort \ diff --git a/reference/3.0/PSWorkflow/About/about_Checkpoint-Workflow.md b/reference/3.0/PSWorkflow/About/about_Checkpoint-Workflow.md index 880588454b48..5b8e466147a9 100644 --- a/reference/3.0/PSWorkflow/About/about_Checkpoint-Workflow.md +++ b/reference/3.0/PSWorkflow/About/about_Checkpoint-Workflow.md @@ -43,7 +43,7 @@ Consider taking checkpoints after critical steps so the workflow can be resumed A checkpoint is a snapshot of the current state of the workflow, including the current values of variables, and any output generated up to that point, and it saves it to disk. -If a workflow is interrupted, intentionally or unintentionally, Windows PowerShell® Workflow automatically uses the data in newest checkpoint to recover and resume the workflow. +If a workflow is interrupted, intentionally or unintentionally, Windows PowerShell Workflow automatically uses the data in newest checkpoint to recover and resume the workflow. When you run the workflow as a job, such as by using the AsJob workflow common parameter, the workflow checkpoints are retained until you delete the job, such as by using the Remove-Job cmdlet. Otherwise, workflow checkpoints are deleted when the workflow completes. diff --git a/reference/3.0/PSWorkflow/About/about_Foreach-Parallel.md b/reference/3.0/PSWorkflow/About/about_Foreach-Parallel.md index 5fadf45c9fc0..ee1fb1fa5a35 100644 --- a/reference/3.0/PSWorkflow/About/about_Foreach-Parallel.md +++ b/reference/3.0/PSWorkflow/About/about_Foreach-Parallel.md @@ -9,7 +9,7 @@ title: about_Foreach Parallel ## SHORT DESCRIPTION -Describes the ForEach -Parallel language construct in Windows PowerShell® Workflow +Describes the ForEach -Parallel language construct in Windows PowerShell Workflow ## LONG DESCRIPTION diff --git a/reference/3.0/PSWorkflow/About/about_Parallel.md b/reference/3.0/PSWorkflow/About/about_Parallel.md index f246d9263217..2d2fad81b395 100644 --- a/reference/3.0/PSWorkflow/About/about_Parallel.md +++ b/reference/3.0/PSWorkflow/About/about_Parallel.md @@ -13,7 +13,7 @@ Describes the Parallel keyword, which runs the activities in a workflow in paral ## LONG DESCRIPTION -The Parallel keyword runs workflow activities in parallel. This keyword is valid only in Windows PowerShell® Workflow. +The Parallel keyword runs workflow activities in parallel. This keyword is valid only in Windows PowerShell Workflow. ### SYNTAX