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. A new updating model
  2. Just a reminder – if you adding Windows 10
  3. Windows 10 anniversary update and Essentials R2
  4. Windows 10 anniversary update and SMB server impact
  5. Tilting at windmills again
  6. More Recent Articles
  7. Search Small Business Susan
  8. Prior Mailing Archive

A new updating model

Further simplifying servicing models for Windows 7 and Windows 8.1

Get ready for a big change to how we install updates for Windows 7 and 8.1.  If you receive updates via windows update, your 7 and 8.1 updates are going to a cumulative 10 model.

If you are managing updates with WSUS and/or SCCM you’ll see one security update bundle and one non security update bundle each month.

    

Just a reminder – if you adding Windows 10

Windows 10 anniversary update and Essentials R2

Steps to take (assuming you haven’t upgraded to Anniversary edition yet)

Step one on your Essentials R2 machine:  Ensure https://support.microsoft.com/en-us/kb/3172614is installed.  It’s the July non security update rollup.

On your clients, uninstall the OLD connector (it will be listed as a windows update) and then go to http://servername/connect and manually reinstall/reconnect your workstations to the server.  This will install the NEW connector as a program not as an update.

Install the anniversary update.  You may (you will) find that the newly revised connector appears to be gone.  It really isn’t it’s just an issue with the notification area cache.  Thanks to Mike (The Office Maven) we have a fix:

EssentialsTrayApp.exe doesn’t work after KB3172614:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/2c21527e-4f91-4513-98d3-6db8d3f83a9b/essentialstrayappexe-doesnt-work-after-kb3172614?forum=winserveressentials

Hi All,

Apparently the “Notification Area Icons” cache becomes (somewhat???) corrupted when installing the Windows 10 Anniversary Update (1607), and this in turn is causing EssentialsTrayApp.exe to error out when it attempts to reset the Essentials notification area icon (as is indicated by the errors that are shown in the EssentialsTrayApp.<SID>.log file).

In order to correct the issue, you simply need to reset the Notification Area Icons cache for each user who is missing the Essentials notification area icon on their Windows 10 client computer. I have tested this on three separate Windows 10 client computers (Pro and Home), and it has corrected the problem on all of them.

To reset the Notification Area Icon cache, simply download the “Reset_Notification_Area_Icons_Cache.bat” file from the following web page (props go out to Shawn Brink and the Windows Ten Fourms for their excellent tutorial!):

How to Reset Notification Area Icons in Windows 10

After the client computer has restarted, you will find the Essentials notification area icon has returned to the notification area of your Windows 10 client computer.

I hope this helps everyone out that is currently experiencing the problem on their Windows 10 client computers.

— MIKE (The Office Maven)

Now here’s step two:

Vote

Hi All,

While you’re at it you might also want to fix the “Alert Evaluations” task in the Task Scheduler as it is also messed up by the new client connector that gets installed by KB3172614.

To do so, open the Task Scheduler (on the client computer), and go to:

Task Scheduler Library -> Microsoft -> Windows -> Windows Server Essentials

Double-click on the “Alert Evaluations” task and click on the “Actions” tab in the Properties window that appears.

Double-click on the “Start a program” action and change the “Program/script” value to:

C:\Program Files\Windows Server\Bin\RunTask.exe

And change the “Add arguments (optional)” value to:

/asm:”C:\Program Files\Windows Server\Bin\AlertFramework.dll” /class:Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.HealthScheduledTask /method:EvaluateAlertsByTriggerTaskAction /task:”Alert Evaluations”

NOTE: Adjujst the location of your client computer’s “C:\Program Files” folder as required (for locals other than English, etc.).

Click OK, answer Yes to the confirmation message that appears, and then click OK again to close the Properties window.

After that, you can manually run the task to make sure that it now works properly (note that you may need to hit Refresh in order to see the updated run result).

— MIKE (The Office Maven)

Susan note:  I realize that all of this is extremely confusing and requires way too many manual steps.  I too wish that Microsoft could release an update that didn’t require a manual uninstall and reinstall.  I find this discouraging (to say the least).

    

Windows 10 anniversary update and SMB server impact

The R2 problem is being investigated at this time – will keep you posted

Issues seen with:

Essentials R2:

I think the old connector isn’t being uninstalled and we’re getting two connectors installed.  I think.  Under investigation.

https://social.technet.microsoft.com/Forums/windowsserver/en-US/36a1e1bc-5948-4058-9372-07e9e96a9fa4/windows-10-clients-and-server-2012r2-essentials?forum=winserveressentials

Bottom line the symptom if it was installed before, you went through the AU release, the connector is lost.  You go to reinstall the connector and it won’t find the server.

See the resolution here:

Windows 10 anniversary update and Essentials R2

SBS 2008:

https://social.technet.microsoft.com/Forums/en-US/1932302f-b31c-4c8b-8dec-d0554852800b/windows-10-version-1607-build-1439310-rww-error-50331656?forum=smallbusinessserver

RWW doesn’t work.  The error points to a mismatch in RDP protocol.  In the past the only way I’ve seen to fix that is to roll back a RDP update which obviously we can’t do in Windows 10.

Bypassing RWW with Rdgateway works.  Given that SBS 2008 is no longer under a support window….

Bottom line use the bypass until we can figure out a workaround.

Working:

SBS 2011 Standard

RWA still works

Unknown:

SBS 2011 Essentials:

No reports yet

    

Tilting at windmills again

https://technet.microsoft.com/en-us/itpro/windows/manage/group-policies-for-enterprise-and-education-editions

If you look at that list it pretty much makes it that group policy doesn’t allow you to block consumerish apps or to customize the start menu.

And be aware that if you go in the group policy some of these aren’t documented inside the group policy editor or listed as needing a certain version in the spreadsheet.

Yes, this change.org is tilting at windmills, but one should at least try.

 

    

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