Updating Lync Phone Edition Devices

By default an installation of Lync Server does not contain any pre-installed or pre-approved updates, this must be performed manually by an administrator.  This is basically the same process as was used in Office Communications Server except that now there are multiple update packages, which on the surface appear to be identical.  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.

Lync Server 2010 now has multiple versions of the update package, as they are both different clients (with different interfaces and features) as well as different device designs between vendors.  The Lync Phone Edition client now has two different interfaces. First, the original touchscreen-based client which started in OCS on the CX700 and was updated for Lync.  This client looks nearly identical to the previous version but has a few tweaks (most prominently a Lync Server branded background). Secondly there is a brand new Lync Phone Edition client which only runs on the new Aries family devices: the Polycom CX500, CX600, CX3000 and Aastra 6721ip, 6725ip. Although the client features are identical between the Aries devices the firmware is unique between the different manufacturer’s devices in order to support differing hardware components and physical features. So there are now three separate packages which can be downloaded: one for the original Tanjay devices, a second for Polycom’s Aries devices, and a third for Aastra’s Aries devices.  These packages unfortunately are all identically named as ucupdates.exe so be careful when downloading more than one at a time.

Additionally Microsoft plans to release new versions of the Lync Phone Edition client quarterly as Cumulative Updates (CU).  Just last week CU1 was released and CU2 is slated for release in Q2 2011.  These are not service pack type updates but are instead the full client repackaged as a single firmware.  Previous releases for the same device family and edition are then taken offline so that only the latest edition is typically available at any given time (previous URLs will be forwarded to the latest editions as well).

This table contains information on the latest updates as well as the most common past editions, including links to download and versions which are still available on the Microsoft Download Center.

Version Date System Details Size KB Article
1.0.199   OCS 2007 Beta Beta version pre-installed on some devices.  Not available for public download.    
1.0.452.0   OCS 2007 Beta Beta version pre-installed on some devices.  Not available for public download.    
1.0.522.101 7/30/2008 OCS 2007 Microsoft Office Communicator 2007 Phone Edition 10.8 MB KB952693
1.0.522.103   OCS 2007 Microsoft Office Communicator 2007 Phone Edition (Interim build included in Device Update Service)    
1.0.522.115 12/10/2009 OCS 2007 Microsoft Office Communicator 2007 Phone Edition (for devices manufactured post August 2009) 10.8 MB KB972640
3.5.6907.222 11/19/2010 OCS 2007 R2 Office Communicator Phone Edition 2007 R2 13.0 MB KB2466291
4.0.7457.0 10/22/2010 Lync 2010 Release Candidate version pre-installed on some devices.  Not available for public download.
4.0.7576.0 11/14/2010 Lync 2010 Microsoft Lync 2010 Phone Edition (RTM)
4.0.7577.107 1/20/2011 Lync 2010 Microsoft Lync 2010 Phone Edition (Cumulative Update 1)
* Polycom CX700 and LG-Nortel IP Phone 8540
* Polycom CX500, CX600, and CX3000
* Aastra 6721ip and 6725ip
 
KB2493722
KB2493723
KB2493724
4.0.7577.250 4/4/2011 Lync 2010 Microsoft Lync 2010 Phone Edition (Cumulative Update 2)
* Polycom CX700 and LG-Nortel IP Phone 8540
* Polycom CX500, CX600, and CX3000
* Aastra 6721ip and 6725ip
 
KB2529974
KB2529977
KB2529978
4.0.7577.296 7/26/2011 Lync 2010 Microsoft Lync 2010 Phone Edition (Cumulative Update 3)
* Polycom CX700 and LG-Nortel IP Phone 8540
* Polycom CX500, CX600, and CX3000
* Aastra 6721ip and 6725ip
 
KB2577593
KB2577594
KB2577595
4.0.7577.4047 11/21/2011 Lync 2010 Microsoft Lync 2010 Phone Edition (Cumulative Update 4)
* Polycom CX700 and LG-Nortel IP Phone 8540
* Polycom CX500, CX600, and CX3000
* Aastra 6721ip and 6725ip
* HP 4110 and 4120
 
KB2636066
KB2636067
KB2636068
KB2636069
4.0.7577.4066 3/1/2012 Lync 2010 Microsoft Lync 2010 Phone Edition (Cumulative Update 5)
* Polycom CX700 and LG-Nortel IP Phone 8540
* Polycom CX500, CX600, and CX3000
* Aastra 6721ip and 6725ip
* HP 4110 and 4120

14.9 MB
24.7 MB
24.5 MB
24.5 MB

KB2670373
KB2672349
KB2672352
KB2672743
4.0.7577.4100 6/16/2012 Lync 2010 Microsoft Lync 2010 Phone Edition (Cumulative Update 6)
* Polycom CX700 and LG-Nortel IP Phone 8540
* Polycom CX500, CX600, and CX3000
* Aastra 6721ip and 6725ip
* HP 4110 and 4120

14.9 MB
24.7 MB
24.5 MB
24.5 MB

KB2724545
KB2701671
KB2701667
KB2701670
4.0.7577.4363
4.0.7577.4372
12/20/2012 Lync 2010
Lync 2013
Microsoft Lync Phone Edition (Cumulative Update 7)
* Polycom CX700 and LG-Nortel IP Phone 8540 (.4363)
* Polycom CX500, CX600, and CX3000  (.4372)
* Aastra 6721ip and 6725ip (.4366)
* HP 4110 and 4120 (.4366)

15.9 MB
27.4 MB
27.2 MB
27.2 MB

KB2737912
KB2737911
KB2737909
KB2737910
4.0.7577.4387 4/18/2013 Lync 2010
Lync 2013
Microsoft Lync Phone Edition (Cumulative Update 8)
* Polycom CX700 and LG-Nortel IP Phone 8540
* Polycom CX500, CX600, and CX3000
* Aastra 6721ip and 6725ip
* HP 4110 and 4120

15.9 MB
27.0 MB
26.8 MB
26.8 MB

KB2819325
KB2819322
KB2819315
KB2819320
4.0.7577.4397 7/15/2013 Lync 2010
Lync 2013
Microsoft Lync Phone Edition (Cumulative Update 9)
* Polycom CX700 and LG-Nortel IP Phone 8540
* Polycom CX500, CX600, and CX3000
* Aastra 6721ip and 6725ip
* HP 4110 and 4120

15.9 MB
27.0 MB
26.8 MB
26.8 MB

