The new update is located in KB3159706, and this time Microsoft is making sure to let customers know that .The manual steps are contained in the knowledge base article, but Microsoft also lays them out in the blog post announcing today’s fixed update: The long-term fix for KB3148812 issues.Until now, we have been manually decrypting these packages prior to releasing to the WSUS channel, the process of which is both time consuming and error prone.
As shown in , code 0x80244021 translates to WU_E_PT_HTTP_STATUS_BAD_GATEWAY, which in turn translates to "The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request." Note that in this situation, the affected computer may or may not be able to automatically check for and download updates from WSUS.
After you set up a client computer, it may take a few minutes before it appears on the Computers page in the WSUS console (this console is available to admins running their own WSUS server, but not for admins who point their clients at the CITES WSUS server).
For client computers configured with an Active Directory-based GPO, it can take about 20 minutes after Group Policy refreshes (that is, applies any new settings to the client computer).
This is part 2 of a 6 part series where I talk through common issues I have seen that skew the numbers for software updates, or make it difficult to explain the results.
Once we are done, hopefully you will be able to look at the SCCM Software Update process in much the same way as Neo saw the Matrix…
NOTE: If you are running your own domain, when you configure the Group Policy settings in Active Directory for WSUS, use a Group Policy Object (GPO) linked to an Active Directory container appropriate for your environment.