ADMX drive mapping issue
We have a customer with 12 drive mappings pushed via Intune Import ADMX. We uploaded the admx for windows and the admx for the drivemappings. In the configuration created one policy with al the driveletters configured and pushed this to every device in the environment. Al worked great, untill we changed one drive letter from X to Z i remembered correctly and changed the path to a folder deeper in the folder three. Then it was pushed to everyone and people got issues with the drivermappings. Only 2 or 3 driveletters were showing in file explorer. When you want to add the drive letter via the wizard you can see all the paths to the different drive letters are there. Adding them via that way is not possible. We checked all the settings, like persistent drive mappings, enable linkedeconnections, setting all the drives to not configured, Create separate policy for every driveletter, removed the admx in intune and uploaded again, but nothing is working. currently using a custom script via our minitoring system to get it working again. I have used the ADMX by many customers and never have had these issues. Also opened a microsoft case but they couldn't get it fixed. Only way is a fresh install of the device. But 150 devices is a bit to much time consuming for us and the customer. Love to hear how i can solve this issue.
Creating ADMX backed Configuration policies
I am trying to figure out how to create an ADMX backed Config Profile in Intune to disable the weather and stock information that is now sent to the Windows 11 lock screen but I cannot get it to work. According to this post, I should use the https://learn.microsoft.com/windows/client-management/mdm/policy-csp-windowslogon#disablelockscreenappnotifications CSP. https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-windowslogon#disablelockscreenappnotifications describes the CSP configuration and as it is an ADMX backed policy, it requires SyncML format to configure. Between https://learn.microsoft.com/en-us/windows/client-management/understanding-admx-backed-policies#enabling-a-policy and https://learn.microsoft.com/en-us/windows/client-management/enable-admx-backed-policies-in-mdm, I created a custom Config Profile like below, Name: Disable App Notifications Description: Blank OMA-URI: ./Device/Vendor/MSFT/Policy/Config/WindowsLogon/DisableLockScreenAppNotifications Data Type: String Value: <SyncML xmlns="SYNCML:SYNCML1.2"> <SyncBody> <Replace> <CmdID>2</CmdID> <Item> <Meta> <Format>chr</Format> <Type>text/plain</Type> </Meta> <Target> <LocURI>./Device/Vendor/MSFT/Policy/Config/WindowsLogon/DisableLockScreenAppNotifications</LocURI> </Target> <Data><Enabled/></Data> </Item> </Replace> <Final/> </SyncBody> </SyncML> I've deployed it to my user account first and after it failed, I deployed it to my device where it also failed. The event log shows this error in both cases Can anyone please help tell me where I am going wrong? Thanks in advance
Updating ADMX Templates in InTune
Hi There, There currently doesn't appear to be a way to update ADMX templates, so I am wondering what the correct process is if you want to update the ADMX template to the latest version, currently the only way is the delete the ADMX template and re-upload, but what will happen to the existing policies if they use that ADMX template? Will the policies be deleted too? Also what happens if you delete and re-upload an ADMX template that is a dependency for another ADMX template? Just want to know what the best practice is here and what will happen if I delete and update an existing template.Chrome Policies - ADMX Ingestion and OMA-URI Values | NotificationsAllowedForUrls
Hi. Has Someone succeeded to apply NotificationsAllowedForUrls policies using OMA-URI values? I have set all stuff for ADMX Ingestion for Chrome, using https://support.google.com/chrome/a/answer/9102677. All other settings are working as expected, just this specific one i'm getting error: Name: NotificationsAllowedForUrls OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~ContentSettings/NotificationsAllowedForUrls Value: <enabled/><data id="NotificationsAllowedForUrls" value="1[*.]workplace.com2[*.]office.com"/> Oliver Kieselbach you who are such guru on OMA-URI stuff... did you saw something like this?
