We deployed this key in this link through GPO before we knew about the ADMX being incorrect. I was hoping that I could change it in a policy file to change the data type.
I have the policy definitions stored on our domain sysvol, but I don't see any reference to the key type in the outlk14 or outlk15 admx files. The .POL file seems to be binary. We have a mixture of XP & Win7 clients, and I'm not crazy about pushing out the GP PReference client side extensions just to fix this bug. What other options do we have to fix this so that it can be managed completely within the GP Mgmt console?
Before going further, we’d better confirm the current issue first. Would you please let me know what did you mean the ADMX file were incorrect? Do you mean you want to convert the Registry Data Types before deploying the Outlook policy settings? If so, please understand that there isn’t any related settings in Group Policy to achieve the target.
Regarding your request, maybe we should use GPP or script to achieve the target. If you have some trouble modifying the script, I suggest we could ask in the script forum.
The Official Scripting Guys Forum!
In addition, here is a similar discussion about how to handle REG_BINARY Data Type via GPO, some people have provided the good suggestions, they may be useful to us.
How to convert a .reg key with a binery value in to an .adm file?
Hope this helps.
TechNet Community Support
Well, per the link I provided, the issue is that one of the settings in the ADMX is using the wrong data type. So when I activate it via GP, the setting doesn't work, and when I use MS Office Configuration Analyzer Tool, it barks about it as well. Instead of having customers jump through these hoops, why not release corrected template files?