SCCM Device Collection Equivalents in Microsoft Intune for App Deployment

We use collection in SCCM to target a deployment. let’s assume we have to apply a patch on all Dell computers to address an issue. The quick way to deploy a fix through SCCM was to create a collection with all Dell computers and target the deployment on that collection. Same concept was being used for application upgrade (legacy package & program model) as well where a collection can be created to include all machines with specific version of application and then target the deployment on that collection.

When it’s come to Intune, we need to handle same requirements differently by combining different options such as Azure AD Group, Intune Assignment Filter, and Win32 App features ( Requirement Rules, Detection rule, Supersedence etc). The Intune Filters allow granular targeting of the deployment and they are reusable. While Requirement Rule allow the deployment when certain conditions are met. This eliminate the need to have only required devices in AD Group. The deployment can be targeted on all Devices and actual installation can be narrow down using Intune Assignment Filters, Requirements rule or other options.

Let’s understand how we can achieve different requirements in Intune with the help of few examples.

Requirements: Deploy an utility on all Dell computers

SCCM approach: Create a dynamic collection for all computers where manufacturer is Dell. Deploy the package to the collection.

Intune approach: Different options can be clubbed to achieve this. See the examples below.

Option 1:

Create an ​AAD Group with Dynamic membership and assign application on that AAD group.

AAD Group query: (device.deviceManufacturer -eq “Dell”)

Option 2:

Use an AAD Group with wider scope, e:g – All Windows 10 Devices.

Apply an Intune Assignment Filter to include only Dell computers.

Filter query: (device.manufacturer -contains “Dell”)

Option 3:

Use an AAD Group, e:g – All Windows 10 Devices

Use Win32 App – Additional Requirement rule to check if Device manufacture is Dell. The application will be offered if requirement rule condition met.

Requirements: Deploy a drivers package to Lenovo Thinkpad T490

SCCM approach: Create a dynamic collection where device model is Thinkpad T490. Deploy package on that collection.

Intune approach: Different options can be clubbed to achieve this. See the examples below.

Option 1:

Create an ​AAD Group with Dynamic membership to all device which model is T490.

Example: (device.deviceModel -contains “Thinkpad T490”)

Option 2:

Use an AAD Group with wider scope, e:g – All Windows 10 Devices

Apply an Assignment Filter, e:g, (device.model -contains “Thinkpad T490”)

Option 3

Use an AAD Group with wider scope, e:g – All Windows 10 Devices

Use Win32 App – Additional Requirement rule to check if Device model is Lenovo Thinkpad T490

Requirements: Deploy an application to All Computers for a specific OS Version

SCCM approach: Create a collection to include all computers with specific OS version. Deploy package to that collection.

Intune approach:

Option 1:

Create an ​AAD Group with Dynamic membership to include all device with specific OS version

AAD Group query example : (device.deviceOSVersion -startsWith “10.0.0”)

Option 2:

Use an AAD Group with wider scope, e:g – All Windows 10 Devices

Apply a Filter, eg, (device.deviceOSVersion -eq “10.0.1”)

Option 3:

Use an AAD Group with wider scope, e:g – All Windows 10 Devices

Use Win32 App Requirement rule to install application only if requirements (such as OS Version) are met.

Stay tuned ! We will cover more such scenarios in upcoming posts.

RelatedPosts:

Subscribe to Techuisitive Newsletter

Be the first to know about our new blog posts. Get our newsletters directly in your inbox and stay up to date about Modern Desktop Management technologies & news.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top