Lync 2013 Issue with EWS integration - Continuous Prompt for Credentials

Reason to write this article is recently i faced an issue for EWS integration with Skype For Business/Lync 2013.This may be helpful for you....

Most of the articles talking about adding the domain to trusted model registry,auto-discovery and EWS URLs configuration.But after doing all these my issue did not solved.

Issue: EWS Status showing EWS is not fully Initialized / EWS Not Deployed

Basic Things we need to check :-

• DNS Entry for autodiscover.domain.com,Client machine should be able to resolve auto discover and EWS URLs
• If the SIP domain and SMTP Domain is different Email address Comparisoncheckdisabled value in Client policy should be True.
• EWS URL Should be deployed in Exchange Organisation
• Basic Authentication should be Enabled for Auto discover and EWS Virtual directory of Exchange server(All CAS Servers).
• Verify the Basic authentication using below command

         AutoDiscovery

Get-AutodiscoverVirtualDirectory -Server <CAS01> |fl BasicAuthentication .This should return value True.

If false set the value using 

Set-AutodiscoverVirtualDirectory -Server <CAS01> -BasicAuthentication $true

EWS

Get-WebServicesVirtualDirectory -Identity CAS01 |fl BasicAuthentication .This Should return value True.

If false set the value using

Set-WebServicesVirtualDirectory -Identity CAS01 -BasicAuthentication $true

• System web Proxy(PAC File or Manual Proxy) should exclude auto discover and EWS URLs

Now Will come to actual issue.Even after implementing all the above Lync client was not able to authenticate with Exchange server.Authentication windows was continuously popping up/Not accepting the credentials.

Solution:-We used fiddler to check what is happening with Exchange URL connectivity from Lync and found Lync client is trying to authenticate with Exchange using Negotiate:Kerberose mode and getting 401 Unauthorized access

• Logged on to Exchange server
• Opened INETMGR
• Clicked on Auto discover Virtual Directory
• Clicked on Authentication
• Right Click on Windows authentication and Select Providers
• Move NTLM to Top
• Repeated the same for EWS

But even after doing this Lync is trying to Negotiate for the challenge

• Logged on to Exchange server
• Opened INETMGR
• Clicked on Auto discover Virtual Directory
• Clicked on Authentication
• Right Click on Windows authentication and Select Providers
• Remove Negotiate mode
• Repeated the same for EWS

Enjoy Reading...Any doubt please comment...

Lync 2013 Guides

Microsoft come up with new product every now and there it is very difficult to support people to upto date on their technologies.Anyway we have to be upto dated else we will be out of market.
Ignite have wonder full document to learn more about Lync 2013 and Exchange 2013 ,here it goes

Lync 2013 Guides

Exchange 2013 Guides

Move CMS from Lync 2010 to Lync 2013

When we introduce Lync 2013 on Lync 2010 infra CMS will be on Lync 2010.So if we want to move the CMS to new 2013 pool here is the steps.
For safer part we can take config backup using export-csconfig and export-cslisconfig.
Next step is to install CMS store new Lync 2013 pool for that run the below command.

Install-Csdatabase -centralmanagementdatabase -usedefaultsqlpaths -sqlserverfqdn <backendsqlserverfqdn>

Next step is to move CMS server.

move-csmanagementserver

If the source cms server is offline you can use below command.

Move-CsManagementServer -ConfigurationFileName "C:\configfile.zip" -LisConfigurationFileName "C:\CsLisConfigfile.zip" -Force

Lync 2013 Evaluation And Subscriber Download available Now

Microsoft has released Lync 2013 Evaluation and Lync Basic Client.
Find the download Link and details below.

http://technet.microsoft.com/en-US/evalcenter/hh973393.aspx?wt.mc_id=TEC_118_1_1

Also Released Lync subscriber download.

https://technet.microsoft.com/en-us/subscriptions/securedownloads/hh442904

What's New Lync 2013

Below is the some major feature about Lync 2013 Preview

• Full IPv6 support
• VDI plugin, allowing full A/V support in virtual desktop environments
• H.264 SVC codec support
• Skype federation support
• Persistent chat (or group chat) becomes a "full-fledged" Lync service, not just a bolted-on add-on
• Audio and video added to Lync Web App
• Consolidation of roles; no separate server role needed for monitoring and archiving
• Hybrid deployments of on-premises and Lync Online cloud servers now supported (this capability is called "hybrid voice")
• Support for M-N trunk routing, plus support for inter-trunk routing. Lasko explains: "This feature allows Lync to act as an intermediary between two or more different phone systems. For example, Lync can accept calls from one PBX, and pass the call through to another PBX. This can be very useful in larger environments and allows Lync to be the backbone of a corporate telephone network."
• Support for a unified contact store, with information maintained in MIcrosoft Exchange Server 2013, enabling users to access/manage contacts from Lync 2013 Preview, Outlook or Outlook Web App