A pinch of 'Settings Catalog', a dash of 'Filters' and you've got yourself a perfect recipe.

-
When Microsoft announced the Settings catalog feature in February this year, it opened a whole new world to endless possibilities of managing various Windows 10 device settings. The settings are generated directly from Windows Configuration Service Providers (CSP), and the experience in the catalog is dynamically generated based on the type of setting and its metadata. While still in preview, one can see that Microsoft is trying to standardize settings throughout Microsoft Endpoint Manager.

Then in May this year, Microsoft released another feature in preview known as Filters which is another game changer in how apps and policies can now be assigned at a granular level on specific devices. While the feature does not support all workloads and has some known issues (understandably considering it is still in Preview), in my experience the feature works well and has reduced the use of Azure AD Dynamic device groups.

Now that we have some background on these features, lets see how they can be used together in live scenarios.

Recently, Microsoft released News and Interests on the Windows 10 Taskbar for Windows 10 2004 and later as part of KB5001391 and immediately this created quite a stir in the technical community. While the use of the feature on Enterprise and Professional SKUs is subjective, I wanted to disable it for a customer I recently worked with. They still had some Windows 10 1909 devices running in the environment so I decided to create a Device filter for devices running Windows 10 2004 and later.

Here is how you can easily create a Device Filter -

2. Browse to Devices and look for Filters (preview) option in the bottom.


3. Click on Create.
4. Give a Name and select Platform as Windows 10.
5. Since the News Feed is enabled for Windows 10 versions 2004 and later, we will be using the osVersion to provide the build values.
6. Provide the Scope tags as necessary.
7. Review and create.



Next, we will go ahead and disable the News & Interests feature using Settings Catalog.

2. Browse to Devices – Windows – Configuration Profiles
3. Click Create Profile
4. Select Platform as Windows 10 and later
5. Select Profile as Settings catalog (Preview)
6. Provide a Name and hit next.
7. Click on Add settings.
8. Search for 'News' and select 'Enable News & Interest' as shown below.


9. Set it to 'Not allowed.'


10. Click on Assignments and select the Filter that we created earlier as shown below.


11. Assign Scope tags as necessary.
12. Review and create.

After the policy applies, one can track the reporting against the Settings Catalog policy.


Update 22012022

The setting in Intune has been updated and it now shows under 'Feeds'



Conclusion

While I have demonstrated a specific Use case in this blog, there can be many other real life applications of these features. Microsoft is continuously adding new settings in the Catalog and device properties along with support for more Workloads in the Filters, so the current complexities around device management should only be reduced from here on, however, only time will tell.

Comments

Post a Comment

Popular posts from this blog

How to force escrowing of BitLocker recovery keys using Intune

-
Image
Every now and then it so happens that BitLocker recovery keys do not escrow in AAD. The usual culprits are incorrect BitLocker policies and\or the device hardware configuration failing to meet the minimum requirements. The other scenario and something I recently experienced is when everything is setup right and still the recovery key doesn’t escrow in AAD. As I understand, this can happen if the escrow process got interrupted the first time due to network or local devices related issues and the process could not resume. To circumvent this issue, one can simply push a PowerShell script to the devices to force the escrow of the recovery keys to AAD. Here is a script to do so. try{ $BitlockerVol = Get-BitLockerVolume -MountPoint $env:SystemDrive         $KPID=""         foreach($KP in $BitlockerVol.KeyProtector){             if($KP.KeyProtectorType -eq "RecoveryPassword"){                 $KPID=$KP.KeyProtectorId                 break;             }         }        $o
Read more

Intune: Configure Printers for Non-Administrative Users

-
Image
Configuring printers for end users or giving them the ability to do it themselves is a normal requirement for organizations. Now if your users are Administrators, then the configuration can be straight forward, but in case of Non-Administrators there are additional steps required as Non-Administrators will not be able to add a driver in the driver store despite being able to install a printer. In this blog, I will cover the steps that I took to address this requirement using Intune. The setup involves 2 steps -  1. Setup registries. 2. Install the driver and configure the printer Setting up registries – The registries that need to be configured are actually part of a GPO setting – Allow non-administrators to install drivers for these device setup classes It can be found under: Computer Configuration -> Policies -> Administrative Templates -> System -> Driver Installation I used a Powershell script to set the values and wrapped it in a Win32 application. $Path1
Read more

Prevent users from running certain programs or applications on Windows endpoints using Intune

-
Image
  When it comes to blocking or preventing users from running an application on Windows devices, one normally uses App locker policy, Windows Defender Application Control and not so new but pretty useful method called Defender Vulnerability management within Microsoft 365 Defender Portal. A recent question on the Tech Community Microsoft forum prompted me to look for all possible alternatives. I started reminiscing over the legacy GPO policies and that is when I stumbled upon the policy  Don’t run specified Windows applications  located under User Administrative Templates - The policy setting does come with its own caveat - " This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from starting pr
Read more