Unmanaged Assets - Possible BES Computer?

(imported topic written by SystemAdmin)

Hi all!

I understand from another (old)

post

that if an agent machine and an unmanaged asset have a matching MAC, IP, and hostname, it will be removed from the unmanaged asset DB.

If there’s a partial match, it will have hostnames in the “possible BES computer” column. I am not sure how partial the match has to be here - it would be good to know exactly how that’s determined.

If I’m thinking about this right, for sites using DHCP, and particularly those with a short lease, matching on all three as the only positive match to auto-remove an item is not really workable. Because the unmanaged assets here would also be on DHCP, we’re very likely to see the unmanaged asset say “possible BES computer” and it could be very wrong, depending on what is used to match.

I think for us a match on hostname and MAC address - neither of which are likely to change - would make managing the unmanaged assets list a pretty easy task.

How does this all work?

Thanks!

(imported comment written by kevin_friedheim)

Just to clarify: Possible bes computers are unmanaged assets that match on any of Hostname, IP Address, or MAC Address with a managed (bes) computer that exists in your deployment.

HTHs

(imported comment written by nberger91)

I have 100’s of IP addresses in ‘Unmanaged’ which report ‘No’ as a ‘Possible BES Computer’ however searching in the BigFix (bes computers) database/and console and I see the hosts listed by computername with the corresponding IP address. Why if there’s an IP address match, does ‘Possible BES Computer’ report ‘No’ ?

Should I being using the ‘Running Client’ table instead of ‘Possible BES Computer’ ? Additionally, does it matter if my BES clients arent used the default port ?

Are there any bugs in 8.1.551.0, or any tweaks to fix ?

(imported comment written by nberger91)

Why am I still seeing assets listed under ‘Unmanaged Assets’ where ‘Running Client’ = “no” in the regular bes computers db view. (where it is running the bes client) ?

Do i need to configure the nmap scan to detect bes client on the non default port (we are not using 52311) ?

(imported comment written by kevin_friedheim)

Upon installing the Import Service, the port through which we consider the TEM Agent to communicate is determined by the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\GlobalOptions.

You can check HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Enterprise Server\AssetDiscovery\NMAP\port to be sure that this port matches with the one you’re using in your TEM deployment.

HTHs