tag:blogger.com,1999:blog-2228947945609574437.post1877454556331915634..comments2024-03-17T16:23:31.499-04:00Comments on Terence Luk: Deploying Office Web Apps for Lync 2013 internal and external accessTerence Lukhttp://www.blogger.com/profile/02612575579652280306noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2228947945609574437.post-46836253761839118862015-03-11T15:56:53.299-04:002015-03-11T15:56:53.299-04:00I'm fully aware of the benefits of using TMG t...I'm fully aware of the benefits of using TMG to publish the service as I've worked with the product since the Microsoft Proxy Server days but the challenge that I come across more and more often now is that most clients I work with does not have TMG or UAG. I also can no longer propose TMG into an environment because the product is being discontinued.Terence Lukhttps://www.blogger.com/profile/02612575579652280306noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-48626816333510189312015-01-13T09:04:09.165-05:002015-01-13T09:04:09.165-05:00Step by step the secure way: http://technet.micros...Step by step the secure way: http://technet.microsoft.com/en-us/library/jj204665.aspxUlfnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-41987037078513813762014-12-05T10:16:07.625-05:002014-12-05T10:16:07.625-05:00If you're already using a Reverse Proxy server...If you're already using a Reverse Proxy server, it's much more secure to publish it using that service, which also alleviates any issues you may have if you have a different internal namespace.<br /><br />Simply create an internal SAN certificate with the internal and external names in it, have those two different names as your InternalURL and ExternalURL in the OWA publication, and use your Internal certificate on your OWA server. You bind your Public certificate only on the Reverse Proxy, not the OWA server!Luke Edsonhttp://www.edsontech.comnoreply@blogger.com