I would look at the support for Exchange 2007 as a solid indicator as that's what you are probably migrating your email off of. For Exchange 2007, the last support date is April 11, 2017. Finding the same information for Windows server 2008 is nearly ...

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. What’s the support lifecycle for SBS 2008?
  2. What’s the support lifecycle for…
  3. RWA on Essentials 2016 only working for a short time?
  4. Problem creating/renaming a folder on a network share with Win10 Anniversary Update (Error 0x8007003B)
  5. Keep the faith
  6. More Recent Articles

What’s the support lifecycle for SBS 2008?

I would look at the support for Exchange 2007 as a solid indicator as that’s what you are probably migrating your email off of.

For Exchange 2007, the last support date is April 11, 2017.

Finding the same information for Windows server 2008 is nearly horrific.  I had to look at Vista sp2 as the matching desktop OS to get the support date.

https://support.microsoft.com/en-us/lifecycle/search?alpha=Vista

Windows Vista Service Pack 2 4/29/2009 4/10/2012 4/11/2017

https://support.microsoft.com/en-us/lifecycle/search?alpha=Exchange%202007

Microsoft Exchange Server 2007 Service Pack 3 6/7/2010 4/10/2012 4/11/2017
    

What’s the support lifecycle for…

The other day I was asked what’s the support lifecycle for SBS 2011.  Bottom line it’s the support of it’s parts.

So it’s Windows Server 2008 R2 and Exchange 2010 which is supported to 1/14/2020.

Windows Server 2008 R2 Service Pack 1 2/22/2011 1/13/2015 1/14/2020
    

RWA on Essentials 2016 only working for a short time?

As noted in these threads…..

https://social.technet.microsoft.com/Forums/windowsserver/en-US/fc9140e3-9ae7-4ba3-898b-1ec196ab8538/remote-web-access-works-for-about-a-week-at-a-time?forum=ws16essentials

https://social.technet.microsoft.com/Forums/en-US/95098edc-e4f8-478d-ab90-edd717cf1e94/server-essentials-2016-rww-broken?forum=winserveressentials

There’s a workaround to use until such time as the final fix is deployed.

https://social.technet.microsoft.com/Forums/en-US/95098edc-e4f8-478d-ab90-edd717cf1e94/server-essentials-2016-rww-broken?forum=winserveressentials

 

Vote as helpful

1
Vote

Hi All,

This issue might occur when you have O365/AAD enabled on the server. The product team is investigating it, in the mean time, the following workaround might help mitigate this issue:

1. On the server, go to folder %programfiles%\Windows Server\Bin\FeatureDefinitions\Microsoft PwdSync\

2. Make a copy of file Definition.xml for backup

3. Edit the original Definition.xml (if you don’t have permission, copy the file out, edit it and put it back in the folder):

Comment out the following two sections:

<!–

<HealthDefinition Name=”PasswordSyncInvalidPassword”

</HealthDefinition>

<HealthDefinition Name=”PasswordSyncOtherFailure”             …

</HealthDefinition>

–>

4. Restart WseEmailSvc windows service.

Please let me know whether it helps nor not.

Thanks,

 

    

Problem creating/renaming a folder on a network share with Win10 Anniversary Update (Error 0x8007003B)

https://support.microsoft.com/en-us/help/4011347

January 26, 2017—KB 3216755 (OS Build 14393.726)

On the catalog site at this time is an update that those of us in the SMB world will want to get and install on our Windows 10 1607 machines.  It fixes a painful bug that if indexing is enabled on the server, causes naming or renaming a file folder to crash.

The bug can be seen discussed in this forum post – https://social.technet.microsoft.com/Forums/windows/en-US/b72c763e-d029-4e65-a2dc-885a5aabf643/problem-creatingrenaming-a-folder-on-a-network-share-with-win10-anniversary-update-error?forum=win10itpronetworking

Also here:  https://networkdefend.blogspot.com/2016/09/fix-windows-10-error-0x8007003b-when.html

It will be in the normal release soon, but for now we can get that update on impacted machines now, not later.

    

Keep the faith

https://networkdefend.blogspot.com/2016/09/fix-windows-10-error-0x8007003b-when.html

The fix is coming soon.

But man, it’s making me seriously consider that I need to not rely on Windows basic indexing as a network feature going forward.  This has taken much too long to fix.

    

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