Dec 10, 2011

Posted by in Tech Tips | 2 Comments

Configuring Lync Mobility – Part 2

Continuing my set of instructions for installing Lync Mobility. Here we cover setting up our servers. See the previous post for details about configuring DNS

Overview of changes

  • Add two new DNS records – one internal, one external
    • Either A records or C-Names
  • Patch everything to Lync RTM CU4
  • Define the “Internal ports” used for mobile clients
  • Install mobility bits on Front-Ends & Directors
    • Enable Dynamic compression in IIS
  • Re-request certificates to support new mobile DNS names
  • Configure your reverse proxy
  • Configure push notifications
  • Test! (Kinda)

Patch your internal servers to CU4

Download CU4 installer from here http://www.microsoft.com/download/en/details.aspx?id=11551

Follow one of the excellent guides about how to install CU 4 like this one: http://blog.insidelync.com/2011/12/lync-client-and-server-cumulative-update-package-cu4/

*** Don’t forget to update your backend database *** (Install-CsDatabase –Update –ConfiguredDatabases –SqlServerFqdn <SQL Server FQDN>)

Define the “Internal ports” used for mobile clients

From a Front-End server use the new shiny powershell commandlets that came with CU4 to configure the ports for mobility on your pools.

Start a Lync management shell

clip_image001

First, set the internal web services port:

Set-CsWebServer –Identity <name of pool> –McxSipPrimaryListeningPort 5086

Repeat for any other pools in your organisation

Now the external services port:

Set-CsWebServer –Identity <name of pool> –McxSipExternalListeningPort 5087

You wont see any confirmation but no errors is good news:

clip_image002

Repeat for any other pools in your organisation

Now apply the changes with the following command:

Enable-CsTopology -verbose

(the -verbose means we get some feedback)

clip_image003

Install mobility bits on Front-Ends & Directors

Ok now we need to actually install the mobility web services on our Lync servers.

Go and download the MSI from hereBUT DON’T RUN THE INSTALLER!

Copy the files into C:\ProgramData\Microsoft\Lync Server\Deployment\cache\4.0.7577.0\Setup\ on each server

clip_image004

Next we need to add Dyamic Content Compression support into IIS & if your running server 2008 R2 you need to tweak some ASP.net settings (on 2008 R2 Lync will do the tweaks for you).

2008 R2:

From powershell run

Import-Module ServerManager

Add-WindowsFeature Web-Server, Web-Dyn-Compression

clip_image005

For 2008:

run an elevated command prompt and use “ServerManagerCMD.exe –Install Web-Dyn-Compression”

Then make the following changes to ASP.net (taken from MS install docs)

  1. Log on to the server as a local administrator.
  2. Use a text editor such as Notepad to open the applicationHost.config file, located at C:\Windows\System32\inetsrv\config\applicationHost.config.
  3. Search for the following:<Add name=”CSExtMcxAppPool”
  4. At the end of the line, before the ending angle bracket (>), type the following:CLRConfigFile=”C:\Program Files\Microsoft Lync Server 2010\Web Components\Mcx\Ext\Aspnet_mcx.config”
  5. Search for the following:<Add name=”CSIntMcxAppPool”
  6. At the end of the line, before the ending angle bracket (>), type the following:CLRConfigFile=”C:\Program Files\Microsoft Lync Server 2010\Web Components\Mcx\Int\Aspnet_mcx.config”

Continue

Now we’re ready to “Bootstrap” our server. Bootstrapping tells Lync to go and read in the Central Store what roles the server is meant to be performing & then add or remove the roles as appropriate.

Run an elevated command prompt and navigate to the Lync deployment directory (C:\Program Files\Microsoft Lync Server 2010\Deployment) and then run the command “Bootstrapper.exe”

clip_image006

After its completed you should see the two new roles being added with a “success” message. If not have a dive through the log file shown at the end of the screen for some hints of where to go troubleshooting.

A quick check in IIS should show our two new virtual directories have been created in the external & internal websites

clip_image007

Continue to Part 3…

Share and Enjoy:
  • Print
  • Add to favorites
  • Google Bookmarks
  • Facebook
  • email
  • Twitter
  • Reddit
Tags: ,
  1. The MCXStandalone.msi does not get installed when running bootstrapper

  2. After running the commands that create the IIS directories, I did receive both success messages, log file shows all success, but the directories are not there….Your thoughts?

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>