We are currently evaluating Lync 2013 Server. We are stuck using the Lync 2010 Client because my organization is still on Office 2007, and Lync 2013 Client does not support Outlook 2007.
The Lync 2013 Web App is superior to the Lync 2010 client for multiparty conferencing, since it allows for multiple video streams to appear at the same time.
I have learned that we can force Lync to use the Lync Web App by appending ?SL=1 to the end of the conference URLs. For example: https://join.org.ca/james/6RYZRGZP?SL=1
. The problem of course is that this solution is not accetable, our users are not going to modify the URLs in the Outlook meeting invitations every time they send one out.
I'm wondering if I can use IIS Rewrite within IIS 7.0 on our 2013 front-end pool server to append the ?SL=1, to force the Web App Client and prevent the local client from loading. This outlines something similar, but it's done on the reverse proxy: http://www.avianwaves.com/Blog/entryid/175/Using-a-Reverse-Proxy-to-Automatically-Force-External-Lync-Meeting-Guests-to-Use-Silverlight-Client.aspx
Perhaps there are other methods to force the Lync Web App?