mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge pull request #10187 from MicrosoftDocs/main
Publish main to live 09/06/2024, 3:30 PM
This commit is contained in:
Gary Moore
GitHub
commit
e44c2bc8c5
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configure Take a Test in kiosk mode
|
||||
description: Learn how to configure Windows to execute the Take a Test app in kiosk mode, using Intune and provisioning packages.
|
||||
ms.date: 11/08/2023
|
||||
ms.date: 09/06/2024
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
@ -26,7 +26,7 @@ The other options allow you to configure Take a Test in kiosk mode using a local
|
||||
|
||||
Follow the instructions below to configure your devices, selecting the option that best suits your needs.
|
||||
|
||||
# [:::image type="icon" source="images/icons/intune.svg"::: **Intune**](#tab/intune)
|
||||
# [:::image type="icon" source="images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
|
||||
|
||||
You can use Intune for Education or a custom profile in Microsoft Intune:
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Take a Test app technical reference
|
||||
description: List of policies and settings applied by the Take a Test app.
|
||||
ms.date: 11/02/2023
|
||||
ms.date: 09/06/2024
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -15,7 +15,7 @@ Assessment vendors can use Take a Test as a platform to lock down the operating
|
||||
|
||||
## PC lock-down for assessment
|
||||
|
||||
When the assessment page initiates lock-down, the student's desktop is locked and the app executes above the Windows lock screen. This provides a sandbox that ensures the student can only interact with the Take a Test app. After transitioning to the lock screen, Take a Test applies local MDM policies to further lock down the device. The whole process of going above the lock screen and applying policies is what defines lock-down. The lock-down process is atomic, which means that if any part of the lock-down operation fails, the app won't be above lock and won't have any of the policies applied.
|
||||
When the assessment page initiates lock-down, the student's desktop is locked and the app executes above the Windows lock screen. This provides a sandbox that ensures the student can only interact with the Take a Test app. After transitioning to the lock screen, Take a Test applies local MDM policies to further lock down the device. The whole process of going above the lock screen and applying policies is what defines lock-down. The lock-down process is atomic, which means that if any part of the lock-down operation fails, the app won't be above lock and won't have any of the policies applied.
|
||||
|
||||
When running above the lock screen:
|
||||
|
||||
@ -64,7 +64,7 @@ When Take a Test is running, the following functionality is available to student
|
||||
- Assistive technology that might be running
|
||||
- Lock screen (not available if student is using a dedicated test account)
|
||||
|
||||
> [!NOTE]
|
||||
> [!NOTE]
|
||||
> The app will exit if the student signs in to an account from the lock screen.
|
||||
> Progress made in the test may be lost or invalidated.
|
||||
- The student can exit the test by pressing <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>Delete</kbd>
|
||||
|
||||
@ -127,5 +127,4 @@ Depending on your configuration, you can have a user to automatically sign in to
|
||||
<!--links-->
|
||||
|
||||
[MEM-1]: /mem/intune/configuration/custom-settings-windows-10
|
||||
[MEM-2]: /mem/intune/fundamentals/licenses#device-only-licenses
|
||||
[WIN-3]: /windows/client-management/mdm/assignedaccess-csp
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configure a shared or guest Windows device
|
||||
description: Description of how to configured Shared PC mode, which is a Windows feature that optimizes devices for shared use scenarios.
|
||||
ms.date: 11/08/2023
|
||||
ms.date: 09/06/2024
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
@ -25,9 +25,7 @@ Shared PC can be configured using the following methods:
|
||||
|
||||
Follow the instructions below to configure your devices, selecting the option that best suits your needs.
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune**](#tab/intune)
|
||||
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
|
||||
|
||||
To configure devices using Microsoft Intune, [create a **Settings catalog** policy][MEM-2], and use the settings listed under the category **`Shared PC`**:
|
||||
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
---
|
||||
ms.date: 11/07/2023
|
||||
ms.date: 09/06/2024
|
||||
title: Access Control overview
|
||||
description: Learn about access control in Windows, which is the process of authorizing users, groups, and computers to access objects on the network or computer.
|
||||
ms.topic: overview
|
||||
appliesto:
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Windows Server 2022</a>
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
---
|
||||
ms.date: 11/07/2023
|
||||
ms.date: 09/06/2024
|
||||
title: Local Accounts
|
||||
description: Learn how to secure and manage access to the resources on a standalone or member server for services or users.
|
||||
ms.topic: concept-article
|
||||
appliesto:
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Windows Server 2022</a>
|
||||
@ -37,7 +37,7 @@ The default Administrator account can't be deleted or locked out, but it can be
|
||||
|
||||
Windows setup disables the built-in Administrator account and creates another local account that is a member of the Administrators group.
|
||||
|
||||
Members of the Administrators groups can run apps with elevated permissions without using the *Run as Administrator* option. Fast User Switching is more secure than using `runas` or different-user elevation.
|
||||
Members of the Administrators groups can run apps with elevated permissions without using the *Run as Administrator* option. Fast User Switching is more secure than using `runas` or different-user elevation.
|
||||
|
||||
#### Account group membership
|
||||
|
||||
@ -219,7 +219,7 @@ The following table shows the Group Policy and registry settings that are used t
|
||||
||Registry value data|0|
|
||||
|
||||
> [!NOTE]
|
||||
> You can also enforce the default for LocalAccountTokenFilterPolicy by using the custom ADMX in Security Templates.
|
||||
> You can also enforce the default for LocalAccountTokenFilterPolicy by using the custom ADMX in Security Templates.
|
||||
|
||||
#### To enforce local account restrictions for remote access
|
||||
|
||||
|
||||
@ -4,7 +4,7 @@ description: Learn about passkeys and how to use them on Windows devices.
|
||||
ms.collection:
|
||||
- tier1
|
||||
ms.topic: overview
|
||||
ms.date: 11/07/2023
|
||||
ms.date: 09/06/2024
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Deploy Virtual Smart Cards
|
||||
description: Learn about what to consider when deploying a virtual smart card authentication solution
|
||||
ms.topic: concept-article
|
||||
ms.date: 11/06/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Deploy Virtual Smart Cards
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Evaluate Virtual Smart Card Security
|
||||
description: Learn about the security characteristics and considerations when deploying TPM virtual smart cards.
|
||||
ms.topic: concept-article
|
||||
ms.date: 11/06/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Evaluate Virtual Smart Card Security
|
||||
|
||||
@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Get Started with Virtual Smart Cards - Walkthrough Guide
|
||||
title: Get Started with Virtual Smart Cards - Walkthrough Guide
|
||||
description: This topic for the IT professional describes how to set up a basic test environment for using TPM virtual smart cards.
|
||||
ms.topic: get-started
|
||||
ms.date: 11/06/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Get Started with Virtual Smart Cards: Walkthrough Guide
|
||||
@ -79,10 +79,11 @@ In this step, you create the virtual smart card on the client computer by using
|
||||
|
||||
`tpmvscmgr.exe create /name TestVSC /pin default /adminkey random /generate`
|
||||
|
||||
This creates a virtual smart card with the name **TestVSC**, omit the unlock key, and generate the file system on the card. The PIN is set to the default, 12345678. To be prompted for a PIN, instead of **/pin default** you can type **/pin prompt**.\
|
||||
For more information about the Tpmvscmgr command-line tool, see [Use Virtual Smart Cards](virtual-smart-card-use-virtual-smart-cards.md) and [Tpmvscmgr](virtual-smart-card-tpmvscmgr.md).
|
||||
This creates a virtual smart card with the name **TestVSC**, omit the unlock key, and generate the file system on the card. The PIN is set to the default, 12345678.
|
||||
|
||||
1. Wait several seconds for the process to finish. Upon completion, Tpmvscmgr.exe provides you with the device instance ID for the TPM Virtual Smart Card. Store this ID for later reference because you need it to manage or remove the virtual smart card.
|
||||
1. Wait several seconds for the process to finish. Upon completion, Tpmvscmgr.exe provides you with the device instance ID for the TPM Virtual Smart Card. Store this ID for later reference because you need it to manage or remove the virtual smart card. To be prompted for a PIN, instead of **/pin default** you can type **/pin prompt**.
|
||||
|
||||
For more information about the Tpmvscmgr command-line tool, see [Use Virtual Smart Cards](virtual-smart-card-use-virtual-smart-cards.md) and [Tpmvscmgr](virtual-smart-card-tpmvscmgr.md).
|
||||
|
||||
## Step 3: Enroll for the certificate on the TPM Virtual Smart Card
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Virtual Smart Card Overview
|
||||
description: Learn about virtual smart card technology for Windows.
|
||||
ms.topic: overview
|
||||
ms.date: 11/06/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Virtual Smart Card Overview
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Tpmvscmgr
|
||||
description: Learn about the Tpmvscmgr command-line tool, through which an administrator can create and delete TPM virtual smart cards on a computer.
|
||||
ms.topic: reference
|
||||
ms.date: 11/06/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Tpmvscmgr
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Understanding and Evaluating Virtual Smart Cards
|
||||
description: Learn how smart card technology can fit into your authentication design.
|
||||
ms.topic: overview
|
||||
ms.date: 11/06/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Understand and Evaluate Virtual Smart Cards
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Use Virtual Smart Cards
|
||||
description: Learn about the requirements for virtual smart cards, how to use and manage them.
|
||||
ms.topic: concept-article
|
||||
ms.date: 11/06/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Use Virtual Smart Cards
|
||||
|
||||
@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Configure Windows Firewall logging
|
||||
title: Configure Windows Firewall logging
|
||||
description: Learn how to configure Windows Firewall to log dropped packets or successful connections with CSP and group policy.
|
||||
ms.topic: how-to
|
||||
ms.date: 11/21/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Configure Windows Firewall logging
|
||||
@ -137,7 +137,7 @@ If not, add *FullControl* permissions for `mpssvc` to the folder, subfolders and
|
||||
|
||||
```PowerShell
|
||||
$LogPath = Join-Path -path $env:windir -ChildPath "System32\LogFiles\Firewall"
|
||||
$NewAcl = Get-Acl -Path $LogPath
|
||||
$NewAcl = Get-Acl -Path $LogPath
|
||||
|
||||
$identity = "NT SERVICE\mpssvc"
|
||||
$fileSystemRights = "FullControl"
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Manage Windows Firewall with the command line
|
||||
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: how-to
|
||||
ms.date: 11/21/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Manage Windows Firewall with the command line
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Configure firewall rules with group policy
|
||||
description: Learn how to configure firewall rules using group policy with the Windows Firewall with Advanced Security console.
|
||||
ms.topic: how-to
|
||||
ms.date: 11/21/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Configure rules with group policy
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Windows Firewall dynamic keywords
|
||||
description: Learn about Windows Firewall dynamic keywords and how to configure it using Windows PowerShell.
|
||||
ms.topic: how-to
|
||||
ms.date: 01/16/2024
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Windows Firewall dynamic keywords
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Filter origin audit log
|
||||
description: Learn about Windows Firewall and filter origin audit log to troubleshoot packet drops.
|
||||
ms.topic: troubleshooting
|
||||
ms.date: 11/21/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Filter origin audit log
|
||||
|
||||
@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Hyper-V firewall
|
||||
title: Hyper-V firewall
|
||||
description: Learn how to configure Hyper-V firewall rules and settings using PowerShell or Configuration Service Provider (CSP).
|
||||
ms.topic: how-to
|
||||
ms.date: 11/21/2023
|
||||
ms.date: 09/06/2024
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
---
|
||||
@ -21,18 +21,18 @@ This section describes the steps to manage Hyper-V firewall using PowerShell.
|
||||
|
||||
### Obtain the WSL GUID
|
||||
|
||||
Hyper-V firewall rules are enabled per *VMCreatorId*. To obtain the VMCreatorId, use the cmdlet:
|
||||
Hyper-V firewall rules are enabled per *VMCreatorId*. To obtain the VMCreatorId, use the cmdlet:
|
||||
|
||||
```powershell
|
||||
Get-NetFirewallHyperVVMCreator
|
||||
Get-NetFirewallHyperVVMCreator
|
||||
```
|
||||
|
||||
The output contains a VmCreator object type, which has unique identifier `VMCreatorId` and `friendly name` properties. For example, the following output shows the properties of WSL:
|
||||
|
||||
```powershell
|
||||
PS C:\> Get-NetFirewallHyperVVMCreator
|
||||
VMCreatorId : {40E0AC32-46A5-438A-A0B2-2B479E8F2E90}
|
||||
FriendlyName : WSL
|
||||
VMCreatorId : {40E0AC32-46A5-438A-A0B2-2B479E8F2E90}
|
||||
FriendlyName : WSL
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
@ -63,7 +63,7 @@ The output contains the following values:
|
||||
To configure Hyper-V firewall, use the [Set-NetFirewallHyperVVMSetting][PS-2] command. For example, the following command sets the default inbound connection to *Allow*:
|
||||
|
||||
```powershell
|
||||
Set-NetFirewallHyperVVMSetting -Name '{40E0AC32-46A5-438A-A0B2-2B479E8F2E90}' -DefaultInboundAction Allow
|
||||
Set-NetFirewallHyperVVMSetting -Name '{40E0AC32-46A5-438A-A0B2-2B479E8F2E90}' -DefaultInboundAction Allow
|
||||
```
|
||||
|
||||
### Firewall Rules
|
||||
@ -76,10 +76,10 @@ Get-NetFirewallHyperVRule -VMCreatorId '{40E0AC32-46A5-438A-A0B2-2B479E8F2E90}'
|
||||
|
||||
To configure specific rules, use the [Set-NetFirewallHyperVRule][PS-4] cmdlet.
|
||||
|
||||
For example, to create an inbound rule to allow TCP traffic to WSL on port 80, use the following command:
|
||||
For example, to create an inbound rule to allow TCP traffic to WSL on port 80, use the following command:
|
||||
|
||||
```powershell
|
||||
New-NetFirewallHyperVRule -Name MyWebServer -DisplayName "My Web Server" -Direction Inbound -VMCreatorId '{40E0AC32-46A5-438A-A0B2-2B479E8F2E90}' -Protocol TCP -LocalPorts 80
|
||||
New-NetFirewallHyperVRule -Name MyWebServer -DisplayName "My Web Server" -Direction Inbound -VMCreatorId '{40E0AC32-46A5-438A-A0B2-2B479E8F2E90}' -Protocol TCP -LocalPorts 80
|
||||
```
|
||||
|
||||
### Target Hyper-V firewall rules and settings to specific profiles
|
||||
@ -95,7 +95,7 @@ The policy options are similar to the ones already described, but are applied to
|
||||
To view the settings per profile, use the following command:
|
||||
|
||||
```powershell
|
||||
Get-NetFirewallHyperVProfile -PolicyStore ActiveStore
|
||||
Get-NetFirewallHyperVProfile -PolicyStore ActiveStore
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
|
||||
@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Windows Firewall overview
|
||||
title: Windows Firewall overview
|
||||
description: Learn overview information about the Windows Firewall security feature.
|
||||
ms.topic: overview
|
||||
ms.date: 11/21/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Windows Firewall overview
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Quarantine behavior
|
||||
description: Learn about Windows Firewall and the quarantine feature behavior.
|
||||
ms.topic: concept-article
|
||||
ms.date: 11/21/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Quarantine behavior
|
||||
@ -77,7 +77,7 @@ Inside the wfpdiag.xml, search for `netEvents` that have `FWPM_NET_EVENT_TYPE_CL
|
||||
The characters in the application ID name are separated by periods:
|
||||
|
||||
```XML
|
||||
<asString> \\.d.e.v.i.c.e.\\.h.a.r.d.d.i.s.k.v.o.l.u.m.e.1.\\.w.i.n.d.o.w.s.\\.s.y.s.t.e.m.3.2.\\.s.v.c.h.o.s.t...e.x.e... </asString>
|
||||
<asString> \\.d.e.v.i.c.e.\\.h.a.r.d.d.i.s.k.v.o.l.u.m.e.1.\\.w.i.n.d.o.w.s.\\.s.y.s.t.e.m.3.2.\\.s.v.c.h.o.s.t...e.x.e... </asString>
|
||||
```
|
||||
|
||||
The `netEvent` contains more information about the dropped packet, including information about its capabilities, the filter that dropped the packet, and much more.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows Firewall rules
|
||||
description: Learn about Windows Firewall rules and design recommendations.
|
||||
ms.date: 11/21/2023
|
||||
ms.date: 09/06/2024
|
||||
ms.topic: concept-article
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows Firewall tools
|
||||
description: Learn about the available tools to configure Windows Firewall and firewall rules.
|
||||
ms.date: 11/20/2023
|
||||
ms.date: 09/06/2024
|
||||
ms.topic: best-practice
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Troubleshooting UWP App Connectivity Issues in Windows Firewall
|
||||
description: Troubleshooting UWP App Connectivity Issues in Windows Firewall
|
||||
ms.topic: troubleshooting
|
||||
ms.date: 11/07/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Troubleshooting UWP App Connectivity Issues
|
||||
@ -83,7 +83,7 @@ package SID, or application ID name. The characters in the application ID name
|
||||
will be separated by periods:
|
||||
|
||||
```XML
|
||||
(ex)
|
||||
(ex)
|
||||
|
||||
<asString>
|
||||
\\.d.e.v.i.c.e.\\.h.a.r.d.d.i.s.k.v.o.l.u.m.e.1.\\.w.i.n.d.o.w.s.\\.s.y.s.t.e.m.3.2.\\.s.v.c.h.o.s.t...e.x.e...
|
||||
@ -118,18 +118,18 @@ remote address, capabilities, etc.
|
||||
<item>FWPM_NET_EVENT_FLAG_LOCAL_PORT_SET</item>
|
||||
<item>FWPM_NET_EVENT_FLAG_REMOTE_PORT_SET</item>
|
||||
<item>FWPM_NET_EVENT_FLAG_APP_ID_SET</item>
|
||||
<item>FWPM_NET_EVENT_FLAG_USER_ID_SET</item>
|
||||
<item>FWPM_NET_EVENT_FLAG_USER_ID_SET</item>
|
||||
<item>FWPM_NET_EVENT_FLAG_IP_VERSION_SET</item>
|
||||
<item>FWPM_NET_EVENT_FLAG_PACKAGE_ID_SET</item>
|
||||
</flags>
|
||||
<ipVersion>FWP_IP_VERSION_V6</ipVersion>
|
||||
<ipProtocol>6</ipProtocol>
|
||||
<localAddrV6.byteArray16>2001:4898:30:3:256c:e5ba:12f3:beb1</localAddrV6.byteArray16>
|
||||
<ipProtocol>6</ipProtocol>
|
||||
<localAddrV6.byteArray16>2001:4898:30:3:256c:e5ba:12f3:beb1</localAddrV6.byteArray16>
|
||||
<remoteAddrV6.byteArray16>2620:1ec:c11::200</remoteAddrV6.byteArray16>
|
||||
<localPort>52127</localPort>
|
||||
<remotePort>443</remotePort>
|
||||
<scopeId>0</scopeId>
|
||||
<appId>
|
||||
<appId>
|
||||
<data>5c006400650076006900630065005c0068006100720064006400690073006b0076006f006c0075006d00650031005c00700072006f006700720061006d002000660069006c00650073005c00770069006e0064006f007700730061007000700073005c00610066003600390032006200660066002d0036003700370039002d0034003200340066002d0038003700300065002d006600360065003500390063003500300032003300340039005f0031002e0031002e00310030002e0030005f007800360034005f005f00350063003000330037006a0061007200350038003300390072005c0075007700700073006f0063006b006500740063006c00690065006e0074002e006500780065000000</data>
|
||||
<asString>\\.d.e.v.i.c.e.\\.h.a.r.d.d.i.s.k.v.o.l.u.m.e.1.\\.p.r.o.g.r.a.m.
|
||||
.f.i.l.e.s.\\.w.i.n.d.o.w.s.a.p.p.s.\\.a.f.6.9.2.b.f.f.-.6.7.7.9.-.4.2.4.f.-.8.7.0.e.-.f.6.e.5.9.c.5.0.2.3.4.9._.1...1...1.0...0._.x.6.4._._.5.c.0.3.7.j.a.r.5.8.3.9.r.\\.u.w.p.s.o.c.k.e.t.c.l.i.e.n.t...e.x.e...</asString>
|
||||
@ -152,7 +152,7 @@ remote address, capabilities, etc.
|
||||
<internalFields>
|
||||
<internalFlags/>
|
||||
<remoteAddrBitmap>0000000000000000</remoteAddrBitmap>
|
||||
<capabilities numItems="3">
|
||||
<capabilities numItems="3">
|
||||
<item>FWP_CAPABILITIES_FLAG_INTERNET_CLIENT</item>
|
||||
<item>FWP_CAPABILITIES_FLAG_INTERNET_CLIENT_SERVER</item>
|
||||
<item>FWP_CAPABILITIES_FLAG_PRIVATE_NETWORK</item>
|
||||
@ -195,7 +195,7 @@ allowed by Filter #125918, from the InternetClient Default Rule.
|
||||
<asString>.+......</asString>
|
||||
</providerData>
|
||||
<layerKey>FWPM_LAYER_ALE_AUTH_CONNECT_V6</layerKey>
|
||||
<subLayerKey>FWPM_SUBLAYER_MPSSVC_WSH</subLayerKey
|
||||
<subLayerKey>FWPM_SUBLAYER_MPSSVC_WSH</subLayerKey
|
||||
<weight>
|
||||
<type>FWP_EMPTY</type>
|
||||
</weight>
|
||||
@ -284,7 +284,7 @@ The important part of this condition is **S-1-15-3-1**, which is the capability
|
||||
From the **netEvent** capabilities section, capabilities from netEvent, Wfpdiag-Case-1.xml.
|
||||
|
||||
```xml
|
||||
<capabilities numItems="3">
|
||||
<capabilities numItems="3">
|
||||
<item>FWP_CAPABILITIES_FLAG_INTERNET_CLIENT</item>
|
||||
<item>FWP_CAPABILITIES_FLAG_INTERNET_CLIENT_SERVER</item>
|
||||
<item>FWP_CAPABILITIES_FLAG_PRIVATE_NETWORK</item>
|
||||
@ -575,7 +575,7 @@ In this example, the UWP app is unable to reach the Intranet target address, 10.
|
||||
<localPort>52998</localPort>
|
||||
<remotePort>53</remotePort>
|
||||
<scopeId>0</scopeId>
|
||||
<appId>
|
||||
<appId>
|
||||
<data>5c006400650076006900630065005c0068006100720064006400690073006b0076006f006c0075006d00650031005c00700072006f006700720061006d002000660069006c00650073005c00770069006e0064006f007700730061007000700073005c00610066003600390032006200660066002d0036003700370039002d0034003200340066002d0038003700300065002d006600360065003500390063003500300032003300340039005f0031002e0031002e00310031002e0030005f007800360034005f005f00350063003000330037006a0061007200350038003300390072005c0075007700700073006f0063006b006500740063006c00690065006e0074002e006500780065000000</data>
|
||||
<asString>\\.d.e.v.i.c.e.\\.h.a.r.d.d.i.s.k.v.o.l.u.m.e.1.\\.p.r.o.g.r.a.m.
|
||||
.f.i.l.e.s.\\.w.i.n.d.o.w.s.a.p.p.s.\\.a.f.6.9.2.b.f.f.-.6.7.7.9.-.4.2.4.f.-.8.7.0.e.-.f.6.e.5.9.c.5.0.2.3.4.9._.1...1...1.1...0._.x.6.4._._.5.c.0.3.7.j.a.r.5.8.3.9.r.\\.u.w.p.s.o.c.k.e.t.c.l.i.e.n.t...e.x.e...</asString>
|
||||
@ -653,7 +653,7 @@ In this example, the UWP app is unable to reach the Intranet target address, 10.
|
||||
<localPort>52956</localPort>
|
||||
<remotePort>53</remotePort>
|
||||
<scopeId>0</scopeId>
|
||||
<appId>
|
||||
<appId>
|
||||
<data>5c006400650076006900630065005c0068006100720064006400690073006b0076006f006c0075006d00650031005c00700072006f006700720061006d002000660069006c00650073005c00770069006e0064006f007700730061007000700073005c00610066003600390032006200660066002d0036003700370039002d0034003200340066002d0038003700300065002d006600360065003500390063003500300032003300340039005f0031002e0031002e00310033002e0030005f007800360034005f005f00350063003000330037006a0061007200350038003300390072005c0075007700700073006f0063006b006500740063006c00690065006e0074002e006500780065000000</data>
|
||||
<asString>\\.d.e.v.i.c.e.\\.h.a.r.d.d.i.s.k.v.o.l.u.m.e.1.\\.p.r.o.g.r.a.m.
|
||||
.f.i.l.e.s.\\.w.i.n.d.o.w.s.a.p.p.s.\\.a.f.6.9.2.b.f.f.-.6.7.7.9.-.4.2.4.f.-.8.7.0.e.-.f.6.e.5.9.c.5.0.2.3.4.9._.1...1...1.3...0._.x.6.4._._.5.c.0.3.7.j.a.r.5.8.3.9.r.\\.u.w.p.s.o.c.k.e.t.c.l.i.e.n.t...e.x.e...</asString>
|
||||
|
||||
@ -5,7 +5,7 @@ ms.topic: concept-article
|
||||
manager: aaroncz
|
||||
ms.author: paoloma
|
||||
author: paolomatarazzo
|
||||
ms.date: 11/07/2023
|
||||
ms.date: 09/06/2024
|
||||
---
|
||||
|
||||
# Zero Trust and Windows device health
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user