locked
1809 Feature Update deployments questions RRS feed

 > 

  • General discussion

  • Discussion
    Sign in to vote
    0
    Sign in to vote

    Hi Champs,

    A question in context of 1809 (Feature update to Windows 10 (business editions), version 1803, en-us ) deployments, apprecaite your help 

    SCCM Clients which still run 1709 or 1803 says compliant in SCCM server reports and also few of related client status message/WMI classes as well (State 300 /StateID=0) and deployments goes skipped , Any idea what could be happening ?

    Thanks, 

    Vasu


    Monday, April 1, 2019 12:50 PM

All replies

  • Discussion
    Sign in to vote
    0
    Sign in to vote

    1. Make sure that the latest servicing stack update has been deployed to the systems as this can/will affect the applicability detection of feature updates.

    2. No. The feature update language must match the OS base language.

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

    Monday, April 1, 2019 2:05 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Thansk Jason, will try this and let you know how it goes

    Vasu

    Monday, April 1, 2019 2:32 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    Hi Jason

    Mentioned articles (SSU)are already installed on clients thru our monhtly patching. 

    https://www.catalog.update.microsoft.com/Search.aspx?q=KB4485448  (on 1709)

    & https://www.catalog.update.microsoft.com/Search.aspx?q=KB4485449 (on 1803)

    However I see this policy is deployed to disable OS upgrade... Do you think if this can lead to incorrect incompliance info. 

    Hive HKEY_LOCAL_MACHINE
    Key path SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    Value name DisableOSUpgrade
    Value type REG_DWORD
    Value data 0x1 (1)

    Vasu

    Monday, April 1, 2019 3:22 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    It's certainly possible as I've never tested this value. If you are managing updates with ConfigMgr though, using this setting/policy simply adds confusion though and it shouldn't be used in the first place so I'd strongly recommend getting rid of it and anyone WU/WUfB centric policies.

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

    Monday, April 1, 2019 8:46 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    We have ensured to install latest SSU and also removed WUfB policies...still no luck

    wondering whatelse we could try / troubleshot further 

    Thanks, 

    Vasu

    Tuesday, April 2, 2019 11:04 AM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    What about the above-noted setting? Have you removed it?

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

    Tuesday, April 2, 2019 11:13 AM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Yes, changed it to 0, but not removed the setting itself...

    Vasu

    Tuesday, April 2, 2019 1:57 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote

    Jason,

    This is solved, after removing a test policy created WuFB (Windows Upgrades Deferral) in SCCM under Windows 10 Servicing node. Wonderful clue you gave, which we used against AD GPO, Imaging Hardening and finally in SCCM itself, which solved the problem. Thansk a ton 

    Thanks,

    Vasu

    Wednesday, April 3, 2019 5:20 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Glad you found it and yes, stay away from all WUfB policies -- delete them and any resulting registry values created on the clients if necessary -- when using ConfigMgr to deploy updates otherwise you're just asking for some blocking behavior.

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

    Wednesday, April 3, 2019 10:01 PM