KB2860672
KB2860671
KB2860668
KB2860669
4.0.7577.4411
4.0.7577.4414
10/7/2013
10/22/2013
Lync 2010
Lync 2013
Microsoft Lync Phone Edition (Cumulative Update 10)
* Polycom CX700 and LG-Nortel IP Phone 8540 (.4411)
* Polycom CX500, CX600, and CX3000 (.4414)
* Aastra 6721ip and 6725ip (.4414)
* HP 4110 and 4120 (.4414)

15.9 MB
27.0 MB
26.8 MB
26.8 MB

KB2889244
KB2889246
KB2889241
KB2889243
4.0.7577.4420 1/8/2014 Lync 2010
Lync 2013
Microsoft Lync Phone Edition (Cumulative Update 11)
* Polycom CX700 and LG-Nortel IP Phone 8540
* Polycom CX500, CX600, and CX3000
* Aastra 6721ip and 6725ip
* HP 4110 and 4120

15.9 MB
27.0 MB
26.8 MB
26.8 MB

KB2918036
KB2918038
KB2918033
KB2918035
4.0.7577.4444 4/28/2014 Lync 2010
Lync 2013
Microsoft Lync Phone Edition (Cumulative Update 12)
* Polycom CX700 and LG-Nortel IP Phone 8540
* Polycom CX500, CX600, and CX3000
* Aastra 6721ip and 6725ip
* HP 4110 and 4120

15.9 MB
27.0 MB
26.8 MB
26.8 MB

KB2954035
KB2954034
KB2954032
KB2954033
4.0.7577.4450 7/18/2014 Lync 2010
Lync 2013
Microsoft Lync Phone Edition (Cumulative Update 13)
* Polycom CX500, CX600, and CX3000
* Aastra 6721ip and 6725ip
* HP 4110 and 4120

27.0 MB
26.8 MB
26.8 MB

KB2973941
KB2973938
KB2973939
4.0.7577.4451 8/20/2014 Lync 2010
Lync 2013
Microsoft Lync Phone Edition (Cumulative Update 14)
* Polycom CX700 and LG-Nortel IP Phone 8540
* Polycom CX500, CX600, and CX3000
* Aastra 6721ip and 6725ip
* HP 4110 and 4120

15.9 MB
27.0 MB
26.8 MB
26.8 MB

KB2988182
KB2988181
KB2988177
KB2988178

 

  • Update 4/8/2011: The table above will be periodically updated to reflect the latest releases but the remainder of the article’s content originally published in January 2011 will be unchanged .
  • Update 7/28/2011: Added CU3 update information to the table.  Be aware that although the KB articles are still online for earlier Cumulative Update releases the download pages are the same page for each successive release.  Thus previous CU releases are no longer available for download as the new package replaces each previous version.
  • Update 12/2/2011: Added CU4 update information to the table as well as a line for the new HP 41×0 series of devices.
  • Update 4/28/2012: Added CU5 update information to the table.
  • Update 6/18/2012: Added CU6 update information to the table.
  • Update 12/21/2012: Added CU7 update information to the table.
  • Update 1/23/2013: Polycom Aries CU7 package was re-released as 4.0.7577.4372 to address some display issues.
  • Update 5/31/2013: Added CU8 update information to the table.
  • Update 9/19/2013: Added CU9 update information to the table.
  • Update 10/8/2013: Added CU10 update information to the table.
  • Update 11/25/2013: Added CU10 re-release (.4144) information for all Aries phones.
  • Update 1/13/2014: Added CU11 release information to the table.
  • Update 4/28/2014: Added CU12 release information to the table.
  • Update 7/20/2014: Added CU13 release information to the table.
  • Update 8/21/2014: Added CU14 release information to the table.

