So when working with a Lync Server already setup for LPE updates then adding VVX updates is as simple as importing and approving the new packages.The experienced Lync administrator can skip to the last section entitled “Lync Pro Guide” for the abbreviated steps.This is the same functionality which Lync Phone Edition devices have always used for firmware updates and now eliminates the need for a separate provisioning server in most Lync environments leveraging VVX Phones.Although the 5.0.0 release added the ability to leverage the Device Update service it was not yet possible to actually leverage the feature until a new update was published.But here’s another problem: Pkgsrc doesn’t seem to keep older releases around and I also haven’t found them mirrored anywhere on the net. Since we don’t control the server, there’s also no way to just add a parameter or something to make it work. Time to get CVS on my slightly more modern Free BSD 11, do the checkout there and tar it all up to copy it over via !We’re going to get 2007Q2 instead, though, since we need things that won’t work on Free BSD 4.11 with later versions.
Obviously Free BSD 4.11 is no longer supported – which is not so much of a surprise. After doing so I found out that 2009Q4 seems to be the last release to bootstrap successfully. Free BSD comes with CVS as part of the base system. And Net BSD’s CVS server won’t accept (which totally makes sense)!
Note that this article is quite lengthy as the entire process is described in detail, accompanied by various log entries and other examples.
Yet in practice using the Lync Device Update service for VVX phone updates is identical to the process used by LPE devices.
Oh, and if you’re not familiar with CVS, don’t worry. Just copy the commands that I prepared for you and you’re good to go: Pkgsrc 2007Q2 bootstrap complete! We just need to adjust the path variable so that the system picks up binaries from the new paths (and make those take precedence over the old system binaries).
We could just change the PATH variable but it’s better to make the changes persistent. This is what we currently have: We’re on 4.11-RELEASE. This old release has a very old port for subversion but that’s fair enough.