We got bit at work by a Microsoft Windows Update from August that just took effect Sept. 9th. Microsoft pulled an Apple and IE disabled your Java ActiveX component if it isn't up-to-date. This affects connections to computers that are outside your IE Intranet and Trusted Zones. See
http://support.microsoft.com/kb/2991000
All fine and good but the one application we moved into the Cloud is (of course) the one that broke and is (of coursed) used by Everybody That Needs It Fixed NOW. Turns out it caught the vendor flat-footed as well. Corporate IT hasn't issued a statement yet.
The ironic thing is we do Windows Updates testing, but since this particular update did not take effect until Sept. 9, it wasn't caught in August. Likewise, any beta users were not the ones who use the application, so testing this month's patches went smoothly. Likewise, the testing cycle for Java Runtime Environment is even worse as JRE updates come out whenever. Plus, once they are pronounced Good, Corporate needs to create a SCCM package which also needs to be tested. Once that is finished, Oracle has usually come out with Yet Another JRE version to correct the exploit that was found in the current version.
SOx SUx.