Monthly Archives: December 2011

Svenska UC Klubben goes mobile

Sorry for the Swedish…

Vi kommer köra ett möte med Svenska UC klubben imorgon kl16 och agendan kommer vara Lync mobile.

  • Hur konfigurerar man servern för Lync mobile.
  • Saker att tänka på vid installation/konfiguration
  • Demo av de klienter som släppts. (hoppas ios hinner komma)

Vill ni vara med online eller på plats maila mig på

Lync Server 2010 Protocol Workloads Poster updated with some mobile goddies – #Lync

But not that much mobile stuff in it? It still missing a lot of stuff when it comes to mobile workloads… so we could probably expect another update in the future Winking smile

Anyway, this poster shows each workload in Microsoft Lync Server 2010 communications software, describing relationships, dependencies, flow of information, and certificate requirements. Version 5.10 incorporates Mobility Services and corrections in the IM and Presence workload. Download

But I also updated the Deepzoom version to the latest one and the link to it is

And of course embedded as always Winking smile

Configuring the Reverse Proxy for Lync Mobility: by using Port 80 (the not recommended way of doing it)

When publishing the services for Lync mobility there are two ways of doing it, HTTP or HTTPS.
If you decide to use HTTPS for the Lync Server 2010 Autodiscover Service it requires you to update the subject alternative names lists on the reverse proxy certificates, i.e. buy a new certificate with a SAN name for every sip domain on your Lync Server.
But if you don’t want to do this, you could enable this service over port 80 (its only the autodiscover information that are being sent here so no authentication information are being sent or anything else. but this is still not the recommended way of doing this.)

This post will guide you through the settings for HTTP and a later post will guide you through the settings for HTTPS.

This information is originally from but edited and with screen dumps for

