in my environment i use some heuristics like
if OS_PLATFORM is x86_64 and RSCD_DIR contains "(x86)" then probably it's a 32bit agent installed on a 64bit machine
7.6 and upper, have a server property named BUILD_ENVIRONMENT that contains x86_64 if the agent is 64bit
that should match OS_PLATFORM version
anyway the real question should be:
what does not work with a 32bit agent on a 64bit machine?
should we reinstall them properly?
if so, i think bmc could do us all a favour by putting an exit -1 in the 32bit installer if a 64bit OS is detected at runtime, so install guys won't do any mistakes anymore
The Processes tab in Task Manager displays Image
Name with suffix * 32 if the installed application is 32 bit on 64 Bit platform.
So, If an RSCD agent installed is 32 Bit, its Image Name should appear as "RSCD.exe *32" & "RSCDsvc.exe * 32".
If it appears to be "RSCD.exe" & "RSCDsvc.exe", then it is 64 bit installation.
Ideally, 32 Bit RSCD should work in compatibility mode on 64 Bit Windows box.
your metrics are indeed correct but not so suitable for building smart groups
aside from working in compatibility mode, does 32bit rscd have somewhat crippled functionality on 64bit windows?
It should not be. At least I did not observed
with the 32 bit agent I don't think you can manage or deploy and 64 bit apps or see into most areas of the registry (there is a separate tree for the 32bit apps created)
After reading all of your comments, in the end, we can conclude that there is no easy way to tell the difference that could be used to create reports or smart groups. Sad.
Thank you all guys. All of your input is indeed valuable.
don't be so pessimistic
the heuristic i gave you are 100% accurate for smart groups in my environment
My understanding is that if this registry key is present, then you have the 64-bit RSCD agent installed. If it is not present, you have the 32-bit:
While not something we use on a regular basis, I have set this up as a component template and used it in compliance jobs, and it did seem to be accurate.