mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-15 14:57:23 +00:00
Update configure-endpoints-vdi.md
This commit is contained in:
parent
e4c8946c0d
commit
dc0413f922
@ -63,25 +63,21 @@ The following steps will guide you through onboarding VDI devices and will highl
|
||||
|
||||
1. Click **Download package** and save the .zip file.
|
||||
|
||||
2. Copy all the extracted files from the .zip into `golden/master` image under the path `C:\WINDOWS\System32\GroupPolicy\Machine\Scripts\Startup`. You should have a folder called `WindowsDefenderATPOnboardingPackage` containing the file `WindowsDefenderATPOnboardingScript.cmd`.
|
||||
2. Copy files from the WindowsDefenderATPOnboardingPackage folder extracted from .zip file into `golden/master` image under the path `C:\WINDOWS\System32\GroupPolicy\Machine\Scripts\Startup`.
|
||||
|
||||
1. If you are not implementing a single entry for each device: copy WindowsDefenderATPOnboardingScript.cmd.
|
||||
|
||||
1. If you are implementing a single entry for each device: copy both Onboard-NonPersistentMachine.ps1 and WindowsDefenderATPOnboardingScript.cmd.
|
||||
|
||||
>[!NOTE]
|
||||
>If you don't see the `C:\WINDOWS\System32\GroupPolicy\Machine\Scripts\Startup` folder, it might be hidden. You'll need to choose the **Show hidden files and folders** option from file explorer.
|
||||
|
||||
3. The following step is only applicable if you're implementing a single entry for each device: <br>
|
||||
**For single entry for each device**:
|
||||
|
||||
1. From the `WindowsDefenderATPOnboardingPackage`, copy the `Onboard-NonPersistentMachine.ps1` and `WindowsDefenderATPOnboardingScript.cmd` file to `golden/master` image to the path `C:\WINDOWS\System32\GroupPolicy\Machine\Scripts\Startup`. <br>
|
||||
|
||||
> [!NOTE]
|
||||
> If you don't see the `C:\WINDOWS\System32\GroupPolicy\Machine\Scripts\Startup` folder, it might be hidden. You'll need to choose the **Show hidden files and folders** option from file explorer.
|
||||
|
||||
4. Open a Local Group Policy Editor window and navigate to **Computer Configuration** > **Windows Settings** > **Scripts** > **Startup**.
|
||||
3. Open a Local Group Policy Editor window and navigate to **Computer Configuration** > **Windows Settings** > **Scripts** > **Startup**.
|
||||
|
||||
> [!NOTE]
|
||||
> Domain Group Policy may also be used for onboarding non-persistent VDI devices.
|
||||
|
||||
5. Depending on the method you'd like to implement, follow the appropriate steps: <br>
|
||||
4. Depending on the method you'd like to implement, follow the appropriate steps: <br>
|
||||
**For single entry for each device**:<br>
|
||||
|
||||
Select the **PowerShell Scripts** tab, then click **Add** (Windows Explorer will open directly in the path where you copied the onboarding script earlier). Navigate to onboarding PowerShell script `Onboard-NonPersistentMachine.ps1`.
|
||||
@ -90,7 +86,7 @@ The following steps will guide you through onboarding VDI devices and will highl
|
||||
|
||||
Select the **Scripts** tab, then click **Add** (Windows Explorer will open directly in the path where you copied the onboarding script earlier). Navigate to the onboarding bash script `WindowsDefenderATPOnboardingScript.cmd`.
|
||||
|
||||
6. Test your solution:
|
||||
5. Test your solution:
|
||||
|
||||
1. Create a pool with one device.
|
||||
|
||||
@ -103,9 +99,9 @@ The following steps will guide you through onboarding VDI devices and will highl
|
||||
1. **For single entry for each device**: Check only one entry in Microsoft Defender Security Center.<br>
|
||||
**For multiple entries for each device**: Check multiple entries in Microsoft Defender Security Center.
|
||||
|
||||
7. Click **Devices list** on the Navigation pane.
|
||||
6. Click **Devices list** on the Navigation pane.
|
||||
|
||||
8. Use the search function by entering the device name and select **Device** as search type.
|
||||
7. Use the search function by entering the device name and select **Device** as search type.
|
||||
|
||||
## Updating non-persistent virtual desktop infrastructure (VDI) images
|
||||
As a best practice, we recommend using offline servicing tools to patch golden/master images.<br>
|
||||
|
Loading…
x
Reference in New Issue
Block a user