locked
Non domain servers not checking into WSUS server after April 2016 updates RRS feed

  • Question

  • Our WSUS server is running Server 2012 R2.  Everything appeared to be working fine before I released the May 2016 updates, and then after the May updates installed and servers rebooted the WSUS console did not work and clients could not check into the WSUS server.  After some research I found that KB3159706 was the problem and that there were post installation steps that needed to be done.  I followed those steps from the KB article:  https://support.microsoft.com/en-us/kb/3159706
    After doing those steps everything started to work correctly again or at least almost everything. 

    I just realized the other day that servers(2008 R2, 2012, and 2012 R2) that are not part of our domain stopped checking into our WSUS server after the April 2016 updates.  What do I need to do to get those servers to start checking back into our WSUS server?

    Thursday, May 19, 2016 2:14 PM

Answers

  • After updating the SSL Certificate on our WSUS server, all domain bound servers worked fine as they automatically received the latest CA Certificate that we updated before the new SSL cert on WSUS, however non domain bound servers did not automatically receive the CA cert so I had to manually import it onto those servers and then everything started working properly.

    • Marked as answer by WSUAL2 Wednesday, June 8, 2016 6:21 PM
    Wednesday, June 8, 2016 6:21 PM

All replies

  • Hi WSUAL2,

    1. Apart from non-domain joined clients, does WSUS server with KB 3159706 work well for other clients?

    2. On problematic clients, try resetting windows update components, check if it could work:

    https://support.microsoft.com/en-us/kb/971058

    3. If reset windows update component still doesn't work, also try reindex WSUS database on WSUS server and run server cleanup wizard:

    https://technet.microsoft.com/en-us/library/dd939795(v=ws.10).aspx

    (On server 2012 R2, the command is: SQLCMD -E -S np:\\.\pipe\MICROSOFT##WID\tsql\query -i <script location>)

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, May 20, 2016 2:36 AM
  • After updating the SSL Certificate on our WSUS server, all domain bound servers worked fine as they automatically received the latest CA Certificate that we updated before the new SSL cert on WSUS, however non domain bound servers did not automatically receive the CA cert so I had to manually import it onto those servers and then everything started working properly.

    • Marked as answer by WSUAL2 Wednesday, June 8, 2016 6:21 PM
    Wednesday, June 8, 2016 6:21 PM