Auto updates are a challenge for system admins. We like sameness. Same app. Same version. Same look. Same feel.
This impulse to control everything no doubt annoys some of our co-workers, but who cares? Our insecurity and narcissism must be appeased.
The setting that we need to search for is a registry value. We're going to use PDQ Inventory to scan all our company computers and search this particular registry path. The features we use in this example are only available in pro mode. (start trial)
The path is
The key for an enabled Java auto update is EnableJavaUpdate and the value is 1 (0x00000001).
Creating a Scan Profile in PDQ Inventory
In PDQ Inventory (start a trial) go to:
File > Preferences > Scan Profiles
Click the Add button. Name your new scan profile. Now it's time to add some scanners. (A Scan Profile is really just a container for different scanners). Select Registry. HKEY_LOCAL_MACHINE is the default hive. Enter the Path (copy from above).
Add another Registry scanner and this time use the path:
Click OK. The custom scan profile is now configured to search for Java auto updates. Simply scan all your computers to collect the info.
Show which computers matched the Java auto update
To see which computers returned positive for Java auto-update we will create a dynamic collection in PDQ Inventory.
In your filter, use the following:
All > Registry > Path > Ends with > JavaSoft\Java Update\Policy
Create a new filter and add:
All > Registry > Value Name > Equals > EnableJavaUpdate
Create one final filter:
All Registry > Value > Equals > 1
Following your inventory scan (started in the previous step) any computers that match that value will now be shown in this collection.
At this point you can use PDQ Deploy to make the change to all your computers. That will be covered in the next blog post. We'll link to it when it goes live.
Video of discovering computers with Java auto update enabled
See Shane and Lex cover discovering and disabling Java auto updates. (We recommend viewing in high definition.)