UAG as a Reverse Proxy for Lync – revisited

Here’s another post in my “revisited” series. This time I am revisiting my previous post about how to use the Forefront UAG as a Reverse Proxy for Lync. At the time I wrote that post (Dec 2012) the Lync server UCWA and Lync 2013 mobile client had not yet been released, and the Modern UI/MX Lync App was not that much applied either. My later experience with these applications have been incompatible with the use of UAG like I described it, and when a colleague contacted me the other day on how to go about using the UAG I decided to do a little follow-up on this.

Advertisement

Lync Server 2013 mobility – revisited

I wrote up a post on this topic a few months ago, named “Lync 2013 Mobile Client deployment – field notes“.

This has somewhat proven to be one of the more popular posts on my blog, both regarding stats and comments/questions. I have promised to update it to reflect some more recent experience and knowledge on the subject, but haven’t had the time until now (vacation time) to do so. But finally, here goes.

Lync 2013 Mobile Client deployment – field notes

I recently enabled the new 2013 mobile client for a couple of customers, through the Lync Server 2013 February update (aka CU1). One of the deployments was a Migration scenario from Lync Server 2010, whereas the other was a “first timer”. A couple of experiences to make notice of:

UAG as a Lync Reverse Proxy

​In a recent Lync project I needed to advice my customer on what reverse proxy to apply. On 12th of September Microsoft announced the end-of-life for my previous favourite, the Forefront TM​G. This was a well documented, proven and stable platform for both Lync as well as other web  applications/services needing to be published safely in the outer perimeter.