Aug 14, 2013. Rolled back the latest CX700 firmware and approved the OCS2007 R2 version and it updatedto 3.5.6907.222. From here I worked out I needed to upgrade to specific Lync firmware, prior to the latest.

January 23, 2011 by 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). The latest firmware packages can be found in the article under the Lync Phone Edition table, which was previously included in this article but has since been moved into the newer article which documents the past of various client and server updates.

Prerequisites If the Lync Server environment is prepared correctly to support standard operation of the devices (detailed in this ) 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 documented by Rui Silva. If a device has the slightly newer beta version 1.0.452 or 1.0.522 then 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 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. Select a device and identify the current version. Download and install the update package on to the Lync Server. Configure a test device to first validate a successful update and working installation. Trigger an update on the test device (or just wait).

Review multiple log files on the Lync Server. Approve the update for all devices. 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. 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. • Execute the downloaded program and select a directory to expand the ucupdates.cab file to.

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: 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. 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 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. Uvlayout V2 08 Keygen Mac. • 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.

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. 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 • 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. 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: 16:46:17,razboynik.s@contoso.com,172.16.103.125,UCPhone, 16:46:17,'0004F2A6508C','3035','POLYCOM','CX3000','Rev-3','ENU',cpe.nbt;4.0.7192.0; 16:46:17 15:33:08 I checked the path using web browser and account — the.nbt file is accessable and downloadable. What else can I do to troubleshoot the issue?

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.

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.

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). 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! 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. Let's see if I can throw a new wrench into the workswe 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' 0x0/200. The server logs show that it is communicatiing with the clients ' 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? 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: 14:25:39,test@domain.int,192.168.130.94,UCPhone, 5:25:36 AM,'001B9E2CD22C',','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[# Seperated for Multiple],Response[# Seperated for Multiple] 07:59:13,test@domain.int,192.168.130.98,UCPhone, 11:59:06 PM,'001B9E2CD170',','Polycom','CX700','A','ENU',cpe.nbt;4.0.7577.4066;2/19/2012 6:15:06 PM 5:34:06 PM.

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 0x2/0. From what I can find that error indicates ERROR_FILE_NOT_FOUND according to. 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. 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.

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 0x2/0. I have not been able to find much information about this error. 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. 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. 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. Hi Jeff, Nice blog, it's very usefull. I follow your advice, and we try the last version of cx600 on test devices.

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.

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. 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. Hi all, I realize this is a little left of the blog-subject – and I hope you will accept my apologies and appeal for help. We are trying to configure a Polycom CX3000 with the latest firmware to display the calendar of an Exchange 2010 (BPOS-D) resource mailbox. Of course, we know this is not normally allowed because the underlying AD account cannot log into the mailbox. I have read several posts on this subject, but we are not clear on how to steer around this. If we are using a separate Global AD Domain from the BPOS-D domain – is there a way to give the CX3k AD/Exchange credentials that will allow us to display the room resoure calendar?

Thanks so much for your help Tim. Hello, We have Polycom CX600 type phones on Lync 2010 EE server back end, which are in generic areas e.g. Print Room where multiple people access the same phone and since they wanted to have ability to have call forwarding and Voice mail – we created generic service accounts in AD and had them Lync enabled instead of setting them up as Common Area Phone. The phones, do however, get locked which is expected since it is there on Site Device configuration – and this is little annoying to users. Is it possible to disable phone lock on a per user / phone basis while keep the site policy of locking intact?

Hi Jeff, Big Fan! Wonder if you could advise on a query please. We have some CX500 (Firmware: 4.0.7577.4451) trying to connect to a SfB on prem installation. I noticed that platform compatibility on your Phone Edition chart () does not start until (4.0.7577.4463). The CX500’s currently will not sign in, however I believe all the settings are correct as we have some RealPresence Trio 8800’s which can sign in using PIN auth. I’ve downloaded the latest UCUpdates cab for this version and created a test device using MAC to try and update, nothing happens. I’ve also looked through the logs (still reviewing) and reviewed comments above for any pointers.

Is there a separate process to bring the CX500 inline with the correct firmware for SfB? If a more up to date firmware version is needed for compatibility, if that is indeed the case in terms of inclusion of “SfB” in the firmware version chart from the other post I mention? Cheers, Matt. Hi Jeff, Got the CX500 phone to sign in using PIN Auth. SRV records were pointing to the FQDN of the FE these had been changed as per.aspx which is reference within the PDF for the RealPresence Trio setup. However I’d made the mistake of using the internal domain as opposed to the SIP domain in the FQDN.

The Trios had been signing in without issue so assumed this was OK. On reviewing another one of your articles: this raised itself as the issue. I then changed the A records referenced by the SRV back to sip.fqdn.com and all is fine.

Phone has also updated the firmware. Contaminant Hydrogeology Fetter Pdf Download on this page.

This is a fast published article Warning: DO NOT UPGRADE TANJAY/ CX700 TO THE LATEST FIRMWARE 4397/4411. Your lync phone will be partially not able signing in with Lync 2013 more info an fix will be provided soon Reference: SOLUTION: As I promised, here it come.

The bug is related to some undocumented processes for the so called old OCS Phone, which are the Tanjay/ cx700. This login process and firmware update process is totally different from other Lync phones.

What do I have to do: TANJAY: Update the phone to the newest firmware, but be aware, the phone holds the version before 4397. LYNC environment: Phone Login: - the OCS Phone Edt, will NOT login via sip., it will only us the sipinternal.

Therefore ensure, the SIPINTERNAL FQDN is on the local certificate. Our findings have shown, Tanjay will still query the sip., will also make an TLS connection, but than it drops the communication. We don't know why. The response from PGI was, possible MS wanna get rid of this old OCS phones. Phone Update: - as we know, the update process is identified with ucupdate-r2. Either via http or https, but here the old OCS environment only allowed https, this is now important to know for Tanjay firmware updates. It only can make updates via https.

Therefor ensure you also put ucupdate-r2. As SAN into your local FE certificates too. Extensive experience in business and market development. Specialized in intercultural and business relationship in Asia.

Successful in providing leadership on new topics and complex global projects that require interfacing with internal/external teams and ecosystems. Early adaptor of visionary technologies. • 20+ year career within different companies in the areas software development, telecommunication, IT, mobility and hosted/cloud services. • Strong technical and business background – Elite Member Microsoft Product Group TEAMS and was member of Microsoft´s German Inner Circle. • Organized, logical, rationale thinker and problem solver with superb communication and collaboration skills. • Business Management skill in strategic and organized developing German SME subsidiaries in Asia Specialties: Management: Start up companies, Business Relation Management, Partner Relation Management, Enterprise Business Sales Skills, strong team leader and motivator, perfect Asian business and human behavior understandings, excellent financial cash flow management Technical: Microsoft Office 365, Public and Private Cloud Computing, specialized in Hybrid Cloud integration, Unified Communication (Skype for Business, Exchange), Security (PKI, ForeFront), Active Directory.