Lync 2013 and Unified Messaging Integration

Integration Features

  • Call Answering
  • Outlook Voice Access(OVA)
  • Auto Attendant
  • Lync Archiving Integration
  • Unified Contact Store – same contacts in Lync and Outlook for a user
  • OWA Integration – allows IM from OWA
  • Fax Services

Integration Steps

  1. Make sure Exchange and Lync trust each others certificates, so don’t use Self Signed Certificates.
  2. Configure the UM Dial Plan(Outlook Voice Acces, Mailbox Policies, Auto Attendant) and associate UM Servers to the Dial Plans.
  3. Run the exchucutil.ps1 PowerShell script on the Exchange server. This automatically creates UM Gateways, UM hunt groups.
  4. Enable Users for UM
  5. Run the ocsumutil.exe tool on the Lync server
  6. Test the integration


1. Exchange certificate

You must asign a certificate to the Unified Messaging and UM Call Router services.

If you get an error message saying that “Microsoft Exchange Unified Messaging is currently set to run in TCP mode only” the you need to configure the Startup Mode on the UM Server to “DUAL”. You can find the instructions here

After you assign the certificate to the two services you will be prompted to restart the UM services.

2. Configure UM Dial-plan

Make sure you select SIP URI and Secured in the two fields.

You have to provide an E.164 number for these services. You can’t add an extension, so you have to create normalization rules if you want to access these numbers with an extension. You should also have a look at your UM Mailbox Policy that was automatically created, especially if you want to make some changes to your PIN settings.

After this you need to asign an UM Server the the Dial Plan, so open the Exchange Management Shell and run:

Set-UmService -Identity "" -DialPlans "Default UM Dial Plan"
Set-UMCallRouterSettings -Server "" -DialPlans "Default UM Dial Plan"

3. Run the exchucutil.ps1 script

Open a Powershell window and change the path of the directory to C:\Program Files\Microsoft\Exchange Server\V15\Scripts and then run the following command:

C:\Program Files\Microsoft\Exchange Server\V15\Scripts>.\ExchUCUtil.ps1

This script will create UM IP gateways and Hunt groups and change security permissions to access the Lync Server Active Directory objects associated with the UM server. You might have to run the command a second time if there is {<not found>} in the DialPlans column.

4. Enable Users for UM

5. Run the ocsumutil.exe tool

Remember that before you go and run this command you need to have a Lync Dial Plan created with suitable normalization rules.

Open a Poweshell window and change the path to C:\Program Files\Common Files\Microsoft Lync Server 2013\Support and then run the following command:

C:\Program Files\Common Files\Microsoft Lync Server 2013\Support>.\ocsumutil.exe /
and then
C:\Program Files\Common Files\Microsoft Lync Server 2013\Support>.\ocsumutil.exe

The second command will launch the tool, and after you press “Load Data” you can make sure that the first command executed corectly. The Subscriber Access and Auto Attendant should be created.

6. Test the integration

Open Lync Management Shell and run the following 2 commands:

$cred = Get-Credential “contoso\test”
Test-CsExUMConnectivity –targetFqdn “” –UserSipAddress "" -UserCredential $cred

The output should say “Success”.


Lync 2013 Updates

Standard Edition Server Cumulative Updates

To apply the latest cumulative updates to a Standard Edition Server, all you need to do is run LyncServerUpdateInstaller.exe and click on Install Updates. The installer will detect what Lync services have been installed on the server and will display whether or not the latest update has been applied. 

Once the updates have been installed, restart the server if prompted to do so and then Install Lync Database Updates. You apply the update by running the following PowerShell cmdlet on all Standard Edition Servers in your environment:

Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose

For more details on updating both Standard and Enterprise servers visit the following links:

Doug Deitterick’s Blog
Technet Article

Lync 2013 Mobility Services

  • Make sure you have LyncDiscoverInternal and LyncDiscover in your Internal and External DNS, and also that your Frontend Server certificate contains those 2 as Subject Alternative Names.
  • On your Frontend Server open Lync Management Shell as administrator and create a new mobility policy:
