New-VBRDiscoveredComputerConfigurationOption
Short Description
Creates new configuration options for Veeam Agent settings.
Important |
|
Make sure to test this cmdlet in the lab before you run it in the production environment. |
Product Edition: Standard, Enterprise, Enterprise Plus, Veeam Universal License
Syntax
|
New-VBRDiscoveredComputerConfigurationOption -Name <String> -Value <Object> [<CommonParameters>] |
Detailed Description
This cmdlet creates the VBRDiscoveredComputerConfigurationOption object. This object contains new configuration options for Veeam Agent settings that you can distribute to discovered computers.
Parameters
|
Parameter |
Description |
Type |
Required |
Position |
Accept Pipeline Input |
|---|---|---|---|---|---|
|
Name |
Specifies the name that you want to assign to a new configuration option. |
|
True |
Named |
True (ByPropertyName, ByValue) |
|
Value |
Specifies a value that the configuration option must store. |
|
True |
Named |
True (ByPropertyName) |
<CommonParameters>
This cmdlet supports Microsoft PowerShell common parameters. For more information on common parameters, see Microsoft Docs.
Output Object
VBRDiscoveredComputerConfigurationOption
Examples
Example 1. Allowing File-Level Restore Without Administrator Privileges on Windows Computers
|
This command creates a new entry of the
|
Example 2. Restricting VPN Connections Usage on Windows Computers
|
This command creates a new entry of the
|
Example 3. Defining Job Queue Maximum Capacity on Linux and Mac Computers
|
This command creates a new entry for the
|
Related Commands
Add-VBRDiscoveredComputerConfigurationPolicyUpdates Veeam Agent settings on discovered computers using available configuration options. Make sure to test this cmdlet in the lab before you run it in the production environment.Get-VBRDiscoveredComputerConfigurationPolicyReturns configuration options applied to protected computers.Remove-VBRDiscoveredComputerConfigurationPolicyRemoves policies that contain configuration options for Veeam Agent settings. Make sure to test this cmdlet in the lab before you run it in the production environment.