| |
Bind View Helpful Hints
Here are some helpful hints using Bind View NETInventory.
 | Useful Fields to Include. |
Last Audit Login Name
Last Audit Login Full Name
Last Audit Date
Node Address
Node Name Same as Last Audit Login Name?
 | Last Audit Login Name is the login ID the machine was logged in as the last time it was
scanned. This can be different from the Node Name. The Node Name is the login ID that was
used when the machine got scanned for the first time. So, if the ID that was used for the
initial scan is not the usual ID, there could be a difference. |
 | Last Audit Login Name provides the full name of the login ID. This requires that there
is a full name entry in NDS for that ID. |
 | Last Audit date can tell you how recent the scanned information is. Remember that the
users must login for the scan to take place. If there are users that leave their machines
logged in overnight, they will not get scanned the next morning. |
 | Node Address is the only useful data that actually represent the physical machine
(Unless the network card gets changed). The Node Name does not necessarily point to a
machine, it only tells you WHO was logged in, not WHAT was logged in. We recommend that
you always include the Node Address with any report for that reason. |
 | Node Name Same as Last Audit Login Name? is a YES/NO field. We recommend that you run
this regularly to reconcile the differences between Node Name and Last Audit Login Name.
Just create and run a grid with the following fields: |
Node Name
Last Login Audit Name
Node Name Same as Last Audit Login Name?
Last Audit Login Date
Node Address
Filter on Node Name Same as Last Audit Login Name? with Is Not True and Is <N/A>.
This will give you a report on any Node Name entries that do not match with the Last
Audit Login Name. You can at this point, double click on the field on the report and
change the Node Name to the proper name.
|