The default schedule for Heartbeat Discovery is set to every 7
days. I typically set this down to every 1 day and know others do it even more
often. I would never recommend setting this to less than 1 or 2 hours
except in very small environments – there isn't really any value in doing so
anyway as nothing in the above list normally changes that frequently.
The Heartbeat Discovery also serves as a “keep alive” or “yes I am
alive” message from the client to the site server. Based on this, the Clear
Install Flag and Delete Aged Discovery Data maintenance tasks perform their
jobs. Note that the Delete Inactive Client Discovery Data does not
directly use the heartbeat time. Instead, Client Status Reporting (available in
R2 and R3), uses the last heartbeat time along with last hardware inventory,
last software inventory, and last policy polling time to determine if a client
is inactive. Once a client is marked inactive by Client Status Reporting, it is
then subject to the Delete Inactive Client Discovery Data task.
Whenever heartbeat discovery agent runs on the machine, it
provides us the below information
•
Is the client installed?
•
Client type (Legacy, Advanced, or Device)
•
Client version
•
NetBIOS Name
•
Character encoding used by the client
•
Default system locale identifier (typically representative of the
client’s language)
•
Date and time of the DDR
•
Date and time of last DDR
•
Short name of system
•
Currently logged in (interactive) user
•
FQDN of system
•
IP Network ID
•
Platform ID (this is an encoding of the OS version)
•
AD Site Name
•
IP Address(es)
•
MAC Address(es)
•
Domain name
•
Assigned (Primary) Site
•
Hardware ID
•
Identifying number (of the computer system)
•
Product name (of the computer system)
•
UUID (of the computer system)
•
Version (of the computer system)
