Here is the working solution. While it is unsupported and will cause high CPU on the CallManager it can be used for testing UDS but not production. I tested this with Jabber for Windows 9.2.4 and a couple other 9.2.x versions. The recommendation is to review the newer versions of Jabber and CallManager 10.5 for UDS/REST performance improvements or use LDAP. But here I was stuck and needed a solution.
Create a file named jabber-config-user.xml and place into %appdata%\Roaming\Cisco\Unified Communications\Jabber\CSF\Config\
My understanding is that 9.2.0 supported UDS, then they started getting TAC cases about 100% CPU due to UDS, so 9.2.7 and 9.6 pulled all support for UDS while they re-wrote the REST APIs, and re-introduced with improved performance.
So dis-regarding whether cisco supports UDS, can I make the 9.2.x client use UDS anyhow? via the jabber-config-user.xml ? It's only 40 users on this cluster and they don't have LDAP/AD. . I doub't we can touch the CPU on the server with so few users.
Or did the developers remove the functionality of UDS from all versions of 9.2.x in the C++ code is a better question?
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.