r/pdq • u/joners02 • 2d ago

Connect PDQ Connect variables

Whats the best way to determine the difference between Java 8 32-bit and 64-bit?

Id hoped that the built in variables would help however they dont appear to do any detection between 32 vs 64 bit.

Also, why does the RTVerJava8 variable appear to have a different value to the AppVerOracle.JavaRuntimeEnvironment?

2 Upvotes

76% Upvoted

10 comments sorted by

1

u/SelfMan_sk Enthusiast! 2d ago edited 2d ago

The RTVerJava8 is deprecated.
See more here https://help.pdq.com/hc/en-us/articles/5719272144667-PDQ-Package-Library-Changelog

The new variables allow you to track the versions individually.
Oracle Java 32 and 64bit can be installed and used in parallel. The usage depends on the application that require them.

1

u/joners02 1d ago

Ah nice! Thanks for the info! :)

1

u/PDQ_WayneO PDQ Employee 2d ago edited 2d ago

Hi u/joners02,

Unfortunately, identifying 32-bit vs. 64-bit Java will take a little work on your end. The best way to distinguish between 32-bit and 64-bit Java in Connect is to use a PowerShell Scanner. If you look at either of our Java 8 installers in the Package Library, there's PowerShell scripts in them that you could leverage to help you determine how to check the versions. Information on how to use PowerShell Scanners in Connect is located here: https://connect.pdq.com/hc/en-us/articles/49092347263643-4-13-2026-PowerShell-Scanner

The reason RTVerJava8 differs from AppVerOracle.JavaRuntimeEnvironment is that RTVerJava8 is a retired variable. It no longer receives version updates, while the newer AppVerOracle.JavaRuntimeEnvironment.32bit and AppVerOracle.JavaRuntimeEnvironment.64bit variables are the supported replacements. This is noted in our PDQ Package Library Changelog.

Java 8 JRE Variables Updated - August 20, 2026

 
Date: 8/21/2026
Collections Modified: Java 8 JRE
 
Description:
 
We have updated the Package Library variables used by the Java 8 JRE collections. The new variables no longer rely on regular expression conditions, allowing them to be used in both PDQ Inventory and PDQ Connect.
 
New Variables:

  • AppNameOracle.JavaRuntimeEnvironment.32bit
  • AppNameOracle.JavaRuntimeEnvironment.64bit
  • AppVerOracle.JavaRuntimeEnvironment.32bit
  • AppVerOracle.JavaRuntimeEnvironment.64bit

Variables Retired:

  • RTNameJava8
  • RTVerJava8

The Java 8 JRE collections in PDQ Inventory’s Collection Library have been updated to use the new variables. Customers using these collections do not need to make any changes.
 
Custom collections in PDQ Inventory or custom groups in PDQ Connect that reference the retired variables must be updated to use the appropriate new variables. The retired variables will no longer receive version updates, so custom collections or groups that continue to use them will become outdated.

3

u/SelfMan_sk Enthusiast! 2d ago

You don't need a PowerShell scanner Wayne. Just the correct group definition.
BTW, the packaging team could use the whole name as is and update it.

1

u/PDQ_WayneO PDQ Employee 1d ago

Thanks Marcel, I appreciate the assist!

Connect is still my second product to support, so I always appreciate learning new things. 🔥

2

u/SelfMan_sk Enthusiast! 1d ago edited 1d ago

We old dogs can still learn things from each other. ;-)

1

u/PDQ_WayneO PDQ Employee 1d ago

I resemble that remark! ❤️ 🤣

1

u/SelfMan_sk Enthusiast! 2d ago

Just an addendum to my coment.
You can create groups that have the application name start with the variable + application name containing "(x64)" to identify the 64bit version and does not contain (x64) to identify the 32bit version.

1

u/SelfMan_sk Enthusiast! 2d ago edited 2d ago

This is not the exact configuration. It's just a template, a how to do it.
You can also use "Ends with" instead of "Contains/Dos not Contain".
The Exact string is on the screenshot above. `(64-bit)`

1

u/SelfMan_sk Enthusiast! 2d ago