Skip to content

deployment-vdi-microsoft-defender-antivirus.md

Latest commit

 

History

History
361 lines (207 loc) · 16.9 KB

deployment-vdi-microsoft-defender-antivirus.md

File metadata and controls

361 lines (207 loc) · 16.9 KB

title: Configure Microsoft Defender Antivirus on a remote desktop or virtual desktop infrastructure environment description: Get an overview of how to configure Microsoft Defender Antivirus in a remote desktop or non-persistent virtual desktop environment. ms.localizationpriority: medium ms.date: 10/20/2025 ms.topic: how-to author: chrisda ms.author: chrisda ms.custom: nextgen ms.reviewer: jesquive manager: bagol ms.subservice: ngp ms.service: defender-endpoint ms.collection:

  • m365-security
  • tier2
  • ContentEngagementFY23
  • mde-ngp search.appverid: met150 appliesto:
    • Microsoft Defender for Endpoint Plan 1
    • Microsoft Defender for Endpoint Plan 2
    • Microsoft Defender Antivirus

Configure Microsoft Defender Antivirus on a remote desktop or virtual desktop infrastructure environment

This article is designed for customers who are using Microsoft Defender Antivirus capabilities only. If you have Microsoft Defender for Endpoint (which includes Microsoft Defender Antivirus alongside other device protection capabilities), see Onboard non-persistent virtual desktop infrastructure (VDI) devices in Microsoft Defender XDR.

You can use Microsoft Defender Antivirus in a remote desktop (RDS) or non-persistent virtual desktop infrastructure (VDI) environment. Using the guidance in this article, you can configure updates to download directly to your RDS or VDI environments whenever a user signs in.

This guide describes how to configure Microsoft Defender Antivirus on your VMs for optimal protection and performance, including how to:

Important

Although a VDI can be hosted on Windows Server 2012 or Windows Server 2016, virtual machines (VMs) should be running Windows 10, version 1607 at a minimum, due to increased protection technologies and features that are unavailable in earlier versions of Windows.

Prerequisites

Supported operating systems

  • Windows

Set up a dedicated VDI file share for security intelligence

In Windows 10, version 1903, Microsoft introduced the shared security intelligence feature, which offloads the unpackaging of downloaded security intelligence updates onto a host machine. This method reduces the usage of CPU, disk, and memory resources on individual machines. Shared security intelligence now works on Windows 10, version 1703 and later. You can set up this capability by using Group Policy or PowerShell.

Group Policy

  1. On your Group Policy management computer, open the Group Policy Management Console, right-click the Group Policy Object you want to configure, and then select Edit.

  2. In the Group Policy Management Editor, go to Computer configuration.

  3. Select Administrative templates. Expand the tree to Windows components > Microsoft Defender Antivirus > Security Intelligence Updates.

  4. Double-click Define security intelligence location for VDI clients, and then set the option to Enabled. A field automatically appears.

  5. In the field, type \\<File Server shared location\>\wdav-update. (For help with this value, see Download and unpackage.)

  6. Select OK, and then deploy the Group Policy Object to the VMs you want to test.

PowerShell

  1. On each RDS or VDI device, use the following cmdlet to enable the feature:

    Set-MpPreference -SharedSignaturesPath \\<File Server shared location>\wdav-update

  2. Push the update as you normally would push PowerShell-based configuration policies onto your VMs. (See the Download and unpackage section in this article. Look for the shared location entry.)

Download and unpackage the latest updates

Now you can get started on downloading and installing new updates. This section contains a sample PowerShell script that you can use. This script is the easiest way to download new updates and get them ready for your VMs. You should then set the script to run at a certain time on the management machine by using a scheduled task. Or, if you're familiar with using PowerShell scripts in Azure, Intune, or Configuration Manager, you could use those scripts instead.

$vdmpathbase = "$env:systemdrive\wdav-update\{00000000-0000-0000-0000-"
$vdmpathtime = Get-Date -format "yMMddHHmmss"
$vdmpath = $vdmpathbase + $vdmpathtime + '}'
$vdmpackage = $vdmpath + '\mpam-fe.exe'

New-Item -ItemType Directory -Force -Path $vdmpath | Out-Null

Invoke-WebRequest -Uri 'https://go.microsoft.com/fwlink/?LinkID=121721&arch=x64' -OutFile $vdmpackage

Start-Process -FilePath $vdmpackage -WorkingDirectory $vdmpath -ArgumentList "/x"

You can set a scheduled task to run once a day so that whenever the package is downloaded and unpacked then the VMs receive the new update. We suggest starting with once a day, but you should experiment with increasing or decreasing the frequency to understand the impact.

