none
SCUP On Windows Server 2016

    Question

  • I am running SCCM CB on Windows Server 2016.  

    When I attempt to install System Center Updates Publisher 2011, the installer stops and prompts to install WSUS 3.0 SP2.  Of course that WSUS 3 install can't be installed as a higher version of WSUS already exists in 2016.

    Is there no support for SCUP on Windows Server 2016?

    Thursday, December 08, 2016 4:54 PM

Answers

  • I already tried this with Server 2016 TP.

    A Workaround is to temporary change the Version String from WSUS in Registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup

    Backup the current value and change it for example to the value from Server 2012 R2 WSUS:

    "VersionString"="6.3.9600.17477"

    After that you should be able to install SCUP. After the Installation you can change the value back.



    • Edited by Michael-CM Thursday, December 08, 2016 6:44 PM
    • Marked as answer by Mark-1020 Thursday, December 08, 2016 7:25 PM
    Thursday, December 08, 2016 6:39 PM

All replies

  • No, this is a known issue at this time. You don't have to install SCUP on a server though.

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

    Thursday, December 08, 2016 5:57 PM
  • I already tried this with Server 2016 TP.

    A Workaround is to temporary change the Version String from WSUS in Registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup

    Backup the current value and change it for example to the value from Server 2012 R2 WSUS:

    "VersionString"="6.3.9600.17477"

    After that you should be able to install SCUP. After the Installation you can change the value back.



    • Edited by Michael-CM Thursday, December 08, 2016 6:44 PM
    • Marked as answer by Mark-1020 Thursday, December 08, 2016 7:25 PM
    Thursday, December 08, 2016 6:39 PM
  • That temporary registry change did the trick.   Thanks mknuel!   
    Thursday, December 08, 2016 7:25 PM
  • That temporary registry change did the trick.   Thanks mknuel!   

    Which still leaves you in an unsupported state. As Jason said: no need to install SCUP on a server. It can also be installed on a Workstation.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, December 09, 2016 7:23 AM
  • Is there any projected release for a fix from Microsoft?  Installing SCUP on an older OS isn't good enough - you also have to install WSUS server on the older OS as the WSUS console must be the same version (or, possibly higher) than the WSUS server.
    Tuesday, January 10, 2017 8:13 PM
  • Not at the moment but you can vote for an idea in UserVoice:

    https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/8803711-3rd-party-patching-scup-integration-with-sccm-co


    • Edited by Michael-CM Tuesday, January 10, 2017 8:56 PM
    Tuesday, January 10, 2017 8:27 PM
  • "you also have to install WSUS server on the older OS as the WSUS console must be the same version (or, possibly higher) than the WSUS server"

    Sorry, not sure what you are trying to say here. The WSUS version is unrelated to SCUP.

    Your WSUS version including the console must always match across the board. That has nothing to do with SCUP though as noted.


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

    Tuesday, January 10, 2017 8:32 PM
  • Wanted to chime in on this. A better option than changing the setup version in the registry is you can just run the MSI with /qb switch and that will skip the prerec check.

    Justin Chalfant | My Blog | LinkedIn | Please mark as helpful/answer if this resolved your post

    • Proposed as answer by Mike Jenne Tuesday, February 14, 2017 8:14 AM
    Monday, February 13, 2017 5:23 PM
  • Thanks for this info!
    Monday, February 13, 2017 6:20 PM
  • This definitely solved the issue for me!
    Thursday, February 16, 2017 7:44 PM