For future reference…
If WSUS starts responding with the message: “Cannot save configuration because the server is still processing a previous configuration change”, run this SQL command:
UPDATE tbSingletonData SET ResetStateMachineNeeded = 0
And in the long term, consider this:
A small curiosity…
The TRIM() function in Excel works completely differently than TRIM in SQL. In Excel, it removes all occurrences of spaces except for a single occurrence between words, while in SQL it removes only spaces from the beginning and end of a string.
After a few surprises that appeared less than a month ago in the article https://www.karolszczepanowski.pl/2015/02/24/problemy-z-vmware-vcenter-server-5-5/, it was time for another one…
This time the vCenter database stopped with the not very informative note “(Suspect)”, probably because something broke after a power failure (again).
Fortunately someone has already described the problem, so here is the source link:
http://www.vmdude.fr/en/tips-tricks-en/suspect-vcenter-database-on-sql-express/
Microsoft Windows OLE Automation Array Remote Code Execution Vulnerability.
Description: https://www.us-cert.gov/ncas/alerts/TA14-318B
Exploit for it: http://packetstorm.igor.onlinedirect.bg/1411-exploits/ms14_064_packager_run_as_admin.rb.txt
And another bug that allows gaining domain administrator privileges:
http://blogs.technet.com/b/srd/archive/2014/11/18/additional-information-about-cve-2014-6324.aspx
There was also a mishap: MS14-066 causes problems with SQL and IIS. That is what happens when instead of focusing on patching, you add new algorithms…