The problem is that it only works on versions previous to ND6, as there have been changes to the field names on the Events form of the LOG.NTF database design. Basically, the Events field is now called EventsList.
I am not very familiar with C, nor do I have a compiler, otherwise I would give it a go to get it to work with ND6. I think only one line needs to be changed, but I could be wrong.
I’ve worked around this by creating a local replica of an ND6 log database and running and agent to create a new field called “Events” and set that field equal to the value of the “EventsList” list then run the clientlv utility against this database.
Do you know of a similar utility that will work with ND6, or if anyone has recompiled that Client Level Tracking utility to work with the ND6 changes?
Subject: Client Level Tracking is now built into ND6, so no more need for the tool.
from the help…REFERENCE
Update client information in Person record
Updates the Notes client license information as well as the Notes client platform, Notes client build, and the Notes client machine.
Triggered by: An incremental update in the client code. It is also kept up to date by dynamic configuration.
Carried out on: Administration server for the Domino Directory.
Carried out: Immediately
Result: Updates the Notes client license information as well as the Notes client platform field, Notes client build field, and the Notes client machine field.
I understand if I had all Notes 6 that the client information is held in the person document using ndyncfg on the client machine. However, I am particularly interested in finding those few 4.6 holdouts as well as those still at 5.0.x.
This is where that client level tracking app comes in so handy.