We're in the same boat. Tested it on a few systems, no issues yet. We don't have much that depends on Java though (except for web apps). Just InDesign, and FileMaker Pro.
Everything is setup in our JSS to push the patch, just waiting to flip the switch after a bit more testing and submitting the paperwork.
I've started rolling it out this morning with Casper to our Macs with Java 7 Update 9 or Java 7 Update 10 installed. We also have Apple's Java 6 2012-006 installed, so we're using Java 7 only as a browser plug-in.
So far, no problems seen. The main thing we're concerned with is our Juniper SSL VPN, and Java 7 Update 11 works fine with it.
For those wanting to check the version of the Java browser plug-in with Extension Attributes, I have a post on how to do that:
@rtrouton You rock! 🙂 A couple testers reported back, they didn't notice anything that broke.
University of Pennsylvania has a nice test link, looks like all is well, at least on our test LAB Macs.
I posted this in the other thread, but I'll post it here in case it's helpful for anyone looking to identify what computers need to be patched. You may not have to create a new extension attribute.
Remember that if you capture plug-ins for inventory you actually already have the Java Internet-Plugin version without an extension attribute.
It's identified by the name: JavaAppletPlugin.plugin
Oracle version numbers are identified by Java 7 Update x (where x is the update). Computers with older Apple Java plug-ins identify with numbers like 14.0 or n/a for older Java installs.