Got a question the other day asking about the media pack availability for Server 2016 essentials. To be honest with you I had totally forgotten about that.
In talking to the folks (Cliff in particular) that still run media servers at home they recommended installing Plex or Kodi
If you are seeing your machines reboot twice after this week’s updates, you aren’t alone.
It appears to be due to an RDP patch that is included inside the rollups.
Bottom line plan on it taking a little longer to reboot this month.
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.
|Windows Vista Service Pack 2
|Microsoft Exchange Server 2007 Service Pack 3
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
As noted in these threads…..
There’s a workaround to use until such time as the final fix is deployed.
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=”PasswordSyncOtherFailure” …
4. Restart WseEmailSvc windows service.
Please let me know whether it helps nor not.
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.
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.
So here’s many of the scripts and links I’ve accumulated and used to “de-consumerize” Windows 10 at the office:
Removing the unwanted apps in Windows 10
Download this zip file taken from this blog site.
Extract the file, launch PowerShell.
Enter the following command:
PowerShell.exe –ExecutionPolicy Bypass –File .\removeapps.ps1
While I can’t turn off the consumer experience via group policy in windows 10 — what I can do is shoot out this same info to the local group policy or registry and doing so removes the other remaining inbox apps and stops the “Microsoft recommends” consumer apps – http://www.ghacks.net/2016/03/02/turn-off-microsoft-consumer-experience/
More ideas here: Windows 10 Decrapifier – Script Center – Spiceworks:
I then uninstall one drive
Disable or Uninstall OneDrive Completely in Windows 10 – Tech Journey:
Once I do all of this, the system should retain these settings when the next Creator’s update gets released.
So to remind myself of the next time I’m rolling out Windows 10… here are some tips to fix annoyances:
Can’t enable numlock?
- Change the value of …ControlPanel/Keyboard/InitialKeyboardIndicators to 2147483650 for ALL USERS not only for .Default (my current user was 2).
- Then SHUTDOWN computer.
- Turn on computer and wait for login screen (NumLock is still off).
- Enable NUMLOCK
- SHUTDOWN computer.
- Turn on computer.
NumLock disabled after booting up Windows 10? from Windows10
Merely enabling it in the bios did NOTHING. I had to do this funky trick of shutting down and registry edits to get it to ‘take’.
Windows 10 1607 [Anniversary release]