We are running IPCCX 4.0.4sr1. The server was added to the domain upon installation to prevent a documented login problem with CAD and domain users (TAC says is not an issue any more since 4.0). Due to domain policies the supervisor is unable to login using the Historical Reporting client unless it uses the domain admins credentials to login and the customer does not want to give her admin rights on the PC. Domain policy will not allow her to login to the local PC instead of the Domain. TAC says I should remove IPCCX from the domain. Are their any work arounds? If not what is the process to remove from the domain? Will this be a reinstall?
Well, actually the above was the cleanest solution.
I was sort of trying to consider everything that would cause the CRS to fail when the server itself is removed from a windows domain.
- CRS services - run by LocalSystem
- CRS node manager - run by .\CRSAdmin (local account afaik)
- The CRS itself is more-or-less Java based, this has nothing to do with Windows domain
- controlling callmanager stuff (CTI route points, CTI ports) - is done by accounts in LDAP - nothing to worry about here
So... if I were you, I would definitely give it a try. Your customer needs a working solution: the best way is to reinstall everything. But before that, you could try just removing the server from the domain. If it fails: reinstall. If it doesn't, test it thoroughly.
Please post your findings, this is a very interesting matter (no pun intended).
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.