Crack the ADMX file and look at the registry values they set. They are probably different values and thus not really mutually exclusive, they just aren't both presented in the ADMXs at the same time. Probably a short-sighted decision by whomever created the Win10 ADMX but there's no reason you can't edit the same GPO using two different ADMX files.
J From: [email protected] [mailto:[email protected]] On Behalf Of Mote, Todd Sent: Tuesday, September 15, 2015 9:14 AM To: [email protected] Subject: [mssms] OT: A little: windows 10 windowsupdate.admx Not really CM related I know, but there are some knowledgeable folks here about all things MS so I thought I'd float this by you all too. I sent this to patchmanagement.org a little bit ago too. So, I'm looking into copying all the Windows 10 group policy admx's to our domain central store and found this: On the left is the Windows 10 windowsupdate local policy from a windows 10 machine, on the right is the current windowsupdate policy from my central store. Notice the descriptions for "defer upgrade" and "turn off the upgrade to the latest version of windows through windows update". The new one requires "At least Windows 10...", and the old one requires "Windows 7 SP1, Windows 8.1 Update". If I replace this admx in my domain central store, it is no longer possible to turn off the upgrade via policy for Windows 7 and 8? And if I replace windowsupdate.admx with the old one so it can, can Windows 10 no longer defer an upgrade? Should these really be mutually exclusive like this? We're going to have a mix of 7, 8, and 10 for a long while... All other policies appear to be the same. [cid:[email protected]] Todd Todd Mote, MCP, MCSA+Messaging, MCSE | [email protected]<mailto:[email protected]> Enterprise Systems Management | Information Technology Services | The University of Texas at Austin
