Skype for Business – Removing an Inactive Edge Pool

You aren't the only one having this issue with some of the April updates not synchronizing with WSUS on Server 2012 (including KB2889923). The following workaround was posted by Microsoft and may work for you.

To work around this problem, use the following method to manually synchronize new updates in WSUS. Repeat these steps for every update category that you want to synchronize.

1. In the WSUS console, disable updates from synchronizing. To do this, follow these steps:

   • In the navigation pane, expand the node.
   • Click the Options node.
   • In the center pane, click Products and Classifications.
   • In the Products and Classifications dialog box, click the Classifications tab.
   • Clear the check box for the classification that you cannot synchronize to WSUS.
2. Run synchronization in WSUS. To do this, follow these steps:
   • In the navigation pane, expand the node.
   • Click the Synchronizations node.
   • In the right pane, click Synchronize now.
3. In the WSUS console, enable updates for synchronizing. To do this, return to the Classifications tab, and then select the check box for a classification that you want to synchronize.
4. Run synchronization in WSUS.
5. Repeat steps 1-4 for any other update classification that you want to synchronize, as appropriate.
   • Note You can enable and disable more than one update classification at a time. However, at least one classification most be enabled for WSUS synchronization to occur.
6. If System Center 2012 Configuration Manager (ConfigMgr) is present in the system, run synchronization in ConfigMgr.

I had a similar issue. I used a PKCS#7 Base64 encoded certificate which lead to the same issue as you saw. Then I re-downloaded it as X509 Base64 encoded and everything started to work as expected.