Clarify VDI scenarios

This commit is contained in:
jobarner
2019-11-24 16:15:45 +02:00
committed by GitHub
parent 2da7d05800
commit e9727b7791

View File

@ -31,14 +31,16 @@ ms.date: 04/24/2018
Microsoft Defender ATP supports non-persistent VDI session onboarding. There might be associated challenges when onboarding VDIs. The following are typical challenges for this scenario: Microsoft Defender ATP supports non-persistent VDI session onboarding. There might be associated challenges when onboarding VDIs. The following are typical challenges for this scenario:
- Instant early onboarding of a short-lived sessions, which must be onboarded to Microsoft Defender ATP prior to the actual provisioning.
- Machine name are typically reused for new sessions.
- Instant early onboarding of a short living session VDI machines can appear in MDATP portal as either:
- A session should be onboarded to Microsoft Defender ATP prior to the actual provisioning.
- Machine name persistence - Single entry for each machine.
- The machine names are typically reused for new sessions. One may ask to have them as a single machine entry while others may prefer to have multiple entries per machine name. Note that in this case, the machine name must be configured when the session is created, for example using an unattended answer file.
- Multiple entries for each machine - one for each session.
You can onboard VDI machines using a single entry or multiple entries for each machine. The following steps will guide you through onboarding VDI machines and will highlight steps for single and multiple entries. The following steps will guide you through onboarding VDI machines and will highlight steps for single and multiple entries.
>[!WARNING] >[!WARNING]
> For environments where there are low resource configurations, the VDI boot proceedure might slow the Microsoft Defender ATP sensor onboarding. > For environments where there are low resource configurations, the VDI boot proceedure might slow the Microsoft Defender ATP sensor onboarding.