locked
SCCM on Windows Server 2008 R2 and WSUS version RRS feed

  • Question

  • Hi,

    Currently we have SCCM 2012 R2 on Windows Server 2008 R2, single primary site. SCCM (current branch) supports Windows Server 2008 R2.

    So there is an option to do an in-place upgrade.

    But if we have Windows Server 2008 R2, then we have WSUS 3.2 and it doesn't support deploying Windows 10 Upgrades (https://technet.microsoft.com/en-us/library/mt613198.aspx).

    If we deploy a remote Software Update Point on Windows Server 2012, then we must deploy same WSUS console version on site server (https://technet.microsoft.com/en-us/library/mt613198.aspx - The WSUS version on the site server must be the same as the WSUS version running on the software update points.) But as I understand we cannot install WSUS 4.0 on Windows Server 2008 R2.

    Does this mean that if we have a primary site server on Windows Server 2008 R2, then we cannot deploy Windows 10 Upgrades?

    Friday, February 26, 2016 7:42 AM

Answers

  • Yes, but don't mix upgrades and updates.

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

    Friday, February 26, 2016 8:13 AM
  • Does this mean that if we have a primary site server on Windows Server 2008 R2, then we cannot deploy Windows 10 Upgrades?

    Yes.

    The WSUS Update that enables the new Servicing Capabilities is only available for WSUS 4.0, which requires a Server 2012 R2.

    Just for your info, startig with ConfigMgr CB 1602, which should be released in the next few weeks, an Inplace Upgrade of the Site Server OS from 2008 R2 to 2012 R2 will be supported.

    Other Scenarios would be a Side-by-Side Migration or a Site Restore on a new 2012 R2 Server.


    Simon Dettling | msitproblog.com | @SimonDettling


    Friday, February 26, 2016 8:31 AM

All replies

  • Yes, but don't mix upgrades and updates.

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

    Friday, February 26, 2016 8:13 AM
  • Thanks.

    What do You mean by "don't mix upgrades and updates"? We will definitely have different processes, deployemnt schedules, packages for upgrades and updates.

    Friday, February 26, 2016 8:24 AM
  • Does this mean that if we have a primary site server on Windows Server 2008 R2, then we cannot deploy Windows 10 Upgrades?

    Yes.

    The WSUS Update that enables the new Servicing Capabilities is only available for WSUS 4.0, which requires a Server 2012 R2.

    Just for your info, startig with ConfigMgr CB 1602, which should be released in the next few weeks, an Inplace Upgrade of the Site Server OS from 2008 R2 to 2012 R2 will be supported.

    Other Scenarios would be a Side-by-Side Migration or a Site Restore on a new 2012 R2 Server.


    Simon Dettling | msitproblog.com | @SimonDettling


    Friday, February 26, 2016 8:31 AM
  • Thanks Simon for info, it is good news, that OS in-place ugprade will be supported.

    Friday, February 26, 2016 8:38 AM
  • What do You mean by "don't mix upgrades and updates"?

    For your scenario (WS2008R2), you *will* be able to deploy and manage Win10 Updates (patches) using the SUM features of CM, but you *will not* be able to deploy and manage Win10 Upgrades using the SUM features of CM.

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Friday, February 26, 2016 9:20 AM
  • Thanks for the answers. Somehow I don't have "Mark as Answer" option, so I cannot do that.

    Here is a blog post that states that OS in-place ugprade will be in 1602 https://blogs.technet.microsoft.com/configmgrteam/2016/02/18/update-1602-for-technical-preview-available-now/

    Friday, February 26, 2016 9:47 AM
  • I've changed the thread type. You should now be able to mark an answer.


    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson

    Friday, February 26, 2016 5:52 PM