Article ID: 116093, created on May 15, 2013, last review on Aug 12, 2014

  • Applies to:
  • Operations Automation 5.4

Important: This KB article can be applied to the Microsoft Lync Hosting Pack Application 1.x. For the Microsoft Lync Hosting Pack Application 2.x and higher, see the PA Lync Server 2013 Hosting Pack Integration Deployment Guide and PA Lync Server 2013 Hosting Pack Integration Provider's Guide to obtain the branding instructions. You can start here: PA Lync Server 2013 Hosting Pack Integration Provider's Guide >> Useful Information > Configuring Application for New Brand.

Symptoms

Vendors (providers, resellers) should have the ability to access specific points depending on the brand the end-user is bound to.

Resolution

This is the only way to brand meeting URLs:
1. For each brand, a provider should create a separate set of Microsoft Lync Hosting Pack application resource types (refer to the Lync Server Integration Provider's guide > Creating Lync Resource Types).
2. In each branded resource type (on the "Global Settings" subtab of the "Activation Parameters" tab on the RT dashboard), a provider should specify the branded "Meeting domain name." For example:

  
  

3. Each meeting domain name should be added into certificates on the FE servers, Directors, and Reverse Proxy. For more information, refer to http://technet.microsoft.com/en-us/library/gg398094.aspx and http://technet.microsoft.com/en-us/library/gg429704.aspx.
4. Each meeting domain name should be added into rules on the Reverse Proxy server (the same way as the provider's "dial-in" and "meet" domains). Refer to http://technet.microsoft.com/en-us/library/gg429712.aspx.
5. Each meeting domain name should have a DNS "A" record that points to the Reverse Proxy server. It should only be resolved externally.
6. Each meeting domain should have the following global rewrite rules on the each FrontEnd and Director servers:
 
                <rule name="HTTPS Redirect Rule for meet.branding.net/" enabled="true" stopProcessing="true">
                    <match url="(.*)" />
                    <conditions>
                        <add input="{HTTP_HOST}/{R:0}" pattern="meet.branding.net/(.*)" />
                        <add input="{HTTPS}" pattern="off" />
                    </conditions>
                    <action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="Found" />
                </rule>
                <rule name="Meet Rule for meet.branding.net" enabled="true" stopProcessing="true">
                    <match url="(.*)" />
                    <conditions>
                        <add input="{HTTP_HOST}" matchType="Pattern" pattern="meet.branding.net" ignoreCase="true" negate="false" />
                        <add input="{R:0}" pattern="^meet/" negate="true" />
                    </conditions>
                    <action type="Rewrite" url="Meet/Default.aspx" />
                </rule>
                <rule name="Meet Rule for meet.branding.net:4443" enabled="true" stopProcessing="true">
                    <match url="(.*)" />
                    <conditions>
                        <add input="{HTTP_HOST}" matchType="Pattern" pattern="meet.branding.net:4443" ignoreCase="true" negate="false" />
                        <add input="{R:0}" pattern="^meet/" negate="true" />
                    </conditions>
                    <action type="Rewrite" url="Meet/Default.aspx" />
                </rule>
 

a. Run Windows Explorer and open the file using Notepad: %windir%\system32\inetsrv\config\applicationHost.config

b. Find the closing tag </system.webServer>. Right above it, create the following construction:

<rewrite>
  <globalRules>
         <<<<<<<<<<<<<<      Insert XML from KB here
  </globalRules>
</rewrite>

c. Insert the XML code between the globalRules tags.
d. Save the file.

The branding of meeting URLs for the Microsoft Lync 2010 package is described here.

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF