locked
SCCM 1607 - Unable to Push Updates to Win 10 1607 Reference Workstation - UNRESOLVED RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi All,

    We are building a Windows 10 LTSB 1607 reference image using the SCCM CB 1607 (we can't use the MDT). There is only 1 WSUS and it is serving the SCCM. How to push the updates to the reference image? Right now the updates image don't go through despite there is a task in the SCCM-native task sequence, because the reference machine is not a part of the domain?

    Many thanks, in advance!
    • Edited by TracyMt36 Wednesday, February 8, 2017 6:24 PM
    Tuesday, February 7, 2017 2:42 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Is your SUP working correctly? From where did the machine pick up those update's you mentioned, the Internet? I've had my B&C collections always configured with REQUIRED Software Updates -deployment, don't know if that helps your case...


    Friday, February 10, 2017 4:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    When Computer is Workgroup-member, you must specify SMSMP= and fail back values in Setup SCCM client step, otherwise workgroup Computer will not use any install options in OSPhase. Also, then your boundaries and subnet ranges must be exactly correct, because workgroup member might not rely on AD sites and subnetting.

    Please remember to mark my post as an answer, if I really helped you out, or vote if usefull. Thank you!

    Friday, February 10, 2017 6:29 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    ConfigMgr (CB) 1607 only exists as a Technical Preview and I doubt that you run this Version in Production.

    Are you running a version of ConfigMgr current branch, which supports Windows 10 LTSB? Did you enable the Windows 10 LTSB Updates in the SUP Properties? Are they downloaded into a Deployment Package? Are the Updates deployed to the Reference Machine?

    Simon Dettling | msitproblog.com | @SimonDettling

    Tuesday, February 7, 2017 2:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for your help, Simon!

    1. SCCM CB 1610.
    2. The Windows 10 LTSB updates are enabled on the SUP in the Product tab.
    3. Yes, they are downloaded into the deployment package.
    4. Yes, the updates are deployed to the device collection in which the reference machine was manually inserted.

    Here is what was done:

    1. Created device collection and manually added the W10 standalone reference workstation referring to its MAC address.
    2. Created brand new software update group, deployment package and assigned this to the device collection in step 2 with option AVAILABLE.
    3. In the task sequence I specified task with the following option:
      Available for installation - All software updates.
    4. WindowsUpdate log has the following entry:
       Found 0 updates and 25 categories in search
    5. When we manually ran Windows Update on the W10 reference machine it picked up and installed 3 updates: 3211320, 3213986, 3214628. 3214628 was also in the SUG, but was not installed originally.
    • Edited by TracyMt36 Wednesday, February 8, 2017 8:25 PM
    Wednesday, February 8, 2017 6:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Any reason you want to really build reference image (capture)? I try to believe, that with Windows 10, capturing is old news, you don´t need to do that anymore. Specially when 1607 is not in CBB, just download the lates bits from MS volume licensing and start using install.wim.

    Sure, with LTSB you would have much longer life time with the current build than CB/CBB, so I guess capturing still makes since in LTSB.

    ..but, specially when there is no update issues anymore with Windows 10, because you would have only one Cumulative Update required to deploy, do you still want to capture?

    Please remember to mark my post as an answer, if I really helped you out, or vote if usefull. Thank you!

    Wednesday, February 8, 2017 8:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Is your SUP working correctly? From where did the machine pick up those update's you mentioned, the Internet? I've had my B&C collections always configured with REQUIRED Software Updates -deployment, don't know if that helps your case...


    Friday, February 10, 2017 4:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    When Computer is Workgroup-member, you must specify SMSMP= and fail back values in Setup SCCM client step, otherwise workgroup Computer will not use any install options in OSPhase. Also, then your boundaries and subnet ranges must be exactly correct, because workgroup member might not rely on AD sites and subnetting.

    Please remember to mark my post as an answer, if I really helped you out, or vote if usefull. Thank you!

    Friday, February 10, 2017 6:29 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yannara and Narcoticoo, thank you very much for your help!

    1. We are using the reference image build and capture as a best Microsoft practice. The image contains Office, Microsoft libraries and .NET Framework 3.5 role enabled. Create a Windows 10 reference image and Building a Windows 10 Reference Image using MDT 2013 Update 1, however, we can't use the MDT because of the environment limitation so we try to use SCCM.
    2. The SUP works fine. The updates are coming to the target reference standalone W10 VM, but they are not getting applied.
    Monday, February 13, 2017 1:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just something I discovered recently:

    • Windows 10 LTSB in products of WSUS / SUP refers to the RTM version (=1507), these are not applicable for the LTSB 2016
    • For LTSB 2016 (=1607) you need to enable the Windows 10 updates for your SUP in the products

    This might be just the case for you as well, the LTSB updates you're trying to install during B&C aren't applicable for the 2016 LTSB version.

    Saturday, March 11, 2017 7:46 AM