To create a web publishing rule for port 80

  1. Create a New Web Publishing Rule page, type a display name for the new publishing rule (LyncDiscoveryURL (HTTP)).
  2. Select Allow, on the Select Rule Action page.
  3. Select Publish a single Web site or load balancer, on the Publishing Type page.
  4. Use non-secured connections to connect to the published Web server or server farm.
  5. Type the pool FQDN for your Front End or Director pool (for example, on the Internal Publishing Details page. (This should point to the External virtual directory on the IIS and will be redirected to port 8080 later in step 15)
  6. In Path, on the Internal Publishing Details page type /* as the path of the folder to be published, and then select Forward the original host header instead of the one specified in the Internal site name field.
  7. On the Public Name Details page, do the following:
    1. Under Accept Requests for, select This domain name.
    2. In Public Name, type something like (the external Autodiscover Service URL)
    3. In Path, type /
  8. On Select Web Listener page, in Web Listener, select the same Web Listener that you used to publish Lync external webservices or create a new one.
    (To find your reverse proxy FQDN use this PowerShell one-liner on your Front End server Get-CsService -WebServer | ft ABHandlerExternalUri )
  9. If you reused your old rule, select it and then click Edit and make sure that Enable HTTP connections on port 80 are checked and that No authentication are selected.
  10. Click Ok on the listener. And then Next on the Select Web Listener page
  11. On the Authentication Delegation page, select No delegation, and client cannot authenticate directly.
  12. Select All Users, on the User Set page
  13. And then click Finish.
  14. Now double-click the new rule you just added and open Properties for it.
  15. On the Bridging tab, configure the following:
    1. Select Redirect requests to HTTP port, and type 8080 for the port number.
    2. Verify that Redirect requests to SSL port is not selected.
  16. Click OK. and Apply the new rules

Microsoft Lync Server 2010 Mobility Service and Microsoft Lync Server 2010 Autodiscover Service for your weekend installation – #Lync

The bits for the mobility service is now live on

These new services for Microsoft Lync Server 2010 support Lync 2010 functionality, such as instant messaging (IM), presence, management of contacts and groups, Call via Work, Single Number Reach, and Single-click Conference Join on mobile and slate devices.

Installing SP2 on Exchange UM still requires you to uninstalling UM language pack first

My Friend Magnus has a great blogpost covering the steps for installing SP2 on Exchange 2010 that rtw´d today.

What is not covered is when UM is installed and it also has a language pack that is non English. What will happen when you try to update to sp2 is that the setup fails and you are prompted to uninstall the language packs before it can update to sp2. (yes I always forget this)


To fix this error close the setup and fire up Exchange management shell and uninstalling the UM language pack.

But don’t get fooled trying to just run just /RemoveUmLanguagePack:sv-SE from the prompt since this will fail and just give you a prompt back.


So what you need to do is to run the original and this is actually documented on TechNet 

“You can’t use the file that’s located in the \Bin folder to remove a UM language pack after you’ve installed any updates for Exchange 2010. You must use the file from the Exchange 2010 DVD or the downloaded source files. If you don’t, you’ll see the following error: There is a version mismatch between the running application and the installed application. “

Ok so find that old iso and mount it and then then try running /RemoveUmLanguagePack:sv-SE from it and you will se something different.


Ok when the UM language packs are uninstalled its time to update the Exchange to sp2, just follow Magnus guide for that.

And when SP2 is applied we have to install the language pack again, but the latest and greatest version that can be downloaded from

And to install it, just run /AddUmLanguagePack:sv-SE /s: d:\MyLocalFolder

(sv-SE could/should of course be switched to the language pack you are installing.)

Btw, I just saw that its now posible to just doubleclick the languagepack.exe file and then install via the gui


Lync Keyboard shortcuts – #Lync

There is a loooong list of keyboard shortcuts for lync over at

Some of the most common that I use are

Windows logo key+Q
Open main user interface when Lync 2010 is minimized.

Windows logo key+A
Accept an incoming invitation notification.

End a call.

Put a call on hold.

View video in full screen. Note that if the stage area is visible in the Conversation window, F5 will not take video full screen.

And with that let me just give you one more to try

Alt+F4 = Over and out.

Best practices when updating Lync Server with those cumulative updates – #Lync

Cumulative Updates (CU) are kind of a service pack that comes out quarterly for Lync Server and the clients. It includes fixes and some times new functionality is added.

The latest is Cumulative Update is CU4 (as of December 2011) and it can be downloaded here


As you can see there are a lot of files to download and you could just download and update specific components or you can download the LyncServerUpdateInstaller.exe package that includes all the latest updates. So go ahead and download it and then copy the file to your Lync Servers.

To start the update process log in to your server. And start the Lync Server Management Shell

  1. Check that no users are talking on the phone or are in a meeting before you start the update. You can do this by running Get-CsWindowsService (read more in this post )
    1. In the screenshot above there are one active call in the call park service and it would be a bad idea to turn off the services right now as this would terminate the call.
  2. So the solution would be to prevent new sessions for a while and drain the active connections. This can be done running Stop-CsWindowsService –Graceful
    (Read more on server draining at )
    1. image
      As seen in the picture the services is now stopped.
  3. Next thing would be to stop the World Wide Web service. By typing: net stop w3svc
  4. Now Close all Lync Server Management Shell windows.
  5. Install the cumulative update for Lync Server 2010 by running LyncServerUpdateInstaller.exe
    This will start the update tool and you should se what updates are needed and what version is already installed. (As you can see in the picture I have already installed the latest update package and it shows a green checkmark at every line. If there were some services that wouldn’t be updated this would show a red stop mark instead.)
    1. Restart the computer if you are prompted to do so
  6. The next step is something that is almost always forgotten. To update the Lync Server Databases (this step is normally not done if you just used Windows Update to update your Lync server and should then be done manually after Windows Update has updated your server.)
    1. Start the Lync Server Management Shell: (Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.)
    2. To apply the changes made by LyncServerUpdateInstaller.exe to the SQL Server databases do one of the following:
      1. On Standard Edition Server and Enterprise Edition: Front end servers, once you have installed update for core components, the updated sql files will be dropped on the server. Then run the following cmdlet to apply the changes:
        Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn <EEBE.Fqdn> -UseDefaultSqlPaths


        • In a Lync Server 2010 Standard Edition environment, run the cmdlet from the Standard Edition server.
        • In a Lync Server 2010 Enterprise Edition environment in which the archiving/monitoring services are collocated with an Enterprise Edition back-end server, run this cmdlet from the Enterprise Edition back-end server.
        • In a Lync Server 2010 Enterprise Edition environment in which the archiving/monitoring services are not collocated with an Enterprise Edition back-end server , run this cmdlet from the Enterprise Edition front-end server.

        If the RTCDyn databases are removed after you run the cmdlet without the UseDefaultSqlPaths parameter, run the following cmdlet to restore the RTCDyn databases:

        Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn < EEBE.Fqdn > -DatabasePaths <RtcDyn log path>, <RtcDyn data path>
  7. Now when the database is also up to date, its time to start the IIS & Lync Server services. At the command line, type:
    net start w3svc

And that’s it Open-mouthed smile you should now be up to date and ready to roll out the client updates to your Lync clients and phones.

Have I missed something that you considerer being a best practice when updating your server? Please comment bellow.