locked
1607 - 1703 Feature Update SCCM/WSUS Failing RRS feed

  • Question

  • Hi,

    I am trying to run a pilot for feature update for 1703 clients going from 1607-1703. Now the update fails to install and in:

    C:\$Windows.~BT\Sources\Panther\setuperr.log I get the error:

    Info MOUPG SetupNotify::Remapping missing decrypt key error [0xC1800118] -> [0x80248008]

    Now I followed https://support.microsoft.com/en-us/help/3194588/-0xc1800118-error-when-you-push-windows-10-version-1607-by-using-wsus and I had 63 results. Went through the article and then did the query again and got 0. I did it for all 1511, 1607 and 1703.

    Deleted the software update package in SCCM and re-ran the servicing plan and still get the same error as above. I am running the latest version of ConfigMgr 1702 and have also got the two patches required on the WSUS server along with the manual steps that need to be complete after that. I haven't uninstalled the SUP and WSUS and don't really want to. I did fiund on the internet a few people with similar issues and someone had apparently modified the scripts microsoft did and got it working however they can't find the article anymore.

    I have also added the File Name Extension .esd MIME type: applicaitonoctect-stream to IIS and same results.

    Does anyone have any ideas?



    • Edited by grayman001 Friday, May 12, 2017 11:10 AM update
    Friday, May 12, 2017 11:06 AM

Answers

  • Finally resolved this. Basically I was cleaning up WSUS but not doing the SCCM side.

    I followed these steps from Hybrid (Mid Way down listed in detail)

    Order of Steps

    I also ran these commands to do the 1703

    1703 CleanUp

    Just tied it all together and then was able to use the Windows Servicing as expected.


    • Marked as answer by grayman001 Wednesday, May 17, 2017 4:14 AM
    • Edited by grayman001 Wednesday, May 17, 2017 4:16 AM
    Sunday, May 14, 2017 7:54 AM

All replies

  • Finally resolved this. Basically I was cleaning up WSUS but not doing the SCCM side.

    I followed these steps from Hybrid (Mid Way down listed in detail)

    Order of Steps

    I also ran these commands to do the 1703

    1703 CleanUp

    Just tied it all together and then was able to use the Windows Servicing as expected.


    • Marked as answer by grayman001 Wednesday, May 17, 2017 4:14 AM
    • Edited by grayman001 Wednesday, May 17, 2017 4:16 AM
    Sunday, May 14, 2017 7:54 AM
  • Hi,

    In the KB there is 2 part. One for the server and one for the client.

    You can reset WU on the client side and delete ccmcache and try it again

    https://support.microsoft.com/en-us/help/971058/how-do-i-reset-windows-update-components

    It seems that you're ok on server side now ! But not on client ;) You can test it with new client from scratch if you want to be sure.


    Merci de marquer comme réponse les sujets qui vous ont permis d'avancer afin que cela puisse être bénéfique aux personnes qui rencontrent le même problème.

    Sunday, May 14, 2017 9:43 AM