We have an internal web application at Commerce that makes extensive use of ActiveX controls.  The application is used primarily by our financial service reps and contact center operators.  Thanks to the Eolas judgment, the application in question was still mostly functional, but required users to manually click on the ActiveX controls before they could interact with them.  Not only were the programmers who maintain the application concerned that their non-technical users would be confused by the "Click here to activate this control" message, but this behavior actually broke a control we use to push client-side updates.  Our programmers took Microsoft's recommeded steps to correct the issue.

The problem is, Microsoft's solution didn't work on about half the machines we tried it on. After a while, we determined that the problem machines were all laptops, so we immediately suspected a difference in the images our desktop team uses on our workstation PCs versus our laptops.  After running through all the usual suspects, like OS patches, our laptop security software, IE build number, etc., we were at a loss and opened a ticket with MSDN developer support.

After a week's worth of research on the Microsoft side, the support analyst suggested I compare version numbers on jscript.dll.  Sure enough, the version on the laptops is outdated.  We downloaded the installer for the most recent version, and all is good again.