From a8e0501663e1eac62d50b0159750aab1a21620d6 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Wed, 17 Feb 2021 15:00:33 -0800 Subject: [PATCH 1/2] remove note add commads --- .../configure-endpoints-vdi.md | 24 ++++++++++++------- 1 file changed, 16 insertions(+), 8 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md b/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md index 766b0d8fcf..1e4a2f4440 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md +++ b/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md @@ -33,15 +33,8 @@ ms.technology: mde ## Onboard non-persistent virtual desktop infrastructure (VDI) devices -[!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)] - - Defender for Endpoint supports non-persistent VDI session onboarding. ->[!Note] ->To onboard non-persistent VDI sessions, VDI devices must be Windows 10 or Windows Server 2019. -> ->While other Windows versions might work, only Windows 10 and Windows Server 2019 are supported. There might be associated challenges when onboarding VDIs. The following are typical challenges for this scenario: @@ -114,7 +107,22 @@ The following steps will guide you through onboarding VDI devices and will highl ## For downlevel SKUs -1. Set registry value 'HKLM\SOFTWARE\Policies\Microsoft\Windows Advanced Threat Protection\DeviceTagging|VDI’ to “NonPersistent' + +> [!NOTE] +> The following registry is relevant only when the aim is to achieve a 'Single entry for each device'. + +1. Set registry value to: + + ```reg + [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Advanced Threat Protection\DeviceTagging] + "VDI"="NonPersistent" + ``` + + or using command line: + + ``` + reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Advanced Threat Protection\DeviceTagging" /v VDI /t REG_SZ /d "NonPersistent" /f + ``` 2. Follow the [server onboarding process](configure-server-endpoints.md#windows-server-2008-r2-sp1-windows-server-2012-r2-and-windows-server-2016). From 17681f4d35dae428025d0dc6b066795835f233ce Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Wed, 17 Feb 2021 15:23:49 -0800 Subject: [PATCH 2/2] vdi note --- .../threat-protection/microsoft-defender-atp/machine-tags.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/machine-tags.md b/windows/security/threat-protection/microsoft-defender-atp/machine-tags.md index 1fabec8569..33158122e0 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/machine-tags.md +++ b/windows/security/threat-protection/microsoft-defender-atp/machine-tags.md @@ -63,7 +63,7 @@ Tags are added to the device view and will also be reflected on the **Devices li >[!NOTE] > Filtering might not work on tag names that contain parenthesis.
-> Filtering will only find portal set tags. +> When you create a new tag, a list of existing tags are displayed. The list only shows tags created through the portal. Existing tags created from client devices will not be displayed. You can also delete tags from this view.