COMMAND EVERYTHING.
Enables a previously disabled main mode rule.
Microsoft NetSecurity reference: Enables a previously disabled main mode rule. 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 Enable-NetIPsecMainModeRule. 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
-All- Indicates that all of the main mode rules within the specified policy store are enabled.
-AsJob- Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete.
-AssociatedNetFirewallAddressFilter (required)- Gets the main mode rules that are associated with the given address filter to be enabled. A NetFirewallAddressFilter object represents the address conditions associated with a rule. See the Get-NetFirewallAddressFilter cmdlet for more information.
-AssociatedNetFirewallProfile (required)- Gets the main mode rules that are associated with the given firewall profile type to be enabled. A NetFirewallProfile object represents the profile conditions associated with a rule. See the Get-NetFirewallProfile cmdlet for more information.
-AssociatedNetIPsecMainModeCryptoSet (required)- Gets the main mode rules that are associated, via the pipeline, with the input main mode cryptographic set to be enabled. A NetIPsecMainModeCryptoSet object represents a main mode cryptographic conditions associated with a main mode rule. This parameter sets the methods for the main mode negotiation by describing the proposals for encryption. See the Get-NetIPsecMainModeCryptoSet cmdlet for more information. Alternatively, the *MainModeCryptoSet* parameter can be used for the same purpose, but does not allow the cryptographic set to be piped into this cmdlet and the set must be specified with the *Name* parameter.
-AssociatedNetIPsecPhase1AuthSet (required)- Gets the IPsec rules that are associated with the given phase 1 authentication set to be enabled. A NetIPsecPhase1AuthSet object represents the phase 1 authorization set conditions associated with an IPsec or main mode rule. This parameter sets the methods for main mode negotiation by describing the proposals for computer authentication. See the Get-NetIPsecPhase1AuthSet cmdlet for more information. Alternatively, the *Phase1AuthSet* parameter can be used for the same purpose, but does not allow the authentication set to be piped into the cmdlet and the set must be specified with the *Name* parameter.
-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 rules of the indicated description are enabled. Wildcard characters are accepted. This parameter provides information about the main mode rule. This parameter specifies the localized, user-facing description of the IPsec rule.
-DisplayGroup- Specifies that only matching main mode rules of the indicated group association are enabled. 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 the Set-NetIPsecMainModeRule 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 value with a universal and world-ready indirect @FirewallAPI name. This parameter cannot be specified upon object creation using the New-NetIPsecMainModeRule cmdlet, but can be modified using dot-notation and the Set-NetIPsecMainModeRule cmdlet.
-DisplayName (required)- Specifies that only matching main mode rules of the indicated display name are enabled. Wildcard characters are accepted. Specifies the localized, user-facing name of the main mode rule being created. When creating a rule 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 scripts in multi-lingual environments, the *Name* parameter should be used instead, where the default value is a randomly assigned value. This parameter cannot be set to All.
-Enabled- Specifies that matching main mode rules of the indicated state are enabled. This parameter specifies that the rule object is administratively enabled or administratively enabled. The acceptable values for this parameter are: - True: Specifies the rule is currently enabled. - False: Specifies the rule is currently disabled. A disabled rule will not actively modify computer behavior, but the management construct still exists on the computer so it can be re-enabled.
-GPOSession- Specifies the network Group Policy Object (GPO) from which to retrieve the rules to be enabled. This parameter is used in the same way as the *PolicyStore* parameter. When modifying 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- Specifies that only matching main mode rules of the indicated group association are enabled. 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 can be used to organize rules by influence and allows batch rule modifications. Using the Set-NetIPsecMainModeRule cmdlets, 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 value with a universal and world-ready indirect @FirewallAPI name. The *DisplayGroup* parameter cannot be specified upon object creation using the New-NetIPsecMainModeRule cmdlet, but can be modified using dot-notation and the Set-NetIPsecMainModeRule cmdlet.
-InputObject (required)- Specifies the input object that is used in a pipeline command.
-MainModeCryptoSet- Gets the IPsec main mode rules that are associated with the given main mode cryptographic set to be enabled. Specifies, by Name, the main mode cryptographic set to be associated with the main mode rule. A NetIPsecMainModeCryptoSet object represents a main mode cryptographic conditions associated with a main mode rule. This parameter sets the methods for main mode negotiation by describing the proposals for encryption. This is only associated with main mode rules. See the Get-NetIPsecMainModeCryptoSet cmdlet for more information. Alternatively, the *AssociatedNetIPsecMainModeCryptoSet* parameter can be used for the same purpose, but is used to pipe the input set into the rule. When specifying cryptographic sets, the *Name* parameter value of the cryptographic set must be used. The object cannot be directly passed into this cmdlet.
-Name (required)- Specifies that only matching main mode rules of the indicated name are enabled. 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 main mode 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 with the same name in a higher-precedence GPO, then it overrides other rules that exist. The default value is a randomly assigned value. When the defaults for main mode encryption need to overridden, specify the customized parameters and set this parameter, making this parameter the new default setting for encryption.
-PassThru- Returns an object representing the item with which you are working. By default, this cmdlet does not generate any output.
-Phase1AuthSet- Gets the main mode rules that are associated with the given phase 1 authentication set to be enabled. This parameter specifies, by name, the Phase 1 authentication set to be associated with the main mode rule. A NetIPsecPhase1AuthSet object represents the phase 1 authentication conditions associated with an IPsec or main mode rule. This parameter sets the methods for main mode negotiation by describing the proposals for computer authentication. See the New-NetIPsecAuthProposal cmdlet of more information. Alternatively, the *AssociatedNetIPsecPhase1AuthSet* parameter can be used for the same purpose, but is used to pipe the input set into the rule.
-PolicyStore- Targets the policy store from which to retrieve the rules to be enabled. 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 system 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 main mode 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 added
-PolicyStoreSource- Specifies that main mode rules matching the indicated policy store source are enabled. This parameter contains a path to the policy store where the rule originated if the object is retrieved from the ActiveStore with the TracePolicyStoreSource option set. This parameter value is automatically generated and should not be modified. The monitoring output from this parameter is not completely compatible with the *PolicyStore* parameter. This parameter value cannot always be passed into the *PolicyStore* parameter. Domain GPOs are one example in which this parameter contains only the GPO name, not the domain name.
-PolicyStoreSourceType- Specifies that main mode rules that match the indicated policy store source type are enabled. This parameter describes the type of policy store where the rule originated if the object is retrieved from the ActiveStore with the TracePolicyStoreSource option set. This parameter value is automatically generated and should not be modified. The acceptable values for this parameter are: - Local: The object originates from the local store. - GroupPolicy: The object originates from a GPO. - Dynamic: The object originates from the local runtime state. This policy store name is not valid for use in the cmdlets, but may appear when monitoring active policy. - Generated: The object was generated automatically. This policy store name is not valid for use in the cmdlets, but may appear when monitoring active policy. - Hardcoded: The object was hard-coded. This policy store name is not valid for use in the cmdlets, but may appear when monitoring active policy.
-PrimaryStatus- Specifies that main mode rules that match the indicated primary status are enabled. This parameter specifies the overall status of the rule. - OK: Specifies that the rule will work as specified. - Degraded: Specifies that one or more parts of the rule will not be enforced. - Error: Specifies that the computer is unable to use the rule at all. See the Status and StatusCode fields of the object for more detailed status information.
-Status- Specifies that main mode rules that match the indicated status are enabled. This parameter describes the status message for the specified status code value. The status code is a numerical value that indicates any syntax, parsing, or runtime errors in the rule or set. This parameter value should not be modified.
-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.
-TracePolicyStore- Indicates that the main mode rules that match the indicated policy store are enabled. This parameter specifies that the name of the source GPO is set to the *PolicyStoreSource* parameter value.
-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.