@Tech_Fiend: there are new ADMX files for Server 2012, see the detailed list above of the new ADMX files. There is no separate download, which is why this blog post exists.

@Francois: I work for Microsoft Support helping customers with Premier Support. And, yes, copying files from winsxs is just as valid as coping from System32. Note that system32 actually has no files in it, it only has links to files in winsxs. See here for a good explanation: blogs.msdn.com/.../disk-space.aspx

@John: So far I've seen problems with editing the 2012/Windows 8 Name Resolution Policies on a 2008 R2 machine. The golden rule of management is always use the latest OS to manage clients where possible. Some of the RSAT tools in Windows 8 aren't backwards compatible with 2008 R2, so a mix is sometimes required.

@ianc3: You're welcome. Blogs are not support statements and I don't work for the Product Group. Blogs are just helpful "how-to's". In the blog post I wrote for upgrading ADMX files from Vista to Win 7, I just recommended copying them from the PolicyDefinitions folders on client and server OSes where all roles and features have been installed. Copying the files from the directory where all the ADMX files exist is a better way to do it. And I could have also left it at saying "just copy the files from winsxs", but added a short list of simple commands as a way of explaining what is going on. The script should not be used verbatim, they are samples (for example, the script doesn't take into account the versioning which happens in CBS). And until a downloadable set of all ADMX files is released, if it will be released, this is the easiest way. If anyone has any better methods, they are more than welcome to share them here.

@Renan Blanco: See my comment from 19 Nov 2012:

"Note that down-level GPMC, gpedit.msc consoles may not understand the settings defined in these files. Therefore you should only edit the GPOs from Windows 8 or Windows Server 2012 once you do this."

Are you editing on a Win8/2012 computer?

It looks like you need that to work with the updated ADMX for VolumeEncryption. The line that the error is complaining about relates to building a new definition of a computer which has Win8, but is not ARM based. This definition could be invalid on a Win7/R2 computer:

 <supportedOn>  

   <definitions>

     <!-- We must make our own definition for Windows 8 without ARM -->  

     <definition name="SUPPORTED_Windows8NoARM" displayName="$(string.SUPPORTED_Windows8NoARM)" />  

   </definitions>

 </supportedOn>