Event banner
Policy management with Microsoft Intune
Event Ended
Tuesday, Oct 25, 2022, 07:30 AM PDTEvent details
You’ve seen all the exciting Microsoft Intune policy news at Microsoft Ignite, now it’s time to go deeper. Come join Julia and Mike as we share our top five Intune policy tips and tricks to help keep...
Heather_Poulsen
Updated Dec 27, 2024
Mike-Danoski
Microsoft
Oct 25, 2022Hi Lucas. Some CSPs are ADMX backed meaning the CSP relies on the built-in windows ADMX files on a machine behind the scenes, and some are just specifically what we call ADMX ingested that we install via the ADMXInstall CSP. For ADMXInstalled settings like Office, Edge, OneDrive and imported ADMX settings there is a chance that the config command lands on the device before the ADMXInstall command completes. We're constantly making improvements to this specific condition, but it will always be a chance it can happen and should be temporary.
Lucas_Chappelle
Oct 25, 2022Occasional Reader
Hi Mike,
Do you know how temporary? These machines have had this error show up for at least 2~ weeks. I've seen some machines remediate themselves after the next sync scan, so I definitely get what you mean. But I imagine after 2 weeks, there is probably another underlying issue?
- Mike-DanoskiOct 25, 2022
Microsoft
Should be less than a day. If it's taking longer, please open a support case. There are some events in the MDM diagnostic logs that should provide more information.