Machines in Unmanaged assets already have agent on them

Usage and Config
1

(imported topic written by rharmer91)

I was told that machines couldn’t exist in both Unmanaged assets and Managed… When I put the IPs in for the XP machines in Unmanaged assets, about 90 percent of them have the agent running on them.

?!

Rich

2

(imported comment written by jeremy_spiegel91)

If the machine is not listening on the BES listen port (52311), then we assume that the agent is not running on that machine. As an extra check, when unmanaged asset data is inserted into the database, we look for BES computers with matching identifying information (IP address, MAC address, and hostname). If an exact match is found, the unmanaged asset is assumed to be managed and not added to the database. If one or two of the pieces of identifying information if found, then we tag the unmanaged asset with the name of the “Possible BES Computer”, which you should see as a column on the Unmanaged Assets tab. This is the behavior in the version of the importer that was recently released. If you haven’t upgraded yet, there should be a relevant task in the Asset Discovery site that will do the upgrade.

3

(imported comment written by BenKus)

Hey Rich,

It sounds like maybe there is some sort of error with the Asset Discovery configuration that isn’t properly identifying that the computers have the BES Agent installed.

We can take a look at it and resolve it, but you should start a trouble-ticket with our support team.

The way it will work when the issue is resolved is:

  • You will see network devices.
  • You will see computers with the agent stopped (with a note that there is a BES Agent on the computer that is not running).
  • You will see computers without the agent installed.

Ben