Windows 10 on the Essentials/SBS platforms

Be aware that at this time Windows 10 will need a connector update in order to connect to/be backed up by Essentials 2012 r2

I have Windows 10 installed behind SBS 2011 and there’s a few tweaks that need to be done that aren’t listed there

1.  Windows 10 RDP group policy

The default Group policy rule on the server allowing RDP/RWA access needs to have an additional rule set to work with Windows 10 (also this is needed for 8.1 as well).

Instead of merely having a firewall rule for RDP, you need a firewall rule for RDP- user mode both the TCP-in rule and the UDP-in rule.


2.  Don’t want your Windows 10 to list like they are Vista machines on SBS 2011’s WSUS?  Then follow Robert’s post:

WSUS already has Windows 10 categories up there ready and waiting for you.

As far as where to get media/how to get media, be aware that behind a domain the Windows 10 reservation icon thing is blocked.  But not to worry you don’t NEED it.  Just manually go to Microsoft update after 7/29 to pull it down or look for more info on means to get it after 7/29.

If you want to TOTALLY block the ability for folks to manually install it from MU

How to manage Windows 10 notification and upgrade options:
To configure this Group Policy Object by using Group Policy, the following conditions apply:

  • The appropriate update must be installed.
  • You must use the updated WindowsUpdate.admx file by copying the file from the editing policy location.
Computer Configuration

To block the upgrade by using Computer Configuration, follow these steps:

  1. Click Computer Configuration.
  2. Click Policies.
  3. Click Administrative Templates.
  4. Click Windows Components.
  5. Click Windows Update.
  6. Double-click Turn off the upgrade to the latest version of Windows through Windows Update.
  7. Click Enable.

Policy path: Computer Configuration / Administrative Templates / Windows Components / Windows Update Policy
Setting: Turn off the upgrade to the latest version of Windows through Windows Update

Windows registry

Important Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

To suppress this offer through the registry, set the following registry value:

Subkey: HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
DWORD value: DisableOSUpgrade = 1

And finally

Single number with 8 digits error code received early on in the process:

Suggests that it’s a Windows update issue.  (Example 0x800700)

Troubleshoot with KB956702

Common root causes:

WU components not functioning properly

Internet connection issue



Two part error number:

Example:  0xc1900101 – 0x2000c and 0xc1900101 – 0x30018

The first part tells you what happened, the second part tells you where.

If the second code starts with 1 or 2 the error occurred during the Downlevel or WinPE/Safe OS setup phases.

If the second code starts with 3 or 4, the error occurred during the first or second boot.


Code 1 or 2:

Check compatibility of the PC with the manufacturer

Remove security and system utility software

Check integrity of download of ISO and recreate if necessary

Common root causes:

System partition out of space

Damaged installation source files

Incompatible security or utility software

Firmware compatibility or security setting issue

Non standard boot configuration


Code 3 or 4:

Errors in this section are difficult to diagnose to a root cause particularly when they end with 17 or 18.  These are often driver errors.  Issues in this category may be caused by other software or hardware issues.

Disconnect all non-essential hardware

Update drivers for remaining hardware

Install all available Windows updates

Common root causes:

Incompatible device or driver

Incompatible security or utility software

Issue with the user profiles during migration of data


More resources:

How to: Troubleshoot common Setup and Stop Errors during Windows – Microsoft Community: Windows 10 system requirements:

  • Processor: 1 gigahertz (GHz) or faster
  • RAM: 1 gigabyte (GB) (32-bit) or 2 GB (64-bit)
  • Free hard disk space: 16 GB
  • Graphics card: Microsoft DirectX 9 graphics device with WDDM driver
  • A Microsoft account and Internet access

Looking for a hosted Exchange that’s ready to rock and roll?

Vlad Mazek – Vladville Blog » Blog Archive » And now something a little different:

Faster than even Microsoft – the first Exchange plug in is ready to go.

Check it out!

Office 365–the elephant the partners will have to deal with

Bring up the topic of Office 365 to partners and you get the elephant in the room problem.  Partners don’t want to sell Office 365 because of it’s low margins, of the low amount you get back per seat and the biggie – the elephant – the fact that they don’t bill the customer – Microsoft does. So Microsoft gets the revenue first and later on cuts a check to the partner.  Yet when that cloud goes down or there are issues – guess who they call – the partner.  So they’d rather sell a hosted Exchange product that is more revenue stream and more importantly control and support.

The big thing in my view is not so much the issue of billing – which is a biggie in and of itself – but that of support.   If you go with the recommended Small Business bundle your support is not at the end of a phone call but in a forum.  Not a good SLA for you the partner.

Then I’d highly highly recommend that you sign up for the cloud essentials and kick the tires here.  You realize pretty quickly that there are things that you may be used to in premises that is just not there yet in the hosted/multi tenant version.

For example take this image –


Take a look at the things not yet in online that we take for granted in premise Exchange (and apologies for the grainy color but I snipped it from a Teched video this morning).  Outlook 2003 that can be done with Exchange 2010 isn’t supported with Exchange online.  Public folders.  A biggie.  Server side code.

Get the idea that you’ll still be needed after everything moves to the cloud?  Not to mention you’ll want to think in terms of building offline backups.  Don’t assume that just because the marketing folks say the cloud doesn’t have issue that it won’t have issues.  It will.  Plan on it.  When you are all premise, you build backup solutions taking the data offsite.  Now that you are looking to cloud solutions, plan on building backups that move the backup of the data onsite. 

So be prepared when looking at Exchange online and compare the things you know how to do in premise and you may have to come up with other solutions or third party solutions in the cloud.

Looking for email migration resources?

E-Mail Migration Overview:

Check out that link.

May be unable to modify some users

May be unable to modify some users and users may disappear from the SBS Essentials Dashboard:

So what’s the guidance for putting Hosted exchange with SBS-Essentials

Right now the SBS-Essentials product is what I call the awkward state.  While the bits are out on technet, the beta for Office 365 is not public, and there’s no official guidance for getting it to work with BPOS other than setting everything up manually.

Once Office 365 RTMs later on this year there will be more official guidance but for now, your best bet is to just set the pieces up manually as if it was a standalone BPOS setup.

How to Sell SBS 2011 to Customers with SBS 2003 or Earlier

How to Sell SBS 2011 to Customers with SBS 2003 or Earlier

How to Respond to Customer Inquiries About Windows SBS 2011 Standard or Essentials Edition

How to Respond to Customer Inquiries About Windows SBS 2011 Standard or Essentials Edition

How to Sell SBS 2011 Essentials Edition to Companies as a First Server

How to Sell SBS 2011 Essentials Edition to Companies as a First Server

How to Upsell Windows SBS 2011 When a Customer Inquires About Windows 7 Professional

How to Upsell Windows SBS 2011 When a Customer Inquires About Windows 7 Professional