This posting is provided "AS IS" with no warranties, and confers no rights.The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway. Please use the Microsoft Forums for support requests.
I recently had to upgrade 2 LG-Nortel IP Phone 8540 (aka Tanjay or OCPE) to the latest firmware available: Microsoft Office Communicator 2007 Phone Edition v1.0.522.101.
The device was running version 1.0.199 (1.23) of the software which was still a Beta version and had, of course, some annoying bugs.
So, how do you upgrade one of these babies? You use Microsoft Office Communications Server 2007 Software Update Service, a kind of WSUS specific for UC devices. I'm not going into details about deploying this service, for that please read Microsoft Office Communications Server 2007 Software Update Service Deployment Guide.
After you setup the OCS Update Service, you just need to turn on the device, sign-in and hopefully the device will automatically upgrade (there are a couple of additional steps, like preparing the infrastructure and approving the update, but let's keep it simple for now).
To sign-in, you must provide 3 things:
My problems started here, I couldn't even sign-in, because the device didn't accept the certificate that was issued with my private Enterprise CA (BTW, using private certificates is 100% supported, as long as you publish the Root CA in Active Directory. I blogged about it recently and Jens Trier Rasmussen also has a great post about the subject).
The error message was "Cannot validate server certificate".
Let the troubleshooting begin:
What else could I do? I was about to send the devices to LG Nortel when I tried a different approach: changing the format of the user name at the sign-in window. Do you know what? IT WORKED!
If you have Beta Tanjay devices running version 1.0.199 of Communicator Phone Edition and don't seem to get it working, try to change the user name to one of these formats:
as opposed of using DOMAIN\user.
I'm now running version 1.0.522.101 that besides some bug fixes, it also supports R2!
Jens wrote a great article that could potentially be related to this issue: When do you need to use DHCP option 119 with OCPE powered devices?
After reviewing my environment, I confirmed that DHCP option 119 was in place, so the problems I had were probably due to some bug in the beta version.
Every OCS deployment needs the appropriate clients rolled out to the users. There are 3 client programs that almost every OCS solution must have:
Since there has been some upgrades and patches to the RTM versions of these programs, I thought I could provide the latest download links to them.
This program is not free, so first of all you should download it from Microsoft Volume Licensing Services site (assuming you have a volume license agreement).
Next, you should apply the October 2008 hotfix, which will fix some issues (this update is needed in order to interoperate with OCS 2007 R2).