Display syntax for Get-DAPolicyChange in the installed PowerShell session.
Get-Command Get-DAPolicyChange -SyntaxGet-DAPolicyChange cmdlet
Gets a list of IP addresses that need to be added and deleted to an IPsec rule based on the differences detected between the IP addresses for the existing rule and the IP addresses derived from the input parameters, and creates a Windows PowerShell® script (.ps1) that updates the IPsec rule in the appropriate policy stores.
Installed syntax (PowerShell)
Get-Command Get-DAPolicyChange -SyntaxThis command prints the parameter sets available in the installed module. Compare the linked Microsoft reference for Windows PowerShell 5.1 / PowerShell 7 differences.
Examples
Read all available parameter sets and help for the installed module.
Get-Help Get-DAPolicyChange -FullDisplay examples from the installed help files.
Get-Help Get-DAPolicyChange -ExamplesParameters, options and clauses
| Option / clause | Description |
|---|---|
-Verbose | Write additional diagnostic detail to the verbose stream. |
-Debug | Write debugging messages to the debug stream. |
-ErrorAction <action> | Control how a non-terminating error is handled. |
-ErrorVariable <name> | Store error records in a variable. |
-WarningAction <action> | Control how warnings are handled. |
-WarningVariable <name> | Store warning messages in a variable. |
-InformationAction <action> | Control how information messages are handled. |
-InformationVariable <name> | Store information messages in a variable. |
-OutVariable <name> | Store output in a variable as well as sending it onward. |
-OutBuffer <count> | Set the number of objects to collect before the next command runs. |
-PipelineVariable <name> | Store the current pipeline object in a variable during processing. |
-ProgressAction <action> | Control progress reporting in versions that support this parameter. |
-WhatIf / -Confirm | Risk-control parameters available only on commands that support ShouldProcess. |
Related PowerShell references
Review a command and its target before running it. Commands that alter files, services, accounts, disks, permissions or databases may be difficult to reverse. Test in a safe environment and keep backups.