Skip to content

Update configure-endpoints-vdi.md #213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Mar 11, 2025
Merged

Update configure-endpoints-vdi.md #213

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f1dc08a
Update configure-endpoints-vdi.md
PremMS-MDE Mar 10, 2025
3d08010
Update date and clarify VDI onboarding delay
denisebmsft Mar 11, 2025
9f92d92
Merge branch 'public' into patch-4
denisebmsft Mar 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions defender-endpoint/configure-endpoints-vdi.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ ms.collection:
- tier2
ms.custom: admindeeplinkDEFENDER
ms.topic: conceptual
ms.date: 03/04/2025
ms.date: 03/11/2025
ms.subservice: onboard
---

Expand Down Expand Up @@ -55,8 +55,8 @@ Defender for Endpoint supports non-persistent VDI session onboarding. There migh
- In a VDI environment, VDI instances can have short lifespans. VDI devices can appear in the Microsoft Defender portal as either single entries for each VDI instance or multiple entries for each device.

- Single entry for each VDI instance. If the VDI instance was already onboarded to Microsoft Defender for Endpoint, and at some point deleted, and then recreated with the same host name, a new object representing this VDI instance is NOT be created in the portal. In this case, the *same* device name must be configured when the session is created, for example using an unattended answer file.

- Multiple entries for each device - one for each VDI instance.
- For all VDI machines, when they onboard for the first time, there's a client delay of approximately 3-4 hours.

> [!IMPORTANT]
> If you're deploying non-persistent VDIs through cloning technology, make sure that your internal template VMs are not onboarded to Defender for Endpoint. This recommendation is to avoid cloned VMs from being onboarded with the same senseGuid as your template VMs, which could prevent VMs from showing up as new entries in the Devices list.
Expand Down