Small Business Server 2011 Standard–Windows 10

August 17, 2015 by 32 Comments

sbsstdUpdated 15/08/2016

Following a comment below, i revisited and noticed an error in my syntax. Confirming this does indeed work on 10586 (1511) and 14393 (1607)

I recently did a series of posts about Essentials Servers and Windows 10.

I am just picking up on one issue with SBS Standard (2011) where you have to manually edit a file relating to the /Connect process.

Normally this is straight forward, and the instructions on the MS blog post are fine, except it gave me a major OCD headache.

The file in question, is this:

C:\Program Files\Windows Small Business Server\Bin\WebApp\ClientDeployment\packageFiles\supportedOS.xml

To allow Windows 10 to join using the /Connect page you need to add it as a supported OS.

The post from Microsoft even helpfully lets you copy and paste the lines directly. But look at it, JUST LOOK AT IT!

OCD Alert

BackwardsIt’s backwards.

Honestly, who did this?!?

Granted, it works, but really?

This seriously upset me, and I’m sure all of those who demand order in the galaxy will feel the same way.

So here is the ‘Correct’ syntax to add to your supportedOS.xml file.

<OS id="9" Name="Windows 10, AMD64" Major="10" Minor="0" Build="10240" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="9"/>
<OS id="10" Name="Windows 10, x86" Major="10" Minor="0" Build="10240" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="0"/>

 


Breathe

And….. breathe.

For newer builds:

Windows 10 – 10586 (1511), 14393 (1607)

<OS id="11" Name="Windows 10, AMD64" Major="10" Minor="0" Build="10586" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="9"/>
<OS id="12" Name="Windows 10, x86" Major="10" Minor="0" Build="10586" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="0"/>
<OS id="13" Name="Windows 10, AMD64" Major="10" Minor="0" Build="14393" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="9"/>
<OS id="14" Name="Windows 10, x86" Major="10" Minor="0" Build="14393" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="0"/>

Filed under General, SBS S, Tips & Tricks Tagged with , , ,

About Robert Pearman
Robert Pearman is a UK based IT worker bee. He has been working within the IT Industry for what feels like forever. Robert likes Piña colada and getting caught in the rain, he also enjoys writing about Technology like PowerShell or System Automation but not as much as he used to. If you're in trouble, and you can find him, maybe you can ask him a question.

32 Responses to Small Business Server 2011 Standard–Windows 10

  1. Leen Kleijwegt says:
    September 6, 2015 at 10:26 am

    Thank you!! (How to declare a product dead… SBS)

    Reply
  2. James Bravo says:
    November 10, 2015 at 6:29 am

    Hi Robert,
    This is the solution I’ve been looking for. Thank for posting it.

    I’m adding a Win 10 Pro client to a SBS 2011 Standard domain.

    If you would be so kind, how do I modify the SUPPORTEDOS.XML file?
    I can’t get it to work.

    Thank you

    Reply
  3. James Bravo says:
    November 10, 2015 at 7:32 am

    Hi Robert,

    Great post. I’ve been looking for this solution.
    I’m trying to set up a Windows 10 Pro client on a SBS 2011 Standard domain.
    How can I edit the XML file?

    Thank you

    Reply
  4. Donny Smith says:
    November 13, 2015 at 6:21 pm

    Great solution. I’m looking to fix this problem, but on Windows Server 2008. Does anyone think they could help me out?

    Reply
  5. Jeremy says:
    May 13, 2016 at 2:22 pm

    What about later builds of Windows 10, such as 1511? How does the xml code get changed for these. I tried changing 10240 to 1511 and/or 10586, and this did not work. Any insight into this would be awesome. Most of the blog posts I have seen point here and to another page.

    Reply
  6. systrar3 says:
    May 25, 2016 at 6:59 pm

    What are the symptoms that the connector is not working? Tried this yesterday and the connector stopped responding at the point of adding users to the computer, the app log indicated an issue with .Net 4.0. Just want to make sure there isn’t another issue. I guess if it doesn’t work, it doesn’t work.

    Reply
  7. systrar3 says:
    May 28, 2016 at 11:50 pm

    SBS Standard 2011

    Reply
  8. David Gilroy says:
    June 1, 2016 at 10:41 am

    I had no need to alter any files I just joined 4 HP refurb win 10 Pro machines to an existing Domain I did install .Net 3.5 and 4.6 before running the connect wizard as I have had a lot of bad experiences with trying to add .Net 3.5 after the domain join .
    Just wondering IF there is a gotya I haven’t came across yet with not editing the XML ?

    Reply
  9. Bert van Raalte says:
    August 13, 2016 at 10:09 pm

    Found a way to work around the windows 10 1511 problem.
    add 2 more lines to the supportedos.xml file

    This worked like a charm for me for both sbs 2008 and sbs 2011.
    Suppose a simular change will be required for the upcoming aniversery edition.

    Reply
  10. singr07 says:
    August 19, 2016 at 12:14 pm

    Hi Could you please advice add 2 lines where? I have added all 6 lines mentioned above and it still don’t work?

    Reply
  11. Alan says:
    September 28, 2016 at 4:25 am

    Thanks for this – was tearing my hair out! (What there is of it!)

    Reply
  12. Nicola says:
    October 18, 2016 at 9:29 am

    Thanks for this, i’ve tried this on 2 different windows 10 pro machines connecting to domain for SBS 2011 Standard Service Pack 1 machines and updated both lines to latest build. Build 14393 is the machines.

    Through the sbs console i got Task > Connect computers to network and put on media. When opening supportedos.xml it isn’t showing the changes.

    Tried connect and launcher and both are saying computer doens’t meet the requirements. Navigating to https://servername/connect i get certificate error and click continue and get 404 File or Directory not found.

    Manually added machine to the domain without issues however unable to login via domain (incorrect username and password) and no it’s not the incorrect passwords :)

    Pulling hair out now….Help….anyone??

    Reply
    • David Gilroy says:
      October 18, 2016 at 2:37 pm

      re unable to login with correct password : reboot again and disconnect from the network and then try login I just added a new desktop and had to do this

      Reply
  13. Nivola says:
    October 18, 2016 at 9:54 am

    This isn’t working for me on SBS 2011 Standard sP1. Latest build of windows 10. Help?

    Reply
  14. mcbsys says:
    January 18, 2018 at 9:04 pm

    Needs more lines for 1703 and 1709. But perhaps most important, and what stumped me for a while, is that http://connect doesn’t work under Internet Explorer–even after adding the required lines, it keeps saying your OS is not supported.

    Fortunately, running http://connect from Edge works fine. Chrome seems good too. See the 12/9/2016 post here: https://social.technet.microsoft.com/Forums/en-US/c64e36b1-71dc-4326-a2df-50cf00cd48b5

    Reply

Leave a reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.