Merge branch 'master' into patch-12

Author: denisebmsft

.openpublishing.redirection.json

@@ -5359,6 +5359,51 @@
       "source_path": "docset/winserver2022-ps/EventTracingManagement/Set-AutologgerConfig.md",
       "redirect_url": "/powershell/module/eventtracingmanagement/Update-AutologgerConfig.md?view=windowsserver2022-ps",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "docset/winserver2016-ps/provisioning/Export-ProvisioningPackage.md",
+      "redirect_url": "/powershell/module/provisioning/Export-ProvisioningPackage.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docset/winserver2016-ps/provisioning/Export-Trace.md",
+      "redirect_url": "/powershell/module/provisioning/Export-Trace.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docset/winserver2016-ps/provisioning/Get-ProvisioningPackage.md",
+      "redirect_url": "/powershell/module/provisioning/Get-ProvisioningPackage.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docset/winserver2016-ps/provisioning/Get-TrustedProvisioningCertificate.md",
+      "redirect_url": "/powershell/module/provisioning/Get-TrustedProvisioningCertificate.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docset/winserver2016-ps/provisioning/Install-ProvisioningPackage.md",
+      "redirect_url": "/powershell/module/provisioning/Install-ProvisioningPackage.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docset/winserver2016-ps/provisioning/Install-TrustedProvisioningCertificate.md",
+      "redirect_url": "/powershell/module/provisioning/Install-TrustedProvisioningCertificate.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docset/winserver2016-ps/provisioning/Provisioning.md",
+      "redirect_url": "/powershell/module/provisioning/Provisioning.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docset/winserver2016-ps/provisioning/Uninstall-ProvisioningPackage.md",
+      "redirect_url": "/powershell/module/provisioning/Uninstall-ProvisioningPackage.md",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docset/winserver2016-ps/provisioning/Uninstall-TrustedProvisioningCertificate.md",
+      "redirect_url": "/powershell/module/provisioning/Uninstall-TrustedProvisioningCertificate.md",
+      "redirect_document_id": false
     }
   ]
 }

docset/winserver2012-ps/activedirectory/Add-ADGroupMember.md

@@ -416,8 +416,8 @@ By default, this cmdlet does not generate any output.
 
 ## NOTES
 * This cmdlet does not work with a read-only domain controller.
-
-  This cmdlet does not work with an Active Directory Snapshot.
+* This cmdlet does not work with an Active Directory snapshot.
+* This cmdlet will allow you to add a group as a member of itself which could lead to unstable behavior.
 
 ## RELATED LINKS
 

docset/winserver2012-ps/activedirectory/Get-ADGroup.md

@@ -36,7 +36,7 @@ Get-ADGroup [-AuthType <ADAuthType>] [-Credential <PSCredential>] -LDAPFilter <S
 The Get-ADGroup cmdlet gets a group or performs a search to retrieve multiple groups from an Active Directory.
 
 The Identity parameter specifies the Active Directory group to get.
-You can identify a group by its distinguished name (DN), GUID, security identifier (SID), Security Accounts Manager (SAM) account name, or canonical name.
+You can identify a group by its distinguished name (DN), GUID, security identifier (SID), or Security Accounts Manager (SAM) account name.
 You can also specify group object variable, such as $\<localGroupObject\>.
 
 To search for and retrieve more than one group, use the Filter or LDAPFilter parameters.

docset/winserver2012-ps/activedirectory/Get-ADOrganizationalUnit.md

@@ -55,6 +55,8 @@ For more information about the how to determine the properties for computer obje
 ### Example 1: Get all of the OUs in a domain
 ```powershell
 PS C:\>Get-ADOrganizationalUnit -Filter 'Name -like "*"' | Format-Table Name, DistinguishedName -A
+```
+```output
 Name                 DistinguishedName
 ----                 -----------------
 Domain Controllers   OU=Domain Controllers,DC=FABRIKAM,DC=COM
@@ -81,6 +83,8 @@ This command gets all of the OUs in a domain.
 ### Example 2: Get an OU by its distinguished name
 ```powershell
 PS C:\> Get-ADOrganizationalUnit -Identity 'OU=AsiaPacific,OU=Sales,OU=UserAccounts,DC=FABRIKAM,DC=COM' | Format-Table Name,Country,PostalCode,City,StreetAddress,State -A
+```
+```output
 Name        Country PostalCode City     StreetAddress    State
 ----        ------- ---------- ----     -------------    -----
 AsiaPacific AU      4171       Balmoral 45 Martens Place QLD