Prerequisites

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 OCPhone 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.  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.  In most cases the latest OCS 2007 R2 software (3.5.6907) will be installed on a Tanjay and this version is capable of signing directly into Lync Server given that the required DHCP options are configured.

  • An important caveat to discuss is that the older OCS 2007 and 2007 R2 clients are programmed to look for ucupdate and ucupdates-r2 hostname, respectively.  This calls for additional DNS records and certificate SAN entries to be included in the Lync deployment.  This is quite undesirable as most often by the time an administrator reaches this portion of the deployment the certificates have already been requested and installed.  Well, the Updating Devices portion of the Lync Server TechNet documentation covers this but does not explain that it is not necessary.  As long as a Lync Server supported client version is already installed on the Tanjay device then by simply signing into the phone using a Lync user the phone will be able to connect to the Device Update Service using the Lync server/pool FQDN passed down to it.  Thus there is no need to use those other hostnames in the environment.  I have updated out-of-the-box Tanjay devices to the Lync RTM edition with no additional configuration in basic Lync Server environments with none of the ucupdates hostnames configured.
    When updating Aries device there are no legacy hostnames used and as these devices only operate with Lync Server.  The process is even simpler to support, except for the case that a pre-release beta device is in question.  The large majority of Aries devices in existence today will have at least the Release Candidate version (4.0.7457), if not already at RTM.

    Overview

    1. Select a device and identify the current version.
    2. Download and install the update package on to the Lync Server.
    3. Configure a test device to first validate a successful update and working installation.
    4. Trigger an update on the test device (or just wait).
    5. Review multiple log files on the Lync Server.
    6. Approve the update for all devices.

     

    Process

    1. Prepare Device

    Selected for this process is a factory-fresh Polycom CX500 Rev-C device, pre-installed with the Lync Release Candidate 7457 build.

    • Connect the phone to the network and sign-in using a SIP-enabled, Enterprise Voice-enabled user account on the Lync Server pool.  (As the CX500 is an Ethernet only device PIN Authentication is used, but a USB-enabled device like the CX600 can be tethered to a laptop to sign-in as well).

    • Complete the device customization wizard if prompt, or just skip it if not concerned with setting time zone or ring tone settings at this point.
    • Once at the home screen press the Menu button and select System information to view the Version number of the currently installed firmware.  The Release Candidate 7457 build is indicated by the following screenshot.

    image

    2. Install Update Package

    Using the links provided in the table in the beginning of this article download the appropriate package(s) and save it on the Lync Server.

    • Download the latest ucupdates.exe package for Microsoft Lync 2010 Phone Edition for Polycom CX500, Polycom CX600 and Polycom CX3000.

    image

    • Execute the downloaded program and select a directory to expand the ucupdates.cab file to.

    image

    The next step is to import the expanded CAB file into Lync Server using the command shell, as this process cannot be performed from the Control Panel.

    • From the Lync Server Management Shell execute the following cmdlet to import the update cab file into Lync Server.  The -Identity value format is important and must be exactly service:WebServer:<LyncFQDN> while the –FileName value is simply an absolute path to the extracted CAB file.

    Import-CsDeviceUpdate -Identity service:WebServer:lync.schertz.local -FileName C:\temp\UCUpdates.cab

    It may take a few seconds for the cmdlet to complete but once it does open the Lync Server Control Panel (LSCP) and go to Clients > Device Update and the new version should be displayed as Pending Version on the appropriate devices.

    image

    The import can also be verified by locating the installed files on the Lync Server which are stored in the Lync File Share path.

    \\lync.schertz.local\lyncshare\1-WebServices-1\DeviceUpdateStore\UCPhone\Polycom\CX500\Rev-4\ENU\4.0.7577.107\CPE

    image

     

    3. Configure Test Device

    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.  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.

    • From the LSCP navigate to Clients > Test Device and select New > Global Test Device.  Enter anything for the Name (e.g. Test CX500) and select the MAC address Identifier Type.  For the Unique Identifier enter the MAC address of the phone with no separator characters. The MAC is most easily viewable directly from the device on the System Information menu pulled up in Step 1 of this process.

    image

    image

     

    4. Trigger Update

    At this point a reboot of the phone can help kick things off a bit quicker as well as make it easy to track the progress though server logs which may be full of activity from other devices in use on the network.  But understand this is not necessary and now that the Test Device is created the associated device will update on it’s own after a period of inactivity (typically 10 minutes).  The reboot simply triggers the phone to look for an update without waiting as long.

    • Make a note of the current time and reboot the device.  It will automatically sign-in with the current user account and immediately lock.  This starts the inactivity timer.

    • Now, do nothing. Seriously, just leave the phone alone.  Don’t unlock it or push any buttons.  Don’t even look at it.  In fact, go to lunch.

     

    5. Review Server Logs

    While waiting the IIS server logs on the Lync Server can be viewed to see what the phone is up to, as well as keep an eye out for the update version check.  There are two different logs which will contain device request details, the IIS logs and the Lync Device Update logs.

    • In the default inetpub directory locate the most recent W3SVC log file and scroll to the end of the file to view the latest activity.  (Here is a tip: close the LSCP when working with the IIS logs as it will create a large amount of “POST /Cscp” entries which must be wade-through to find the device connection entries.)

    C:\inetpub\logs\LogFiles\W3SVC<randomID>

    image

    • When the phone signs-in to Lync Server a number of log entries will appear from the IP address of the device showing the login process utilizing web tickets and a Location Information Service (LIS) data.  The current firmware version (4.0.7457) can be seen in the client requests.

    2011-01-23 17:39:21 192.168.103.23 POST /RequestHandler/ucdevice.upx – 443 – 192.168.103.105 Microsoft+UCPhone+Device+(lcs_se_w14_main:824457:2010/10/21:23:13:00) 200 0 0 42

    2011-01-23 17:39:21 192.168.103.23 POST /WebTicket/WebTicketService.svc/cert – 443 – 192.168.103.105 OCPhone/4.0.7457.0+(Microsoft+Lync+2010+Phone+Edition) 200 0 0 36

    2011-01-23 17:39:21 192.168.103.23 POST /RequestHandler/ucdevice.upx – 443 – 192.168.103.105 Microsoft+UCPhone+Device+(lcs_se_w14_main:824457:2010/10/21:23:13:00) 200 0 0 160

    2011-01-23 17:39:21 192.168.103.23 POST /locationinformation/liservice.svc/WebTicket_Bearer – 443 – 192.168.103.105 OCPhone/4.0.7457.0+(Microsoft+Lync+2010+Phone+Edition) 200 0 0 130

    • Immediately after the device will perform two HTTP GET requests for the NBT and CAT files of the latest firmware version allowed for its device type.  Because the MAC address for this device matches the Test Device created earlier the Device Update server passes files for version 4.0.7577.107 to the device request.

    2011-01-23 17:40:26 192.168.103.23 GET /RequestHandler/Files/UCPhone/POLYCOM/CX500/Rev-4/ENU/4.0.7577.107/CPE/CPE.nbt – 80 – 192.168.103.105 Microsoft+UCPhone+Device+(lcs_se_w14_main:824457:2010/10/21:23:13:00) 200 0 0 63991


    2011-01-23 17:40:26 192.168.103.23 GET /RequestHandler/Files/UCPhone/POLYCOM/CX500/Rev-4/ENU/4.0.7577.107/CPE/CPE.cat – 80 – 192.168.103.105 Microsoft+UCPhone+Device+(lcs_se_w14_main:824457:2010/10/21:23:13:00) 200 0 0 17

    • Once the device completes downloading and installing the new firmware it waits for additional inactivity time before rebooting.  This allows the updates process to run in the background, yet the device will not reboot while it’s in use.  since the device in this example has been locked throughout the process happens pretty fast.  In this log it was 7 minutes later when the device rebooted and the web ticket request now shows the updated version number.

    2011-01-23 17:47:16 192.168.103.23 POST /CertProv/CertProvisioningService.svc/mex – 80 – 192.168.103.105 OCPhone/4.0.7577.107+(Microsoft+Lync+2010+Phone+Edition) 200 0 0 9

    Okay, now the phone can be used. Go ahead.  Unlock it and check the System Information menu to see the new version number reported.

    image

    The Device Update Update server logs can also be used, which show even more detail.  But unless a device ‘checks-in’ for an update nothing will appear in these logs so starting with the IIS logs is a good troubleshooting habit.

    • Browse to the Lync Server’s DeviceUpdateLogs directory which is stored in the Lync File Share and open the RequestHandlerAuditLog_lync_xxxxxxxx.log for the current day.

    \\lync.schertz.local\lyncshare\1-WebServices-1\DeviceUpdateLogs\Server\Audit\imageUpdates

    image

    Within the log two distinct entries should be seen for the specific CX500 device which was updated.  The first line shows the device on it’s original 7457 build asking for the internal and external URLs to download an approved update from.  Also note that the device’s specific hardware revision (Rev-4) is listed in the request.  This information is later used to select which packages should be approved for updates in the specific environment.

    01/23/2011 11:39:21,chicx500@mslync.net,192.168.103.105,UCPhone,1/23/2011 11:39:18 AM,"0004F2953DFC","0004f2953dfc","POLYCOM","CX500","Rev-4","ENU",cpe.nbt;
    4.0.7457.0;12/24/2010 8:11:02 AM,
    http://<internalFQDN>/RequestHandler/Files/UCPhone/POLYCOM/CX500/Rev-4/ENU/4.0.7576.0/CPE/CPE.nbt;
    https://<externalFQDN>.mslync.net/RequestHandlerExt/Files/UCPhone/POLYCOM/CX500/Rev-4/ENU/4.0.7576.0/CPE/CPE.nbt;4.0.7576.0;10/22/2010
    3:15:24 AM

    Less than 10 minutes later a second entry from the same device appears, this time reporting that it is running the latest 7577 build.  The device is again asking for a download package, but since it is now on the latest approved no URL response is given by the Lync Server.

    01/23/2011 11:47:19,chicx500@mslync.net,192.168.103.105,UCPhone,1/23/2011 11:47:18 AM,"0004F2953DFC","0004f2953dfc","POLYCOM","CX500","Rev-4","ENU",cpe.nbt;
    4.0.7577.107;1/11/2011 3:33:08 PM,

     

    6. Approve Updates

    After some time has passed and sufficient testing has been completed in the environment then each of the supported device updates should be approved so any device can be updated automatically.  The Test Device object can be retained for later use or deleted if no longer testing with that specific device.

    • From the Lync Server Control Panel navigate to Clients > Device Updates, highlight the desired devices and select the Approve action.

    image

    As my test environment contains Polycom production Aries devices then only the Rev-4 package was selected for approval.  Notice that the previously approved 7576 version is now configured as the Restore Version. Additionally the latest Tanjay package has not yet been installed, but the previous RTM version of 7576 is already approved.

    image

    About Jeff Schertz
    Site Administrator

    Comments

    102 Responses to “Updating Lync Phone Edition Devices”
    1. Vadim says:

      Hi Jeff,

      Many thanks for this great article, it saved a lot of my time.
      Shame on me, even with such detailed description I managed to get an issue :)
      The problem is that both of our test devices (Polycom CX3000 and Aastra 6725ip) cannot download the update.
      In the RequestHandlerAuditLog files I can see the following:

      01.28.2011 16:46:17,razboynik.s@contoso.com,172.16.103.125,UCPhone,28.01.2011 16:46:17,"0004F2A6508C","343030303661326663383035","POLYCOM","CX3000","Rev-3","ENU",cpe.nbt;4.0.7192.0;29.12.2010 16:46:17 ,http://lsfe.contoso.com/RequestHandler/Files/UCPhone/POLYCOM/CX3000/Rev-3/ENU/4.0.7577.107/CPE/CPE.nbt;https://lsfe.contoso.com/RequestHandlerExt/Files/UCPhone/POLYCOM/CX3000/Rev-3/ENU/4.0.7577.107/CPE/CPE.nbt;4.0.7577.107;11.01.2011 15:33:08

      I checked the path using web browser and razboynik.s@contoso.com account — the .nbt file is accessable and downloadable. What else can I do to troubleshoot the issue?

      • jeffschertz says:

        I'm working on another article for troubleshooting this process but in the meantime what does the IIS log show when the device tries to 'GET' the update? And are the devices connected internally or externally (via Edge)?

    2. @Agile_IT says:

      Excellent article Jeff! I'm so glad someone posted a detailed walkthrough on the process since the TechNet documentation was fragmented.

      I recently enabled external updates two weeks ago to our users and also have some tips. First, on the Polycom CX600 (or other Tanjay devices) do NOT support wildcard certificates (*.domain.com) for updates/provisioning or for exchange calendaring/autodiscover lookups. The full Lync client might give you a false sense of security everything is working, but external updates and full calendaring (to join concalls from your device without entering a meeting code) on your Tanjay device work best using SAN certificates.

      Another tip is the front end pools external device logging won't show any connections since the session will terminate at negotiation (invalid certificate) in this scenario.

      Hope this saves someone the their Saturday afternoon ;)

      John G.
      http://www.agileit.com/blog

    3. Christian says:

      hi jeff, excellent blog. I got a problem with the update. I’ve a cx600 and when I run the update the phone runs fine the new firmware but is stuck in the “connecting to lync server…” window.

      do you see this before? is there a way to write log files (i’m seeing the log update, but everything seems normal)

      thanks in advanced.

      • jeffschertz says:

        Christian, Microsoft has an open PSS case right now related to some phones getting stuck at the sign-in process after being updated to the CU1 4.0.7577.107 release. In the meantime I would suggest you roll-back the update until the root cause is determined. I'll update this post when I get an update on the case.

        • Philipp says:

          Hi Christian,

          i also did have this issue after updating to 4.0.7577.107. I was able to resolve ist by resetting the CX 600. To reset, unplug the phone, wait 10 seconds, keep * and # pressed while plugging into power again. Device will ask you if you wish to erase all user data, which should be answered with ‘yes’. Now it takes some time until the device comes up again, you will have to do initial setup of the phone one more time.

          Hope it works for you!

          • Chad says:

            Just an FYI that this was an issue resolved in CU2. So if you update to CU2 you will no longer have this issue.

    4. peter says:

      Hi Jeff,__Thanks for your excellent blog. How can you rollback to a previous version of the phone edition, when its not listened under "restore version". We have a problem with an Aastra6725ip phone. We get the error code 0xd/200…seems is has something to do with the flash.
      Maybe you can help me with that question.
      Thank you
      Peter

      • jeffschertz says:

        The phone will store its previous firmware version locally and can be reverted using the factory-reset key combination of holding 4 and 6 while booting the phone.

    5. Alexandre says:

      Thanks by Article "Updating Lync Phone Edition Devices". I very helped.

    6. Peter L. says:

      Hi Jeff,

      thanks for your great lync blog.
      I have a problem, updateing aastra 6725ip. Our Polycom phones update perfectly, but the aastra doesn´t work.
      The current version is 4.0.7313.501 and I tryed to update to 4.0.7577.107 and to 4.0.7577.250. Both went wrong.
      The IIS Log looks ok for me:

      2011-04-06 13:30:39 192.168.3.208 GET /RequestHandler/Files/UCPhone/AASTRA/6725ip/A/ENU/4.0.7577.107/CPE/CPE.nbt – 80 – 192.168.3.161 Microsoft+UCPhone+Device 200 0 995 12
      2011-04-06 13:32:07 192.168.3.208 GET /RequestHandler/Files/UCPhone/AASTRA/6725ip/A/ENU/4.0.7577.107/CPE/CPE.nbt – 80 – 192.168.3.161 Microsoft+UCPhone+Device 200 0 0 87184
      2011-04-06 13:32:07 192.168.3.208 GET /RequestHandler/Files/UCPhone/AASTRA/6725ip/A/ENU/4.0.7577.107/CPE/CPE.cat – 80 – 192.168.3.161 Microsoft+UCPhone+Device 200 0 0 4
      2011-04-06 13:32:07 192.168.3.208 GET /RequestHandler/Files/UCPhone/AASTRA/6725ip/A/ENU/4.0.7577.107/CPE/CPE.cat – 80 – 192.168.3.161 Microsoft+UCPhone+Device 200 0 0 3

      Server Log is looking good too. Did I make a mistake?

      Thanke you Peter

      • jeffschertz says:

        Peter,

        I've only tested this process with the Polycom devices, but the current version you state (4.0.7313.501) is an older beta release of Lync Phone Edition, some of which did not yet work with the Lync Device Update service. So you may not be able to update that phone depending on the hardware version; I would contact Aastra support foassistancece.

        • That release (4.0.7313.501) can be updated with an RTM pool but I was only able update to RC bits (4.0.7457). Once at RC, I was able to update to RTM and then to the latest 7577.250.

          • jeffschertz says:

            Jamie, thanks for the info on that. I haven't had a chance to test all the different version iterations so good to know there are some workarounds for those pre-release versions still floating around out there.

      • John B. says:

        Hi Peter,

        I've got about 46 Aastra 6725ip phones that are running 4.0.7313.501 that I would like to try and apply the gradual update to and get them up to date, unfortunately I cannot find the earlier versions of the phone software.

        Looking to 4.0.7457.0 or 4.0.7576.0. Any idea where I might find them?

        Thanks.

        -John

    7. jason says:

      Jeff, can you shed some light on the revision of each update? I installed the latest package released the other day for the Polycom phones and it appears the same update is listed as revision 3, revision 4 and revision 5… can you explain what is going on with that?

      • jeffschertz says:

        Each the software revisions are mapped to specific hardware revision of each device type, so you don't need to worry about the different software packages in each folder. Just enable each revision for each specific device that you have in your environment and the phone will actually ask for the correct software revision it needs.

    8. RayB says:

      Jeff, looking forward to your debugging article. In our case, we don't see the phone asking for the update. I've checked that the MAC address is correct in the test device as a Global test device. I also found the reskit and ran the logging tool with snooper. I found a line that said IsTestDevice: False.

      Any pointers would be appreciated. Keep up the great work. You stuff is by far the best information available.

    9. Greg says:

      As usual, thx for the very thorough posts. I still find it funny that non-MSFT blogs such as yours are usually more detailed than the actual TechNet documentation, and thus save lots of time for those of us scratching our head. For example, specifying the MAC address without the dashes, little things like that sometimes waste time when they fail to clarify a bit more.

    10. DGA says:

      We have a bunch of cx700′s. We have deployed the newest firmware. We lost power over the weekend. The phones reverted to the previos version. How can I make them stop reverting?

      • jeffschertz says:

        David,

        If the CX700 is rebooted 5 times in a row in a short period of time the device will protect itself by reverting to the other partition with the previous firmware installation. So if power was on/off a number of times this may have happened. Since the original partition still has the newer firmware version then the phones will not update themselves to the approved version as it will never install the same version on both partitions. In this case you’ll need to either approve an even newer firmware version (if one exists) or you’ll have to manually reset the phones 5 times in a row with the reset button on the button of the device (using a paperclip).

    11. @thetootall says:

      Jeff you're blog has been invaluable to me for helping me not only setup the VLAN tagging but also in updating my CX500/600/3000 devices.

      I had been fighting to get my devices to operate on Layer 3 and pass the switch port on the CX600 to my data VLAN, while my phone resided on my voice VLAN. After calls to Dell (using their new 7000 series enterprise switches) when it didn't work, I tried updating my phone from RTM (build 107) to CU3 (build 296) using your instructions and my phone as the test device. Sure enough, after the reboot the phone was finally reading the MSCPEClient option 10 properly and landing on the voice VLAN, and my laptop hanging off the back was on the data VLAN.

      So after 2 days I can finally breathe and know that in the future the first thing I do in my Lync deployments is setup the updates on the server so when they boot for the first time they update. Maybe then I don't waste hours of time trying and retrying your instructions!

    12. kurtde says:

      Hello Jef,
      I however still have a problem updating Polycom CX600 phones. All was functioning fine till we received the last series of CX600 phones. They are having onboard version 4.0.7577.107. They don't upgrade to version 296. All the older phones have upgraded without issue. I have noticed there is also a difference in the hardware. The older ones are Rev-4. They are working without issues. The newer ones are Rev-5. None of them are upgrading… Any suggestions ?

      • jeffschertz says:

        Kurt, make sure that you have also approved the updates in the Lync Control Panel for the Rev-5 devices as well. Each different revision has a separate entry in the Device Update for each revision per device model, so it's possible you have the UCPhone/CX600/Rev-4 entry approved but not the UCPhone/CX600/Rev-5 entry.

    13. Laurent says:

      Hi Jeff, you blog is great and so helpfull. One question, we have a bunch of CX600 and when trying to update them and checking the IIS logs, I do not see any GET for any of those devices. I do have an astra and can see that device log with some GET but not the CX600 :( Any idea?

      Thanks!

      • jeffschertz says:

        If you do not see a GET entry then the device is not attempting to download the update. What is the "Last Update Status" code shown on the phone's system information menu? Either device cannot locate the donwload URL or it's not attempting to download the update since it may not think it's needed. If the devices were rolled back and the other partition already contains the same update version approved on the server the device will not install the same version on both partitions. I have a new article coming out soon which will address the troubleshooting processes in more detail.

    14. @jxjack83 says:

      Jeff,

      I have completed all of the major steps here, but when looking at the logs, I don't see any GET requests at all for my phones. The phone is an old Tanjay, build 3.5.6907.56. It logs in just fine on the phone and I can place/receive calls just fine. However, it never updates, and I can never see any logs on the Lync server showing it tried to connect to get updates.

      • jeffschertz says:

        What is the Last Update Status code on the phone? You can try flipping to the other firmware partition (reset with paper-clip 5 times in a row) to see what the other version is and if that will update correctly.

    15. Thomas Wenzl says:

      Hey Jeff,

      great article as always. You may want to add a note for the later added HP Aries devices.

      Regards,
      Thomas

    16. GeneSass says:

      Let's see if I can throw a new wrench into the works…we just approved CU5 for our devices and need it since the three new CX600's are on .296 and reboot when coming out of hibernation. The rest of our devices are Aastra 6725's and 6721's on CU4 (.4047).
      All phones show they are reaching out for updates with "Last update Status" 0×0/200.
      The server logs show that it is communicatiing with the clients "03/30/2012 11:02:54,e6eb20e1-bdf5-4753-8ea1-eecfd0ad6aee@wilton.com,172.20.148.28,UCPhone,3/30/2012 11:04:27 AM,"0004F296F37B","0004f296f37b","POLYCOM","CX3000","Rev-5","ENU",cpe.nbt;4.0.7577.4047;11/9/2011 5:32:04 PM,"
      The UC files and approved updates have been removed, deleted and re-pushed to the server.
      IIS logs do not seem to be showing any GET requests and only Post requests for lcs_se_w14_main

      I've been reading your blogs most of the day..
      What am I missing?

      • jeffschertz says:

        If the device log file does not show the download URL in the entry then the server has decided that the device does not need an update. Make sure you have CU5 approved for the the proper revision of the CX600, or try using a Test Device with the phone's MAC address to force the update.

        • Kruno says:

          I've had the situation where i was testing phone update to RU6 (I have upgraded phones to RU5 using test VM environment), but couldn't get it to work because in logs there wasn't URL included in response to the phone:
          10/25/2012 14:25:39,test@domain.int,192.168.130.94,UCPhone,10/25/2012 5:25:36 AM,"001B9E2CD22C","1108007563","Polycom","CX700","A","ENU",cpe.nbt;4.0.7577.4066;2/19/2012 6:15:06 PM,

          I have added test device using the MAC 001B9E2CD22C (in the log above) but I have added it as Global – since I was in the middle of OCS 2007 RTM to Lync migration, i still had BackCompatSite in my UC environment.
          Adding test device as SITE TEST DEVICE instead of Global solved my missing updates download URL! :)

          Logging DateTime,User Name,User Host Address,Device Type,Request DateTime,Mac Address,Serial Number,Vendor,Model,Revision,Locale,Requested<FileName;Version;TimeStamp>[# Seperated for Multiple],Response<Internal FileName;External FileName;Version;TimeStamp>[# Seperated for Multiple]
          10/29/2012 07:59:13,test@domain.int,192.168.130.98,UCPhone,10/28/2012 11:59:06 PM,"001B9E2CD170","1108007367","Polycom","CX700","A","ENU",cpe.nbt;4.0.7577.4066;2/19/2012 6:15:06 PM ,http://vlyncfe.domain.int/RequestHandler/Files/UCPhone/Polycom/CX700/A/ENU/4.0.7577.4100/CPE/CPE.nbt;https://rp.domain.com/RequestHandlerExt/Files/UCPhone/Polycom/CX700/A/ENU/4.0.7577.4100/CPE/CPE.nbt;4.0.7577.4100;5/26/2012 5:34:06 PM

    17. Gary says:

      Hi Jeff,

      Can this be done to all devices that are connecting from outside through the Edge?

      Thanks,
      Gary

      • jeffschertz says:

        Yes, LPE can update itself externally as long as the external web services are published correctly via a Reverse Proxy or equivalent configuration.

    18. Mike Curtsinger says:

      Hi Jeff,

      I have a CX700 running 3.5.6907.222 (2.1) in a Lync environment. I have approved update 4.0.7577.410 and the phone downloads ucdevice.upx, CPE.nbt, and CPE.cat with code 200 in the IIS logs. However, the phone does not update and reports status 0×2/0. I have not been able to find much information about this error. Any ideas? I have CX3000 devices in the network that update perfectly. Just can't seem to figure out this CX700.

      Thanks,
      Mike

      • jeffschertz says:

        Mike, has this same environment been upgrading phones across previous versions without issue or is this a new deployment?

        • Mike Curtsinger says:

          Jeff,

          Phones are new to our Lync deployment. We currently only have CX3000s and those have updated without issue. The CX700 was recently purchased. It did complete one update to 3.5.6907.222, however this was only after I switched the device to the partition that had 3.5.x.x on it. The first partition running 1.0.522.115 has never updated. It always show 0×0/200 but never applies the update. I have verified that it downloads all files just doesn't apply them.

          Mike

      • Mark says:

        I am having the same issue. I have 3 new IP8540 phones that shipped with 3.5.6907.35(2.1) and I can see in the logs that they are connecting and getting version 4.0.7577.4100 advertised to them. They are downloading the CPE.nbt, and CPE.cat files according to the IIS logs with code 200, but then fail to install with the with error 0×2/0. From what I can find that error indicates ERROR_FILE_NOT_FOUND according to http://msdn.microsoft.com/en-us/library/ms681382….. I have CX600 and 6725ip devices and they update just fine. The environment has been around for about 6 months and was migrated from OCS, but these are the first phones we have of this model and we are trying to update them.

    19. Matt Davies says:

      Hi Jeff,

      Great article however i have an issue…..

      I have Lync 2010 and have just ended up with some CX700's running 1.0.522.0 (1.23), when I try to get these devices to update i see them download the version 4 software and never install it, they do not seem to make any attempt to download the interim software (1.0.522.103).

      any ideas?

      Many thanks,

      Matt

    20. Ivaylo Bratanov says:

      Hello,

      Is it possible to integrate Polycom CX500,600,700,3000 phones with Lync Environment based in Microsoft Office 365?

      • jeffschertz says:

        Ivaylo, Microsoft does not currently support any Lync phones with O365 due to a number of limitations. Mainly the ADFS (OAuth) authentication protocols rewuired by O365 are not included in the Lync Phone Edition client yet, be also O365 does not yet support Enterprise Voice (another requirement to use LPE devices). With the latest Cumulative Update (June 2012) Microsoft has added wildcard support in the phones so the first step in connecting to O365 (which uses wildcard entries on the Edge Servers) has been addressed. Only USB devices like the CX100 or CX5000 which do not require EV will work with O365 today as they can be connected to a Lync client on a workstation which has the O365 sign-in assistant installed.

    21. BryCel says:

      I am having the same issue with a CX700 – Does the updates then I get status 0×2/0. The logs of the phone show an error with the update but nothing helpful.

      If anyone has any insight please let me know.

    22. Ivaylo Bratanov says:

      Thanks for you fast and professional answer Jeff.

    23. Francesco Bosticco says:

      Hi Jeff,

      I have a dozen CX700 running 3.5.6907.222 (2.1) in a Lync environment. I have approved update 4.0.7577.4100 and the phone downloads ucdevice.upx, CPE.nbt, and CPE.cat with code 200 in the IIS logs. However, the phone does not update and reports status 0×2/0. I have not been able to find much information about this error. Any ideas?
      My opinion is that the leap from 3.5.6907.222 to 4.0.7577.4100 is not allowed, and I argued this during my update experience with some Aastra 6215ip delivered with 4.0.7313.501 (pre-beta), which did not directly upgraded. So, I advertised an "interim" 4.0.7400.0 (whic did succeed), and then to 4.0.7577.4100 with no issue.
      The real tough thing, is that I could get the 4.0.4700.0 build (Aaastra only) just only thanks to a blogger (sorry can't remember the name) who had a stored copy somewhere and passed it. But now, no previous build is available/reachable on MS sites, and ANY backlink leads to the most recent build.
      Any chance you have in your archives some 4.0.7577.xxx lower than 4100 to give it a try?

      Just to point it out, the environment is MS "approved" (DNS records ok, services up, certs ok…)
      Thanks,
      Francesco

    24. Joel C. says:

      Is there a way I can get the version that each of the phones are running on from a scripting perspective rather than having to sift through log files? This would be nice via the Lync Server Management Shell.

      Cheers!
      Joel

    25. Nvv says:

      I followed this article but with no luck. My import fails. I have tried various ways to do import but … :( Maybe someone have any ideas? There is output

      Import-CsDeviceUpdate -Identity service:WebSever:lyncpool.lc.local -FileName C:AAstraUpdatesUCUpdates.cab

      Import-CsDeviceUpdate : Object reference not set to an instance of an object.
      At line:1 char:22
      + Import-CsDeviceUpdate <<<< -Identity service:WebSever:lyncpool.lc.local -FileN
      ame C:AAstraUpdatesUCUpdates.cab
      + CategoryInfo : NotSpecified: (:) [Import-CsDeviceUpdate], NullR
      eferenceException
      + FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Rtc.Mana
      gement.Xds.ImportOcsDeviceUpdateCmdlet

    26. Andrew eddicott says:

      Jeff.
      Thanks for this article. Have sucessfully managed to update all phones within our organisation to the latest revision of the software this being 4.0.7577.4366. Have noticed however that when depressing the * and # keys to wipe the phone if need be for whatever reason the user can no longer authenticate with the lync server and gets an error logging in message. The nonly way to clear this I have found is to completely re set the phone to factory defaults by depressing 4 and 6 on start up and letting it go back to a previous version of the firmware. The user can then log ion as normal. After then leaving the phone for 10 mins it updates to the latest version. Have you ever seen this before?

      Your help is greatly appreciated.

      thanks.

      AE

    27. Marc says:

      Hi Jeff,
      Nice blog, it's very usefull.
      I follow your advice, and we try the last version of cx600 on test devices. But it doesn't download the last firmware:

      2013-01-11 09:53:02 10.6.0.11 GET /abs/handler/192da4b0d4fb42288607b59ee06d4c2c.photo – 443 sip:test@test.fr 10.6.0.31 OC/4.0.7577.4356+(Microsoft+Lync+2010) 200 0 0 10
      2013-01-11 09:53:02 10.6.0.11 GET /abs/handler/9f7ebafc1bc049529502558ba214f068.photo – 443 sip:test@test.fr 10.6.0.31 OC/4.0.7577.4356+(Microsoft+Lync+2010) 200 0 0 5
      2013-01-11 09:53:03 10.6.0.11 GET /abs/handler/e1e45ed868794bbf8a9fcd48c07c65ec.photo – 443 sip:test@test.fr 10.6.0.31 OC/4.0.7577.4356+(Microsoft+Lync+2010) 200 0 0 110
      2013-01-11 09:53:03 10.6.0.11 POST /RequestHandler/ucdevice.upx – 443 – 10.6.0.31 Microsoft+UCPhone+Device+(lcs_se_w14_main:1131444:2012/05/25:17:05:27) 200 0 0 10
      2013-01-11 09:53:03 10.6.0.11 POST /RequestHandler/ucdevice.upx – 443 – 10.6.0.31 Microsoft+UCPhone+Device+(lcs_se_w14_main:1131444:2012/05/25:17:05:27) 200 0 0 105
      2013-01-11 09:53:03 10.6.0.11 POST /groupexpansion/service.svc/WebTicket_Bearer – 443 – 10.6.0.31 OC/4.0.7577.4356+(Microsoft+Lync+2010) 200 0 0 105

      Do you have any ideas on it?
      Thanks!

    28. LyncingMan says:

      Hi Jeff,

      there's a Problem with the 4366 Update for Polycom CX500, CX600, and CX3000.
      KB2737911 link is down.

      • jeffschertz says:

        This is correct, the original CU7 package for Polycom Aries phones contained a bug in the display driver update and was causing screen display issues on a small percentage of devices. Microsoft has removed that package and will post a new version when the problem is resolved.

    29. Jon says:

      Hi Jeff, we have an issue where contact's Lync display pictures do not show up on our Polycom CX600 devices & never have one. I thought they should show by default? Running .4100 firmware, had upgraded to .4366 but rolled it back due to a handful of display issues.will try the latest firmware revision this week. However, if this is by default this should be working on the .4100 already & our contact pictures should show already??

      • jeffschertz says:

        The photos should appear on the CX600 regardless of the firmware version as that feature has been supported since the original RTM release. I would suspect a configuration problem on the server side which is preventing the device from retrieving the photo data. Try looking at the IIS logs on your Front End server to see if the device client is requesting the photo images as HTTPS downloads.

    30. Fritz says:

      Hi Jeff,
      after upgrade to 4366 we have the problem that we cannot change users. You can´t login a new user after log out the first one. After reset with 4/6 back to the old firmware it looks good.

      • jeffschertz says:

        If the new user happens to be hosted on a different Lync Server/pool than the originally signed-in user then this can happen in the event that the certificate CA chains are different between the servers. LPE does not download CA certificates again after the initial sign-in, so a soft-reset (*,#) would be required. If this is not your case and you must use a hard-reset to rollback the firmware then please contact support to track this issue.

    31. CFB says:

      Hi Jeff, I have an issue where we have an SE active/active environment in two seperate geo locations. We have Polycom CX600's in both offices. I have imported the update cab's into the exact same place on both FE's All phones sign in fine even the CX500's in the boardrooms the problem is updates. The phones in the site that was built first that houses the CMS and the federated Edge update perfectly the phones at the other site request updates daily but never seem to complete the process. I have of course homed the users/phones to thier local FE's. Is this potentially a cert error ? have I missed something? Lync mobility works perfectly for everyone all other connectivity if fine. I have already tried a soft reset, not sure how to progress.
      Thanks,
      CFB

      • jeffschertz says:

        All devices should be able to update themselves from their local pool so I'd have to guess something is wrong with the configuration of the new pool, but no ideas what that could be.

    32. Petri says:

      Any ways to schedule the update? None of us, would like to see update process at middle of day.

      • jeffschertz says:

        No the schedule is not customizable, the behavior is hard-coded into the LPE clients. To prevent updates in the middle of the day you could schedule a process to run the PowerShell cmdlets twice a day (before/after work hours) to approve and unapprove the updates in Lync. In theory this should prevent daytime updates, but it not typically necessary as LPE will only reboot to update after a period of inactivity (e.g. user is away from desk/phone for extended period of time).

    33. diego bravo says:

      hi jeff, i have a CX600 version 4387, when call ring (with better together) the client lync 2013 sound, but the phone only make a beep. Do you know this issue?

    34. Jiang Peng says:

      Greate article. After deploying a couple hundred of polycom cx600 phones and upgrade to the latest version, I found a strange behavior. The phone will sign out and sign in automatically each time it perform a update request (default is every 24 hours based MS documentation). Is it a normal behavior or some known issues? For some users, it's quite annoying to see the phone sign out/in automatically.
      Thanks,
      JP

      • jeffschertz says:

        As far as I know it's not possible for LPE to automatically sign a user out and back in. Any sign-out procedure will purge the user credentials, making it impossible to sign back in again. I believe what you are seeing is the standard reboot process that is triggered when the phone updates the firmware. Because the new software is installed in a secondary partition then it must reboot itself to 'flip' over to the other partition to utilize the new version. This reboot will only occur after a specific amount of idle time is reached on the phone, so it can't happen while the phone is actively in a call.

    35. Jens Madsen says:

      How do we obtain previous release firmwares? – the KB articles all end up pointing to the same latest firmware.

      • jeffschertz says:

        There is no official repository of older firmware updates. Microsoft only provides the most recent cumulative update package for each device online.

    36. Craig Gauntlett says:

      Hi Jeff

      I have had call quality issues since the July 2013 was applied to my CX600 phones, specifically when a device come off of hold. Can you advise if you have seen this issue in the field or had any similar reports?

      • jeffschertz says:

        I have not heard of this issue but if it's attributed to the firmware release then you should open a support ticket with Microsoft to find out what change in that version may be causing your problems and how to resolve them.

    37. Hello Jeff, in U10 you have switched CX700 and the CX500/600 KB article links around.

      KB2889246 is for CX500 etc.

      KB2889244 is for CX700 etc.

      cheers

    38. Sriram says:

      Hey Jeff,

      All the download links for CX700 v4.0.7577.x are pointing to the latest version 4.0.7577.4411. Can you pls fix this issue?

      Thanks.

      • jeffschertz says:

        That is correct, there is nothing 'fix'. As explained in the article Microsoft only provides the latest packages on their download server. You cannot download older releases from them once a newer CU has been published, they retire the older packages.

    39. Korbyn says:

      Thanks for keeping the page updated, sucks that the links for downloads end up in the most recent. FYI, 4414 is an updated release to 4411 (Oct 2013) but we're seeing an issue on a number of CX600's with them rebooting several times a day. Really wish I had maintained a library history…

    40. Dennis says:

      Where kan i download early version for the polycom CX 600 because the laterst firmware did not work fine for me. And my telephone is from 2011 and i can not use this phone then for lync 2013.

      Thank you in advance

      • jeffschertz says:

        If you have issues with the latest firmware release I suggest contacting Microsoft support. They can assist with troubleshooting the issue if it is in fact due to the latest update, and can even provide an older version in the meantime if needed. There is no online repository of older, replaced versions.

    41. kenc1163 says:

      HI Jeff, We recently updated our firmware to version 4.7577.4420 from 4100. I kicked-off off the update on a Saturday morning after comfirming the test device update worked fine. The following Monday, on checking the devices, about one quarter din't recieve the update. Out of 200 phone, 53 did not update. I had one of my techs bounce the ethernet switch port on a phone that did not update and it successfully updated the firmware. Any idea on why some phone recieved the updated and some did not. They are all internal and are not specific to one switch or location. Thanks.

      • jeffschertz says:

        The phones will update on a arbitrary schedule to prevent flooding the web server with requests so there are a couple possibilities. Typically I wouldn't assume that 100% of the devices would be updated over a single evening as sometime a reboot is required for a handful of devices to trigger the update. A 75% success rate is not uncommon on the first try.

        • kenc1163 says:

          Jeff, Thanks for your response. It is now day 5 since I kicked off the update. The same devices are not updated. Is this normal or should all phones have updated by now? My concern is that this is manageable with 50 plus phones but when our inventory of phones gets into the thousands, 25% is a very large number to deal with. I am also concerned as to why the phones didn't update. Any insight is greatly appreciated. Thanks.

    42. Ryan says:

      Anyone having any issue using a CX3000 with firmware version 4.0.7577.4372 and logging into Lync 2013 running the January 2014 CU. All of our CX3000's running 4.0.7577.4372 can NOT login while all CX3000's running 4.0.7577.4420 have no problem.

      We can not update the 4.0.7577.4372 because it needs to be logged into lync to get the updated version.

    43. Ralf Scholl says:

      Hello Jeff,

      your Blog is really helpful. Thank you.
      One question from my side:
      Is there a Lync phone edition emulator (or someting else) to be able getting screenshots?
      I will create training documents.

      Thank you.
      Regards,
      Ralf

      • jeffschertz says:

        None that I've ever seen, although Microsoft may have one internally. I just use a camera for my images :)

    44. Boris T says:

      this was very helpful, I just wanted to point others who may show up here: http://www.microsoft.com/en-us/download/details.a

      since many of you probably aren't running ocs 2007 (or r2) anymore

      the above trial from Microsoft worked perfectly, the only trick was changing the clock back on all the VMs to before December 2013 since all of the certs were expired, I was able to upgrade to 3.5 from this hyper-v environment after that did the 2 step CU5 to CU7 via lync 2013.

    45. MiSFiT in a Box says:

      Jeff, Avid reader.
      how to you remove an update all together? We have an instance where we have an old cx700 with OCS firmware coming on and we have all our systems updated to the latest Lync 2013 firmware, suggestions?

    Speak Your Mind

    Tell us what you're thinking...
    and oh, if you want a pic to show with your comment, go get a gravatar!