http://blogs.technet.com/extreme/archive/2009/04/10/admx-policy-missing-or-blank-bug.aspxWhen you create a policy with a custom ADMX template which uses a registry key outside of the standard 4 recommended locations (below) and open up your group policy editor using gpedit.msc, the policy will not be listed and you will get no error. Theen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.technet.com/extreme/archive/2009/04/10/admx-policy-missing-or-blank-bug.aspx#3225245Sat, 11 Apr 2009 05:27:39 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3225245Ned<p>Any reason why a Group Policy Preference couldn't be used instead? Custom ADMX's should usually be unnecessary (and are kind of the devil).</p>http://blogs.technet.com/extreme/archive/2009/04/10/admx-policy-missing-or-blank-bug.aspx#3225852Mon, 13 Apr 2009 19:38:15 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3225852David Tesar<p>Group policy preferences couldn't be used because they are just that - preferences, not permanent enforced settings. &nbsp;Custom ADMX files are very handy and what is recommended to use if you want to roll out a number of different registry keys to all of your clients. &nbsp;They really are fairly easy to deal once you start working with them and have your group policy infrastructure setup streamlined.</p>