Security intelligence packages are typically published once every three to four hours. Setting a frequency shorter than four hours isn't advisable because it increases the network overhead on your management machine for no benefit.

You can also set up your single server or machine to fetch the updates on behalf of the VMs at an interval and place them in the file share for consumption. This configuration is possible when the devices have share and read access (NTFS permissions) to the share so they can grab the updates. To set up this configuration, follow these steps:

  1. Create an SMB/CIFS file share.

  2. Use the following example to create a file share with the following share permissions.

    PS c:\> Get-SmbShareAccess -Name mdatp$

Name   ScopeName AccountName AccessControlType AccessRight
----   --------- ----------- ----------------- -----------
mdatp$ *         Everyone    Allow             Read

    [!NOTE] An NTFS permission is added for Authenticated Users:Read:.

    For this example, the file share is \\FileServer.fqdn\mdatp$\wdav-update.

Set a scheduled task to run the PowerShell script

  1. On the management machine, open the Start menu and type Task Scheduler. From the results, select Task Scheduler and then select Create task... in the side panel.

  2. Specify the name as Security intelligence unpacker.

  3. On the Trigger tab, select New... > Daily, and select OK.

  4. On the Actions tab, select New....

  5. Specify PowerShell in the Program/Script field.

  6. In the Add arguments field, type -ExecutionPolicy Bypass c:\wdav-update\vdmdlunpack.ps1, and then select OK.

  7. Configure any other settings as appropriate.

  8. Select OK to save the scheduled task.

To initiate the update manually, right-click on the task, and then select Run.

Download and unpackage manually

If you would prefer to do everything manually, here's what to do to replicate the script's behavior:

  1. Create a new folder on the system root called wdav_update to store intelligence updates. For example, create the folder c:\wdav_update.

  2. Create a subfolder under wdav_update with a GUID name, such as {00000000-0000-0000-0000-000000000000}

    Here's an example: c:\wdav_update\{00000000-0000-0000-0000-000000000000}

    [!NOTE] We set the script so that the last 12 digits of the GUID are the year, month, day, and time when the file was downloaded so that a new folder is created each time. You can change this so that the file is downloaded to the same folder each time.

  3. Download a security intelligence package from https://www.microsoft.com/wdsi/definitions into the GUID folder. The file should be named mpam-fe.exe.

  4. Open a Command Prompt window and navigate to the GUID folder you created. Use the /X extraction command to extract the files. For example, mpam-fe.exe /X.

    [!NOTE] The VMs pick up the updated package whenever a new GUID folder is created with an extracted update package or whenever an existing folder is updated with a new extracted package.

Microsoft Defender Antivirus configuration settings

It's important to take advantage of the included threat protection capabilities by enabling them with the following recommended configuration settings. It's optimized for VDI environments.

Tip

The latest Windows group policy administrative templates are available in Create and manage Central Store.

Root

  • Configure detection for potentially unwanted applications: Enabled - Block

  • Configure local administrator merge behavior for lists: Disabled

  • Control whether or not exclusions are visible to Local Admins: Enabled

  • Turn off routine remediation: Disabled

  • Randomize scheduled scans: Enabled

Client Interface

  • Enable headless UI mode: Enabled

    [!NOTE] This policy hides the entire Microsoft Defender Antivirus user interface from end users in your organization.

  • Suppress all notifications: Enabled

    [!NOTE] Sometimes, Microsoft Defender Antivirus notifications are sent to or persist across multiple sessions. To help avoid user confusion, you can lock down the Microsoft Defender Antivirus user interface. Suppressing notifications prevents notifications from Microsoft Defender Antivirus from showing up when scans are done or remediation actions are taken. However, your security operations team sees the results of a scan if an attack is detected and stopped. Alerts, such as an initial access alert, are generated, and appear in the Microsoft Defender portal.

MAPS

  • Join Microsoft MAPS (Turn on cloud-delivered protection): Enabled - Advanced MAPS

  • Send file samples when further analysis is required: Send all samples (more secure) or Send safe sample (less secure)

MPEngine

  • Configure extended cloud check: 20

  • Select cloud protection level: Enabled - High

  • Enable file hash computation feature: Enabled

Note

"Enable file hash computation feature" is only needed if using Indicators – File hash. It can cause higher amount of CPU utilization, since it has to parse through each binary on disk to get the file hash.

