{"id":952,"date":"2016-07-07T09:48:51","date_gmt":"2016-07-07T07:48:51","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=952"},"modified":"2016-07-07T09:48:51","modified_gmt":"2016-07-07T07:48:51","slug":"microsoft-explains-the-kb3159398-gpo-problem","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2016\/07\/07\/microsoft-explains-the-kb3159398-gpo-problem\/","title":{"rendered":"Microsoft explains the KB3159398 GPO problem"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2013\/03\/winb.jpg\" width=\"58\" align=\"left\" height=\"58\">Microsoft's update KB3159398, released on patch day June 14, 2016, is causing serious problems in Windows Group Policy. Now Microsoft explains what's happened. <\/p>\n<p><!--more--><\/p>\n<p>I've addressed this issue in blog post <a href=\"https:\/\/borncity.com\/win\/2016\/06\/16\/update-kb3159398-breaks-group-policy-in-windows\/\">Update KB3159398 breaks Group Policy in Windows<\/a>. Some users are explaining already, what's happened (see <a href=\"https:\/\/sdmsoftware.com\/group-policy-blog\/bugs\/new-group-policy-patch-ms16-072-breaks-gp-processing-behavior\/\" target=\"_blank\">New Group Policy Patch MS16-072\u2013 \"Breaks\" GP Processing Behavior<\/a>). Finally, Microsoft has also addressed this issue in a Technet blog post <a href=\"https:\/\/blogs.technet.microsoft.com\/askpfeplat\/2016\/07\/05\/who-broke-my-user-gpos\/\" target=\"_blank\">Who broke my user GPOs?<\/a> on June 5, 2016.<\/p>\n<blockquote>\n<p><strong>What did I miss.<\/strong><\/p>\n<p>We released new security patches for all currently supported Operating Systems. Among those patches was this one: <a href=\"https:\/\/support.microsoft.com\/en-us\/kb\/3163622\" target=\"_blank\">MS 16-072<\/a>, which is also referenced as <a href=\"https:\/\/support.microsoft.com\/en-us\/kb\/3163622\" target=\"_blank\">KB 3163622<\/a>. OS Specific articles are released as 3159398, 3163017, 3163018, and 3163016.  <\/p>\n<p><a href=\"http:\/\/support.microsoft.com\/kb\/3159398\" target=\"_blank\">KB 3159398<\/a> \u2013 Vista, 2008, 7, 2008 R2, 2012, 8.1, 2012 R2<br \/><a href=\"http:\/\/support.microsoft.com\/kb\/3163017\" target=\"_blank\">KB 3163017<\/a> \u2013 Windows 10 TH1<br \/><a href=\"http:\/\/support.microsoft.com\/kb\/3163018\" target=\"_blank\">KB 3163018<\/a> \u2013 Windows 10 TH2 and Server 2016 TP4<br \/><a href=\"https:\/\/support.microsoft.com\/en-us\/kb\/3163016\" target=\"_blank\">KB 3163016<\/a> \u2013 Server 2016 TP5  <\/p>\n<p>After applying the appropriate patch to your systems, User group policies are retrieved from SYSVOL differently than before. Prior to the update, domain joined computers used the <strong>user's security<\/strong> context to make the connection and retrieve the policies. After the update is applied, domain joined computers will now retrieve all policies using the <strong>computer security<\/strong> context. The users that get the policy is still controlled by the policy scope just like before. The only change is the computer is getting the policy for the user.<\/p>\n<\/blockquote>\n<p>Further details and explanations may read in the article <a href=\"https:\/\/blogs.technet.microsoft.com\/askpfeplat\/2016\/07\/05\/who-broke-my-user-gpos\/\" target=\"_blank\">Who broke my user GPOs?<\/a>. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>Microsoft's update KB3159398, released on patch day June 14, 2016, is causing serious problems in Windows Group Policy. Now Microsoft explains what's happened.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22,2],"tags":[270,269,194],"class_list":["post-952","post","type-post","status-publish","format-standard","hentry","category-update","category-windows","tag-gpo-problem","tag-kb3159398","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/952","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=952"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/952\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=952"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=952"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=952"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}