New-CsMobilityPolicy -Identity site:SITENAME -EnableMobility $true -EnableIPAudioVideo $true -RequireWIFIForIPAudio $false -RequireWIFIForIPVideo $true
  • Check Client Version Configuration from the Admin Control Panel.
  • Configure Push Notifications:
Set-CsHostingProvider -Identity lynconline -enabled $true
New-CsAllowedDomain -Identity ""
Set-CsPushNotificationConfiguration -EnableApplePushNotificationService $true -EnableMicrosoftPushNotificationService $true

Lync Clients Address Book Synchronization

1. On the Lync 2010 Server launch the “Lync Server Management Shell” and execute the following command:


2. Go and have a cup of coffee, then come back and check in the event logs, you should see, Event 21005 (Sync has Started), 21010 (Sync has completed), 21056 (Details of the sync), and 21004 (Time of next sync).

3. If that does not rectify the problem you can run the following command with administrative privileges:

 reg add HKLM\Software\Policies\Microsoft\Communicator /v GalDownloadInitialDelay /t REG_DWORD /d 0 /f

Create or edit a the DWORD GalDownloadInitialDelay and set its value to 0.

4. Close the Lync Client and delete the GalContacts.db and GalContacts.db.idx files form that PC. you will find those file in the following locations

Windows 7,8 : %userprofile%\AppData\Local\Microsoft\Communicator\sip_<the_username@the_domain>\

4. Restart Lync Client. That’s it.

By petenetlive

Lync 2013 Standard Edition Installation

Lync Server 2013 Deployment by Jeff Schertz

Lync Server Administration Tools:

  • Control Panel
  • Topology Builder
  • Deployment Wizard
  • Management Shell
  • Logging Tool
  • Response Groups Services Configuration Tool(Web based)

Lync Server Features:

  • Instant messaging and presence
  • Role-based access control(RBAC) – it’s similar to an ACL
  • Mobility
    1. Call via Work
    2. Single Number Reach
  • Persistence Chat (collocated on Standard edition and dedicated on Enterprise)
  • Conferencing
  • Remote Call Control (enables a user to control their PBX phone using the Lync Client)
  • VoIP (Enterprise Voice)
    1. Call on Hold
    2. Call Forward
    3. Call Transfer
    4. Call Park
    5. Unassigned Number
    6. Transfer call to differente device
    7. Delegation
    8. Team Calling
    9. Automatic Call Distribution(Response Groups) – Hunt group(basic workflow) and IVR(advanced workflow)
    10. E9-1-1
    11. Media Bypass
  • Unified Messaging Integration Features
    1. Call Answering(Personal Greeting, Record Message, Store Message in Users Mailbox)
    2. Outlook Voice Access
    3. Auto Attendant
    4. Unified Contact Store(Contacts syncronized between Lync and Exchange)
    5. OWA Integration(IM and Presence in OWA)
    6. Lync Archiving Integration(IM and Web Conferencing can be archived in Exchange In-Place Archive)
    7. Fax Services
  • Monitoring (collocated on the FE, but requires SQL Standard or Enterprise, does not work with Express)
    1. Call Detail Recording (ROI, Troubleshooting, Phone Inventory)
    2. Quality of Experience (CAC, Issues reported to End Users, latency, jitter, dropped packets)
  • Reporting (requires SQL Reporting Services; in order to see Monitoring reports you need to activate reporting)
  • Archiving (Exchange or SQL Server Archiving)
    1. Peer-to-Peer IM archiving
    2. Conference Content archiving(files, whiteboards, poling, etc)
  • Call Admission Control(Bandwidth Management) Technet Link

