Please explain custom configuration policy oma-uri settings.
I have tried and tried to understand custom config policies. I have read every document Microsoft has on the topic and I have walked away with less understanding than I started. I have never been able to get it to work. I don't understand the premise. I keep having to search for examples but most don't work and most don't detail why or how to get working. It is like Microsoft spent more time not documenting it than just telling us what to do. So please someone can you dumb it down a whole lot? I really want to understand it but I'm just giving up and need a boost to try again.Custom profile: hide known file extensions
Hi, i would like to configure our WIndows 10 clients so that they show all the file extensions. There is a GPO to configure this but i would like to configure this through MS Intune. Do you have any advice on how to achive this? (I already know how to use custom admx policies, how to ingest them, but i don't know how to configure this.) Is there a way to do this via OMA-URI or any other possibilities to set a registry value? (I don't like the powershell via intune way) Thank you in advance. 🙂 Kind regards Patrickmanage Interactive logon & Windows Hello multi-factor unlock
Hi everyone, We're going step by step on the passwordless strategy from Microsoft. Windows Hello multi-factor unlock is deployed in a Pilot Group but now I have two questions, which I hope someone here can answer. Question 1: disable Windows Hello multi-factor unlock Managed to enable WHMFU over custom OMA-URI Settings. But how can I disable it again? I tried it with a second custom OMA-URI Settings configuration profile which is configured as follows: It works, but it seems, that it isn't disabled correctly. Sometimes I still get a message in the logon process which says something like "additional factor needs to verify" but it displays very quickly, and I verified that I can log on with only one factor again. Disabling the second unlock factor is configured like this as well. Question 2: Enable "Interactive logon: Require Windows Hello for Business or smart card" We want to enable this security option. However, Intune doesn't offer to manage this setting. So, I think that I must enable this over a custom OMA-URI Setting too or PowerShell script. How can I achieve this? Thanks so much for any support ❤️OMA-URI Lockscreen
Recently our Organization started to migrate our client infrastructure to Microsoft Intune. Windows 10 OMA-URI Lockscreen Timeout: To personalize a timer of inactivity to lock Windows 10 you will have to create a custom device configuration profile with an OMA-URI path. I will now explain you which settings you have to set to get it working: How-to The OMA-URI Path is: To define a time of inactivity create the Data type Integer. Use your preferenced amount in seconds. (for exampe: 900 for 15 minutes.) Take a look to the image attachment for exact configuration. Now assign this device configuration profile to your device group. Make sure you also sync it to the client from the web portal of Intune, but also on the client in the company portal. Perfect, the assigned devices will now lock after a user inactivity time which you defined.
Enable WinRM through Intune
Hello everybody, I'm trying to enable WinRM to remotely manage our devices, when onprem. Therefore i tried to add a custom profile with the following OMA-URI: ./Device/Vendor/MSFT/Policy/Config/RemoteManagement/AllowRemoteServerManagement (With value <enabled>). Unfortunatelly the result is "-2016281112 (Remediation failed)". What am i making wrong? Thanks in advance. 🙂 Regards Patrick
