Skip to content

Commit 1b7df0c

Browse files
committed
Add help for Test-WindowsBestPractices parameters
- Improve inline help for -Repair parameter - Add help for -Force parameter
1 parent b49368a commit 1b7df0c

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

PureStoragePowerShellToolkit.WindowsAdministration/PureStoragePowerShellToolkit.WindowsAdministration.psd1

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ RootModule = 'PureStoragePowerShellToolkit.WindowsAdministration.psm1'
2929

3030
# Version number of this module.
3131

32-
ModuleVersion = '3.0.1'
32+
ModuleVersion = '3.0.2'
3333

3434
# Supported PSEditions
3535
#CompatiblePSEditions = @("Desktop", "Core")

PureStoragePowerShellToolkit.WindowsAdministration/PureStoragePowerShellToolkit.WindowsAdministration.psm1

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1495,11 +1495,13 @@ function Test-Pfa2WindowsBestPractices() {
14951495
This cmdlet will retrieve the curretn host infromation, and iterate through several tests around MPIO (FC) and iSCSI OS settings and hardware, indicate whether they are adhearing to Pure Storage FlashArray Best Practices, and offer to alter the settings if applicable.
14961496
All tests can be bypassed with a negative user response when prompted, or simply by using Ctrl-C to break the process.
14971497
.PARAMETER Repair
1498-
Optional. If this parameter is present, the cmdlet will repair settings to their recommended values.
1498+
Optional. When this parameter is absent or equals $false, the cmdlet checks settings only and reports any non-recommended value. When the -Repair parameter is present or equals $true, the cmdlet checks each setting and ensures it has the recommended value. By default, the cmdlet asks the user confirmation for every change. While these interactive prompts allow fine user control on every change, they prevent usage of the cmdlet in an unattended script. Use -Force or -Comfirm:$false parameter to suppress confirmation prompts as shown in the example section. For more information about confimation prompts in PowerShell visit [about_CommonParameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_commonparameters#-confirm) and [Everything you wanted to know about ShouldProcess](https://learn.microsoft.com/powershell/scripting/learn/deep-dives/everything-about-shouldprocess).
14991499
.PARAMETER IncludeIscsi
15001500
Optional. If this parameter is present, the cmdlet will run tests for iSCSI settings.
15011501
.PARAMETER LogFilePath
15021502
Optional. Specify the full filepath (ex. c:\mylog.log) for logging. If not specified, the default file of %TMP%\BestPractices.log will be used.
1503+
.PARAMETER Force
1504+
Optional. When the -Force parameter is present, the cmdlet suppresses interactive comfirmaiton prompts including prompts for repair actions (see Repair parameter description).
15031505
.INPUTS
15041506
Optional parameter for iSCSI testing.
15051507
.OUTPUTS
@@ -1522,7 +1524,7 @@ function Test-Pfa2WindowsBestPractices() {
15221524
.EXAMPLE
15231525
Test-Pfa2WindowsBestPractices -Repair -Confirm:$false
15241526
1525-
Run the cmdlet against the local machine, repair settings to their recommended values skipping confirmation prompt.
1527+
Run the cmdlet against the local machine, repair settings to their recommended values without confirmation prompts.
15261528
#>
15271529

15281530
[CmdletBinding(SupportsShouldProcess, ConfirmImpact = 'High')]

0 commit comments

Comments
 (0)