Ip communicator error updating locale
When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently.
Alert Comment Messages Alert Messages Archive Manager Messages Archive Manager Errors Comm Cell Migration Comm Net Alert Comm Net Browser Comm Net Licensing Comm Net QSM Comm Net Registration Comm Net Scheduler Common Event Messages Comm Serve License Manager Data Set Manager Content Indexing Data Pipe Communications Service Remote Exec Client Install Manager Library and Drive Configuration Media Management Service Network Module Connection Manager SAN Volume Configuration Meta-Data Database Data Classifier Client Documentum i Data Agent Datamover Comm Serve Disaster Recovery External Data Connector Ev Archive Manager Ev Library Controller Ev Media Manager Event Manager Client Event Manager Server Restore i Data Agent Firewall Port Reservations File Replication Messages Backup i Data Agent File System Backup i Data Agent File System Restore i Data Agent General GUI Audit Operations GUI Audit Parameters GUI Messages Index Manager Scan Module Informix i Data Agent Image Level i Data Agent Job Manager Service Lotus Notes Media Library Manager Media Manager Messages Media Manager Errors Media Manager Media Manager Events MS Exchange Backup i Data Agent MS Exchange Restore i Data Agent MS SQL i Data Agent My SQL i Data Agent NAS Client Wizard i Data Agent for NDMP 1-Touch Messages Oracle i Data Agent Pass Thru Patch Platform Information Module Postgre SQL i Data Agent Comm Net Replication Client Reports Simple Data Transfer Pipeline Software Installation Manager SRM Advice Locale SRM Error Locale SRM Locale SRM Report Locale Sybase i Data Agent VSB Locale Comm Net Server could not connect to QSMCell. QSMCell version is older than 5.9.0 QNet New Line 2.
Previously the only supported devices that used the Office Communicator Phone Edition client were the Microsoft reference-design “Tanjay” family of devices: the Polycom CX700 and LG-Nortel IP8540.
Both phones were identical and used the exact same software so a single installation package was distributed and updated on a regular basis.
If the Lync Server environment is prepared correctly to support standard operation of the devices (detailed in this previous article) then the following process can be used to prepare, test, and update devices.When working with Tanjay devices the Lync Server Client Version Policy by default blocks clients running version 1.0.196 or older.These are very old beta versions that I have not even had my hands on in a long time and unfortunately cannot test upgrading them directly against Lync Server.My advice is to upgrade these using an OCS environment with this process documented by Rui Silva. As with all software updates it would be prudent to first test one a single device before blasting it out to all of the phones in the organization.If a device has the slightly newer beta version 1.0.452 or 1.0.522 then this process also documented by Rui can be used. The Test Device configuration in Lync Server allows for a single device to automatically download the latest version of the software available regardless of whether it has been approved yet or not.