deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-15 14:57:23 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Merge pull request #4786 from MicrosoftDocs/vdi-note

Browse Source 
remove note add commands
This commit is contained in:
jcaparas 2021-02-17 15:30:24 -08:00 committed by GitHub
commit 5213f6942f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 17 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi.md
View File

@ -33,15 +33,8 @@ ms.technology: mde
## Onboard non-persistent virtual desktop infrastructure (VDI) devices ## 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. 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: 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 ## 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). 2. Follow the [server onboarding process](configure-server-endpoints.md#windows-server-2008-r2-sp1-windows-server-2012-r2-and-windows-server-2016).

2
windows/security/threat-protection/microsoft-defender-atp/machine-tags.md
View File

@ -63,7 +63,7 @@ Tags are added to the device view and will also be reflected on the **Devices li
>[!NOTE] >[!NOTE]
> Filtering might not work on tag names that contain parenthesis.<br> > Filtering might not work on tag names that contain parenthesis.<br>
> 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. You can also delete tags from this view.