SUA collects OS(operating system) and general software information into BF server. then generate several reports in our system. while the OS_MAJOR_VERSION field has invalid value input.
For instances, IBM AIX. with general scan tool ,it should be:
OS_NAME: AIX
OS_MAJOR_VERSION: 7.1
But BF collects as below:
OS_NAME: AIX 7.1
OS_MAJOR_VERSION: 2016-01-19-13.55.59.000000
latter OS_MAJOR_VERSION definitely is not a standard OS version, and won’t be part of a signature. thus this OS will be missing in report inventory system. wondering if this happens general with BF or just an exceptional incident.
seems not “uname” result.
Like rhel, bigfix return info “Linux Red
Hat Enterprise Server 6.7 (2.6.32-573.7.1.el6.x86_64)”, no idea how this
strings’re gathered,
because “uname” collects info like “Linux XhostnameXX 2.6.32-573.7.1.el6.x86_64 #1 XXXtimestamp***…x86_64 GNU/linux”,
and /etc/redhat-release contains “Red Hat Enterprise Linux Server release 6.7 (Santiago)” , which is similar but not same.
so back to original question, how does BF collect this info.
BTW, anyone knows if there’s local bigfix scan output locally on server ?
Different operating systems get the information from different locations.
RedHat systems get a combination of the name from the redhat-release file and the kernel information from uname and other C calls
AIX gets it from uname and other C calls
Windows gets it directly from the Win32 calls (the version number at least) and we form the name from that.
I’m not sure how you are getting the name in your original posting but the Console has a property that shows the OS name and I have never seen the form you are showing
oh, good reply.
my original posting was processed data within company system after (BigFix) client gathering.
Anyway thank you very much for detailed explanation. Alan .