- #Unable to install lync web app plugin update#
- #Unable to install lync web app plugin driver#
- #Unable to install lync web app plugin windows 7#
Note the confusing version numbers shown for the About section in the Citrix Receiver vs the Programs and Features.
#Unable to install lync web app plugin update#
Step #1 - Update Citrix Receiver on the HP t610 thin client to version 4.0īegin by checking the existing version # of the Citrix Receiver installed onto the thin client:
#Unable to install lync web app plugin windows 7#
VDI Operating System: Windows 7 Enterprise with SP1 and latest hotfixes Lync Client: Lync 2013 with September 2013 updates Lync Version: Lync Server 2013 with September 2013 updates VDI Client: HP t610 with Windows 7 embedded The video device appears to work as expected:īefore I begin, I would like to highlight a few important components of the setup: If you have one already, try checking Windows Device Manager to make sure it’s installed and working.
![unable to install lync web app plugin unable to install lync web app plugin](https://i0.wp.com/y0av.me/wp-content/uploads/2015/04/enable-plugins.png)
We didn’t find an audio device, which you need for calling The contents of the setup in the blog post above was done over a weekend and I made it a priority to slowly walk through the steps myself this week with a HP t610 thin client so I could document the procedure.įirst off, if nothing is set up within the XenDesktop environment and your thin client is just taken out of the box, you will see the following message when you attempt to setup your audio: The rough notes and blog post I wrote of the process can be found here:įixing the “We didn’t find an audio device, which you need for calling” issue with Lync 2013 client in a Citrix XenDesktop 5.6 Virtual Desktop
![unable to install lync web app plugin unable to install lync web app plugin](https://geektnt.com/static/2016/11/jetpack.png)
This client is extremely technical so I would have to thank him for working with me to get this solution going. I was in Bermuda and he was in a London office trying to get Lync calls to work. My first shot at setting this up was with a client who was setting up a new London office with a 50Mb pipe to the Bermuda office.
![unable to install lync web app plugin unable to install lync web app plugin](http://blog.schertz.name/wp-content/uploads/2011/11/image10.png)
I must say that I’d wish setting this up was a bit easier but for the audio and video quality I’ve seen, I’m not going to complain. The solution is quite simple when you look at it at a high level – simply install a strip down version of the Lync client onto the thin or fat client and use that as the engine to drive audio and video to and out from the user. Fast forward to today and I’m finally glad that Microsoft has taken the steps to solve the issue by introducing the ability for administrators to configure Lync to use media devices local to the thin or fat client on a remote VDI session but instead of sending traffic to the VDI and back out, it would allow the local client to send traffic directly to the Lync Server and/or another peer using Lync to provide local like user experience. Those who have known me over the past 5 years of my career would know that I’ve also been fortunate enough to get to work with Lync 2010 / 2013 and the previous OCS 2007 version deploying the solution as a PBX and I knew there was going to be a day when I’d have to tell a client that I don’t really have a solution for every device they may have to use Lync in a VDI.
![unable to install lync web app plugin unable to install lync web app plugin](https://roofgenerous.weebly.com/uploads/1/2/6/1/126143405/343674388.jpg)
While this solution provided acceptable quality for the user, it wasn’t practical for most environments I worked in as this was not an option for thin clients from HP loaded with their ThinPro OS (has anyone gotten audio out to work with these via analog jacks?) or laptops that don’t come with analog input jacks.
#Unable to install lync web app plugin driver#
I still remember how terrified I was with the audio quality the first time I plugged in a USB headset into a thin client and trying to do a WebEx call with VMware View a year ago and the solution all throughout the web was to use analog mini stereo jack headsets and the popular Teradici driver to send audio in and out to the virtual desktop. One of the challenges I’ve had over the past 2 years working with either VMware View or Citrix XenDesktop was to provide an acceptable audio and video experience to users who work within a virtual desktop environment.