I have about 200 users in the company that are showing no information in the Administration section of their person document under the Client Build section. I have just performed an upgrade of everyone in the company to 8.0.2 and these users still have no information in their person doc for the client build. Anyone have any info regarding this?
Subject: Finding my way
Still not sure what the issue is but this is getting closer
Problem
An administrator has removed the data from the fields in the Client Information section on the Administration tab of a user’s Person document. The Admin reauthenticated with the server and also tried running the Ndyncfg task, but neither approach updated this information. How is this information repopulated?
Cause
Solution
The client information in the Person document is populated by the Dynamic Configuration task when it notices that the client has been updated to a later release. The client release information is stored in the INI file on the workstation with the parameters “Setup =” and “DYNINFOCR_…”
If the values of these parameters have not changed, the Ndyncfg task will not make an AdminP request to update this information.
An enhancement request for additional Admin functionality has been submitted to Quality Engineering as SPR# KTOT5HTVC4, which would allow you to request that the client information be updated, regardless of whether the INI parameters indicate it as necessary.
Workaround:
If the DYNINFOCR_… entry is removed from the Notes.INI, the next time the user restarts the Notes Client and authenticates with their home mail server, then an Admin request will be made to repopulate the client information. The DYNINFOCR_ entry will be repopulated at the same time.
Additional Troubleshooting:
If the workaround does not yield the expected results, be sure to check the value of the InstallType parameter in the Notes.INI. If the value is not one of the client parameters (0, 1, 2, or 6), then this will also prevent the AdminP request from being issued because the system is not recognized as a client. For details on the various InstallType codes, refer to the document titled " What NOTES.INI Install Settings Are New to Domino 5.x?" (# 1098221)
If all the above steps have been followed on the client, and the Notes Client build field is still blank, then try the following:
-
Open the Admin Requests (Admin4.NSF) database on the user’s home mail server and open the “all requests by name” view.
-
Search for the user’s name; if the name is not there, the problem is on the client, and we should troubleshoot the DCC further.
-
If the user’s name is there, expand it and see if there is a request to populate the Notes Client build. There may or may not be a response document:
a) If there is no response document, and the request has a lightning bolt, then replicate this Admin4.NSF to the Admin server for the Domino Directory. The Domino Directory on the Admin server should then show the client build in the Person document. If not, then run AdminP command Tell AdminP Process Now.
b) If there is a response document, either an X or a green checkmark, then there is an issue with AdminP not functioning properly, or the field in the Person document cannot be updated by the server or the originator of the request. The same applies if the user’s home mail server is the same as the Admin server for the Domino directory.
Supporting Information:
Note that, if the Setup= line of the Notes.INI is not populated correctly, this can also create instances in which the Client Information will not be updated correctly.
The Client Information section is made up of the following descriptions and corresponding fields:
Notes Client License - ClientType
Notes Client Machine - CIntMachine
Notes Client Platform - CIntPltfrm
Notes Client Build - CIntBld
Related information
What NOTES.INI Install Settings Are New to Domino 5.x?
Historical Number
197699
Product Alias/Synonym
Lotus Notes Client
Subject: Six possible causes for missing client info
The recording of client information in Domino Directory person documents got introduced some time around Notes R5 or Notes 6. The mechanism for this is a combination of ndyncfg.exe (aka Dynamic Client Configuration, aka DCC) on the client side, and AdminP on the server side.
If you don’t see this for some users, here are the causes that I’d be looking for:
-
Maybe these people no longer use Notes and never got deleted from the directory. If they haven’t used a Notes client in a very long time their person docs will never have been updated.
-
Maybe they are current but just use a client version that’s earlier than when this functionality was introduced (an early R5 client, perhaps). Let’s hope it’s not this cause.
-
Maybe they are current but use some non-Notes client. There are a dozen or more ways to access mail on a Domino server without using Notes (iNotes, POP3, IMAP, DAMO, Blackberry, Traveler, other mobile products, etc). If these users only use alternative access methods, then its unlikely any AdminP request will ever have been triggered.
-
If you’re sure that they’re current Notes users, then maybe DCC isn’t running on their machines. There are various reasons to disable this (via Notes.ini), but generally it’s better enabled as you’ll need it to use client policies. Search on DCC in this forum, the 6 and 7 forum, and the support Tech Notes for copious detail.
-
If DCC is enabled, maybe the Administration process is broken in your domain. Admin Requests to update Client Build data will be created on the user’s mail server. If ADMIN4.NSF on the mail server isn’t replicating with the one on the admin server for your doamin, then they’ll never get updated. Same if the two DBs aren’t replicas, or if the ACL prevents updates from the mail server.
-
Maybe you haven’t waited long enough. Actually, I’m pretty sure that’s not your cause, but for completeness, people should be aware that for the Client Build info to appear there needs to be time for DCC to detect the need for the update and generate the request (generally on the next client restart), then for the Admin Request to replicate to the admin server for the Domain (depends on what you’ve set up), for the server to process the request (should be almost immediate, but depends on load) and for the Domino Directory to replicate to whichever server you’re viewing it from (again, YMMV).
Let us know what you find out,
Rupert Clayton
Chicago