We released the update yesterday and it is found here. Until now it has not been easy for an administrator to see if a given user had been migrated to UCS, but with the update we introduced the cmdlet Debug-CsUnifiedContactStore!
The cmdlet will show the UCS status for a given user or for all users on a pool. The user needs to be homed on a pool running the July update for the cmdlet to work, since it is using a new server based interface to get the status. An example of running the cmdlet is below:
Debug-CsUnifiedContactStore -Identity email@example.com
UcsMigrationAttemptCount LastUcsMigrationAttempt SipUri UcsMode
------------------------ ----------------------- ------ -------
2 3/20/2013 1:00:00 PM firstname.lastname@example.org Migrated
The cmdlet shows how many attempts have been made to migrate the user, when the last attempt was made, the SIP URI of the user and the UcsMode of the user. UcsMode can have the values:
You can also use it to see the general UCS status for all users on a given pool. An example of this is shown below:
Debug-CsUnifiedContactStore -PoolFqdn pool.contoso.dk
FrontEnd : pool.contoso.dk
UcsDisabledCount : 8
UcsAllowedCount : 0
UcsMigratingCount : 0
UcsMigratedCount : 2
You can also use the cmdlet to export the UCS contacts for a migrated user by using –ContactDataExportFileName. The cmdlet will read the UCS contacts from Exchange 2013 and save them in the ZIP file used as parameter.
PS C:\> Debug-CsUnifiedContactStore -Identity email@example.com –ContactDataExportFileName c:\ucs1.zip
The ZIP file contains two files as shown in the picture below. The actual contacts are stored in an XML format in the file DocItemSet.xml.
I'm having problems getting UCS working.
I've made all configurations, and tests returns 'Succes'.
But my contact list isn't migrated.
I was thinking that maybe it could be due to our DNS record naming.
Our Autodiscover is called, autodiscover.domain.com (domain.com being maildomain).
And Lyncpool is called, lyncpool.internal.local (internal.local being AD domainname).
Could it raise an issue, that theese domainnames, are different?
Jens>No, that shouldn't be the root cause of your issue.