Domino Directory Client Classifications
I am currently involved in IT audits on companies deploying Lotus Domino products. I have been under the impression that the Domino Directory has 100% correct figures regarding the client classifications i.e. how many Designer users, Notes Messaging users, etc. However I have been receiving different opinions from collegues in our international offices. They believe the directory shows incorrect numbers of clients per Lotus product classification.
Have you heard or read any news that the directory is unreliable? If so do you know if it is version specific? I really need some reference data to back up any information you can offer. I really would appreaciate some help at your soonest convenience . . . .
Software/Hardware used:
Software/Hardware used:
ASKED:
March 13, 2006 7:03 AM
UPDATED:
March 13, 2006 7:30 PM
Answer Wiki:
This is configured on each client. To make this work, the support group would have to monitor which users are configured and work with them to set it up. See technote. I haven't read it recently, but it should give you the idea.
Lotus Software Knowledge Base Document
Title: Frequently Asked Questions About Dynamic Client Configuration (DCC)
Doc #: 1212699
URL: http://www.ibm.com/support/docview.wss?rs=899&uid=swg21212699
To see all answers submitted to the Answer Wiki: View Answer History.
The Rel 6 client together with Rel 6 server SHOULD update the person document with the current client build version etc. However, it is a bit flaky from my experience.
I had hoped to do exactly what you explain but I found it was unreliable. Sometimes the person doc is updated perfectly, other times it isn’t or worse, it is updated with duplicate values!
If push comes to shove you might try (as I did once), making a mod to the email template so a script is initiated on database open. There are properties of the Session class which provide the current user’s client version. You could incorporate into the script perhaps an email back to you with details of the client version in the email body. A bit of a pain but does work. Obviously you have to wait for users to open the email database in order to get the feedback.