SSO first and foremost means you have some kind of consistency between logins.
There are several questions you need to answer:
1) Are user IDs the same on the PC and call manager?
1a) If user IDs are not the same, how do you get from the windows user id to the phone user id?
2) Are passwords synchronized
2a) If not, how do you want to handle the password thing? Do you want it to be stored somewhere on the user PC, or do you want to e.g. go by the NTLM authentication you can do with an IIS webserver that's in the same domain and then just not ask for a password, or what other means do you want to use for the password (you could just send the user ID of the user currently logged in on the PC.. then via 3 get the phone, and look up the user password via some other means)
3) How can I associate a user ID with a phone?
4) If the answer to 2a was other means.. then how do you handle the scenario where the user changes his password?
Those are questions that pop into my mind when I hear SSO and call manager. If you have CCM 5.0, you can synchronize - not integrate - your CCM with your active directory and your logins and passwords will be synchronized, making things a little easier.
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.