locked
Servicing with SCCM, but WSUS on another server RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    We currently use SCCM to deploy software and manage clients

    We currently have WSUS setup on another machine for patching.

    I would like to setup Windows Servicing in SCCM as a way to manage the OS upgrades easily, (rather than push via WSUS)

    I have updates downloaded, servicing plan created, but it fails to work as my group policy is setting my WSUS server which differs to the SCCM system update point.

    is it possible to setup and use both?

    any ideas on what i should do?

    Cheers

    Monday, June 1, 2020 5:56 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    You can't manage SCCM and WSUS on the same client, SCCM sets the SUP WSUS server for scanning for updates by setting the Local GPO to point to that server. If you override it using your own GPO, you'll get conflicts and SCCM's patch flow will not function.

    You can use only SCCM for windows 10 upgrade - Check the below blog

    https://www.prajwaldesai.com/sccm-windows-10-servicing-plans/

    For windows 10 upgrade errors - https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolve-windows-10-upgrade-errors

    Monday, June 1, 2020 10:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Kalyan

    Thanks for that.  that is disappointing for me.. i like WSUS and GP because we can control via AD OU structure and AD groups with policies

    if we move the whole WSUS to SCCM can it be setup to achieve same/similar purpose?

    our other issue is that we don't manage servers with SCCM, they need dedicated WSUS

    Tuesday, June 2, 2020 1:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    > if we move the whole WSUS to SCCM can it be setup to achieve same/similar purpose?

    Yes of course but with far more flexibility and control. I would never call organization by OU "control" as its simple directory where objects can only exist in one location at a time. 

    > our other issue is that we don't manage servers with SCCM, they need dedicated WSUS

    For this, you will need to maintain a separate WSUS infrastructure. Why do "need" to do this?

    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, June 2, 2020 1:58 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    when i say control, obvs OU structure isn't a control, more that we can put them in required containers, and use AD groups to help with the patching.

    we will need WSUS standalone for servers, as we don't have them in SCCM

    Tuesday, June 2, 2020 7:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Right, but that's the point because collections in ConfigMgr are so much more flexible and provide far more control. Collections can be configured to directly leverage OUs and security groups if desired but aren't restricted to these and of course can be dynamic which OUs and security groups can't be.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, June 2, 2020 3:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    thanks for your input

    i am trying to work out pros and cons for my boss to decide which route we need to take.

    we currently use WSUS for everything, and we are currently performing in place upgrades for Win10

    Wednesday, June 3, 2020 4:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This is older but still valid: https://ccmexec.com/2012/08/top-11-reasons-why-you-should-use-configmgr-2012-for-managing-software-updates/

    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, June 3, 2020 6:25 PM