Merging latest changes to Live

dsc/secureMOF.md

@@ -217,7 +217,7 @@ Import-Certificate -FilePath "$env:temp\DscPublicKey.cer" -CertStoreLocation Cer
 ```powershell
 # Import to the root store so that it is trusted
 $mypwd = ConvertTo-SecureString -String "YOUR_PFX_PASSWD" -Force -AsPlainText
-Import-PfxCertificate -FilePath "$env:temp\DscPrivateKey.pfx" -CertStoreLocation Cert:\LocalMachine\Root -Password $mypwd > $null
+Import-PfxCertificate -FilePath "$env:temp\DscPrivateKey.pfx" -CertStoreLocation Cert:\LocalMachine\My -Password $mypwd > $null
 ```
 
 ## Configuration data

dsc/windowsfeatureResource.md

@@ -31,7 +31,7 @@ WindowsFeature [string] #ResourceName
 
 | Property | Description | 
 |---|---| 
-| Name| Indicates the name of the role or feature that you want to ensure is added or removed. This is the same as the __Name__ property from the [Get-WindowsFeature](https://technet.microsoft.com/en-us/library/jj205469.aspx) cmdlet, and not the display name of the role or feature.| 
+| Name| Indicates the name of the role or feature that you want to ensure is added or removed. This is the same as the __Name__ property from the [Get-WindowsFeature](/powershell/module/servermanager/Get-WindowsFeature) cmdlet, and not the display name of the role or feature.| 
 | Credential| Indicates the credentials to use to add or remove the role or feature.| 
 | Ensure| Indicates if the role or feature is added. To ensure that the role or feature is added, set this property to "Present" To ensure that the role or feature is removed, set the property to "Absent".| 
 | IncludeAllSubFeature| Set this property to __$true__ to ensure the state of all required subfeatures with the state of the feature you specify with the __Name__ property.| 

reference/3.0/Microsoft.PowerShell.Core/Functions/Get-Verb.md

@@ -68,60 +68,32 @@ Description
 This command gets all approved verbs that begin with "un".
 
 ### Example 3
+```powershell
+PS C:\> Get-Verb | Where-Object Group -EQ Security
+
+Verb Group
+---- -----
+Block Security
+Grant Security
+Protect Security
+Revoke Security
+Unblock Security
+Unprotect Security
 ```
-get-verb | where-object {$_.Group -eq "Security"}
-
-Verb Group
----- -----
-Block Security
-Grant Security
-Protect Security
-Revoke Security
-Unblock Security
-Unprotect Security
-```
-
-Description
-
------------
 
 This command gets all approved verbs in the Security group.
 
 ### Example 4
+```powershell
+Get-Command -Module Microsoft.PowerShell.Utility | where Verb -NotIn (Get-Verb).Verb
+# CommandType Name Version Source
+# ----------- ---- ------- ------
+# Cmdlet Sort-Object 3.1.0.0 Microsoft.PowerShell.Utility
+# Cmdlet Tee-Object 3.1.0.0 Microsoft.PowerShell.Utility
 ```
-get-command -module MyModule | where { (get-verb $_.Verb) -eq $null }
-```
-
-Description
-
------------
 
 This command finds all commands in a module that have unapproved verbs.
 
-### Example 5
-```
-$approvedVerbs = get-verb | foreach {$_.verb}
-
-C:\PS> $myVerbs = get-command -module MyModule | foreach {$_.verb}
-
-# Does MyModule export functions with unapproved verbs?
-C:\PS> ($myVerbs | foreach {$approvedVerbs -contains $_}) -contains $false
-True
-
-# Which unapproved verbs are used in MyModule?
-C:\PS> ($myverbs | where {$approvedVerbs -notcontains $_})
-ForEach
-Sort
-Tee
-Where
-```
-
-Description
-
------------
-
-These commands detect unapproved verbs in a module and tell which unapproved verbs were detected in the module.
-
 ## PARAMETERS
 
 ### -verb

reference/3.0/Microsoft.PowerShell.Management/Get-Process.md

@@ -114,9 +114,10 @@ This command gets the modules for the processes that have names that begin with
 
 To run this command on Windows Vista (and later versions of Windows) with processes that you do not own, you must start Windows PowerShell with the "Run as administrator" option.
 ### Example 8
-```
-PS C:\> $p = get-wmiobject win32_process -filter "name='powershell.exe'"
-PS C:\> $p.getowner()
+```powershell
+PS C:\> $p = Get-WmiObject Win32_Process -Filter "name='powershell.exe'"
+PS C:\> $p.GetOwner()
+
 
 __GENUS : 2
 __CLASS : __PARAMETERS
@@ -134,33 +135,38 @@ User : user01
 ```
 
 This command shows how to find the owner of a process.
-Because the System.Diagnostics.Process object that Get-Process returns does not have a property or method that returns the process owner, the command uses
-
-the Get-WmiObject cmdlet to get a Win32_Process object that represents the same process.
+Because the System.Diagnostics.Process object that `Get-Process` returns does not have a property or method that returns the process owner, the command uses the `Get-WmiObject` cmdlet to get a Win32_Process object that represents the same process.
 
-The first command uses Get-WmiObject to get the PowerShell process.
+The first command uses `Get-WmiObject` to get the PowerShell process.
 It saves it in the $p variable.
 
 The second command uses the GetOwner method to get the owner of the process in $p.
-The command reveals that the owner is Domain01\user01.
+The output reveals that the owner is Domain01\user01.
+
 ### Example 9
-```
-PS C:\> get-process powershell
+```powershell
+PS C:\> Get-Process powershell
 
 Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
 ------- ------ ----- ----- ----- ------ -- -----------
-308 26 52308 61780 567 3.18 5632 powershell
-377 26 62676 63384 575 3.88 5888 powershell PS C:\> get-process -id $pid
+308 26 52308 61780 567 3.18 5632 powershell
+377 26 62676 63384 575 3.88 5888 powershell
+
+
+PS C:\> Get-Process -Id $PID
+
 Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
 ------- ------ ----- ----- ----- ------ -- -----------
-396 26 56488 57236 575 3.90 5888 powershell
+396 26  56488 57236 575 3.90 5888 powershell
 ```
 
-These commands show how to use the $pid automatic variable to identify the process that is hosting the current Windows PowerShell session.
-You can use this method to distinguish the host process from other Windows PowerShell processes that you might want to stop or close.
-The first command gets all of the Windows PowerShell processes in the current session.
+These commands show how to use the $PID automatic variable to identify the process that is hosting the current PowerShell session.
+You can use this method to distinguish the host process from other PowerShell processes that you might want to stop or close.
+
+The first command gets all of the PowerShell processes in the current session.
+
+The second command gets the PowerShell process that is hosting the current session.
 
-The second command gets the Windows PowerShell process that is hosting the current session.
 ### Example 10
 ```
 PS C:\> get-process | where {$_.mainWindowTitle} | format-table id, name, mainwindowtitle -autosize

reference/3.0/Microsoft.PowerShell.Utility/Get-Member.md

@@ -102,33 +102,22 @@ This command gets the methods and properties of service objects that were extend
 The Get-Member command uses the View parameter to get only the extended members of the service objects.
 In this case, the extended member is the Name property, which is an alias property of the ServiceName property.
 ### Example 4
-```
-PS C:\> get-eventlog -log system | gm -membertype scriptproperty
-TypeName: System.Diagnostics.EventLogEntry
+```powershell
+PS C:\> Get-EventLog -Log System | Get-Member -MemberType ScriptProperty
 
-Name MemberType Definition
----- ---------- ----------
-EventID ScriptProperty System.Object EventID {get=$this.get_EventID() -band 0xFFFF;}
-```
 
-This command gets the script properties of event log objects in the System log in Event Viewer.
-In this case, the only script property is the EventID.
-### Example 5
-```
-PS C:\> get-eventlog -log system | get-member -membertype scriptproperty
-TypeName: System.Diagnostics.EventLogEntry
+ TypeName: System.Diagnostics.EventLogEntry
 
 Name MemberType Definition
 ---- ---------- ----------
 EventID ScriptProperty System.Object EventID {get=$this.get_EventID() -band 0xFFFF;}
 ```
 
 This command gets the script properties of event log objects in the System log in Event Viewer.
+The command uses the **MemberType** parameter to get only objects with a value of ScriptProperty for their MemberType property.
+The command returns the EventID property of the **EventLog** object.
 
-The command uses the MemberType parameter to get only objects with a value of AliasProperty for their MemberType property.
-
-The command returns the EventID property of the EventLog object.
-### Example 6
+### Example 5
 ```
 PS C:\> $a = "get-process", "get-service", "get-culture", "get-psdrive", "get-executionpolicy"
 PS C:\> foreach ($cmdlet in $a) {invoke-command $cmdlet | get-member -name machinename}
@@ -152,7 +141,7 @@ The first command stores the names of several cmdlets in the $a variable.
 The second command uses a ForEach statement to invoke each command, send the results to Get-Member, and limit the results from Get-Member to members that have the name "MachineName."
 
 The results show that only process objects (System.Diagnostics.Process) and service objects (System.ServiceProcess.ServiceController) have a MachineName property.
-### Example 7
+### Example 6
 ```
 PS C:\> $a = get-member -inputobject @(1)
 PS C:\> $a.count
@@ -179,7 +168,7 @@ In this case, the array contains only one object, the integer 1.
 The third command uses the Get-Member cmdlet to get the properties and methods of an array of integers, and the command saves them in the $a variable.
 
 The fourth command uses the Count property of the array to find the number of objects in the $a variable.
-### Example 8
+### Example 7
 ```
 PS C:\> $file = get-item c:\test\textFile.txt
 PS C:\> $file.psobject.properties | where-object {$_.issettable} | format-table -property name
@@ -212,7 +201,7 @@ The first command uses the Get-Item cmdlet to get a text file, and then it saves
 The second command gets all of the changeable properties of the file object in the $file variable and displays the names of the properties in a table.
 
 The third command gets the changeable properties of all objects in your Windows PowerShell session.
-### Example 9
+### Example 8
 ```
 PS C:\> $s = get-service
 PS C:\> $s | get-member

reference/4.0/Microsoft.PowerShell.Core/Functions/Get-Verb.md

@@ -68,60 +68,32 @@ Description
 This command gets all approved verbs that begin with "un".
 
 ### Example 3
+```powershell
+PS C:\> Get-Verb | Where-Object Group -EQ Security
+
+Verb Group
+---- -----
+Block Security
+Grant Security
+Protect Security
+Revoke Security
+Unblock Security
+Unprotect Security
 ```
-get-verb | where-object {$_.Group -eq "Security"}
-
-Verb Group
----- -----
-Block Security
-Grant Security
-Protect Security
-Revoke Security
-Unblock Security
-Unprotect Security
-```
-
-Description
-
------------
 
 This command gets all approved verbs in the Security group.
 
 ### Example 4
+```powershell
+Get-Command -Module Microsoft.PowerShell.Utility | where Verb -NotIn (Get-Verb).Verb
+# CommandType Name Version Source
+# ----------- ---- ------- ------
+# Cmdlet Sort-Object 3.1.0.0 Microsoft.PowerShell.Utility
+# Cmdlet Tee-Object 3.1.0.0 Microsoft.PowerShell.Utility
 ```
-get-command -module MyModule | where { (get-verb $_.Verb) -eq $null }
-```
-
-Description
-
------------
 
 This command finds all commands in a module that have unapproved verbs.
 
-### Example 5
-```
-$approvedVerbs = get-verb | foreach {$_.verb}
-
-C:\PS> $myVerbs = get-command -module MyModule | foreach {$_.verb}
-
-# Does MyModule export functions with unapproved verbs?
-C:\PS> ($myVerbs | foreach {$approvedVerbs -contains $_}) -contains $false
-True
-
-# Which unapproved verbs are used in MyModule?
-C:\PS> ($myverbs | where {$approvedVerbs -notcontains $_})
-ForEach
-Sort
-Tee
-Where
-```
-
-Description
-
------------
-
-These commands detect unapproved verbs in a module and tell which unapproved verbs were detected in the module.
-
 ## PARAMETERS
 
 ### -verb

reference/4.0/Microsoft.PowerShell.Management/Get-Process.md

@@ -139,9 +139,16 @@ This command gets the modules for the processes that have names that begin with
 To run this command on Windows Vista (and later versions of Windows) with processes that you do not own, you must start Windows PowerShell with the "Run as administrator" option.
 
 ### Example 8
-```
-PS C:\> $p = get-wmiobject win32_process -filter "name='powershell.exe'"
-PS C:\> $p.getowner()
+```powershell
+PS C:\> Get-Process powershell -IncludeUserName
+
+Handles WS(K) CPU(s) Id UserName ProcessName
+------- ----- ------ -- -------- -----------
+ 782 132080 2.08 2188 DOMAIN01\user01 powershell
+
+PS C:\> $p = Get-WmiObject Win32_Process -Filter "name='powershell.exe'"
+PS C:\> $p.GetOwner()
+
 
 __GENUS : 2
 __CLASS : __PARAMETERS
@@ -158,35 +165,41 @@ ReturnValue : 0
 User : user01
 ```
 
-This command shows how to find the owner of a process.
-Because the System.Diagnostics.Process object that Get-Process returns does not have a property or method that returns the process owner, the command uses
+The first command shows how to find the owner of a process.
+The **IncludeUserName** parameter requires elevated user rights (Run as Administrator).
+The output reveals that the owner is Domain01\user01.
 
-the Get-WmiObject cmdlet to get a Win32_Process object that represents the same process.
+The second and third command are another way to find the owner of a process.
 
-The first command uses Get-WmiObject to get the PowerShell process.
+The second command uses `Get-WmiObject` to get the PowerShell process.
 It saves it in the $p variable.
 
-The second command uses the GetOwner method to get the owner of the process in $p.
-The command reveals that the owner is Domain01\user01.
+The third command uses the GetOwner method to get the owner of the process in $p.
+The output reveals that the owner is Domain01\user01.
 
 ### Example 9
-```
-PS C:\> get-process powershell
+```powershell
+PS C:\> Get-Process powershell
 
 Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
 ------- ------ ----- ----- ----- ------ -- -----------
-308 26 52308 61780 567 3.18 5632 powershell
-377 26 62676 63384 575 3.88 5888 powershell PS C:\> get-process -id $pid
+308 26 52308 61780 567 3.18 5632 powershell
+377 26 62676 63384 575 3.88 5888 powershell
+
+
+PS C:\> Get-Process -Id $PID
+
 Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
 ------- ------ ----- ----- ----- ------ -- -----------
-396 26 56488 57236 575 3.90 5888 powershell
+396 26  56488 57236 575 3.90 5888 powershell
 ```
 
-These commands show how to use the $pid automatic variable to identify the process that is hosting the current Windows PowerShell session.
-You can use this method to distinguish the host process from other Windows PowerShell processes that you might want to stop or close.
-The first command gets all of the Windows PowerShell processes in the current session.
+These commands show how to use the $PID automatic variable to identify the process that is hosting the current PowerShell session.
+You can use this method to distinguish the host process from other PowerShell processes that you might want to stop or close.
+
+The first command gets all of the PowerShell processes in the current session.
 
-The second command gets the Windows PowerShell process that is hosting the current session.
+The second command gets the PowerShell process that is hosting the current session.
 
 ### Example 10
 ```