So this may be a quick one for everyone here. We recently upgraded to 14.2.2 and the phonebooks are all up and running but on the client end, old user addresses (most likely from history) are showing. We cant seem to clear these out of the individual clients. This is on both PC and MAC. Attached is a picture of the Jabber Video phone book. All of our users are firstname.lastname@example.org, .movi is a carry over on the client itself from the previous version of tms 13.2.1, when we upgraded we created a new DB and our new TMS was fresh and we had to build from scratch (on purpose). .Movi is not coming from the phonebook source, just the client.
Interesting this seems to be occuring on alot of users. A major problem we have noticed is if I move someone in and out of AD security group, the phonebooks will not show up for at least a day if not two, even after everything is properly updated.
Keep in mind we have over 1500 jabber video users and the caching is happening on a good amount of them.
We figured this out... to a point. We went back and cleared all of the Jabber phone books and re added them (sources and all). Once this was done the old entries dissapeared but over time when names changed it would not update on time but eventually it would. We found out there is a hard code time for Jabber video and provisioning extension based units to update their information and it is sometime around 3AM. The rest of our duplicates and old data was able to be cleared on clients themselves, mostly favorites and history that would show up when we were typing in a search. This can be done from the settings icon on the clients themselves. Took a little time but we got it. Also endpoint favorites turned out to be a big culperate of holding onto the old information. Clear all of those and you will be in the best possible standing until the bugs are fixed.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.