申明：文章中部分内容有涉及官方帮助或者网上资源整合，如有违权，请速与作者联系，谢谢！

作者：316191099@qq.com

培训：Skype for Business Server 2015-项目实战-培训-QQ群:65235615。（学员群，非所有人员都加。）

参照：

Using IIS Application Request Routing (ARR) as a TMG Replacement

http://masteringlync.com/2013/02/12/using-iis-application-request-routing-arr-as-a-tmg-replacement/

1. 创建-服务器场

SFBFEPool01.i-x-Cloud.com

SFBFEPool01.i-x-Cloud.com

8080

4443

SFBFEPool01.i-x-Cloud.com

SFBFEPool01.i-x-Cloud.com

8080

4443

2. 修改设置

3. URL重写

Double click the ARR_Lync_Loadbalance_SSL rule and let’s understand what you see here:

In the Match URL is basically what we are going to make after the / in the URL. So if our URL was www.domain.com/website the pattern would be /website for example. You will see under Using you will have the option to use Regular Expressions.

The Conditions is a set of inputs that are required to match this rule. Here we will we have HTTPS which basically means we must match SSL requests only.

This is a continuation of the above. The Action section tells us what we should do if we match. So here we will route to the Lync Server Farm. This part is pretty straight forward and will be basically the same for all rules. So let’s create our first Lync Rule.

Meeting/Dialin/External Web Services Rule

Here you have some options based on how you do your simple URLs. If you do “Option A” where you URL would look like:

https://meet.domain.com and https://dialin.domain.com then you would need to use the below rule.

Change Using to: Regular Expression

Change Pattern to: (.*)

{HTTP_HOST}

(SFBFEPool01.i-x-Cloud.com|dialin.i-x-Cloud.com|meet.i-x-Cloud.com)

Add to Conditions: {HTTP_HOST} on the pattern of (externalwebservices.domain.com|dialin.domain.com|meet.domain.com).

If you use Option B where your simple URLs might look like this:

https://meet.domain.com/ID/ and https://meet.domain.com/dialin/ your rule would look like this.

((?:^dialin|^id|^Abs|^autodiscover|^CertProv|^CollabContent|^Fonts|^GroupExpansion|^HybridConfig|^lwa|^mcx|^PassiveAuth|^PersistentChat|^Reach|^RequestHandlerExt|^RgsClients|^Scheduler|^Storage|^ucwa|^WebTicket).*)

NOTE: You will need to change dialin and id to whatever you use if using Option B for simple URL’s

NOTE: This is the list of all potential directories as of RTM of Lync 2013. CU1 will most likely add some items so this may need to be edited.

Add to Conditions: {HTTP_HOST} on the pattern of (externalwebservices.domain.com|dialin.domain.com|meet.domain.com).

NOTE: You should NOT add LyncDiscover.domain.com to this rule. The reason we don’t want to add this is because our regular expression doesn’t include the root of the website and lyncdiscover.domain.com/?sipuri= won’t match any of these rules. If you wanted to, you could change your pattern to (.*) and add lyncdiscover.domain.com to the list. I don’t have a good reason to do it either way. Whatever makes the most sense to you but I like to separate them out.

Lync Discover Rule

Now we create a rule for Lync Discover services. Here is what I have created. This rule is created as brand new and not one of the existing rules.

Lyncdiscover.i-x-Cloud.com

{HTTP_HOST}

Lyncdiscover.i-x-Cloud.com

Here I am defining my pattern match as any request (.*) anything from lyncdiscover.thegaragelab.info URL. Here I am not requiring HTTPS on this rule Lync Discover will use either HTTP or HTTPS.

查询-公网IP:

修改-公网DNS的A记录：

HOSTS中未配置：

测试：

https://meet.i-x-cloud.com/sfb01/BP9J6NQ4

https://dialin.i-x-cloud.com

https://sfbfepool01.i-x-cloud.com/PersistentChat/RM?clientlang=zh-CN

https://LyncDiscover.i-x-Cloud.com

https://mail.i-x-cloud.com/owa

https://mail.i-x-cloud.com/ecp/