Straight from Niehaus about this update: The new ADMX files define the "Turn off the upgrade to the latest version of Windows through Windows Update" policy. So if you are interested in blocking Windows 10, grab the updated ADMX from the update (or a machine running the update) and set the policy for your domain (which may require copying the ADMX to your sysvol).
We always recommend deploying all updates, especially to the Windows Update agent itself :) And... A machine running an Enterprise SKU won't get the "Get Windows 10" notifications, nor will you be able to manually initiate an optional upgrade. A machine running Windows 10 Pro that is domain-joined or MDM-managed won't receive the "Get Windows 10" notifications, but if they've installed the updates to enable Windows 10 upgrades, they would be able to manually check for it and perform an installation that way. So that's what the policy blocks. If they have admin rights, they would still be able to download media and initiate the upgrade that way; the policy won't block that. There has already been a small uproar about the lack of documentation in this update. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Wednesday, July 08, 2015 7:35 AM To: [email protected] Subject: [mssms] Windows Update Agent Update Updated Hi folks If you are still moving through your deployment cycle of the June WUA Agent to your W7SP1 and W2K8R2SP1 estate just a note that this was updated for the July release http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3065987 Main change is support for Embedded & POSReady SKUs The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
