New-SettingOverride

The Component parameter specifies the component that the setting override is applied to. For example:

• TimeBasedAssistants
• OwaServer

The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.

• Destructive cmdlets (for example, Remove-* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.
• Most other cmdlets (for example, New-* and Set-* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.

The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.

The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.

You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.

The MaxVersion parameter specifies the latest version of Exchange 2016 that this override applies to (up to and including the specified value).

Valid input for this parameter is an Exchange 2016 version value in the format 15.1.xxx.xx. You can use values with leading zeros, but the leading zeros are removed from the results. For example, 15.01.0225.042 is stored as 15.1.225.42.

The default value is blank ($null), which means the override applies to all versions of Exchange 2016.

The MinVersion parameter specifies the earliest version of Exchange 2016 that this override applies to (up to and including the specified value).

Valid input for this parameter is an Exchange 2016 version value in the format 15.1.xxx.xx. You can use values with leading zeros, but the leading zeros are removed from the results. For example, 15.01.0225.042 is stored as 15.1.225.42.

The default value is blank ($null), which means the override applies to all versions of Exchange 2016.

The Name parameter specifies the unique name of the setting override. If the value contains spaces, enclose the value in quotation marks (").

The Parameters parameter specifies one or more parameters for the override that are available for the combination of the Component and Section parameter values. This parameter uses the syntax: @("Parameter1=Value1","Parameter2=Value2"...). For example:

• @("Enabled=true")
• @("IMServerName=<SkypePoolFQDN>","IMCertificateThumbprint=<ThumbprintGUID>")

The Reason parameter specifies why you are creating the setting override. If the value contains spaces, enclose the value in quotation marks (").

The Section parameter specifies the name of the section for which the override is created. The available values for this parameter depend on the value of the Component parameter.

The Server parameter specifies the name of the Exchange 2016 server where you want the override applied. You can specify a single Exchange 2016 server name, or an array of Exchange 2016 server name wildcards. For example, if you have three Exchange 2016 servers named Exchange01, Exchange02 and Exchange03, specify the value Exchange* to apply the override to all of them.

If you don't use this parameter to specify a server, the override applies to all Exchange 2016 servers in the Active Directory forest.

The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.