Open Filisteos opened 3 weeks ago
Hello,
Sp sorry, I missed this somehow.
What version did you use to export the policy?
You should see properties in the exported file starting with #Definition_. This will not work unless you have these properties.
Custom ADMX is complicated. Each import generates new policy IDs. Even in the same tenant, and the feature has been broken a couple of times because Microsoft changed something in the background. The script will add the #Definition and #Presentation properties so it can find policy setting to import in other tenants.
Cheers!
Hi @Micke-K ! I am using Intune Management Master version 3.9.6 I'm going to show you step by step the error I encountered and I hope you can help me:
Pre-importing ADMX templates (always en-US)![image](https://github.com/Micke-K/IntuneManagement/assets/143745549/cee116e2-c565-4f18-a4b8-6d3c27198a92)
Importing the profile containing ADMX template settings from Chrome.admx![image](https://github.com/Micke-K/IntuneManagement/assets/143745549/820b911e-d866-4cca-9c6b-280359b806c2)
Here I notice the error, and that is that the imported profile does not contain any policy:![image](https://github.com/Micke-K/IntuneManagement/assets/143745549/c13d5382-dee5-499a-b1e7-44d799568941)
There should really only be one policy listed which is the following policy:![image](https://github.com/Micke-K/IntuneManagement/assets/143745549/fcfacd08-f822-4782-95d9-bcc083ca5b36)
The only thing I see different from the original profile I exported it from are the “?” characters in the policy name that don’t appear in the original profile. Here’s what it looks like in the original profile:![image](https://github.com/Micke-K/IntuneManagement/assets/143745549/89f8c95c-8988-484a-9409-a16a2accb849)
The policy I'm working on allows device information to be collected when using Google Chrome allowing Conditional Access to be applied to Microsoft account logins from Chrome.
Thanks for your help. :)