Testing Unified Contact Store access in Lync Server 2013
Letztes Änderungsdatum des Themas: 2015-05-15
When run locally using the Lync Server-Verwaltungsshell, users must be members of the RTCUniversalServerAdmins security group.
When run using a remote instance of Windows PowerShell, users must be assigned an RBAC role that has permission to run the Test-CsUnifiedContactStore cmdlet. To see a list of all RBAC roles that can use this cmdlet, run the following command from the Windows PowerShell prompt:
The unified contact store introduced in Lync Server 2013 gives administrators the option of storing a user's contacts in Microsoft Exchange Server 2013 instead of in Lync Server. This allows the user to access the same set of contacts in Outlook Web Access in addition to Lync 2013. (Or, you can continue to store contacts in Lync Server. In that case, users will have to maintain two separate sets of contacts: one for use with Outlook and Outlook Web Access, and one for use with Lync 2013.)
You can determine whether or not a user's contacts were moved to the unified contact store by running the Test-CsUnifiedContactStore cmdlet. The Test-CsUnifiedContactStore cmdlet will take the specified user account, connect to the unified contact store, and attempt to retrieve a contact for the user. If no contacts can be retrieved then the command will fail together with the message "No contacts were received for the user. Verify that contacts exist for the user."
Note that the Test-CsUnifiedContactStore cmdlet will fail if the user has successfully migrated to the unified contact store but has no contacts on his or her Contacts list. The specified user must have at least one contact for the Test-CsUnifiedContactStore cmdlet to complete successfully.
Running the test
The commands shown in in the following example determine whether contacts for the user litwareinc\kenmyer can be found in the unified contact store. To do this, the first command in the example uses the Get-Credential cmdlet to create a Windows PowerShell command-line interface credentials object for the user litwareinc\kenmyer. Note that you must supply the password for this account to create a valid credentials object and to make sure that the Test-CsUnifiedContactStore cmdlet can run its check.
The second command in the example uses the supplied credentials object ($x) and the SIP address of the user litwareinc\kenmyer to determine whether his contacts can be found in the unified contact store.
$credential = Get-Credential "litwareinc\kenmyer" Test-CsUnifiedContactStore -TargetFqdn "atl-cs-001.litwareinc.com" -UserSipAddress "sip:email@example.com" -UserCredential $credential
Determining success or failure
If access to the contact store is configured correctly, you'll receive output similar to this, with the Result property marked as Success:
Target Fqdn : atl-cs-001.litwareinc.com
Result : Success
Latency : 00:00:14.9862716
Error Message :
If access to the contact store is not configured correctly, the Result will be shown as Failure, and additional information will be recorded in the Error and Diagnosis properties:
WARNING: Failed to read Registrar port number for the given fully qualified
domain name (FQDN). Using default Registrar port number. Exception:
System.InvalidOperationException: No matching cluster found in topology.
Target Fqdn : atl-cs-001.litwareinc.com
Result : Failure
Latency : 00:00:00
Error Message : 10060, A connection attempt failed because the connected party
did not properly respond after a period of time, or
established connection failed because connected host has
failed to respond 10.188.116.96:5061
Inner Exception:A connection attempt failed because the
connected party did not properly respond after a period of
time, or established connection failed because connected host
has failed to respond 10.188.116.96:5061
Reasons why the test might have failed
Here are some common reasons why Test-CsUnifiedContactStore might fail:
An incorrect parameter value was supplied. If used, the optional parameters must be configured correctly or the test will fail. Rerun the command without the optional parameters and see whether that succeeds.
Connect to the unified contact store failed, and the attempt to retrieve a contact for the user was not possible. There may be network connectivity issues.