mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-21 17:57:22 +00:00
Update Onboard-Windows-10-multi-session-device.md
This commit is contained in:
parent
0ae16edbf5
commit
aa5f497d66
@ -36,8 +36,8 @@ Familiarize yourself with the [considerations for non-persistent VDI](https://do
|
||||
> Depending on your choice of onboarding method, devices can appear in Microsoft Defender for Endpoint portal as either:
|
||||
> - Single entry for each virtual device
|
||||
> - Multiple entries for each virtual device
|
||||
>
|
||||
> Microsoft recommends onboarding Windows Virtual Devices as a single entry per virtual device. This ensures that the investigation experience in the MDATP portal is in the context of one device based on the machine name. Organizations that frequently delete and re-deploy WVD hosts should strongly consider using this method as it prevents multiple objects for the same machine from being created in the MDATP portal. This can lead to confusion when investigating incidents. For test or non-volatile environments, you may opt to choose differently.
|
||||
|
||||
Microsoft recommends onboarding Windows Virtual Devices as a single entry per virtual device. This ensures that the investigation experience in the MDATP portal is in the context of one device based on the machine name. Organizations that frequently delete and re-deploy WVD hosts should strongly consider using this method as it prevents multiple objects for the same machine from being created in the MDATP portal. This can lead to confusion when investigating incidents. For test or non-volatile environments, you may opt to choose differently.
|
||||
|
||||
Microsoft recommends adding the Microsoft Defender for Endpoint onboarding script to the WVD golden image. This way, you can be sure that this onboarding script runs immediately at first boot. It is executed as a startup script at first boot on all the WVD machines that are provisioned from the WVD golden image. However, if you are using one of the gallery images without modification, place the script in a shared location and call it from either local or domain group policy.
|
||||
|
||||
@ -47,8 +47,8 @@ Microsoft recommends adding the Microsoft Defender for Endpoint onboarding scrip
|
||||
### Scenarios
|
||||
There are several ways to onboard a WVD host machine:
|
||||
|
||||
Run the script in the golden image (or from a shared location) during startup.
|
||||
Use a management tool to run the script.
|
||||
- Run the script in the golden image (or from a shared location) during startup.
|
||||
- Use a management tool to run the script.
|
||||
|
||||
#### *Scenario 1: Using local group policy*
|
||||
This scenario requires placing the script in a golden image and uses local group policy to run early in the boot process.
|
||||
@ -110,21 +110,21 @@ In addition, if you are using FSlogix user profiles, we recommend you exclude th
|
||||
|
||||
**Exclude Files:**
|
||||
|
||||
%ProgramFiles%\FSLogix\Apps\frxdrv.sys
|
||||
%ProgramFiles%\FSLogix\Apps\frxdrvvt.sys
|
||||
%ProgramFiles%\FSLogix\Apps\frxccd.sys
|
||||
%TEMP%\*.VHD
|
||||
%TEMP%\*.VHDX
|
||||
%Windir%\TEMP\*.VHD
|
||||
%Windir%\TEMP\*.VHDX
|
||||
\\storageaccount.file.core.windows.net\share\*\*.VHD
|
||||
\\storageaccount.file.core.windows.net\share\*\*.VHDX
|
||||
> ProgramFiles%\FSLogix\Apps\frxdrv.sys
|
||||
> %ProgramFiles%\FSLogix\Apps\frxdrvvt.sys
|
||||
> %ProgramFiles%\FSLogix\Apps\frxccd.sys
|
||||
> %TEMP%\*.VHD
|
||||
> %TEMP%\*.VHDX
|
||||
> %Windir%\TEMP\*.VHD
|
||||
> %Windir%\TEMP\*.VHDX
|
||||
> \\storageaccount.file.core.windows.net\share\*\*.VHD
|
||||
> \\storageaccount.file.core.windows.net\share\*\*.VHDX
|
||||
|
||||
**Exclude Processes:**
|
||||
|
||||
%ProgramFiles%\FSLogix\Apps\frxccd.exe
|
||||
%ProgramFiles%\FSLogix\Apps\frxccds.exe
|
||||
%ProgramFiles%\FSLogix\Apps\frxsvc.exe
|
||||
> %ProgramFiles%\FSLogix\Apps\frxccd.exe
|
||||
> %ProgramFiles%\FSLogix\Apps\frxccds.exe
|
||||
> %ProgramFiles%\FSLogix\Apps\frxsvc.exe
|
||||
|
||||
#### Licensing requirements
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user