Sorry I had not updated this but thought I would also share my experience. From this post that @Alexander Novak sent and Tony's input I did manage to run this properly -
- check stnamechange.nsf for namechange tasks > remove all open
- create a new csv file with the only one entry LDAP
- import the new csv file into stnamechange.nsf
- add the following two parameters to your sametime.ini for better stnamechange debugging/infos > will create a <domprog>/trace/stnamechange_date.txt
> section [Debug]
VP_NCSA_TRACE=1
> section [Config]
NC_LOCAL_CONVERSION=1
- stop your Domino Server > there is a change since Domino 11.0.1FP3 to start Domino process outside from Domino, but if the server is stopped you should be able to run the stnamechange in a command window
- change to domino program folder and enter the following parameter > please add domprog and domdata path otherwise it could be that the script will not find the correct paths
> stnamechange.cmd <domprogpath> <domdatapath)
e.g c:\hcl\domino>stnamechange c:\hcl\domino c:\hcl\domino\data
It turned out my assumption that you can only run this once when it works was correct which was why I was seeing an error when I tried to run it again.
After this I started the new server and all was fine, (you can actually run the original Sametime server and the new 12 server side by side and login to both to check it works.) The issue I then ran into was at this point there was no way to migrate the chat history sat in mongo. My migration was put on pause because of this until recently. Also most of my customers do not want to deploy Sametime in Docker and do not want to go away from having the chat service in a stand alone Domino server so there was no rush.
Recently I have managed to successfully use the mongo migration script for the chat history that was released with 12.0.1 however as a company we are still running the old instance at the moment due to as I said our customers not wanting to migrate over.
To use the convert script I actually did the following as the documentation didn't actually work for me:
BackUp and Restore MongoDBs onto new server (this is because we created a new mongo environment for the new Sametime12 build, it also means we can run the old and new servers side by side for testing before DNS switch over)
Install Mongosh if not already installed (it is a requirement for the script to run)
change to the sametime build directory /utility/ConvertDominoDirectoryToLDAP
mongosh
use admin
load("convertDominoDirectoryToLDAP.js")
This runs the change command across the mongodbs and we could then see the chat history in the new environment.