We moved a user to a new certifier in Domino. Ran the STNamechange utility to reflect the change all the tasks ran fine, however the persistent chat for the user has gone. I would assume that Mongo needs something else ran on it to associate the old name with the new name as a separate task but I can't find anything for this.
Has anyone come across this before?
Please open a case - we may need to provide you a different utility to cover this scenario.
I assume you used the new database utility to do the name change, is that correct?
Hi Tony,
This is version 11.6 and we used the stnamechange.nsf utility to complete the name change. We have not completed anything else apart from the Domino change obviously.
Hi Richard -
The namechange utility in 11.6 does not touch anything in MongoDB where the chatlogging data is stored. Since it is stored according to the users DN, this explains why you are not seeing it.
Please open a case so that we can discuss how the new v12 utilities might be useful for you.
For example, see - https://help.hcltechsw.com/sametime/1201/admin/t_namechangeutility.html
But I don't believe that will cover a certifier change, as that is something you want to do to 'all' records with a single script (assumed).
Thanks for getting back to me Tony,
I am a bit confused. The mongoDB exists in ST 11.6 as it is required for persistent chat as this was when it was introduced. Are you saying there was no way to do a name change of a user in this version of Sametime?
I looked at the link you sent but that seems to be just for the containerised version (12) of Sametime. The MongoDB install for this 11.6 ST Server is on Windows so I can't see how I can use that. The cert change is actually only for 2 users so in theory using a csv file as per the new utility would have worked if it was on 12.
Right - the NameChange utility in 11.6 (and prior) only worked with VPUserInfo.nsf - where the contact list was stored. It had no MongoDB capabilities, so we would have to run a mongo query/statement to update the chatlogging information separately.
The new database utility will still work against a Windows based MongoDB, since it connects to it via a mongoURL, but you would need to run it on a host where you can run docker.
I do wonder if the utility would work for your scenario, since it (the utility) will also be looking for VPUserinfo data, and it would not exist.
Open a case and I can help you work out a mongo query to resolve this.
OK thanks Tony I will open a case.