Skip to main content

Lync Server integration with Exchange Outlook Web Access.


Lync Server integration with Exchange Outlook Web Access.

Recently I have deployed Lync integration with Exchange Outlook Web Access. Whenever you accessing Outlook web access you will be able to chat you’re your buddy without Lync application. This is the main feature which is enable after above integration.
Feature: Instance Messaging enable on Outlook Web Access.

You must have:
  • Microsoft Exchange Server 2010 in your organization.
  • Lync Server 2010.
  • Obtained a certificate that's trusted by the Lync Server 2010 server and the Client Access server and is issued by the same authority. The certificate must have the Client Access server namespace as the subject on the Subject line. The namespace may be the name of a particular Client Access server, or it may be a DNS name that's used for load balancing across multiple Client Access servers.
  • Recorded the fully qualified domain name (FQDN) of the Lync Server 2010 server or the Lync Server 2010 pool that the Client Access server will connect to. The server or pool should be geographically close to the Client Access server.
  • Enabled your users to use Lync Server 2010 via the Lync Server 2010 user administration tools.
 Steps:
1.     On the Client Access server running Windows Server 2008 or a later version, download and install UCMA 2.0 from Unified Communications Managed API 2.0, Core Runtime (64-bit). It will update the UC managed API

URL:

2.     On the Client Access server, download and extract the CWAOWASSPMain.msi file from Microsoft Office Communications Server 2010 R2 Web Service Provider. Version: 3.5.69.07.244. The following files are extracted to the Web Service Provider installer package location:

a.     UcamRedist.msi

b.     CWAOWAASSP.msi

c.      Donnetfx35setup.exe

d.     Vcredist_x64.exe
This will required IM and Presence feature in OWA.

3.     Double-click CWAOWASSP.msi to install the Microsoft Office Lync Server 2010 R2 Web Service Provider.

4.     Download and install the hotfix from OCS 2007 R2 Web Service Provider Hotfix.

Cross verify the following things before doing next steps-
  • Look for the InstantMessaging key in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange OWA\. The string under InstantMessaging with the name ImplementationDLLPath and the value "\ClientAccess\owa\bin\Microsoft.Rtc.UCWeb.dll" should have been created.
  • The Microsoft.Rtc.UCWeb.dll file should be present in the directory <installation drive>\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\Bin.
  • The files SIPEPS.dll and Microsoft.Rtc.Collaboration.dll should be present in the Microsoft .NET Framework Global Assembly Cache.

5.     Verify the Certificate:

a.     Open Exchange management power shell.
                   get-ExchangeCertificate | fl Services,Thumbprint                  

b.     Locate the certificate you want to use, and then record its thumbprint and subject.
IMG:

6.     Use the Management Shell to set the Lync Server 2010 Server used by the Client Access Server and to enable integration. 

Note: certificate to be used, and enables the Client Access server to use trusted Lync Server 2010 for instant messaging. 

Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingServerName  -InstantMessagingCertificateThumbprint  -InstantMessagingEnabled $true -InstantMessagingType 1
 
You can restart the IIS service; open the Command Prompt window and using the iisreset/noforce command to reflect the changes. 
 
7.     Under Lync server do the following configuration:

You have to create Outlook Web App pool entry on the Lync Server 2010 server.
a.     Run the Get-CsSite cmdlet to get the siteID for the siteName in which you are creating the pool.
b.     Run the New-CsTrustedApplicationPool cmdlet to create the trusted application pool. This also creates the external service entry in Lync Server 2010.
New-CsTrustedApplicationPool -Identity  -Registrar  -Site  -RequiresReplication $false
 
Run the New-CsTrustedApplication cmdlet to add a trusted service port for the application.
New-CsTrustedApplication -ApplicationId  -TrustedApplicationPoolFqdn < OwaPoolfqdn same as what is used in SN of cert>  -Port 
 
Run the Enable-CsTopology cmdlet in the Shell to enable the topology.
               Enable-CsTopology
 
Thank you.

Comments

Popular posts from this blog

Outlook Add-in for Skype meeting getting disable after restarting Outlook.

Issue: Outlook Add-in for Lync meeting getting disable after restarting Outlook.
Problem Statement: Outlook Add-ins gets install automatically when Office 2013 installs (Lync and Skype for Business clients are part of Office package). Add-ins name is Lync Meeting Scheduling Outlook Addin or Skype meeting Add-in for Microsoft Office 2013. Sometime if other add-ins conflict with Outlook add-ins then outlook add-in keep getting disabled. And user has to enable it manually after Outlook restarts. 
Resolution: By default Lync Meeting Scheduling Outlook Addin or Skype Meeting Add-in for Microsoft Office 2013 installs wit load behavior "Load at Startup". However due to some conflict users Lync or Skype add-ins load behavior get changed to loaded instead of "Load at Startup" had to re-enable Lync Meeting Add-In in each time Outlook 2013 was started as it was not set to "Load at Startup". Look at the below screenshot. Now question is how we can change load behavior …

Unable to share desktop in Skype for Business?

Unable to share desktop in Skype for Business?
You can show your entire desktop or just a program to everyone in a Skype for Business Meeting, call, or instant messaging (IM) conversation. However sometime this feature does not work and give different errors.  Error message: ·Cannot start Desktop/Application Sharing due to network issues. ·An error occurred during the screen presentation. Resolution: There are multiple thing which may affect application/desktop sharing. 1.Make sure application / desktop sharing enabled on Skype for Business / Lync Server. SfB /Lync Control Panel > Conferencing > Conferencing policy > select Global or create new policy and set enable ‘Enable application and desktop sharing’. Refer below image. 2.Make sure your Skype for Business (Lync) client is updated with latest cumulative updates. Download latest update Skype (Lync) client. 3.Update your Video and Display drivers. a.Go to Start > Control panel. b.Search for Device Manager, and then open it. c.Find V…

Unable to login to Skype for Business client?

Unable to login to Skype for Business client? In order to sign-in on Skype (Lync) you must have login credential provided to you from your organization. ·Sign-in address: bilag@orgname.com ·User name: orgname\bilag ·Password: ************
Note: Orgname.com is my SIP domain name. Here are the most common mistake people make while sign-in on Skype for Business (Lync).
1.If you have login credential however still unable to sign-in then make sure you are putting proper login credential. Below error shows when you are wrong entering your sign-in address:
2.If you are writing correct Sign-in address however getting DNS error then contact administrator/ Support team there may be a DNS resolution or configuration issue. Administrator need to verify the SfB (Lync) AutoDiscover DNS records. 3.Sometime users password may expired/ lockout: Make sure that you password is not expire and lockout. If yes then call to helpdesk and reset your password / unlock. 4.Make user to have updated Skype for Business cli…