This has happened to me in some cases, usually due to there being an unusual kernel in use that trips up the BigFix Client/Agent detection of the OS.
This is actually more likely to be a problem with Ubuntu/Debian specifically than RHEL family due to the way the agent does the detection, which is more likely to fall back to
/proc/version on Ubuntu/Debian.
I’ve asked for the failback for OS detection to be handled differently to address this.
I see this especially with docker containers that share a kernel with the host rather than have their own.
I also see this with Windows 10 WSL containers.
I suppose this might also be the case for some kinds of virtualization, but in most virtualization the VM has it’s own kernel, so that would just work in most cases.
I should follow up on this, I think we may already have an internal enhancement request for this.
You might also want to try the newest version of the agent to see if it has a fix.
- Can you provide more info about these systems?
- Are they containers or virtualized?
- If so, what technology is used?