Click here to read this mailing online.

Your email updates, powered by FeedBlitz

 
Here is a sample subscription for you. Click here to start your FREE subscription


"Small Business Susan" - 5 new articles

  1. Essentials connector update for Windows 10
  2. Windows 10 trick for updates
  3. Fixing up group policies
  4. …well not so fast
  5. After applying MS16-072
  6. More Recent Articles
  7. Search Small Business Susan
  8. Prior Mailing Archive

Essentials connector update for Windows 10

Windows 8.1 and Windows Server 2012 R2 update history:
https://support.microsoft.com/en-us/help/24717/windows-8-1-windows-server-2012-r2-update-history

Updated the inbox component in Windows Server 2012 R2 Essentials to use
the new client connector, so that the inbox component won’t get
uninstalled during Windows 10 upgrades.

July 2016 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2:
https://support.microsoft.com/en-us/kb/3172614

It’s in that update rollup just out today.

And may I say… finally!

Note that the fix gets installed ON THE SERVER, not on the clients/Windows 10.

    

Windows 10 trick for updates

In the zeal to get windows updating… or rather rebooting … more palatable I think Microsoft swung a little too far away from notifications.  I’m running 1511 and so many times odd things start occurring and I realize that updates have been installed, but the system hasn’t been rebooted.

I personally feel that you need to reboot after installing updates so I’m going to run this Windows 10 testbed that I have here with the “metered” connection trick.  Lifehacker has blogged this long ago trick where you make the network connection think it’s on a metered connection which then holds back the patches.  Windows 10 has no “download but do not install” in the gui.

I know when windows updates come out, but I don’t like the side effects one gets when updates have been installed and the system hasn’t yet been rebooted.

    

Fixing up group policies

When Group Policies Suddenly Stop Working

My apologies, I didn’t blog my follow up to the issues introduced by MS16-072.  Wayne blogged a solution over on the thirdtier blog site that you can do to fix up your group policies and get them back working again.  I’m not a fan of uninstalling security updates and leaving them off, rather find the solution to fix the underlying problem.

    

…well not so fast

Group Policy not working on SBS 2008, SBS 2011 and Windows Server 2008/2008R2 since MS16-072

Sigh.  I’ve seen this too.  Okay so my workaround isn’t so easy.  Hang tight.

    

After applying MS16-072

http://www.gpanswers.com/never-a-dull-moment-with-group-policy-or-what-to-do-about-ms16-072/

On SBS 2011 and 2008 certain preconfigured group policies provided by Microsoft no longer work.

Log into the server, and drill down into the event logs, and specifically the one for Group policy.   Look for Event 5313 and it will list the Group policies no longer working.

failsurue

The three in particular that no longer work are:

Update Services Client Computers Policy

Windows SBS User Policy

Windows SBS CSE Policy

To fix this log into the Group policy console and in the security filtering section add the Domain Computers.

Literally click on add and type in domain computers in the window and click ok.

oakdy

Do the same for each group policy indicating that it failed to process.

 

 

    

More Recent Articles


You Might Like

Click here to safely unsubscribe from "Small Business Susan."
Click here to view mailing archives, here to change your preferences, or here to subscribePrivacy