WVD Intune Filters to Target Apps Policies Only to Windows 10 Multi-session VMs | Windows Virtual Desktop | Endpoint Manager

Let’s learn about creating WVD Intune Filters to Target Apps Policies Only to Windows 10 Multi-session VMs. Well, this is not applicable for single session or Windows 10 persistent VM created using normal Windows 10 Enterprise SKUs. Well, the filters are also known as assignment filers(?).

I have a detailed post that explains how to start managing Windows 10 multi-session devices with Microsoft Endpoint Manager (#MEM) Intune. While writing this post, the only option to enroll Windows 10 Multi-Session VMs to Intune us using Group Policy. Thanks to Scott for the hint on Twitter.

What is Intune Filter Evaluation Engine

The Intune filter engine is here to help the admins create filter rules to identify a special set of devices using device properties exposed through Intune (#MEM) portal. You can easly identify Windows 10 multi-session devices with this filter evaluation engine. You can see the filter evaluation Engine details in the below screenshot.

It’s important to note that all the device properties are not supported while writing this post. The MEM Intune filters can help to reduce the dependency on Azure AD static or Dynamic groups based on WVD VM names etc…

WVD Intune Filters to Target Apps Policies Only to Windows 10 Multi-session VMs | Windows Virtual Desktop | Endpoint Manager
WVD Intune Filters to Target Apps Policies Only to Windows 10 Multi-session VMs | Windows Virtual Desktop | Endpoint Manager. Credits to Microsoft

WVD Intune Filters to Target Apps Policies Only to Windows 10 Multi-session VMs

Let’s see how to Create Intune MEM Filter Rules to filter only Windows 10 multi-session VMs (a.k.a, session hosts in WVD world). While writing this post, Intune filters are in public preview; hence you need to enable it from the tenant administration node.

You can read more details about enabling filters for your Intune tenant from Jitesh’s post-Use Filters For Assigning Apps Policies And Profiles In Intune Portal | Endpoint Manager. Don’t forget to check the details about the prerequisites and known issues of filters from the above post.

1E Nomad
WVD Intune Filters to Target Apps Policies Only to Windows 10 Multi-session VMs | Windows Virtual Desktop | Endpoint Manager
WVD Intune Filters to Target Apps Policies Only to Windows 10 Multi-session VMs | Windows Virtual Desktop | Endpoint Manager

Now, you head into Intune MEM Filter creation work flow. Let’s have a look how to create filters using the following workflow from Endpoint Manager portal.

  • From the Basics page.
    • Enter the MEM Filter name: Enter the appropriate name for the filter – WVD Windows 10 Multi-Session WVD VMs.
    • Enter the Description: Enter a description for the filterFilter for Windows 10 Multi-Session VMs, not for a single session with normal Windows 10 enterprise SKUs.
  • Select the platform – Windows 10.

You can go to the next page (Rules) by clicking on NEXT button.

WVD Intune Filters to Target Apps Policies Only to Windows 10 Multi-session VMs | Windows Virtual Desktop | Endpoint Manager
WVD Intune Filters to Target Apps Policies Only to Windows 10 Multi-session VMs | Windows Virtual Desktop | Endpoint Manager

Intune Assignment How to Create Filter Rules

You need to create the rules for assignment filters, and this is the brain of the filter engine within Microsoft Endpoint Manager (a.k.a MEM) Intune. This is similar to Azure AD dynamic rules and SCCM collection queries.

To create filter rules, you need to be on the Rules page, as shown in the below screenshot. There are two ways to create or build MEM Intune Filter rules. As you know, I’m a GUI lover, so my preference is to use rule builder to create the rules.

  • Use Rule Builder
  • Use the syntax

Let’s go into the configuration of rules for Windows 10 Multi-session VMs. As you know, WVD Windows 10 Multi-session SKU is a server SKU, and we need to identify and select the “special SKU” for this type of Windows 10 operating system. This operating system SKU is only available in Azure.

You need to select three properties from Filter Rule Builder as mandatory to create the filter rule to identify WVD Windows 10 multi-session VMs (session hosts).

  1. Select the Property as OperatingSystemSKU
  2. Select Operator as Equals
  3. Select Value as ServerRdsh

NOTE! ServerRdsh is the key-value here to identify WVD Windows 10 multi-session VMs (session hosts). The operating system SKU for Windows 10 multi-session is ServerRdsh.

WVD Intune Filters to Target Apps Policies Only to Windows 10 Multi-session VMs | Windows Virtual Desktop | Endpoint Manager
WVD Intune Filters to Target Apps Policies Only to Windows 10 Multi-session VMs | Windows Virtual Desktop | Endpoint Manager

You can refer to the rule syntax created by the Rule builder within filter engine below.

(device.operatingSystemSKU -eq "ServerRdsh")

Click on NEXT, Next, and Create buttons to complete the Intune filters for Windows 10 multi-session. You can assign scope tags if needed, depending on the Intune RBAC scenarios.

How to Use Filters for App Policy and Profile Deployments

The step-by-step details of Use Of Filter, Change or Modify an Existing Filter, Delete a Filter, Reports, and Known Issue are covered by Jitesh in his post. If you looking for more details like How to Use Filters for App Policy and Profile Deployments, then go through Use Filters For Assigning Apps Policies And Profiles In Intune Portal | Endpoint Manager.

MEM Intune Filter Assignments
WVD Intune Filters to Target Apps Policies Only to Windows 10 Multi-session VMs | Windows Virtual Desktop | Endpoint Manager

Resources

Using Windows Virtual Desktop multi-session with Microsoft Endpoint Manager | Microsoft Docs

Create filters in Microsoft Intune – Azure | Microsoft Docs

Categories WVD

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.