locked
WSUS 3.2 - "Uprgades" appeared in Classifications list - Should we enable it for Windows 10? RRS feed

  • Question

  • Up till now, we knew that only WSUS 4 supports the "Upgrades" classification for use with Windows 10, in order to download and distribute the upgrade versions (e.g. win 10 1511) to clients.

    A few days ago we noticed that on our customer's WSUS 3.2 servers, the "Upgrades" option appeared in the Classifications list.

    Can we safely enable it for Windows 10 on WSUS 3.2?

    Will it work as expected?

    Will WSUS 3.2 need a patch (as is the case for Wsus 4)?


    Tuesday, March 8, 2016 8:31 AM

Answers

  • Hi Winfried & Steven,

    Than you both for your answers. We thought to try your suggestions BUT...

    The thing is that KB 3095113 is supposed to be installed on server 2012/2012r2 only.

    What we are talking here, are customers with Server 2003r2 and 2008r2 which are PDCs + Wsus 3.2.

    According to all the above and seeing the Upgrades classification appearing, a logical approach should be NOT to install the patch due to older server versions and simply check the upgrades option after performing SUSDB backup.

    So in order to not experiment on production servers, we need solid answers from MS:

    • Can we install KB 3095113 on Server 2003r2?
    • Can we install KB 3095113 on Server 2008r2?
    • Can we enable WSUS 3.2 Upgrades classification on Server 2003r2?
    • Can we enable WSUS 3.2 Upgrades classification on Server 2008r2?

    Dimitris Grivas

    - No
    - No
    - You are not "blocked" from doing so by the WSUS console, but you *SHOULD NOT* do so
    - You are not "blocked" from doing so by the WSUS console, but you *SHOULD NOT* do so

    http://blogs.technet.com/b/wsus/archive/2016/01/30/quot-help-i-synched-upgrades-too-soon-quot.aspx

    Please see the comments section of the blog post, where this question about WSUS 3.2 is asked, and answered by Steve Henry (MSFT)


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



    • Edited by DonPick Wednesday, March 9, 2016 8:42 AM
    • Proposed as answer by Steven_Lee0510 Sunday, March 27, 2016 2:56 PM
    • Marked as answer by Steven_Lee0510 Monday, March 28, 2016 3:21 PM
    Wednesday, March 9, 2016 8:41 AM

All replies

  • Am 08.03.2016 schrieb solutions-it.gr:

    Up till now, we knew that only WSUS 4 supports the "Upgrades" classification for use with Windows 10, in order to download and distribute the upgrade versions (e.g. win 10 1511) to clients.

    A few days ago we noticed that on our customer's WSUS 3.2 servers, the "Upgrades" option appeared in the Classifications list.

    Can we safely enable it for Windows 10 on WSUS 3.2?

    Will it work as expected?

    Will WSUS 3.2 need a patch (as is the case for Wsus 4)?

    This patch will enable WSUS support for Windows 10 Clients and
    classification Upgrade. https://support.microsoft.com/en-us/kb/3095113
    The hotfix is not for 2008R2 available, i don't think that WSUS 3.2.x
    will support Upgrades for Windows 10 Clients. But you can try it and
    give us feedback. ;)

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Tuesday, March 8, 2016 6:27 PM
  • Hi,

    As far as I know, WSUS 3.0 SP2 only supports the updates for Windows 10.

    Enable the "Upgrades" may cause SUSDB corruption, please backup your WSUS server before you try it.

    If you try to sync any upgrades without having first installed KB 3095113, you will populate the SUSDB with unusable data that must be cleared before upgrades can be properly distributed.  This situation is recoverable but the process is nontrivial and can be avoided altogether if you make sure to install the update before enabling sync of upgrades. 

    Quote from the link below:

    https://support.microsoft.com/en-us/kb/3095113

    Best Regards,


    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, March 9, 2016 2:54 AM
  • Hi Winfried & Steven,

    Than you both for your answers. We thought to try your suggestions BUT...

    The thing is that KB 3095113 is supposed to be installed on server 2012/2012r2 only.

    What we are talking here, are customers with Server 2003r2 and 2008r2 which are PDCs + Wsus 3.2.

    According to all the above and seeing the Upgrades classification appearing, a logical approach should be NOT to install the patch due to older server versions and simply check the upgrades option after performing SUSDB backup.

    So in order to not experiment on production servers, we need solid answers from MS:

    • Can we install KB 3095113 on Server 2003r2?
    • Can we install KB 3095113 on Server 2008r2?
    • Can we enable WSUS 3.2 Upgrades classification on Server 2003r2?
    • Can we enable WSUS 3.2 Upgrades classification on Server 2008r2?

    Dimitris Grivas

    Wednesday, March 9, 2016 7:52 AM
  • Hi Winfried & Steven,

    Than you both for your answers. We thought to try your suggestions BUT...

    The thing is that KB 3095113 is supposed to be installed on server 2012/2012r2 only.

    What we are talking here, are customers with Server 2003r2 and 2008r2 which are PDCs + Wsus 3.2.

    According to all the above and seeing the Upgrades classification appearing, a logical approach should be NOT to install the patch due to older server versions and simply check the upgrades option after performing SUSDB backup.

    So in order to not experiment on production servers, we need solid answers from MS:

    • Can we install KB 3095113 on Server 2003r2?
    • Can we install KB 3095113 on Server 2008r2?
    • Can we enable WSUS 3.2 Upgrades classification on Server 2003r2?
    • Can we enable WSUS 3.2 Upgrades classification on Server 2008r2?

    Dimitris Grivas

    - No
    - No
    - You are not "blocked" from doing so by the WSUS console, but you *SHOULD NOT* do so
    - You are not "blocked" from doing so by the WSUS console, but you *SHOULD NOT* do so

    http://blogs.technet.com/b/wsus/archive/2016/01/30/quot-help-i-synched-upgrades-too-soon-quot.aspx

    Please see the comments section of the blog post, where this question about WSUS 3.2 is asked, and answered by Steve Henry (MSFT)


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



    • Edited by DonPick Wednesday, March 9, 2016 8:42 AM
    • Proposed as answer by Steven_Lee0510 Sunday, March 27, 2016 2:56 PM
    • Marked as answer by Steven_Lee0510 Monday, March 28, 2016 3:21 PM
    Wednesday, March 9, 2016 8:41 AM