locked
Windows 10 Servicing and WSUS on Windows 2016 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Everything I've seen says that to perform Windows 10 servicing via SCCM 2012, my WSUS server must be on Windows 2012 R2. Does that mean 2012 R2 only? Or 2012 R2 or newer?

    I've got a 2016 server hosting my WSUS service, and I'm having problems.  If I have to downgrade my server, so be it, but I'd rather not if this configuration is supported.

    Monday, April 10, 2017 6:52 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Task Sequences are generally considered much better and are preferred by most for servicing anyway because they offer pre and post tasks as well as pre-req checking/validation and better control of the process in general.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, April 11, 2017 3:10 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    It is supported: https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/supported-operating-systems-for-site-system-servers

    What kind of problems do you have?

    Simon Dettling | msitproblog.com | @SimonDettling

    Please remember to mark the post(s), which answered your question.

    Monday, April 10, 2017 6:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You cannot service Win 10 With ConfigMgr/SCCM 2012 or 2012 R2. You need to be on ConfigMgr Current Branch. WSUS can be on a Server 2012, 2012 R2, or 2016 system. Your site server must also be on the same OS version.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, April 10, 2017 8:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm running SCCM 2012 1610, but my site server is 2012 R2 and my WSUS server is 2016. I have a decision to make. 
    Monday, April 10, 2017 9:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    "SCCM 2012 1610"

    There's no such thing.

    1610 is a version of ConfigMgr/SCCM Current Branch (CB) and has nothing to do with 2012.

    The OS on the site server and the WSUS server must match to be technically supported although it may work.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, April 10, 2017 9:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It is supported: https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/supported-operating-systems-for-site-system-servers

    What kind of problems do you have?

    Simon Dettling | msitproblog.com | @SimonDettling

    Please remember to mark the post(s), which answered your question.


    Overread that you're still on ConfigMgr 2012. What I wrote applied to ConfigMgr current branch, which is also what Jason wrote.

    Simon Dettling | msitproblog.com | @SimonDettling

    Please remember to mark the post(s), which answered your question.

    Tuesday, April 11, 2017 4:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    My mistake.  I AM running SCCM 1610. 

    My Windows 2016 server is both my WSUS server and my SUP.  Is THAT good enough, or does my primary site server need to be 2016 as well?

    Tuesday, April 11, 2017 12:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Please see my comment below.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, April 11, 2017 2:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you, and yuck.  It looks like I have a SCCM backup/restore in my future.  I'll try to postpone it by switching to an OS upgrade task sequence.

    Tuesday, April 11, 2017 3:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Task Sequences are generally considered much better and are preferred by most for servicing anyway because they offer pre and post tasks as well as pre-req checking/validation and better control of the process in general.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, April 11, 2017 3:10 PM