locked
ConfigMgr 1602 with WSUS 3.0 SP2 and Anniversary update RRS feed

  • Question

  • Hello,

    There is something I want to run by you guys, and get a second opinion.

    We are currently running ConfigMgr 1602 with WSUS 3.0 SP2 (Win 2k8 R2 OS). From what I understand, Windows 10 Update 1607 is becoming business ready on 1st of next month, i.e. computers that have deferred update selected will install that patch.

    We have found out that Update 1607 is causing some issues in our environment, and would like to delay the patch deployment on our machines until its resolved. Will our machines automatically start installing 1607 update once it becomes current for business-ready computers?

    We have 'Configure Automatic Updates' setting disabled via GPO, and ConfigMgr server is listed for 'Specify intranet Microsoft update service location' on all machines (I believe thats set by ConfigMgr client). Also, since we are still on WSUS 3.0 SP2, we dont have the capability to get Windows 10 Update 1607, since that feature is supported on WSUS 4.0. So currently I dont see Windows 10 Update 1607 feature update under 'All Software Updates' node.

    Because of all these reasons, I believe that Win10 1607 wont get installed on machines in our environment come November 1st, but I just want to get a second opinion. I appreciate your help.

    Thanks,

    -Sneh

    Wednesday, October 26, 2016 6:23 PM

Answers

  • "Because of all these reasons, I believe that Win10 1607 wont get installed on machines in our environment come November 1st,"

    Correct. There's no other way for them to be deployed automatically.


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

    Wednesday, October 26, 2016 7:12 PM

All replies

  • Also, since we are still on WSUS 3.0 SP2, we dont have the capability to get Windows 10 Update 1607, since that feature is supported on WSUS 4.0. So currently I dont see Windows 10 Update 1607 feature update under 'All Software Updates' node.

    Since you run WSUS 3.0, you won't get the Upgrade Classification in your SUP Settings, which is needed to get the Feature Upgrade.

    One possibility would be to inplace upgrade your Site-Server OS from Server 2008 R2 to Server 2012 R2 to get a WSUS 4.0.

    If I remember it correctly, only ConfigMgr 1606 provides support for Windows 10 1607, so you would need to upgrade ConfigMgr aswell.


    Simon Dettling | msitproblog.com | @SimonDettling

    Wednesday, October 26, 2016 6:49 PM
  • Thanks for the response, Simon! I really appreciate it.

    Yes, we do have a project plan to get our ConfigMgr infrastructure upgraded to later versions (Server 2012 R2, WSUS 4, ConfigMgr 1606 etc.). However my current concern is that Update 1607 doesn't get installed on machines in our environment come November 1st. Do you know if I need to do anything to not have this update installed in our environment?

    According to me, the GPO for automatic update installation (disabled) and local microsoft update server settings should prevent this. I hope these GP settings are still effective even after MS changed their patching approach with Win10 :).

    Wednesday, October 26, 2016 7:00 PM
  • "Because of all these reasons, I believe that Win10 1607 wont get installed on machines in our environment come November 1st,"

    Correct. There's no other way for them to be deployed automatically.


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

    Wednesday, October 26, 2016 7:12 PM
  • Hi,

        >>"We have found out that Update 1607 is causing some issues in our environment, and would like to delay the patch deployment on our machines until its resolved. Will our machines automatically start installing 1607 update once it becomes current for business-ready computers?"

        Since you are using ConfigMgr for update management, machines will not automatically upgrade to 1607. Only after you upgrade your ConfigMgr to 1606 and complete the prerequisites in this guide you will be able to deploy feature upgrade to your environment via a service plan.

        https://docs.microsoft.com/en-us/sccm/osd/deploy-use/manage-windows-as-a-service

    Best regards,

    Jimmy


    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 Subscriber Support, contact tnmff@microsoft.com.

    Thursday, October 27, 2016 6:53 AM