Lync Server Roles(more info):

  • Lync Standard Edition Server (contains the Registrar)
  • Lync Enterprise Edition – Front End Server and Back End Server (the Front End contains the Registrar)
  • Edge Server(more info)
    1. Access Edge Service – For inbound/outbound SIP traffic.
    2. Web Conferencing Edge Service – For joining meeting on the Lync server.
    3. Audio/Video Edge Service – For audio, video, desktop sharing, etc. inside meetings. Internal users can communicate using audio and/or video directly with an external user in point-to-point sessions.
  • Reverse Proxy Server(more info)
    1. Simple URLs(meet, dialin)
    2. Download meeting content
    3. Distribution List Expansion
    4. Address Book Download
    5. Phone Device Update Services
    6. Mobile Device AutoDiscovery
  • Mediation Server (for PSTN integration)
  • Director Server
  • Persistent Chat Server (collocated with Standard Edition, separate server for Enterprise Edition)
  • Archiving and Monitoring (collocated on the Front End for both editions)
  • Unified Messaging Server(Exchange)

Lync Server Clients:

  • Lync 2013
  • Lync 2013 Basic
  • Online Meeting Add-In (for Outlook)
  • Lync Web Scheduler
  • Lync Web App
  • Lync Windows Store App
  • Lync 2010 and 2013 Mobile
  • Lync Phone Edition
  • Lync 2010 Attendant

DNS Records

A Records:

Internal Records
Standard - pointing to your lync server - pointing to lync - pointing to lync - pointing to lync - Lync Phone Edition Autodiscovery, pointing to lync - Phone Edition Updates, pointing to lync
//It depends if you use HW Load-Balancer or DNS Load-Balancer - one pointing to the VIP of the HW Load-Balancer or multiple pointing to each Lync Server in the pool - pointing to the VIP of the HW Load-Balancer - pointing to the VIP of the HW Load-Balancer - pointing to the VIP of the HW Load-Balancer - pointing to the VIP of the HW Load-Balancer - Phone Edition Updates, pointing to the VIP of the HW Load-Balancer - used for WebServices only if you use DNS Load-Balancer; points to the HW Load-Balancer - points to the Back End SQL Server
External Records - pointing to your Reverse Proxy - pointing to Reverse Proxy - pointing to Reverse Proxy - pointing to Reverse Proxy - pointing to the external interface of the Edge server

CNAME Records:

//Lync 2013 Client Internal Autodiscovery
LyncDiscoverInternal --->
//Lync 2013 Clinet External Autodiscovery
LyncDiscover --->

SRV Records:

//Lync 2010 Client Internal Autodiscovery
Service: _sipinternalTls
Protocol: _tcp
Priority: 0
Weight: 0
Port number: 5061
//Lync 2010 Client External Autodiscovery
Service: _sip
Protocol: _tls
Priority: 0
Weight: 0
Port number: 443


1. Open Lync 2013 Deployment Wizard and prepare AD for the Lync Installation.

2. Add administrators into the “CSAdministrator” and “RTCUniversalReadOnlyAdmins” groups.

3. Install Administrative Tools so that you can create your topology with the Topology Builder.

4. Mount the Windows Server 2012 installation media on the server to an available drive letter as some of the components to be installed will need to be read from the installation media as provided by the Source parameter in the following cmdlet (e.g. D:\sources\sxs).

 Install-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Windows-Identity-Foundation, Desktop-Experience, Telnet-Client, BITS -Source D:\sources\sxs -Restart

5. In the deployment wizard select Prepare First Standard Edition server (installs a local SQL Express Server and the first SQL instance RTC).

6. After you start planning your topology keep in ming:

  • The first site is the Central Site, and has no connection to the AD site.
  • For Standard you specify the server name, for Enterprise you specify the pool name
  • Enterprise version will require a back-end SQL Server and local SQL Express, while Standard will require only local SQL Express(which is installed automatically)
  • Enterprise version will require a network file share(file store), Standard can have the file store locally. You need to create the share manually otherwise you will get an error when you will publish the topology.
  • For Archiving Microsoft SQL Server 2008 R2 Express and Microsoft SQL Server 2012 Express are not supported. Standard or Enterprise editions must be used for Archiving storage.
  • The database storage for Monitoring must also be Standard or Enterprise.

7. Set the Administrative Access URL and the location for the Central Management Server.


8. Publish topology

9. Install Lync components on Front-End/Edge servers in topology.