Ms lync 2013 client
![ms lync 2013 client ms lync 2013 client](http://lh5.ggpht.com/-2J1cQtGMj-4/UWHTJ7VopNI/AAAAAAAAcFU/irE-mWUTHmU/image_thumb.png)
- #MS LYNC 2013 CLIENT DRIVER#
- #MS LYNC 2013 CLIENT FULL#
- #MS LYNC 2013 CLIENT WINDOWS 7#
- #MS LYNC 2013 CLIENT WINDOWS#
#MS LYNC 2013 CLIENT DRIVER#
Warning: You are about to uninstall this device from your system.ĭelete the driver software for this device. One of the more prominent solutions in Citrix forum posts is to remove the Citrix remote USB bus and Citrix remote USB host controller as such: The problem appears to be that the Lync 2013 client does not like or see the Citrix HDX Audio device:
#MS LYNC 2013 CLIENT WINDOWS#
If you have one already, try checking Windows Device Manager to make sure it’s installed and working. We didn’t find an audio device, which you need for calling … but when you click on the Audio Device, you see the following:
#MS LYNC 2013 CLIENT WINDOWS 7#
You have the Lync 2013 client installed onto a Windows 7 Citrix XenDesktop virtual desktop and you noticed that the client correctly finds the Video Device as the Citrix HDX Web Camera and it works as expected: Sorry about format as it’s not very organized so I’ll follow up with a proper post demonstrating the process step by step. As I’ve been extremely busy lately with multiple projects on the go and haven’t been blogging as much, I felt it was important to set aside a bit of time today to just dump all of the information I have in my head that was required to get this going. This weekend was the actual deployment and we noticed that the Lync clients within their VDIs wasn’t fully functional which then kicked off a 5 hour troubleshooting exercise on Saturday and another 5 hours on Sunday until we got it going. I want to determine if the connections are routing over the fastest links available to them for Lync client communications.I’ve been working with a client that had two new offices opening in London with HP t610 thin clients as desktops to access the XenDesktop 5.6 environment I built last year at their Bermuda office. The reason I ask the question in bold is because we are trying to decipher how much Lync client traffic is "lan client to lan client" vs. So, am I interpreting the logs and what the MS tech said incorrectly or not? User-Agent: UCCAPI/.1004 OC/.1004 (Microsoft Lync) Looking at the UCCAPI.log on my client I see a lot of activity back and forth to the Lync server itself, but never really direct peer-to-peer traffic: From: "Bob Smith" tag=e7833a30 epid=1275117fecd
![ms lync 2013 client ms lync 2013 client](http://blog.icewolf.ch/images/blog_icewolf_ch/201302/Lync2013_09.jpg)
He said that even though 2 clients may be on the same LAN they will still relay their traffic through the Lync Online server, in essence acting as the proxy for the call/IM. However, after working with MS support on a desktop sharing issue within Lync, the tech stated that the Lync server is always the MCU, even during basic IM messages. Servers, but talk directly between themselves for actualĬommunications unless of course a conference is involved, in whichĬase they connect all to the front-end servers which acts as a MCU. Now, as everyone knows, Lync clients are only managed by the Lync Massimo's question here: How can two Lync client talk when there is no route between them? states: My question is: does the Lync client really talk straight peer-to-peer for its IM and video call communications when not in a "Lync Meeting"? (Note: for me it's Lync Online/Office 365, but it should function very similar to an on-premise deployment)
#MS LYNC 2013 CLIENT FULL#
I have yet to do full on packet captures to really nail it down.simply for lack of time. I've done my own research in the UccAPI logs as well as opening a ticket with Office 365 support but the results are still muddled and confusing.