@@ -91,6 +95,8 @@ This command gets the OU with the distinguished name OU=AsiaPacific,OU=Sales,OU=
 ### Example 3: Get child OUs
 ```powershell
 PS C:\> Get-ADOrganizationalUnit -LDAPFilter '(name=*)' -SearchBase 'OU=Sales,OU=UserAccounts,DC=FABRIKAM,DC=COM' -SearchScope OneLevel | Format-Table Name,Country,PostalCode,City,StreetAddress,State
+```
+```output
 Name                    Country                 PostalCode             City                   StreetAddress          State
 ----                    -------                 ----------             ----                   -------------          -----
 AsiaPacific             AU                      4171                   Balmoral               45 Martens Place       QLD

docset/winserver2012-ps/activedirectory/Get-ADUser.md

@@ -36,7 +36,7 @@ Get-ADUser [-AuthType <ADAuthType>] [-Credential <PSCredential>] -LDAPFilter <St
 The **Get-ADUser** cmdlet gets a specified user object or performs a search to get multiple user objects.
 
 The *Identity* parameter specifies the Active Directory user to get.
-You can identify a user by its distinguished name (DN), GUID, security identifier (SID), Security Account Manager (SAM) account name, or name.
+You can identify a user by its distinguished name (DN), GUID, security identifier (SID), or Security Account Manager (SAM) account name.
 You can also set the parameter to a user object variable such as `$<localUserObject>` or pass a user object through the pipeline to the *Identity* parameter.
 
 To search for and retrieve more than one user, use the *Filter* or *LDAPFilter* parameters.

docset/winserver2012-ps/adcsdeployment/install-adcsnetworkdeviceenrollmentservice.md

@@ -43,47 +43,38 @@ Int is equivalent to Int32 in the .NET Frameworkhttp://msdn.microsoft.com/en-us/
 
 ## EXAMPLES
 
-### -------------------------- EXAMPLE 1 --------------------------
+### Example 1: Display the default NDES settings
 ```
-C:\PS>Install-AdcsNetworkDeviceEnrollmentService -ApplicationPoolIdentity -WhatIf
+PS C:\> Install-AdcsNetworkDeviceEnrollmentService -ApplicationPoolIdentity -WhatIf
 ```
 
-Description
-
------------
-
-This command displays the default Network Device Enrollment Service settings when the service is running as the default application identity without making any changes to the configuration.
+This command displays the default NDES settings that will be configured if it is installed.
 
-### -------------------------- EXAMPLE 2 --------------------------
+### Example 2: Display the default NDES settings using a service account name and password
 ```
-C:\PS>Install-AdcsNetworkDeviceEnrollmentService -ServiceAccountName <Domain>\<AccountName> -ServiceAccountPassword (read-host "Set user password" -assecurestring) -WhatIf
+PS C:\> Install-AdcsNetworkDeviceEnrollmentService -ServiceAccountName "CONTOSO\svcNDES" -ServiceAccountPassword (read-host "Set user password" -assecurestring) -WhatIf
 ```
 
-Description
-
------------
-
 This command displays the default settings when NDES is using a service account without making any changes to the configuration.
-This command assumes that the \<Domain\>\\\<AccountName\> service account is a member of the local machine's IIS_USRS group.
-Substitute the domain name for \<Domain\> and the user account name for \<AccountName\>.
+This command uses the service account named CONTOSO\svcNDES that is a member of the local computer's IIS_USRS group.
 
-### -------------------------- EXAMPLE 3 --------------------------
+### Example 3: Install NDES using the application pool identity
 ```
-C:\PS>Install-AdcsNetworkDeviceEnrollmentService -ApplicationPoolIdentity -CAConfig <CAComputerName>\<CACommonName>
+PS C:\> Install-AdcsNetworkDeviceEnrollmentService -ApplicationPoolIdentity -CAConfig "<CAComputerName>\<CACommonName>"
 ```
 
-Description
-
------------
-
-This command installs the Network Device Enrollment Service using the application pool identity to use a remote CA as specified by the CA computer \<CACompterName\>\\\<CACommonName\>.
-Substitute the appropriate CA computer name and common name for \<CAComputerName\> and \<CACommonName\>.
+This command installs NDES using the application pool identity to use a remote CA as specified by the CA computer `<CAComputerName>\<CACommonName>`.
+Substitute the appropriate CA computer name and common name for `<CAComputerName>` and `<CACommonName>`.
 
-### -------------------------- EXAMPLE 4 --------------------------
+### Example 4: Install NDES using a specific service account
 ```
