COMMAND EVERYTHING.
Modifies existing main mode cryptographic sets.
Microsoft NetSecurity reference: Modifies existing main mode cryptographic sets. The syntax and selected example below are adapted from the pinned Windows Server 2025 reference. Module availability, target configuration and delegated permissions determine whether it can run in your environment. Documentation and parameter text: Microsoft, CC BY 4.0; formatting adapted by Cmdlet World. No execution testing is claimed.
Use an account with the target resource permissions documented for Set-NetIPsecMainModeCryptoSet. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.
Windows / NetSecurity · Windows Server 2025 documentation; feature/module prerequisites apply
-AsJob- Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete.
-CimSession- Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.
-Confirm- Prompts you for confirmation before running the cmdlet.
-Description- Specifies that matching main mode cryptographic sets of the indicated description are modified. Wildcard characters are accepted. This parameter provides information about the main mode cryptographic sets. This parameter specifies a localized, user-facing description of the object.
-DisplayGroup (required)- Specifies that only matching main mode cryptographic sets of the indicated group association are modified. Wildcard characters are accepted. The *Group* parameter specifies the source string for this parameter. If the value for this parameter is a localizable string, then the *Group* parameter contains an indirect string. Rule groups can be used to organize rules by influence and allows batch rule modifications. Using this cmdlet, if the group name is specified for a set of rules or sets, then all of the rules or sets in that group receive the same set of modifications. It is good practice to specify the *Group* parameter with a universal and world-ready indirect @FirewallAPI name. This parameter cannot be specified upon object creation using the New-NetIPsecMainModeCryptoSet cmdlet, but can be modified using dot notation and this cmdlet.
-DisplayName (required)- Specifies that only matching main mode cryptographic sets of the indicated display name are modified. Wildcard characters are accepted. This parameter specifies the localized, user-facing name of a single main mode cryptographic sets. When creating a set this parameter is required. This parameter value is locale-dependent. If the object is not modified, this parameter value may change in certain circumstances. When writing resilient scripts, the *Name* parameter should be used instead, where the default value is a randomly assigned value. This parameter value cannot be All.
-ForceDiffieHellman- Indicates that matching main mode cryptographic sets of the indicated value are modified. If this parameter is set to True, then IPsec uses Diffie-Hellman exchanges to protect the main mode key exchange when AuthIP is used. AuthIP is specified by KeyModule. This provides stronger security for the key exchange. The default value is False.
-GPOSession- Specifies the network GPO from which to retrieve the sets to be modified. This parameter is used in the same way as the *PolicyStore* parameter. When modifying Group Policy Objects (GPOs) in Windows PowerShell®, each change to a GPO requires the entire GPO to be loaded, modified, and saved back. On a busy Domain Controller (DC), this can be a slow and resource-heavy operation. A GPO Session loads a domain GPO onto the local computer and makes all changes in a batch, before saving it back. This reduces the load on the DC and speeds up the Windows PowerShell cmdlets. To load a GPO Session, use the Open-NetGPO cmdlet. To save a GPO Session, use the Save-NetGPO cmdlet.
-Group (required)- Specifies that only matching main mode cryptographic sets of the indicated group association are modified. Wildcard characters are accepted. This parameter specifies the source string for the *DisplayGroup* parameter. If the *DisplayGroup* parameter value is a localizable string, then this parameter contains an indirect string. Rule groups organize rules by influence and allows batch rule modifications. Using this cmdlet, if the group name is specified for a set of rules or sets, then all of the rules or sets in that group receive the same set of modifications. It is good practice to specify this parameter with a universal and world-ready indirect @FirewallAPI name. The *DisplayGroup* parameter cannot be specified upon object creation using the New-NetIPsecMainModeCryptoSet cmdlet, but can be modified using dot notation and this cmdlet.
-InputObject (required)- Specifies the input object that is used in a pipeline command.
-MaxMinutes- Specifies that matching main mode cryptographic sets of the indicated maximum lifetime, in minutes, are modified. This parameter specifies the number of minutes established for a main mode security association before it expires and must be renegotiated. The acceptable values for this parameter are: 0 through 2879. - A non-zero value specifies the desired minute lifetime. - NotConfigured: Valid only when configuring a GPO. Removes the setting from the GPO, which results in the policy not changing the value on the computer when the policy is applied. The default value is 480 minutes (eight hours). When managing a GPO, the default setting is NotConfigured.
-MaxSessions- Specifies that matching main mode cryptographic sets of the indicated maximum lifetime, in sessions, are modified. This parameter specifies the number of sessions established for a main mode security association before it expires and must be renegotiated. The acceptable values for this parameter are: 0 through 2147483647. - A value of zero (0) specifies that there should be no maximum session lifetime. - A non-zero value specifies the desired session number. - NotConfigured: Valid only when configuring a GPO. Removes the setting from the GPO, which results in the policy not changing the value on the computer when the policy is applied. The default value is zero (0) sessions. When managing a GPO, the default setting is NotConfigured.
-Name (required)- Specifies that only matching main mode cryptographic sets of the indicated name are modified. Wildcard characters are accepted. This parameter acts just like a file name, in that only one rule with a given name may exist in a policy store at a time. During group policy processing and policy merge, rules that have the same name but come from multiple stores being merged, will overwrite one another so that only one exists. This overwriting behavior is desirable if the rules serve the same purpose. For instance, all of the firewall rules have specific names, so if an administrator can copy these rules to a GPO, and the rules will override the local versions on a local computer. GPOs can have precedence. So, if an administrator has a different or more specific rule the same name in a higher-precedence GPO, then it overrides other rules that exist. The default value is a randomly assigned value. When you want to override the defaults for main mode encryption, specify the customized parameters and set this parameter, making this parameter the new default setting for encryption.
-NewDisplayName- Specifies the new display name for a main mode cryptographic set.
-PassThru- Returns an object representing the item with which you are working. By default, this cmdlet does not generate any output.
-PolicyStore- Specifies the policy store from which to retrieve the sets to be modified. A policy store is a container for firewall and IPsec policy. The acceptable values for this parameter are: - PersistentStore: Sometimes called static rules, this store contains the persistent policy for the local computer. This policy is not from GPOs, and has been created manually or programmatically, during application installation, on the computer. Rules created in this store are attached to the ActiveStore and activated on the computer immediately. - ActiveStore: This store contains the currently active policy, which is the sum of all policy stores that apply to the computer. This is the resultant set of policy (RSOP) for the local computer (the sum of all GPOs that apply to the computer), and the local stores (the PersistentStore, the Static Windows Service Hardening (WSH), and the Configurable WSH). ---- GPOs are also policy stores. Computer GPOs can be specified as follows. ------ -PolicyStore hostname. ---- Active Directory GPOs can be specified as follows. ------ -PolicyStore domain.fqdn.com\GPO_Friendly_Namedomain.fqdn.comGPO_Friendly_Name. ------ Such as the following. -------- -PolicyStore localhost -------- -PolicyStore corp.contoso.com\FirewallPolicy ---- Active Directory GPOs can be created using the New-GPO cmdlet or the Group Policy Management Console. - RSOP: This read-only store contains the sum of all GPOs applied to the local computer. - SystemDefaults: This read-only store contains the default state of firewall rules that ship with Windows Server® 2012. - StaticServiceStore: This read-only store contains all the service restrictions that ship with Windows Server 2012. Optional and product-dependent features are considered part of Windows Server 2012 for the purposes of WFAS. - ConfigurableServiceStore: This read-write store contains all the service restrictions that are ad
-Proposal- Associates the specified cryptographic proposal to the corresponding cryptographic set to be used in main mode negotiations. Separate multiple entries with a comma.
-ThrottleLimit- Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.
-WhatIf- Shows what would happen if the cmdlet runs. The cmdlet is not run.
Windows with the NetSecurity module and the Windows feature or management tools that provide it. Confirm target connectivity and version compatibility using the linked Microsoft reference.
This cmdlet changes system state. Review every target and parameter in the official reference, test outside production, and prepare an appropriate backup or rollback. Do not execute the example automatically.