mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-11 21:07:23 +00:00
updates
This commit is contained in:
Paolo Matarazzo
parent
de4e423604
commit
c03403df59
@ -6,4 +6,4 @@ ms.topic: include
|
||||
ms.prod: windows-client
|
||||
---
|
||||
|
||||
To configure a device using group policy, use the [Local Group Policy Editor](/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc731745(v=ws.10)). To configure multiple devices joined to Active Directory, [create or edit](/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc754740(v=ws.11)) a group policy object (GPO) and use the following settings:
|
||||
To configure a device with group policy, use the [Local Group Policy Editor](/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc731745(v=ws.10)). To configure multiple devices joined to Active Directory, [create or edit](/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc754740(v=ws.11)) a group policy object (GPO) and use the following settings:
|
||||
|
||||
@ -6,4 +6,4 @@ ms.topic: include
|
||||
ms.prod: windows-client
|
||||
---
|
||||
|
||||
To configure devices using Microsoft Intune, [create a Settings catalog policy](/mem/intune/configuration/settings-catalog) and use the following settings:
|
||||
To configure devices with Microsoft Intune, [create a Settings catalog policy](/mem/intune/configuration/settings-catalog) and use the following settings:
|
||||
@ -6,4 +6,4 @@ ms.topic: include
|
||||
ms.prod: windows-client
|
||||
---
|
||||
|
||||
To configure devices using the [Registry Editor](/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc755256(v=ws.11)), use the following settings:
|
||||
To configure devices with the [Registry Editor](/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc755256(v=ws.11)), use the following settings:
|
||||
@ -10,11 +10,9 @@ ms.date: 10/30/2023
|
||||
To configure BitLocker, you can use one of the following options:
|
||||
|
||||
- Configuration Service Provider (CSP): this option is commonly used for devices managed by a Mobile Device Management (MDM) solution, like Microsoft Intune. The [BitLocker CSP][WIN-1] is used to configure BitLocker, and to report the status of different BitLocker functions to the MDM solution. With Microsoft Intune, you can use the BitLocker status in [compliance policies][INT-1], combining them with [Conditional Access][ENTRA-1]. Conditional Access can prevent or grant access to services like Exchange Online and SharePoint Online, based on the status of BitLocker. To learn more about the Intune options to configure and monitor BitLocker, check the following articles:
|
||||
|
||||
- [Manage BitLocker policy for Windows devices with Intune][INT-2]
|
||||
- [Monitor device encryption with Intune][INT-3]
|
||||
- [Use compliance policies to set rules for devices you manage with Intune][INT-4]
|
||||
|
||||
- Group policy (GPO): this option can be used for devices that are joined to an Active Directory domain and aren't managed by a device management solution. Group policy can also be used for devices that aren't joined to an Active Directory domain, using the local group policy editor
|
||||
- Microsoft Configuration Manager: this option can be used for devices that are managed by Microsoft Configuration Manager using the BitLocker management agent. To learn more about options to configure BitLocker via Microsoft Configuration Manager, see [Deploy BitLocker management][MCM-1]
|
||||
|
||||
|
||||
@ -1,45 +1,48 @@
|
||||
---
|
||||
title: Windows Defender Firewall with Advanced Security Administration with Windows PowerShell
|
||||
description: Windows Defender Firewall with Advanced Security Administration with
|
||||
title: Manage Windows Firewall with PowerShell
|
||||
description: Learn how to manage Windows Firewall from the command line. This guide provides examples how to manage Windows Firewall with PowerShell and Netsh.
|
||||
ms.topic: conceptual
|
||||
ms.date: 09/08/2021
|
||||
ms.date: 11/14/2023
|
||||
---
|
||||
|
||||
# Manage Windows Firewall with PowerShell
|
||||
|
||||
The Windows Defender Firewall with Advanced Security Administration with Windows PowerShell Guide provides essential scriptlets for automating Windows Defender Firewall management. It's designed for IT pros, system administrators, IT managers, and others who use and need to automate Windows Defender Firewall management in Windows.
|
||||
You can use Windows PowerShell to manage your firewall and IPsec deployments. This object-oriented scripting environment will make it easier for you to manage policies and monitor network conditions than was possible in netsh. Windows PowerShell allows network settings to be self-discoverable through the syntax and parameters in each of the cmdlets. This guide demonstrates how common tasks were performed in netsh and how you can use Windows PowerShell to accomplish them.
|
||||
In future versions of Windows, Microsoft might remove the netsh functionality for Windows Defender Firewall. Microsoft recommends that you transition to Windows PowerShell if you currently use netsh to configure and manage Windows Defender Firewall.
|
||||
Windows PowerShell and netsh command references are at the following locations.
|
||||
- [Netsh Commands for Windows Defender Firewall](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc771920(v=ws.10))
|
||||
## Scope
|
||||
This guide doesn't teach you the fundamentals of Windows Defender Firewall, which can be found in [Windows Firewall](index.md). It doesn't teach the fundamentals of Windows PowerShell, and it assumes that you're familiar with the Windows PowerShell language and the basic concepts of Windows PowerShell. For more info about Windows PowerShell concepts and usage, see the reference topics in the [Additional resources](#other-resources) section of this guide.
|
||||
## Audience and user requirements
|
||||
This guide is intended for IT pros, system administrators, and IT managers, and it assumes that you're familiar with Windows Defender Firewall, the Windows PowerShell language, and the basic concepts of Windows PowerShell.
|
||||
This article provides examples how to manage Windows Firewall with PowerShell and `netsh.exe`, which can be used to automate the management of Windows Firewall.
|
||||
|
||||
## Set profile global defaults
|
||||
|
||||
Global defaults set the device behavior in a per-profile basis. Windows Defender Firewall supports Domain, Private, and Public profiles.
|
||||
Global defaults set the device behavior in a per-profile basis. Windows Firewall supports Domain, Private, and Public profiles.
|
||||
|
||||
### Enable Windows Defender Firewall with Advanced Security
|
||||
### Enable Windows Firewall
|
||||
|
||||
Windows Firewall drops traffic that doesn't correspond to allowed unsolicited traffic, or traffic that is sent in response to a request by the device. If you find that the rules you create aren't enforced, you might need to enable Windows Firewall. Here's how to enable Windows Firewall on a local device:
|
||||
|
||||
#### [:::image type="icon" source="images/powershell.svg"::: **PowerShell**](#tab/powershell)
|
||||
|
||||
Windows Defender Firewall drops traffic that doesn't correspond to
|
||||
allowed unsolicited traffic, or traffic that is sent in response to a request by the device. If you find that the rules you create aren't being enforced, you may need to enable Windows Defender Firewall. Here's how to enable Windows Defender Firewall on a local domain device:
|
||||
**Netsh**
|
||||
``` cmd
|
||||
netsh.exe advfirewall set allprofiles state on
|
||||
```
|
||||
**Windows PowerShell**
|
||||
```powershell
|
||||
Set-NetFirewallProfile -Profile Domain,Public,Private -Enabled True
|
||||
```
|
||||
|
||||
### Control Windows Defender Firewall with Advanced Security behavior
|
||||
#### [:::image type="icon" source="images/cmd.svg"::: **Command Prompt**](#tab/cmd)
|
||||
|
||||
The global default settings can be defined through the command-line interface. These modifications are also available through the Windows Defender Firewall with Advanced Security console.
|
||||
``` cmd
|
||||
netsh.exe advfirewall set allprofiles state on
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Control Windows Firewall behavior
|
||||
|
||||
The global default settings can be defined through the command-line interface. These modifications are also available through the Windows Firewall console.
|
||||
The following scriptlets set the default inbound and outbound actions, specifies protected network connections, and allows notifications to be displayed to the user when a program is blocked from receiving inbound connections. It allows unicast response to multicast or broadcast network traffic, and it specifies logging settings for troubleshooting.
|
||||
|
||||
**Netsh**
|
||||
#### [:::image type="icon" source="images/powershell.svg"::: **PowerShell**](#tab/powershell)
|
||||
|
||||
```powershell
|
||||
Set-NetFirewallProfile -DefaultInboundAction Block -DefaultOutboundAction Allow -NotifyOnListen True -AllowUnicastResponseToMulticast True -LogFileName %SystemRoot%\System32\LogFiles\Firewall\pfirewall.log
|
||||
```
|
||||
|
||||
#### [:::image type="icon" source="images/cmd.svg"::: **Command Prompt**](#tab/cmd)
|
||||
|
||||
```cmd
|
||||
netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound
|
||||
@ -48,34 +51,47 @@ netsh advfirewall set allprofiles settings unicastresponsetomulticast enable
|
||||
netsh advfirewall set allprofiles logging filename %SystemRoot%\System32\LogFiles\Firewall\pfirewall.log
|
||||
```
|
||||
|
||||
```powershell
|
||||
Set-NetFirewallProfile -DefaultInboundAction Block -DefaultOutboundAction Allow -NotifyOnListen True -AllowUnicastResponseToMulticast True -LogFileName %SystemRoot%\System32\LogFiles\Firewall\pfirewall.log
|
||||
```
|
||||
### Disable Windows Defender Firewall with Advanced Security
|
||||
Microsoft recommends that you don't disable Windows Defender Firewall because you lose other benefits provided by the service, such as the ability to use Internet Protocol security (IPsec) connection security rules, network protection from attacks that employ network fingerprinting, [Windows Service Hardening](https://go.microsoft.com/fwlink/?linkid=104976), and [boot time filters](https://blogs.technet.microsoft.com/networking/2009/03/24/stopping-the-windows-authenticating-firewall-service-and-the-boot-time-policy/).
|
||||
Disabling Windows Defender Firewall with Advanced Security can also cause problems, including:
|
||||
---
|
||||
|
||||
### Disable Windows Firewall
|
||||
|
||||
Microsoft recommends that you don't disable Windows Firewall because you lose other benefits provided by the service, such as the ability to use Internet Protocol security (IPsec) connection security rules, network protection from attacks that employ network fingerprinting, [Windows Service Hardening](https://go.microsoft.com/fwlink/?linkid=104976), and [boot time filters](https://blogs.technet.microsoft.com/networking/2009/03/24/stopping-the-windows-authenticating-firewall-service-and-the-boot-time-policy/).
|
||||
Disabling Windows Firewall can also cause problems, including:
|
||||
|
||||
- Start menu can stop working
|
||||
- Modern applications can fail to install or update
|
||||
- Activation of Windows via phone fails
|
||||
- Application or OS incompatibilities that depend on Windows Defender Firewall
|
||||
Microsoft recommends disabling Windows Defender Firewall only when installing a third-party firewall, and resetting Windows Defender Firewall back to defaults when the third-party software is disabled or removed.
|
||||
If disabling Windows Defender Firewall is required, don't disable it by stopping the Windows Defender Firewall service (in the **Services** snap-in, the display name is Windows Defender Firewall and the service name is MpsSvc).
|
||||
Stopping the Windows Defender Firewall service isn't supported by Microsoft.
|
||||
Non-Microsoft firewall software can programmatically disable only the parts of Windows Defender Firewall that need to be disabled for compatibility.
|
||||
- Application or OS incompatibilities that depend on Windows Firewall
|
||||
|
||||
Microsoft recommends disabling Windows Firewall only when installing a third-party firewall, and resetting Windows Firewall back to defaults when the third-party software is disabled or removed.
|
||||
If disabling Windows Firewall is required, don't disable it by stopping the Windows Firewall service (in the **Services** snap-in, the display name is Windows Firewall and the service name is MpsSvc).
|
||||
Stopping the Windows Firewall service isn't supported by Microsoft.
|
||||
Non-Microsoft firewall software can programmatically disable only the parts of Windows Firewall that need to be disabled for compatibility.
|
||||
You shouldn't disable the firewall yourself for this purpose.
|
||||
The proper method to disable the Windows Defender Firewall is to disable the Windows Defender Firewall Profiles and leave the service running.
|
||||
Use the following procedure to turn off the firewall, or disable the Group Policy setting **Computer Configuration|Administrative Templates|Network|Network Connections|Windows Defender Firewall|Domain Prolfile|Windows Defender Firewall:Protect all network connections**.
|
||||
For more information, see [Windows Defender Firewall with Advanced Security deployment guide](windows-firewall-with-advanced-security-deployment-guide.md).
|
||||
The following example disables Windows Defender Firewall for all profiles.
|
||||
The proper method to disable the Windows Firewall is to disable the Windows Firewall Profiles and leave the service running.
|
||||
Use the following procedure to turn off the firewall, or disable the Group Policy setting **Computer Configuration|Administrative Templates|Network|Network Connections|Windows Firewall|Domain Prolfile|Windows Firewall:Protect all network connections**.
|
||||
For more information, see [Windows Firewall deployment guide](windows-firewall-with-advanced-security-deployment-guide.md).
|
||||
The following example disables Windows Firewall for all profiles.
|
||||
|
||||
#### [:::image type="icon" source="images/powershell.svg"::: **PowerShell**](#tab/powershell)
|
||||
|
||||
```powershell
|
||||
Set-NetFirewallProfile -Profile Domain,Public,Private -Enabled False
|
||||
```
|
||||
|
||||
#### [:::image type="icon" source="images/cmd.svg"::: **Command Prompt**](#tab/cmd)
|
||||
|
||||
---
|
||||
|
||||
## Deploy basic firewall rules
|
||||
|
||||
This section provides scriptlet examples for creating, modifying, and deleting firewall rules.
|
||||
|
||||
### Create firewall rules
|
||||
|
||||
Adding a firewall rule in Windows PowerShell looks a lot like it did in Netsh, but the parameters and values are specified differently.
|
||||
Here's an example of how to allow the Telnet application to listen on the network. This firewall rule is scoped to the local subnet by using a keyword instead of an IP address. Just like in Netsh, the rule is created on the local device, and it becomes effective immediately.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall firewall add rule name="Allow Inbound Telnet" dir=in program= %SystemRoot%\System32\tlntsvr.exe remoteip=localsubnet action=allow
|
||||
```
|
||||
@ -83,9 +99,10 @@ netsh advfirewall firewall add rule name="Allow Inbound Telnet" dir=in program=
|
||||
```powershell
|
||||
New-NetFirewallRule -DisplayName "Allow Inbound Telnet" -Direction Inbound -Program %SystemRoot%\System32\tlntsvr.exe -RemoteAddress LocalSubnet -Action Allow
|
||||
```
|
||||
|
||||
The following scriptlet shows how to add a basic firewall rule that blocks outbound traffic from a specific application and local port to a Group Policy Object (GPO) in Active Directory. In Windows PowerShell, the policy store is specified as a parameter within the **New-NetFirewall** cmdlet. In Netsh, you must first specify the GPO that the commands in a Netsh session should modify. The commands you enter are run against the contents of the GPO, and the execution remains in effect until the Netsh session is ended or until another set store command is executed.
|
||||
Here, **domain.contoso.com** is the name of your Active Directory Domain Services (AD DS), and **gpo\_name** is the name of the GPO that you want to modify. Quotation marks are required if there are any spaces in the GPO name.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall set store gpo=domain.contoso.com\gpo_name
|
||||
netsh advfirewall firewall add rule name="Block Outbound Telnet" dir=out program=%SystemRoot%\System32\telnet.exe protocol=tcp localport=23 action=block
|
||||
@ -94,7 +111,9 @@ netsh advfirewall firewall add rule name="Block Outbound Telnet" dir=out program
|
||||
```powershell
|
||||
New-NetFirewallRule -DisplayName "Block Outbound Telnet" -Direction Outbound -Program %SystemRoot%\System32\tlntsvr.exe -Protocol TCP -LocalPort 23 -Action Block -PolicyStore domain.contoso.com\gpo_name
|
||||
```
|
||||
|
||||
### GPO Caching
|
||||
|
||||
To reduce the burden on busy domain controllers, Windows PowerShell allows you to load a GPO to your local session, make all your changes in that session, and then save it back at all once.
|
||||
The following command performs the same actions as the previous example (by adding a Telnet rule to a GPO), but we do so by applying GPO caching in PowerShell. Changing the GPO by loading it onto your local session and using the *-GPOSession* parameter aren't supported in Netsh
|
||||
|
||||
@ -103,11 +122,14 @@ $gpo = Open-NetGPO -PolicyStore domain.contoso.com\gpo_name
|
||||
New-NetFirewallRule -DisplayName "Block Outbound Telnet" -Direction Outbound -Program %SystemRoot%\System32\telnet.exe -Protocol TCP -LocalPort 23 -Action Block -GPOSession $gpo
|
||||
Save-NetGPO -GPOSession $gpo
|
||||
```
|
||||
|
||||
This command doesn't batch your individual changes, it loads and saves the entire GPO at once. So if any other changes are made by other administrators, or in a different Windows PowerShell window, saving the GPO overwrites those changes.
|
||||
|
||||
### Modify an existing firewall rule
|
||||
|
||||
When a rule is created, Netsh and Windows PowerShell allow you to change rule properties and influence, but the rule maintains its unique identifier (in Windows PowerShell, this identifier is specified with the *-Name* parameter).
|
||||
For example, you could have a rule **Allow Web 80** that enables TCP port 80 for inbound unsolicited traffic. You can change the rule to match a different remote IP address of a Web server whose traffic will be allowed by specifying the human-readable, localized name of the rule.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall firewall set rule name="Allow Web 80" new remoteip=192.168.0.2
|
||||
```
|
||||
@ -115,6 +137,7 @@ netsh advfirewall firewall set rule name="Allow Web 80" new remoteip=192.168.0.2
|
||||
```powershell
|
||||
Set-NetFirewallRule -DisplayName "Allow Web 80" -RemoteAddress 192.168.0.2
|
||||
```
|
||||
|
||||
Netsh requires you to provide the name of the rule for it to be changed and we don't have an alternate way of getting the firewall rule. In Windows PowerShell, you can query for the rule using its known properties.
|
||||
When you run `Get-NetFirewallRule`, you may notice that common conditions like addresses and ports don't appear. These conditions are represented in separate objects called Filters. As shown before, you can set all the conditions in New-NetFirewallRule and Set-NetFirewallRule. If you want to query for firewall rules based on these fields (ports, addresses, security, interfaces, services), you'll need to get the filter objects themselves.
|
||||
You can change the remote endpoint of the **Allow Web 80** rule (as done previously) using filter objects. Using Windows PowerShell, you query by port using the port filter, then assuming other rules exist affecting the local port, you build with further queries until your desired rule is retrieved.
|
||||
@ -123,11 +146,13 @@ In the following example, we assume the query returns a single firewall rule, wh
|
||||
```powershell
|
||||
Get-NetFirewallPortFilter | ?{$_.LocalPort -eq 80} | Get-NetFirewallRule | ?{ $_.Direction -eq "Inbound" -and $_.Action -eq "Allow"} | Set-NetFirewallRule -RemoteAddress 192.168.0.2
|
||||
```
|
||||
|
||||
You can also query for rules using the wildcard character. The following example returns an array of firewall rules associated with a particular program. The elements of the array can be modified in subsequent `Set-NetFirewallRule` cmdlets.
|
||||
|
||||
```powershell
|
||||
Get-NetFirewallApplicationFilter -Program "*svchost*" | Get-NetFirewallRule
|
||||
```
|
||||
|
||||
Multiple rules in a group can be simultaneously modified when the associated group name is specified in a Set command. You can add firewall rules to specified management groups in order to manage multiple rules that share the same influences.
|
||||
In the following example, we add both inbound and outbound Telnet firewall rules to the group **Telnet Management**. In Windows PowerShell, group membership is specified when the rules are first created so we re-create the previous example rules. Adding rules to a custom rule group isn't possible in Netsh.
|
||||
|
||||
@ -135,6 +160,7 @@ In the following example, we add both inbound and outbound Telnet firewall rules
|
||||
New-NetFirewallRule -DisplayName "Allow Inbound Telnet" -Direction Inbound -Program %SystemRoot%\System32\tlntsvr.exe -RemoteAddress LocalSubnet -Action Allow -Group "Telnet Management"
|
||||
New-NetFirewallRule -DisplayName "Block Outbound Telnet" -Direction Outbound -Program %SystemRoot%\System32\tlntsvr.exe -RemoteAddress LocalSubnet -Action Allow -Group "Telnet Management"
|
||||
```
|
||||
|
||||
If the group isn't specified at rule creation time, the rule can be added to the rule group using dot notation in Windows PowerShell. You can't specify the group using `Set-NetFirewallRule` since the command allows querying by rule group.
|
||||
|
||||
```powershell
|
||||
@ -142,25 +168,29 @@ $rule = Get-NetFirewallRule -DisplayName "Allow Inbound Telnet"
|
||||
$rule.Group = "Telnet Management"
|
||||
$rule | Set-NetFirewallRule
|
||||
```
|
||||
|
||||
With the help of the `Set` command, if the rule group name is specified, the group membership isn't modified but rather all rules of the group receive the same modifications indicated by the given parameters.
|
||||
The following scriptlet enables all rules in a predefined group containing remote management influencing firewall rules.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall firewall set rule group="Windows Defender Firewall remote management" new enable=yes
|
||||
netsh advfirewall firewall set rule group="Windows Firewall remote management" new enable=yes
|
||||
```
|
||||
|
||||
```powershell
|
||||
Set-NetFirewallRule -DisplayGroup "Windows Defender Firewall Remote Management" -Enabled True
|
||||
Set-NetFirewallRule -DisplayGroup "Windows Firewall Remote Management" -Enabled True
|
||||
```
|
||||
|
||||
There's also a separate `Enable-NetFirewallRule` cmdlet for enabling rules by group or by other properties of the rule.
|
||||
|
||||
```powershell
|
||||
Enable-NetFirewallRule -DisplayGroup "Windows Defender Firewall Remote Management" -Verbose
|
||||
Enable-NetFirewallRule -DisplayGroup "Windows Firewall Remote Management" -Verbose
|
||||
```
|
||||
|
||||
### Delete a firewall rule
|
||||
|
||||
Rule objects can be disabled so that they're no longer active. In Windows PowerShell, the **Disable-NetFirewallRule** cmdlet will leave the rule on the system, but put it in a disabled state so the rule no longer is applied and impacts traffic. A disabled firewall rule can be re-enabled by **Enable-NetFirewallRule**. This cmdlet is different from the **Remove-NetFirewallRule**, which permanently removes the rule definition from the device.
|
||||
The following cmdlet deletes the specified existing firewall rule from the local policy store.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall firewall delete rule name="Allow Web 80"
|
||||
```
|
||||
@ -168,11 +198,13 @@ netsh advfirewall firewall delete rule name="Allow Web 80"
|
||||
```powershell
|
||||
Remove-NetFirewallRule -DisplayName "Allow Web 80"
|
||||
```
|
||||
|
||||
Like with other cmdlets, you can also query for rules to be removed. Here, all blocking firewall rules are deleted from the device.
|
||||
|
||||
```powershell
|
||||
Remove-NetFirewallRule -Action Block
|
||||
```
|
||||
|
||||
It may be safer to query the rules with the **Get** command and save it in a variable, observe the rules to be affected, then pipe them to the **Remove** command, just as we did for the **Set** commands. The following example shows how you can view all the blocking firewall rules, and then delete the first four rules.
|
||||
|
||||
```powershell
|
||||
@ -180,27 +212,34 @@ $x = Get-NetFirewallRule -Action Block
|
||||
$x
|
||||
$x[0-3] | Remove-NetFirewallRule
|
||||
```
|
||||
|
||||
## Manage remotely
|
||||
|
||||
Remote management using WinRM is enabled by default. The cmdlets that support the *CimSession* parameter use WinRM and can be managed remotely by default.
|
||||
The following example returns all firewall rules of the persistent store on a device named **RemoteDevice**.
|
||||
|
||||
```powershell
|
||||
Get-NetFirewallRule -CimSession RemoteDevice
|
||||
```
|
||||
|
||||
We can perform any modifications or view rules on remote devices by using the *-CimSession* parameter. Here we remove a specific firewall rule from a remote device.
|
||||
|
||||
```powershell
|
||||
$RemoteSession = New-CimSession -ComputerName RemoteDevice
|
||||
Remove-NetFirewallRule -DisplayName "AllowWeb80" -CimSession $RemoteSession -Confirm
|
||||
```
|
||||
|
||||
## Deploy basic IPsec rule settings
|
||||
|
||||
An Internet Protocol security (IPsec) policy consists of rules that determine IPsec behavior. IPsec supports network-level peer authentication, data origin authentication, data integrity, data confidentiality (encryption), and replay protection.
|
||||
Windows PowerShell can create powerful, complex IPsec policies like in Netsh and the Windows Defender Firewall with Advanced Security console. However, because Windows PowerShell is object-based rather than string token-based, configuration in Windows PowerShell offers greater control and flexibility.
|
||||
Windows PowerShell can create powerful, complex IPsec policies like in Netsh and the Windows Firewall console. However, because Windows PowerShell is object-based rather than string token-based, configuration in Windows PowerShell offers greater control and flexibility.
|
||||
In Netsh, the authentication and cryptographic sets were specified as a list of comma-separated tokens in a specific format. In Windows PowerShell, rather than using default settings, you first create your desired authentication or cryptographic proposal objects and bundle them into lists in your preferred order. Then, you create one or more IPsec rules that reference these sets. The benefit of this model is that programmatic access to the information in the rules is much easier. See the following sections for clarifying examples.
|
||||
|
||||
|
||||
### Create IPsec rules
|
||||
|
||||
The following cmdlet creates basic IPsec transport mode rule in a Group Policy Object. An IPsec rule is simple to create; all that is required is the display name, and the remaining properties use default values. Inbound traffic is authenticated and integrity checked using the default quick mode and main mode settings. These default settings can be found in the console under Customize IPsec Defaults.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall set store gpo=domain.contoso.com\gpo_name
|
||||
netsh advfirewall consec add rule name="Require Inbound Authentication" endpoint1=any endpoint2=any action=requireinrequestout
|
||||
@ -209,12 +248,14 @@ netsh advfirewall consec add rule name="Require Inbound Authentication" endpoint
|
||||
```powershell
|
||||
New-NetIPsecRule -DisplayName "Require Inbound Authentication" -PolicyStore domain.contoso.com\gpo_name
|
||||
```
|
||||
|
||||
### Add custom authentication methods to an IPsec rule
|
||||
|
||||
If you want to create a custom set of quick-mode proposals that includes both AH and ESP in an IPsec rule object, you create the associated objects separately and link their associations. For more information about authentication methods, see [Choosing the IPsec Protocol](/previous-versions/windows/it-pro/windows-server-2003/cc757847(v=ws.10)) .
|
||||
You can then use the newly created custom quick-mode policies when you create IPsec rules. The cryptography set object is linked to an IPsec rule object.
|
||||
|
||||
In this example, we build on the previously created IPsec rule by specifying a custom quick-mode crypto set. The final IPsec rule requires outbound traffic to be authenticated by the specified cryptography method.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall set store gpo=domain.contoso.com\gpo_name
|
||||
netsh advfirewall consec add rule name="Require Outbound Authentication" endpoint1=any endpoint2=any action=requireinrequestout qmsecmethods=ah:sha1+esp:sha1-3des
|
||||
@ -225,15 +266,20 @@ $AHandESPQM = New-NetIPsecQuickModeCryptoProposal -Encapsulation AH,ESP -AHHash
|
||||
$QMCryptoSet = New-NetIPsecQuickModeCryptoSet -DisplayName "ah:sha1+esp:sha1-des3" -Proposal $AHandESPQM -PolicyStore domain.contoso.com\gpo_name
|
||||
New-NetIPsecRule -DisplayName "Require Inbound Authentication" -InboundSecurity Require -OutboundSecurity Request -QuickModeCryptoSet $QMCryptoSet.Name -PolicyStore domain.contoso.com\gpo_name
|
||||
```
|
||||
|
||||
### IKEv2 IPsec transport rules
|
||||
|
||||
A corporate network may need to secure communications with another agency. But, you discover the agency runs non-Windows operating systems and requires the use of the Internet Key Exchange Version 2 (IKEv2) standard.
|
||||
You can apply IKEv2 capabilities in Windows Server 2012 by specifying IKEv2 as the key module in an IPsec rule. This capability specification can only be done using computer certificate authentication and can't be used with phase-2 authentication.
|
||||
|
||||
```powershell
|
||||
New-NetIPsecRule -DisplayName "Require Inbound Authentication" -InboundSecurity Require -OutboundSecurity Request -Phase1AuthSet MyCertAuthSet -KeyModule IKEv2 -RemoteAddress $nonWindowsGateway
|
||||
```
|
||||
|
||||
For more info about IKEv2, including scenarios, see [Securing End-to-End IPsec Connections by Using IKEv2](securing-end-to-end-ipsec-connections-by-using-ikev2.md).
|
||||
|
||||
### Copy an IPsec rule from one policy to another
|
||||
|
||||
Firewall and IPsec rules with the same rule properties can be duplicated to simplify the task of re-creating them within different policy stores.
|
||||
To copy the previously created rule from one policy store to another, the associated objects must also be copied separately. There's no need to copy associated firewall filters. You can query rules to be copied in the same way as other cmdlets.
|
||||
Copying individual rules is a task that isn't possible through the Netsh interface. Here's how you can accomplish it with Windows PowerShell.
|
||||
@ -243,36 +289,44 @@ $Rule = Get-NetIPsecRule -DisplayName "Require Inbound Authentication"
|
||||
$Rule | Copy-NetIPsecRule -NewPolicyStore domain.costoso.com\new_gpo_name
|
||||
$Rule | Copy-NetPhase1AuthSet -NewPolicyStore domain.costoso.com\new_gpo_name
|
||||
```
|
||||
|
||||
### Handling Windows PowerShell errors
|
||||
|
||||
To handle errors in your Windows PowerShell scripts, you can use the *-ErrorAction* parameter. This parameter is especially useful with the **Remove** cmdlets. If you want to remove a particular rule, you'll notice that it fails if the rule isn't found. When rules are being removed, if the rule isn't already there, it's acceptable to ignore that error. In this case, you can do the following to suppress any "rule not found" errors during the remove operation.
|
||||
|
||||
```powershell
|
||||
Remove-NetFirewallRule -DisplayName "Contoso Messenger 98" -ErrorAction SilentlyContinue
|
||||
```
|
||||
|
||||
The use of wildcards can also suppress errors, but they could potentially match rules that you didn't intend to remove. These wildcards can be a useful shortcut, but should only be used if you know there aren't any extra rules that will be accidentally deleted. So the following cmdlet will also remove the rule, suppressing any "not found" errors.
|
||||
|
||||
```powershell
|
||||
Remove-NetFirewallRule -DisplayName "Contoso Messenger 98*"
|
||||
```
|
||||
|
||||
When using wildcards, if you want to double-check the set of rules that is matched, you can use the *-WhatIf* parameter.
|
||||
|
||||
```powershell
|
||||
Remove-NetFirewallRule -DisplayName "Contoso Messenger 98*" -WhatIf
|
||||
```
|
||||
|
||||
If you only want to delete some of the matched rules, you can use the *-Confirm* parameter to get a rule-by-rule confirmation prompt.
|
||||
|
||||
```powershell
|
||||
Remove-NetFirewallRule -DisplayName "Contoso Messenger 98*" -Confirm
|
||||
```
|
||||
|
||||
You can also just perform the whole operation, displaying the name of each rule as the operation is performed.
|
||||
|
||||
```powershell
|
||||
Remove-NetFirewallRule -DisplayName "Contoso Messenger 98*" -Verbose
|
||||
```
|
||||
|
||||
### Monitor
|
||||
|
||||
The following Windows PowerShell commands are useful in the update cycle of a deployment phase.
|
||||
To allow you to view all the IPsec rules in a particular store, you can use the following commands. In Netsh, this command doesn't show rules where profile=domain,public or profile=domain,private. It only shows rules that have the single entry domain that is included in the rule. The following command examples will show the IPsec rules in all profiles.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall consec show rule name=all
|
||||
```
|
||||
@ -280,9 +334,10 @@ netsh advfirewall consec show rule name=all
|
||||
```powershell
|
||||
Show-NetIPsecRule -PolicyStore ActiveStore
|
||||
```
|
||||
|
||||
You can monitor main mode security associations for information such as which peers are currently connected to the device and which protection suite is used to form the security associations.
|
||||
Use the following cmdlet to view existing main mode rules and their security associations:
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall monitor show mmsa all
|
||||
```
|
||||
@ -290,18 +345,23 @@ netsh advfirewall monitor show mmsa all
|
||||
```powershell
|
||||
Get-NetIPsecMainModeSA
|
||||
```
|
||||
|
||||
### Find the source GPO of a rule
|
||||
|
||||
To view the properties of a particular rule or group of rules, you query for the rule. When a query returns fields that are specified as **NotConfigured**, you can determine which policy store a rule originates from.
|
||||
For objects that come from a GPO (the *-PolicyStoreSourceType* parameter is specified as **GroupPolicy** in the **Show** command), if *-TracePolicyStore* is passed, the name of the GPO is found and returned in the **PolicyStoreSource** field.
|
||||
|
||||
```powershell
|
||||
Get-NetIPsecRule -DisplayName "Require Inbound Authentication" -TracePolicyStore
|
||||
```
|
||||
|
||||
It's important to note that the revealed sources don't contain a domain name.
|
||||
|
||||
### Deploy a basic domain isolation policy
|
||||
|
||||
IPsec can be used to isolate domain members from non-domain members. Domain isolation uses IPsec authentication to require that the domain-joined devices positively establish the identities of the communicating devices to improve security of an organization. One or more features of IPsec can be used to secure traffic with an IPsec rule object.
|
||||
To implement domain isolation on your network, the devices in the domain receive IPsec rules that block unsolicited inbound network traffic that isn't protected by IPsec. Here we create an IPsec rule that requires authentication by domain members. Through this authentication, you can isolate domain-joined devices from devices that aren't joined to a domain. In the following examples, Kerberos authentication is required for inbound traffic and requested for outbound traffic.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall set store gpo=domain.contoso.com\domain_isolation
|
||||
netsh advfirewall consec add rule name="Basic Domain Isolation Policy" profile=domain endpoint1="any" endpoint2="any" action=requireinrequestout auth1="computerkerb"
|
||||
@ -312,9 +372,11 @@ $kerbprop = New-NetIPsecAuthProposal -Machine -Kerberos
|
||||
$Phase1AuthSet = New-NetIPsecPhase1AuthSet -DisplayName "Kerberos Auth Phase1" -Proposal $kerbprop -PolicyStore domain.contoso.com\domain_isolation
|
||||
New-NetIPsecRule -DisplayName "Basic Domain Isolation Policy" -Profile Domain -Phase1AuthSet $Phase1AuthSet.Name -InboundSecurity Require -OutboundSecurity Request -PolicyStore domain.contoso.com\domain_isolation
|
||||
```
|
||||
|
||||
### Configure IPsec tunnel mode
|
||||
|
||||
The following command creates an IPsec tunnel that routes traffic from a private network (192.168.0.0/16) through an interface on the local device (1.1.1.1) attached to a public network to a second device through its public interface (2.2.2.2) to another private network (192.157.0.0/16). All traffic through the tunnel is checked for integrity by using ESP/SHA1, and it's encrypted by using ESP/DES3.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall consec add rule name="Tunnel from 192.168.0.0/16 to 192.157.0.0/16" mode=tunnel endpoint1=192.168.0.0/16 endpoint2=192.157.0.0/16 localtunnelendpoint=1.1.1.1 remotetunnelendpoint=2.2.2.2 action=requireinrequireout qmsecmethods=esp:sha1-3des
|
||||
```
|
||||
@ -324,12 +386,16 @@ $QMProposal = New-NetIPsecQuickModeCryptoProposal -Encapsulation ESP -ESPHash SH
|
||||
$QMCryptoSet = New-NetIPsecQuickModeCryptoSet -DisplayName "esp:sha1-des3" -Proposal $QMProposal
|
||||
New-NetIPSecRule -DisplayName "Tunnel from HQ to Dallas Branch" -Mode Tunnel -LocalAddress 192.168.0.0/16 -RemoteAddress 192.157.0.0/16 -LocalTunnelEndpoint 1.1.1.1 -RemoteTunnelEndpoint 2.2.2.2 -InboundSecurity Require -OutboundSecurity Require -QuickModeCryptoSet $QMCryptoSet.Name
|
||||
```
|
||||
|
||||
## Deploy secure firewall rules with IPsec
|
||||
In situations where only secure traffic can be allowed through the Windows Defender Firewall, a combination of manually configured firewall and IPsec rules are necessary. The firewall rules determine the level of security for allowed packets, and the underlying IPsec rules secure the traffic. The scenarios can be accomplished in Windows PowerShell and in Netsh, with many similarities in deployment.
|
||||
|
||||
In situations where only secure traffic can be allowed through the Windows Firewall, a combination of manually configured firewall and IPsec rules are necessary. The firewall rules determine the level of security for allowed packets, and the underlying IPsec rules secure the traffic. The scenarios can be accomplished in Windows PowerShell and in Netsh, with many similarities in deployment.
|
||||
|
||||
### Create a secure firewall rule (allow if secure)
|
||||
|
||||
Configuring firewalls rule to allow connections if they're secure requires the corresponding traffic to be authenticated and integrity protected, and then optionally encrypted by IPsec.
|
||||
The following example creates a firewall rule that requires traffic to be authenticated. The command permits inbound Telnet network traffic only if the connection from the remote device is authenticated by using a separate IPsec rule.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall firewall add rule name="Allow Authenticated Telnet" dir=in program=%SystemRoot%\System32\tlntsvr.exe security=authenticate action=allow
|
||||
```
|
||||
@ -337,8 +403,9 @@ netsh advfirewall firewall add rule name="Allow Authenticated Telnet" dir=in pro
|
||||
```powershell
|
||||
New-NetFirewallRule -DisplayName "Allow Authenticated Telnet" -Direction Inbound -Program %SystemRoot%\System32\tlntsvr.exe -Authentication Required -Action Allow
|
||||
```
|
||||
|
||||
The following command creates an IPsec rule that requires a first (computer) authentication and then attempts an optional second (user) authentication. Creating this rule secures and allows the traffic through the firewall rule requirements for the messenger program.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall consec add rule name="Authenticate Both Computer and User" endpoint1=any endpoint2=any action=requireinrequireout auth1=computerkerb,computerntlm auth2=userkerb,userntlm,anonymous
|
||||
```
|
||||
@ -353,14 +420,18 @@ $anonyauthprop = New-NetIPsecAuthProposal -Anonymous
|
||||
$P2Auth = New-NetIPsecPhase2AuthSet -DisplayName "User Auth" -Proposal $ukerbauthprop,$unentlmauthprop,$anonyauthprop
|
||||
New-NetIPSecRule -DisplayName "Authenticate Both Computer and User" -InboundSecurity Require -OutboundSecurity Require -Phase1AuthSet $P1Auth.Name -Phase2AuthSet $P2Auth.Name
|
||||
```
|
||||
|
||||
### Isolate a server by requiring encryption and group membership
|
||||
|
||||
To improve the security of the devices in an organization, you can deploy domain isolation in which domain-members are restricted. They require authentication when communicating among each other and reject non-authenticated inbound connections. To improve the security of servers with sensitive data, this data must be protected by allowing access only to a subset of devices within the enterprise domain.
|
||||
IPsec can provide this extra layer of protection by isolating the server. In server isolation, sensitive data access is restricted to users and devices with legitimate business need, and the data is additionally encrypted to prevent eavesdropping.
|
||||
|
||||
### Create a firewall rule that requires group membership and encryption
|
||||
|
||||
To deploy server isolation, we layer a firewall rule that restricts traffic to authorized users or devices on the IPsec rule that enforces authentication.
|
||||
The following firewall rule allows Telnet traffic from user accounts that are members of a custom group called "Authorized to Access Server." This access can additionally be restricted based on the device, user, or both by specifying the restriction parameters.
|
||||
A Security Descriptor Definition Language (SDDL) string is created by extending a user or group's security identifier (SID). For more information about finding a group's SID, see: [Finding the SID for a group account](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc753463(v=ws.10)#bkmk_FINDSID).
|
||||
Restricting access to a group allows administrations to extend strong authentication support through Windows Defender Firewall and/or IPsec policies.
|
||||
Restricting access to a group allows administrations to extend strong authentication support through Windows Firewall and/or IPsec policies.
|
||||
The following example shows you how to create an SDDL string that represents security groups.
|
||||
|
||||
```powershell
|
||||
@ -368,15 +439,17 @@ $user = new-object System.Security.Principal.NTAccount ("corp.contoso.com\Admini
|
||||
$SIDofSecureUserGroup = $user.Translate([System.Security.Principal.SecurityIdentifier]).Value
|
||||
$secureUserGroup = "D:(A;;CC;;;$SIDofSecureUserGroup)"
|
||||
```
|
||||
|
||||
By using the previous scriptlet, you can also get the SDDL string for a secure computer group as shown here:
|
||||
|
||||
```powershell
|
||||
$secureMachineGroup = "D:(A;;CC;;;$SIDofSecureMachineGroup)"
|
||||
```
|
||||
|
||||
For more information about how to create security groups or how to determine the SDDL string, see [Working with SIDs](/previous-versions/windows/it-pro/windows-powershell-1.0/ff730940(v=technet.10)).
|
||||
Telnet is an application that doesn't provide encryption. This application can send data, such as names and passwords, over the network. This data can be intercepted by malicious users. If an administrator would like to allow the use of Telnet, but protect the traffic, a firewall rule that requires IPsec encryption can be created. This firewall rule is necessary so that the administrator can be certain that when this application is used, all of the traffic sent or received by this port is encrypted. If IPsec fails to authorize the connection, no traffic is allowed from this application.
|
||||
In this example, we allow only authenticated and encrypted inbound Telnet traffic from a specified secure user group through the creation of the following firewall rule.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall set store gpo=domain.contoso.com\Server_Isolation
|
||||
netsh advfirewall firewall add rule name="Allow Encrypted Inbound Telnet to Group Members Only" program=%SystemRoot%\System32\tlntsvr.exe protocol=TCP dir=in action=allow localport=23 security=authenc rmtusrgrp ="D:(A;;CC;;; S-1-5-21-2329867823-2610410949-1491576313-1735)"
|
||||
@ -385,17 +458,21 @@ netsh advfirewall firewall add rule name="Allow Encrypted Inbound Telnet to Grou
|
||||
```powershell
|
||||
New-NetFirewallRule -DisplayName "Allow Encrypted Inbound Telnet to Group Members Only" -Program %SystemRoot%\System32\tlntsvr.exe -Protocol TCP -Direction Inbound -Action Allow -LocalPort 23 -Authentication Required -Encryption Required -RemoteUser $secureUserGroup -PolicyStore domain.contoso.com\Server_Isolation
|
||||
```
|
||||
|
||||
### Endpoint security enforcement
|
||||
|
||||
The previous example showed end to end security for a particular application. In situations where endpoint security is required for many applications, having a firewall rule per application can be cumbersome and difficult to manage. Authorization can override the per-rule basis and be done at the IPsec layer.
|
||||
In this example, we set the global IPsec setting to only allow transport mode traffic to come from an authorized user group with the following cmdlet. Consult the previous examples for working with security groups.
|
||||
|
||||
```powershell
|
||||
Set-NetFirewallSetting -RemoteMachineTransportAuthorizationList $secureMachineGroup
|
||||
```
|
||||
|
||||
### Create firewall rules that allow IPsec-protected network traffic (authenticated bypass)
|
||||
|
||||
Authenticated bypass allows traffic from a specified trusted device or user to override firewall block rules. This override is helpful when an administrator wants to use scanning servers to monitor and update devices without the need to use port-level exceptions. For more information, see [How to enable authenticated firewall bypass](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc753463(v=ws.10)).
|
||||
In this example, we assume that a blocking firewall rule exists. This example permits any network traffic on any port from any IP address to override the block rule, if the traffic is authenticated as originating from a device or user account that is a member of the specified device or user security group.
|
||||
**Netsh**
|
||||
|
||||
```cmd
|
||||
netsh advfirewall set store gpo=domain.contoso.com\domain_isolation
|
||||
netsh advfirewall firewall add rule name="Inbound Secure Bypass Rule" dir=in security=authenticate action="bypass" rmtcomputergrp="D:(A;;CC;;;S-1-5-21-2329867823-2610410949-1491576313-1114)" rmtusrgrp="D:(A;;CC;;; S-1-5-21-2329867823-2610410949-1491576313-1735)"
|
||||
@ -404,22 +481,3 @@ netsh advfirewall firewall add rule name="Inbound Secure Bypass Rule" dir=in sec
|
||||
```powershell
|
||||
New-NetFirewallRule -DisplayName "Inbound Secure Bypass Rule" -Direction Inbound -Authentication Required -OverrideBlockRules $true -RemoteMachine $secureMachineGroup -RemoteUser $secureUserGroup -PolicyStore domain.contoso.com\domain_isolation
|
||||
```
|
||||
|
||||
## Other resources
|
||||
For more information about Windows PowerShell concepts, see the following topics.
|
||||
- [Windows PowerShell Getting Started Guide](/powershell/scripting/overview)
|
||||
- [Windows PowerShell User Guide](/powershell/scripting/overview)
|
||||
- [Windows PowerShell About Help Topics](https://go.microsoft.com/fwlink/p/?linkid=113206)
|
||||
- [about\_Functions](/powershell/module/microsoft.powershell.core/about/about_functions)
|
||||
- [about\_Functions\_Advanced](/powershell/module/microsoft.powershell.core/about/about_functions_advanced)
|
||||
- [about\_Execution\_Policies](/powershell/module/microsoft.powershell.core/about/about_execution_policies)
|
||||
- [about\_Foreach](/powershell/module/microsoft.powershell.core/about/about_foreach)
|
||||
- [about\_Objects](/powershell/module/microsoft.powershell.core/about/about_objects)
|
||||
- [about\_Properties](/powershell/module/microsoft.powershell.core/about/about_properties)
|
||||
- [about\_While](/powershell/module/microsoft.powershell.core/about/about_while)
|
||||
- [about\_Scripts](/powershell/module/microsoft.powershell.core/about/about_scripts)
|
||||
- [about\_Signing](/powershell/module/microsoft.powershell.core/about/about_signing)
|
||||
- [about\_Throw](/powershell/module/microsoft.powershell.core/about/about_throw)
|
||||
- [about\_PSSessions](/powershell/module/microsoft.powershell.core/about/about_pssessions)
|
||||
- [about\_Modules](/powershell/module/microsoft.powershell.core/about/about_modules)
|
||||
- [about\_Command\_Precedence](/powershell/module/microsoft.powershell.core/about/about_command_precedence)
|
||||
|
||||
@ -7,9 +7,6 @@ ms.date: 11/07/2023
|
||||
|
||||
# Create Windows Firewall rules in Intune
|
||||
|
||||
>[!IMPORTANT]
|
||||
>This information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
|
||||
|
||||
To get started, Open the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), and then go to **Devices** > **Windows** > **Configuration profiles** > **Create profile** > Choose **Windows 10 and later** as the platform, Choose **Templates**, then **Endpoint protection** as the profile type.
|
||||
Select Windows Defender Firewall.
|
||||
:::image type="content" source="images/windows-firewall-intune.png" alt-text="Example of a Windows Defender Firewall policy in Microsoft Intune and the Intune admin center.":::
|
||||
|
||||
@ -0,0 +1,9 @@
|
||||
<svg width="20" height="17" viewBox="0 0 20 17" fill="none" xmlns="http://www.w3.org/2000/svg">
|
||||
<rect x="0.90909" y="1.88889" width="18.1818" height="14.1667" fill="black"/>
|
||||
<path d="M4.45117 6.87549C4.30957 6.93245 4.17204 6.97477 4.03857 7.00244C3.90674 7.03011 3.76921 7.04395 3.62598 7.04395C3.39648 7.04395 3.19303 7.01058 3.01562 6.94385C2.83984 6.87549 2.69092 6.77458 2.56885 6.64111C2.4484 6.50765 2.35645 6.34245 2.29297 6.14551C2.23112 5.94694 2.2002 5.71663 2.2002 5.45459C2.2002 5.18604 2.23438 4.94759 2.30273 4.73926C2.37109 4.5293 2.46875 4.3527 2.5957 4.20947C2.72266 4.06462 2.87646 3.95475 3.05713 3.87988C3.23942 3.80339 3.44368 3.76514 3.66992 3.76514C3.74316 3.76514 3.81152 3.76676 3.875 3.77002C3.9401 3.77327 4.00358 3.77979 4.06543 3.78955C4.12728 3.79769 4.18994 3.80908 4.25342 3.82373C4.31689 3.83838 4.38281 3.8571 4.45117 3.87988V4.47559C4.31283 4.41048 4.18099 4.3641 4.05566 4.33643C3.93034 4.30876 3.81641 4.29492 3.71387 4.29492C3.5625 4.29492 3.43311 4.32259 3.32568 4.37793C3.21826 4.43164 3.12956 4.50814 3.05957 4.60742C2.99121 4.70508 2.94076 4.82227 2.9082 4.95898C2.87565 5.09408 2.85938 5.243 2.85938 5.40576C2.85938 5.57829 2.87565 5.73291 2.9082 5.86963C2.94238 6.00472 2.99447 6.11947 3.06445 6.21387C3.13444 6.30827 3.22396 6.3807 3.33301 6.43115C3.44206 6.47998 3.57145 6.50439 3.72119 6.50439C3.7749 6.50439 3.83268 6.49951 3.89453 6.48975C3.95801 6.47835 4.02148 6.46452 4.08496 6.44824C4.15007 6.43034 4.21354 6.40999 4.27539 6.38721C4.33887 6.36279 4.39746 6.33838 4.45117 6.31396V6.87549ZM6.12354 4.49512C6.18538 4.49512 6.24316 4.50651 6.29688 4.5293C6.35059 4.55208 6.39697 4.58382 6.43604 4.62451C6.4751 4.66357 6.50602 4.70996 6.52881 4.76367C6.5516 4.81738 6.56299 4.87435 6.56299 4.93457C6.56299 4.99642 6.5516 5.0542 6.52881 5.10791C6.50602 5.16162 6.4751 5.20801 6.43604 5.24707C6.39697 5.28613 6.35059 5.31706 6.29688 5.33984C6.24316 5.36263 6.18538 5.37402 6.12354 5.37402C6.06169 5.37402 6.00391 5.36263 5.9502 5.33984C5.89811 5.31706 5.85173 5.28613 5.81104 5.24707C5.77197 5.20801 5.74105 5.16162 5.71826 5.10791C5.69548 5.0542 5.68408 4.99642 5.68408 4.93457C5.68408 4.87435 5.69548 4.81738 5.71826 4.76367C5.74105 4.70996 5.77197 4.66357 5.81104 4.62451C5.85173 4.58382 5.89811 4.55208 5.9502 4.5293C6.00391 4.50651 6.06169 4.49512 6.12354 4.49512ZM6.12354 6.17725C6.18538 6.17725 6.24316 6.18864 6.29688 6.21143C6.35059 6.23421 6.39697 6.26514 6.43604 6.3042C6.4751 6.34326 6.50602 6.38965 6.52881 6.44336C6.5516 6.49707 6.56299 6.55404 6.56299 6.61426C6.56299 6.67611 6.5516 6.73389 6.52881 6.7876C6.50602 6.84131 6.4751 6.88851 6.43604 6.9292C6.39697 6.96826 6.35059 6.99919 6.29688 7.02197C6.24316 7.04476 6.18538 7.05615 6.12354 7.05615C6.06169 7.05615 6.00391 7.04476 5.9502 7.02197C5.89811 6.99919 5.85173 6.96826 5.81104 6.9292C5.77197 6.88851 5.74105 6.84131 5.71826 6.7876C5.69548 6.73389 5.68408 6.67611 5.68408 6.61426C5.68408 6.55404 5.69548 6.49707 5.71826 6.44336C5.74105 6.38965 5.77197 6.34326 5.81104 6.3042C5.85173 6.26514 5.89811 6.23421 5.9502 6.21143C6.00391 6.18864 6.06169 6.17725 6.12354 6.17725ZM8.36719 3.55029L10.0737 7.5249H9.49268L7.78857 3.55029H8.36719ZM10.2471 8.00098V7.52979H12.9961V8.00098H10.2471ZM12.9961 8.00098V7.52979H15.7451V8.00098H12.9961Z" fill="white"/>
|
||||
<rect x="0.90909" y="0.944443" width="18.1818" height="1.88889" fill="#D9D9D9"/>
|
||||
<rect x="17.2727" y="0.944443" width="0.909091" height="0.944444" fill="#605E5C"/>
|
||||
<rect x="15.4545" y="0.944443" width="0.909091" height="0.944444" fill="#605E5C"/>
|
||||
<rect x="13.6364" y="0.944443" width="0.909091" height="0.944444" fill="#605E5C"/>
|
||||
<rect x="0.5" y="0.5" width="19" height="16" stroke="#CDCDCD"/>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 3.6 KiB |
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 31 KiB |
Loading…
x
Reference in New Issue
Block a user