Windows 10 and SBS/Essentials 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

http://blogs.technet.com/b/sbs/archive/2015/07/23/client-connector-availability-with-windows-home-server-small-business-server-and-windows-server-essentials-for-supported-client-os.aspx

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.

rdoub

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

http://titlerequired.com/2015/07/22/windows-10-on-wsus-shows-as-windows-vista/

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:
https://support.microsoft.com/en-us/kb/3080351
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

https://support.microsoft.com/en-us/kb/956702

Common root causes:

WU components not functioning properly

Internet connection issue

Malware

 

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:

http://answers.microsoft.com/en-us/insider/wiki/insider_wintp-insider_install/how-to-troubleshoot-common-setup-and-stop-errors/324d5a5f-d658-456c-bb82-b1201f735683 Windows 10 system requirements: http://www.zdnet.com/article/windows-10-will-your-pc-run-it/

  • 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


3 Thoughts on “Windows 10 and SBS/Essentials platforms

  1. Simon Weel on July 28, 2015 at 1:44 am said:

    As for the firewall tweak – on my SBS 2011 Standard machine there’s no predefined Rule Type ‘Remote Desktop – User Mode’? How to fix this?

  2. Andy on July 28, 2015 at 3:04 am said:

    Thanks for this. Very useful. I was wondering if you could expand on point 1 (the RDP policy for Win 10). Do you have step by step instructions for this? At the moment, my GPM program doesn’t show a “Windows SBS Client – Windows 10” policy. I could create one with that name, but what ties it to that version of Windows? It’s not just on string match in the name is it? Anyway, any additional instrucions would be great!

    Also, do you think it is safe to do this now – or do you think after the Win10 release, microsoft will patch SBS to have a GP for Win10?

    Sorry if these are basic questions!

  3. Dear Susan,

    Thanks for this info.
    Do you also have info on a SBS 2008 integration with Win10?
    – can clients be upgraded without issues
    – will there be a connector update
    – will there be an SBS update (like they did for WIn8)

    Greets,

    Mike

Post Navigation