I've found that when the Client Information doesn't get updated properly, it's because either the Admin process didn't run against the request, or that the Admin process believes that someone else modified the person document, and it marks the request as failed. Probably when the Client's Password information is updated.

Open your Admin4 database, go to the Requests -> All Requests by Action view, and scroll down to 'Update Client Information in Person Record'. Open each twistie to verify whether the request was processed or failed.

If failed, you can mark the request to be processed again.

That has usually fixed THAT particular issue for me - almost 100% of the time. The only caveat is, you need to make the check a couple times a week, otherwise requests will fall off.

I've never found a way to force the Client to resend the information, possibly short of re-upgrading the client. I would suspect one could write an agent to submit the AdminP request, but have never looked into it.

My other problem has been with the usefulness of the information over the years. I've got clients (well, HAD clients) that had over 10 entries of mixed machine names, Notes versions and dates. Finally created a manual agent to wipe the info completely, then, when i think about it, I can wipe the fields and reprocess the AdminP request, which leaves me a clean, one line log of the user's configuration.

I just have the request. No response.

I checked around and normally the log.nsf is empty.

When I punch AdminP (Admin Process) to rerun everything (a dicey prospect at best if it never has run 'em), I get an odd message about needing to add DOMAIN= to the Notes.INI. Butbut, it's already in the server doc.

Does it still need to be in the Notes.INI?

I'm helping diagnosis, but not an admin on this particular server.

Thanks Mark,

I have looked in Admin4, but only one of the failed names are in there [see below] ? So the failed user updates from the last week didn't trigger any requests ?

What is even stranger (and relevant to your second point) our MACs are on DCHP and so get a different IP each time they log in - The machine then has this IP as part its name, so each time a MAC starts up and goes to LN it creates a new machine line in the Admin Tab.

The one of our effected MAC users [from above] had logged in today, with his new machine name - and it has processed successfully as 8.5.3 ??

There must be something in the client that is still thinking it is 8.5.3, even though everything around it is 9.0.1 !

Mike, I do have a line in my Notes.ini that specifies Domain:

Domain=<notes domain>

Open your Notes.ini in notespad, do a text search, and see if you have a similar line - maybe it's been made part of another line? Read thru with a fine tooth comb....

I HAVE had my notes.ini become corrupted (long time ago, knock on wood) and saw lines combined, almost as if it didn't see the CR/LF at the end of a line for some reason.

If you ever update Notes.ini manually, always make sure that there is at least one blank line at the end before saving.

http://www-01.ibm.com/support/docview.wss?rs=0&q1=1212699&uid=swg21212699&loc=fr&cs=utf-8&lang=&cm_mc_uid=08220163333514508050108&cm_mc_sid_50200000=1468502989

http://www.andypedisich.com/blogs/andysblog.nsf/dx/run-ndyncfgexe-while-the-client-is-up.htm?opendocument&comments

Part of the process was to move from the Lotus\Notes\Data Folder to the IBM\Notes\Data Folder.

So logic says the problem must come from here, as ID files, desktops and local address books are copied over.

Does anyone know where the trigger for the version update is stored and then passed to AdminP ??

From your last statement about the moves...  (oh, and none of your screenshots make it to the forum, by the way...)

I've done the same thing over time. When we upgrade a client to new hardware, we install Notes using the new directory structure, then copy the ID, names.nsf, journal.nsf (if there is one), desktop.dsk, backup copy of bookmarks.nsf (but let the install create a new bookmarks.nsf), user.dic, and maybe a couple other things i can't remember off the top of my head into the data directory and start Notes.

The notes.ini is created/updated from scratch.

When starting the client, names.nsf and other files should be updated from the new client, DCC should run which should cause the client to send the new Client info to the Admin process. See the links Barry posted. You should see that DCC has run from the client's logs.

I'm not sure exactly how to trigger the client to send the info again. I know that installing a fixpack will trigger it, so I'd supposed that un-installing the fix pack, re-starting the client might also trigger it. Then install the fixpack again. I haven't tested that, so don't know for sure.

Re: the MAC issues - II assume there is a Notes.ini for MAC users... What version does it have listed?

The MACs have a preferences file, not held in the data folder, but in a system folder with all the other app preferences files.  It is just a Notes.ini with a different name and location.

We have identified a 'friendly' user who will enjoy being part of the investigation.

Slowly coming out of this, it seems most (maybe all) of these users were 'early adopters' with Notes on a MAC, some have gone back to windows others continue with MACs.  So also possible is something hanging around from the early MAC days ?  One of them has had 2 new MACs built from scratch in last 2 years, but still the NAB is listing his old MAC OS and 8.5.3 in the NAB.

More questions than answers now !!  Does anyone have a spare carpet to hide this under??

I'll update any finding tomorrow.

No identification of the issue or fix found so far.  It is all vaguely pointing towards the early MAC LN builds.

Struggling with holiday season absences and lethargy (as it is all working fine from the users viewpoint), so may have to wait a few weeks to get the right people into one team to investigate.

I'll update here when we find something concrete

I have done a bit of digging and eliminated all of the windows / citrix users from my list.

All the Mac users on the list have a full section of 10 entries at the bottom of the Admin Tab in their Person Document.

So it looks to be an issue with our MACs that have filled all 10 available lines for Client details are not able to replace an entry with the 11th and subsequent entries.

The fact our MACs use the DHCP IP they get, when switched on as part of the machine name (Notes Client Machine) so they all will fill up regularly (even if I clear them now).

I'm not sure if there is a solution for this that I can implement, is it a know 'feature' of the Person Document ??