-C:\PS>Install-AdcsNetworkDeviceEnrollmentService -ServiceAccountName MyDomain\AccountName -ServiceAccountPassword (read-host "Set user password" -assecurestring) -CAConfig "CAMachineName\CAName" -RAName "Contoso-NDES-RA" -RACountry "US" -RACompany "Contoso" -SigningProviderName "Microsoft Strong Cryptographic Provider" -SigningKeyLength 4096 -EncryptionProviderName "Microsoft Strong Cryptographic Provider" -EncryptionKeyLength 4096
+PS C:\> Install-AdcsNetworkDeviceEnrollmentService -ServiceAccountName "CONTOSO\svcNDES" -ServiceAccountPassword (read-host "Set user password" -assecurestring) -CAConfig "CAComputerName\CAName" -RAName "Contoso-NDES-RA" -RACountry "US" -RACompany "Contoso" -SigningProviderName "Microsoft Strong Cryptographic Provider" -SigningKeyLength 4096 -EncryptionProviderName "Microsoft Strong Cryptographic Provider" -EncryptionKeyLength 4096
 ```
 
+This command installs the NDES using a service account named CONTOSO\svcNDES that is a member of the local computer's IIS_USRS group.
+The command also specifies several non-default parameters.
+
+
 Description
 
 -----------

docset/winserver2012-ps/dism/Get-WindowsImage.md

@@ -119,7 +119,7 @@ Accepted values: Errors, Warnings, WarningsInfo
 
 Required: False
 Position: Named
-Default value: None
+Default value: 3
 Accept pipeline input: True (ByPropertyName)
 Accept wildcard characters: False
 ```

docset/winserver2012-ps/netadapter/Get-NetAdapterPowerManagement.md

@@ -25,8 +25,7 @@ Get-NetAdapterPowerManagement [-AsJob] [-CimSession <CimSession[]>] [-IncludeHid
 ```
 
 ## DESCRIPTION
-The **Get-NetAdapterPowerManagement** cmdlet gets the state of the power management features of a Power Management capable network adapter.
-You must be an administrator in order to run this cmdlet.
+The **Get-NetAdapterPowerManagement** cmdlet gets the state of the power management features of a Power Management capable network adapter. You need to run this cmdlet in an elevated (Run as Administrator) Windows PowerShell session.
 
 ## EXAMPLES
 

docset/winserver2012-ps/scheduledtasks/New-ScheduledTask.md

@@ -38,18 +38,18 @@ PS C:\> Register-ScheduledTask T1 -InputObject $task
 
 In this example, the set of commands uses several cmdlets and variables to define and then register a scheduled task.
 
-The first command uses the **New-ScheduledTaskAction** cmdlet to assign the executable file tskmgr.exe to the variable $A.
+The first command uses the **New-ScheduledTaskAction** cmdlet to assign the executable file `tskmgr.exe` to the variable `$action`.
 
-The second command uses the **New-ScheduledTaskTrigger** cmdlet to assign the value AtLogon to the variable $T.
+The second command uses the **New-ScheduledTaskTrigger** cmdlet to assign the value `AtLogon` to the variable `$trigger`.
 
-The third command assigns the principal of the scheduled task `Contoso\Administrator` to the variable $P.
+The third command assigns the principal of the scheduled task `Contoso\Administrator` to the variable `$principal`.
 
-The fourth command uses the **New-ScheduledTaskSettingsSet** cmdlet to assign a task settings object to the variable $S.
+The fourth command uses the **New-ScheduledTaskSettingsSet** cmdlet to assign a task settings object to the variable `$settings`.
 
-The fifth command creates a new task and assigns the task definition to the variable $D.
+The fifth command creates a new task and assigns the task definition to the variable `$task`.
 
 The sixth command (hypothetically) runs at a later time.
-It registers the new scheduled task and defines it by using the $D variable.
+It registers the new scheduled task and defines it by using the `$task` variable.
 
 ### Example 2: Define a scheduled task with multiple actions
 ```powershell

docset/winserver2012-ps/storage/Format-Volume.md

@@ -388,6 +388,8 @@ Accept wildcard characters: False
 Shows what would happen if the cmdlet runs.
 The cmdlet is not run.
 
+**NOTE**: The WhatIf switch does not work with this cmdlet.
+
 ```yaml
 Type: SwitchParameter
 Parameter Sets: (All)