Aastra 6725ip and Polycom cx600. I want to upgrade firmware without using lync server. I want to use both phones for Skype business. Anyone can help me with steps how to upgrade firmware and how to make them work on Skype business. Moved from: Mobile Devices / Other Windows mobile devices / Software update / Other/Unknown. This entry was posted in Lync and tagged Aastra 6721ip, Aastra 6725ip, cx3000, CX500, cx600, firmware update, HP 4110, HP 4120, LG-Nortel IP Phone 8540, Lync 2010, lync 2013, Microsoft Lync Phone Edition, polycom, powershell on May 16, 2013 by Jack. Aug 07, 2012 Hi, please update firmware with Microsoft Lync 2010 Phone Edition for Polycom CX700 and LG-Nortel IP Phone 8540. Best regards, Tuesday, November 23, 2010 7:21 AM.
Configuration of Device Updates for Lync Server 2010 and 2013 is pretty much straight forward. Device Updates are controlled by the Front End server web services and it use the Lync File Share to distribute the firmware update files.
The Lync File Share has to be configured with read/write access to everyone so that the devices can fetch the device update files and put log files in to the Device Logs folder.
To start the process, download the device update file from Microsoft site. once downloaded, run the UCUpdates.exe file
Specify a location to extract the cabinet file which contains the update bits. click on Next to proceed with the installation.
Navigate in to the given folder and notice that the ucupdates.cab file is saved in the folder
Run the command,
Import-CsDeviceUpdate -Identity service:WebServer:lyncpool.contoso.com -FileName C:SoftUCUpdates.cab
To import the update files in to the Lync Server 2013 web server platform and go in to the Lync Server Control Panel and check the Device Updated in Clients tab. there should be bunch of update files appeared for Polycom CX series devices.
Go in to the Lync Share and navigate in to the 1-WebService-1DeviceUpdateStore and verify that the device updates files are populated in respective folders and ready to be picked up by the devices.
Configure a test device to test the update and to verify everything's in order before updating the rest of the phones. go in to the 'Test Device' tab and configure the MAC ID of the device
Once committed, It'll take up to 10 minutes for the device to pick up the update or a reboot of the device will instantly pick up the update file. do not try to use the device while the update is taking place.
The device will stop responding for a while and re boot upon the completion of the update.
I recently received two 'original' Tanjay (Polycom CX700) phones from a colleague asking me if I could get them upgraded to Lync. These contained beta Phone Edition software on them: 1.0.199 (1.23)
Since this was pre-OCS R1, I really wasn't interested in installing OCS R1 and configuring the awful WSS method to update devices. I know for a fact, that you cannot directly upgrade these to Lync firmware, so all of my hopes were being able to perform the first couple of upgrades using an OCS R2 server.
I started searching the Internet for tips and came across a guide that addressed my exact need! Rick Varvel wrote this very detailed guide that explained the process of getting the beta firmware to an OCS R2 firmware. Once on an OCS R1/R2 firmware, I knew I could easily get it to Lync firmware since either version can be upgraded directly to Lync.
I won't go into too much detail since the guide is very detailed itself. You must follow this guide exactly! I actually skipped a step that made my first couple of attempts fail. My OCS R2 deployment was internal only so I thought I could get away with not setting the External URL settings for the Device Update service. As the guide says, you must configure the ExternalUpdatesDownloadURL and ExternalUpdatesStoreURL to a non-NULL value. Once I did this, the updates started flowing.
The high-level update process was as follows:
Aastra 6725ip and Polycom cx600. I want to upgrade firmware without using lync server. I want to use both phones for Skype business. Anyone can help me with steps how to upgrade firmware and how to make them work on Skype business. Moved from: Mobile Devices / Other Windows mobile devices / Software update / Other/Unknown. This entry was posted in Lync and tagged Aastra 6721ip, Aastra 6725ip, cx3000, CX500, cx600, firmware update, HP 4110, HP 4120, LG-Nortel IP Phone 8540, Lync 2010, lync 2013, Microsoft Lync Phone Edition, polycom, powershell on May 16, 2013 by Jack. Aug 07, 2012 Hi, please update firmware with Microsoft Lync 2010 Phone Edition for Polycom CX700 and LG-Nortel IP Phone 8540. Best regards, Tuesday, November 23, 2010 7:21 AM.
Configuration of Device Updates for Lync Server 2010 and 2013 is pretty much straight forward. Device Updates are controlled by the Front End server web services and it use the Lync File Share to distribute the firmware update files.
The Lync File Share has to be configured with read/write access to everyone so that the devices can fetch the device update files and put log files in to the Device Logs folder.
To start the process, download the device update file from Microsoft site. once downloaded, run the UCUpdates.exe file
Specify a location to extract the cabinet file which contains the update bits. click on Next to proceed with the installation.
Navigate in to the given folder and notice that the ucupdates.cab file is saved in the folder
Run the command,
Import-CsDeviceUpdate -Identity service:WebServer:lyncpool.contoso.com -FileName C:SoftUCUpdates.cab
To import the update files in to the Lync Server 2013 web server platform and go in to the Lync Server Control Panel and check the Device Updated in Clients tab. there should be bunch of update files appeared for Polycom CX series devices.
Go in to the Lync Share and navigate in to the 1-WebService-1DeviceUpdateStore and verify that the device updates files are populated in respective folders and ready to be picked up by the devices.
Configure a test device to test the update and to verify everything's in order before updating the rest of the phones. go in to the 'Test Device' tab and configure the MAC ID of the device
Once committed, It'll take up to 10 minutes for the device to pick up the update or a reboot of the device will instantly pick up the update file. do not try to use the device while the update is taking place.
The device will stop responding for a while and re boot upon the completion of the update.
I recently received two 'original' Tanjay (Polycom CX700) phones from a colleague asking me if I could get them upgraded to Lync. These contained beta Phone Edition software on them: 1.0.199 (1.23)
Since this was pre-OCS R1, I really wasn't interested in installing OCS R1 and configuring the awful WSS method to update devices. I know for a fact, that you cannot directly upgrade these to Lync firmware, so all of my hopes were being able to perform the first couple of upgrades using an OCS R2 server.
I started searching the Internet for tips and came across a guide that addressed my exact need! Rick Varvel wrote this very detailed guide that explained the process of getting the beta firmware to an OCS R2 firmware. Once on an OCS R1/R2 firmware, I knew I could easily get it to Lync firmware since either version can be upgraded directly to Lync.
I won't go into too much detail since the guide is very detailed itself. You must follow this guide exactly! I actually skipped a step that made my first couple of attempts fail. My OCS R2 deployment was internal only so I thought I could get away with not setting the External URL settings for the Device Update service. As the guide says, you must configure the ExternalUpdatesDownloadURL and ExternalUpdatesStoreURL to a non-NULL value. Once I did this, the updates started flowing.
The high-level update process was as follows:
OCS R2 Update Service
- 1.0.199 (1.23) –> 1.0.522.101 (1.23)
Lync Server Update Service
Polycom Cx700 Firmware Upgrade Lynching
- 1.0.522.101 (1.23) –> 4.0.7577.296 (1.23)
Polycom Cx700 Microsoft Teams
Now my newly updated CX700 shows the latest Lync firmware:
Polycom Cx600 Phones User Guide
I know this post won't help out too many people unless they find a dusty closet with a bunch of phones in it, but thought I would document the experience any way.
