Lync 2010 -> Skype for Business Migration – Address Book/Authentication Issues



Lync Server 2010 – Enterprise Edition

Skype for Business Server 2015 – Enterprise Edition


When migrating a user from Lync Server 2010 to Skype for Business 2015 we encountered 2 issues:

  1. Address book search was not returning any values
  2. Authentication pop-up


The Lync Server 2010 web services can have connectivity issues that are centric to Kerberos authentication, which affect the Lync client’s ability access to them. In the Lync Server 2010 we had setup a Kerberos Account Assignment.

First we had to find the Kerberos Account that is used by running: Get-CsKerberosAccountAssignment

When the Kerberos Account Assignment was tested:  Test-CsKerberosAccountAssignment -Identity “Site:Ottawa” -Report “C:\temp\report.htm” – Verbose

The error below was received:

Test-CsKerberosAccountAssignment : The Kerberos configuration on is invalid. The expected assigned account is Company\kerberosuser. Ensure that the account has not expired, and the configured password on the machine matches the Active Directory password of the account.
At line:1 char:33
+ Test-CsKerberosAccountAssignment <<<<  -Identity “site:central”
    + CategoryInfo          : InvalidData: ([0] Company\kerberosacct:SourceCollection) [Test-CsKerberosAccountAssignment], Exception
    + FullyQualifiedErrorId : InvalidKerberosConfiguration,Microsoft.Rtc.Management.Deployment.TestKerberosAccountAssignmentCmdlet
WARNING: Test-CsKerberosAccountAssignment encountered errors. Consult the log file for a detailed analysis, and ensure all errors (1) and warnings (0) are addressed before continuing.
WARNING: Detailed results can be found at


We decided to copy the password from the account that is assigned on the Lync 2010 FE server by running the cmdlets below:

Set-CsKerberosAccountPassword -FromComputer “” -ToComputer “”

Set-CsKerberosAccountPassword -FromComputer “” -ToComputer “”

After the above cmdlets completed, we signed out of the Skype for Business client and signed back in the issues were resolved.



Leave a Reply

Your email address will not be published. Required fields are marked *