alenat Posted January 14, 2013 Report post Posted January 14, 2013 Microsoft published CU0 for 2012 SP1 addressing the issue. I blogged it here: http://777notes.wordpress.com/2013/01/14/sccm-2012-sccm-2012-sp1-client-update-failed-error-couldnt-verify-cwindowsccmsetupmicrosoftpolicyplatformsetup-msi-authenticode-signature-return-code-0x800b0101/ Quote Share this post Link to post Share on other sites More sharing options...
rayik Posted January 18, 2013 Report post Posted January 18, 2013 Thank you. I had set up SCCM 2012 SP1 about 2 weeks ago. Deployment to 15 clients went fine. In the last week I tried to add to 2 more clients and could not get to install. Nothings worked (SUP, push and manual install from client). Never would have thought an expired Cert problem. Even though the CU instructions said to install prior to SCCM SP1 installation, no problems when CU applied to existing install. Client deployment now works fine. You might want to PIN this for a while until MS releases an automatic update. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted January 19, 2013 Report post Posted January 19, 2013 Well, KB2801987 is Microsoft solution from ConfigMgr perspective. When you want to solve it from a clients' perspective via WSUS/SUP/Offline servicing then you can use KB2756872. On a side-node: It says the update should be installed prior to installing the ConfigMgr 2012 SP1 client. Logically, on a site server it should be applied after installing SP1, as the issue doesn't exist before installing SP1. Quote Share this post Link to post Share on other sites More sharing options...
alenat Posted January 30, 2013 Report post Posted January 30, 2013 Microsoft published new bits of SCCM 2012 SP1 addressing the problem. So it should not happen if you use this new files. For early installations with original bits we need to use the workarounds described before Quote Share this post Link to post Share on other sites More sharing options...
