Starting to move to 1703

On June 25, 2017, in news, by susan

At the office I recently purchased two Windows 10 machines and they both came with 1703.  While the rest in the fleet are on 1607, I’m glad that this is pushing me to ensure that we’re ready for 1703.  There are some side effects I’m tracking that I’m hoping are fixed soon (see my known issues post) but so far I’m not finding major show stoppers like the new file folder/indexing bug we hit with 1607.

Coming up in the NEXT major release, Microsoft is removing SMBv1 (see this link)  on clean install versions to proactively prevent more ransomware issues like the recent ones that infected machines using SMBv1 vulnerabilities.

It probably is wise now to start an investigation into your clients networks on how much they depend on SMBv1.  It won’t disable smbv1 on existing updated machines, but will on clean/new installed Windows 10 in the future.



Looking for migration advice?

On May 15, 2017, in news, by susan

There’s a couple of sources you can look to:

Mariette’s site at

Robert Pearman’s guide to moving from SBS 2011 to server 2016 –


What about the media pack?

On May 15, 2017, in news, by susan

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





Dual rebooting after this week’s update

On April 12, 2017, in news, by susan

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.


What’s the support lifecycle for SBS 2008?

On March 1, 2017, in news, by susan

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 4/29/2009 4/10/2012 4/11/2017

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

What’s the support lifecycle for…

On March 1, 2017, in news, by susan

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?

On February 28, 2017, in news, by susan

As noted in these threads…..

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


Vote as helpful


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 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 –

Also here:

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

On January 18, 2017, in news, by susan

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.


De-consumerizing Windows 10 Pro

On January 9, 2017, in news, by susan

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

Step one:

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  –

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.