Real-time protection

  • Configure monitoring for incoming and outgoing file and program activity: Enabled – bi-directional (full on-access)

  • Monitor file and program activity on your computer: Enabled

  • Scan all downloaded files and attachments: Enabled

  • Turn on behavior monitoring: Enabled

  • Turn on process scanning whenever real-time protection is enabled: Enabled

  • Turn on raw volume write notifications: Enabled

Scans

  • Check for the latest virus and spyware security intelligence before running a scheduled scan: Enabled

  • Scan archive files: Enabled

  • Scan network files: Not configured

  • Scan packed executables: Enabled

  • Scan removable drives: Enabled

  • Turn on catch-up full scan (Disable catch-up full scan): Not configured

  • Turn on catch-up quick scan (Disable catchup quick scan): Not configured

    [!NOTE] If you want to harden, you could change "Turn on catch-up quick scan" to Enabled, which helps when VMs are offline, and have missed two or more consecutive scheduled scans. But since it's running a scheduled scan, it uses additional CPU.

  • Turn on e-mail scanning: Enabled

  • Turn on heuristics: Enabled

  • Turn on reparse point scanning: Enabled

General scheduled scan settings

  • Configure low CPU priority for scheduled scans (Use low CPU priority for scheduled scans): Not configured

  • Specify the maximum percentage of CPU utilization during a scan (CPU usage limit per scan): 50

  • Start the scheduled scan only when computer is on but not in use (ScanOnlyIfIdle): Not configured

  • Use the following cmdlet, to stop a quick or scheduled scan whenever the device goes idle if it is in passive mode.

    Set-MpPreference -ScanOnlyIfIdleEnabled $false

Tip

The setting, "Start the scheduled scan only when computer is on but not in use" prevents significant CPU contention in high-density environments.

Daily quick scan

  • Specify the interval to run quick scans per day: Not configured

  • Specify the time for a daily quick scan (Run daily quick scan at): 12 PM

Run a weekly scheduled scan (quick or full)

  • Specify the scan type to use for a scheduled scan (Scan type): Not configured

  • Specify the time of day to run a scheduled scan (Day of week to run scheduled scan): Not configured

  • Specify the day of the week to run a scheduled scan (Time of day to run a scheduled scan): Not configured

Security Intelligence Updates

  • Turn on scan after security intelligence update (Disable scans after an update): Disabled

    [!NOTE] Disabling a scan after a security intelligence update prevents a scan from occurring after receiving an update. You can apply this setting when creating the base image if you have also run a quick scan. This way, you can prevent the newly updated VM from performing a scan again (as you've already scanned it when you created the base image).

    [!IMPORTANT] Running scans after an update helps ensure your VMs are protected with the latest security intelligence updates. Disabling this option reduces the protection level of your VMs and should only be used when first creating or deploying the base image.

  • Specify the interval to check for security intelligence updates (Enter how often to check for security intelligence updates): Enabled - 8

  • Leave other settings in their default state

Threats

  • Specify threat alert levels at which default action shouldn't be taken when detected: Enabled

  • Set Severe (5), High (4), Medium (2), and Low (1) all to Quarantine (2), as shown in the following table:

    Value name Value
    1 (Low) 2
    2 (Medium) 2
    4 (High) 2
    5 (Severe) 2

Attack surface reduction rules

Configure all available rules to Audit.

Enable network protection

Prevent users and apps from accessing dangerous websites (Enable network protection): Enabled - Audit mode.

SmartScreen for Microsoft Edge

  • Require SmartScreen for Microsoft Edge: Yes

  • Block malicious site access: Yes

  • Block unverified file download: Yes

Run the Windows Defender Cache Maintenance scheduled task

Optimize the "Windows Defender Cache Maintenance" scheduled task for non-persistent and/or persistent VDI environments. Run this task on the main image before sealing.

  1. Open up the Task Scheduler mmc (taskschd.msc).

  2. Expand Task Scheduler Library > Microsoft > Windows > Windows Defender, and then right-click on Windows Defender Cache Maintenance.

  3. Select Run, and let the scheduled task finish.

    [!WARNING] If you don't do this, it can cause higher cpu utilization while the cache maintenance task is running on each of the VMs.

Enable tamper protection

Enable tamper protection to prevent Microsoft Defender Antivirus from being disabled in the Microsoft Defender portal.

Exclusions

If you think you need to add exclusions, see Manage exclusions for Microsoft Defender for Endpoint and Microsoft Defender Antivirus.

Next step

If you're also deploying endpoint detection and response (EDR) to your Windows-based VDI VMs, see Onboard non-persistent virtual desktop infrastructure (VDI) devices in Microsoft Defender XDR.

See also

If you're looking for information about Defender for Endpoint on non-Windows platforms, see the following resources: