We help IT Professionals succeed at work.

Adding Win Server 2016 to SBS2011 domain

Barry Brown
Barry Brown asked
I added a new 2016 server to an SBS2011 domain.  In the SBS Standard Console the 2016 server is shown listed under Client Computers and not under Servers.  Is this a problem?  Also, on the 2016 server in Server Manager > Servers the SBS2011 does not show up at all.  What have I missed?
Watch Question

Technology and Business Process Advisor
Most Valuable Expert 2013
2016 is 6 years newer than 2008R2 which is what SBS is built on.  Microsoft's support cycle is 5 years in mainstream support, 5 years in maintenance (essentially just security and required compatibility patches).  I wouldn't expect either of these two issues to be resolved, nor would I worry about them.  Did you use the connect computer wizard to join the server (That I wouldn't have done) - just make sure it's not in the same OU as the workstation computers or the same group policies will likely affect it.

Keep in mind, you need 2016 user CALs for all your users that use any service on the 2016 server.


I joined the 2016 server to the domain using the network settings in 2016 server and that seemed to work.  I did notice that the sbs client agent  is installed on the 2016.  

Can I move the 2016 into the SBS servers OU or do I need to create a new one?  

Also found that Windows Update is not working.  I changed the registry key HKLM\SOFTWARE\Policies\Microsoft\WindowsUpdate\AU\UseWUServer from 1 to 0 but still not getting updates.
Lee W, MVPTechnology and Business Process Advisor
Most Valuable Expert 2013

I don't have any SBS 2011 servers I actively manage any longer.  At one time I knew the product well.  But it's old now and Microsoft has in essence given up on it.  I would manage the server indepdently of SBS.  It can be a member of the domain, joined, and users can access it, but when it comes to policies specific to it or Windows Updates, I would not rely on SBS.

OUs are just organizational points that have Group Policies apply.  Frankly, I would probably create a separate OU for it and apply group policies you wanted it to fall under there.
I assume you are attempting to replace the old server with a new server, the server will only be added to the servers automatically if its a domain controller. If my assumption is right, you should just scrap what you have attempted and remove the new 2016 off the domain and then install and configure the ADDS role on the new 2016 server which will join to the domain and promote it as the second domain controller. when you are ready just move the fsmo roles.


For now we are keeping SBS as we need Exchange.  Hope to set up another 2016 with Exchange as a VM, at which time, SBS will be bid farewell.  Could be 3 to 6 months before that happens.
PberSolutions Architect

No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

-- Lee W MVP (https:#a42355544)
-- ExchangeKB (https:#a42355797)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

Experts-Exchange Cleanup Volunteer