My environment consists of CX3000, CX600, CX500, and VVX300 phones in Lync 2013. I have used the device updater in Lync console for all models but VVX300 until now. I managed to get a fresh VVX300 phone to update to the latest firmware but the remaining devices are all pointing to a separate FTP server for updates. I have read through the guide below but it is confusing in regards to having the Lync server as the 'firmware updater' and still having a provisioning server send out configurations. My goal is to have Lync provide the updates while still being able to provide the "LoudRing.wav" ringtone to the phones and set their web HTTP interface to enabled.
This blog has some good info on getting this working.
One big thing is make sure you don't have "APP_FILE_PATH" pointed to a directory where there are UCS install images. I wouldn't even have and UCS images on your provisioning server.
Thanks James. I did read that article but it doesn't talk about having the provisioning server in tandom in detail. He made a separate blog earlier regarding JUST the provisioning server doing everything. So I have both extremes, but not detail on in-the-middle config. I just want to get a ringtone on each phone and to have the web-interface/portal enabled on HTTP after the phones update through Lync. Currently I cannot roll out the latest update through Lync until I can figure out how to get the ringtone to stay (requires the provisioning server link).
Have you set up the provisioning server? If not start there but don’t add it to your DHCP. Make sure you don’t have any *.sip.lp files on your server.
Then use the web UI to manually point a test phone at your provisioning server. Check to make sure the phone is backing up log and config files to the server. It should also back up any custom ring tones and images.
Once you have that working use Lync to push the update to just that phone. (Test Devices)