The Lync MX Client is a new client that was released in late October 2012. Maybe people will refer to this client as the Lync MX client. In fact, when viewing log files, you will see the log files refer to MX. The interesting part about this client is it appears to be a hybrid between a full Lync client and the Lync client you will find on your other mobile devices such as IOS (both Iphone and IPad), Android, and Windows Phone 7. The biggest difference with the Lync RT client, is that it supports voice and video which allows you to use this client as a full blown client. It also allows my to expand Exchange Distribution Lists I have on my contact list, visual voicemail, conversation history, etc.. It is a richer client. That is for sure.
When first installing the Lync RT app from the Microsoft Store, logging will be turned off. However, the directory that will house the log files will be created similar to the full Lync 2010 and Lync 2013 client.
For the remainder of the article, I will use the following terminology:
- Lync MX (instead of Lync RT, Lync Metro, Lync Store App, etc…)
- Lync Desktop Client (instead of Lync 2010 or Lync 2013)
- Lync Mobile Client (used when referring to the IOS, WP7, or Android client)
So far, it seems like Lync MX is structured more like the full Lync desktop client.
From below, we can see the location of the tracing log files would be: C:\Users\Username\AppData\Local\Packages\Microsoft.LyncMX_8wekyb3d8bbwe\LocalState\Tracing. That Microsoft.LyncMX_8wekyb3d8bbwe directory may seem like a dynamic name, but it is not. It’s static and will be the same path no matter what installation you are looking at.
So far, we have no UCCAPI Logs which are the tracing logs we would use in Snooper to see what the client is doing. We also see no ETL logs which are the log files that provide more information that you would care to see (in 99.9% of cases). After logging into Lync MX, I still have no UCAAPI log files. What I realize is, that for the Lync MX Client, the log file we are looking for no longer does not end in the extension of UCCAPI as we’re used to with the Lync Desktop Client. The log file we’re looking for is actually Lynclog and does open in Snooper. But even though this log file exists, no data will be written to it just yet. We still need to configure a setting first.
Once in Options, scroll to the very bottom and turn on Diagnostic Logs.
Once this is On, I’ll log off and log back on to the Lync MX client. After doing so, I see some new ETL data and a WPPMedia folder. But, still no UCAPPI Log that we would use in Snooper to view client-side traces. What I realized is, with Diagnostic Logging turned on, I now also see some data in the Lynclog file.
So I tried opening the Lynclog file in Snooper and low and behold, it appears that LyncLog is the replacement for UCCAPI… at least for the Lync MX client.
If you have experience with the mobile client, you will know that once you turn on Diagnostic Logging, there is some action you must perform to save the log files. For example, in the WP7 client, you choose to save the log file and it creates a JPG that you can attach to an e-mail, rename to log on a PC, and view the log information.
So going back into the Lync MX Settings (Windows + I), go to About, scroll to the bottom and choose Save logs.
From digging around, it appears that the Save logs option doesn’t actually do anything. I’ll keep looking around to see if it actually does anything. If you discover it does anything, be sure to let me know and I’ll update the article accordingly.
Sorry, but how do you get into Lync "Settings" and "options" in RT?
You need to use the Charm and choose Settings.
I added your blog to favorites Looking for more update.
Great post. I must say thanks for the information. Education is definitely a sticky subject. However, is still among the leading topics of our time. I appreciate your post and look forward to more.
Yes entering CNAME for Lyncdiscover is must, without CNAME is invalid.
So I've been able to logon and make lync to lync IM's as well as federated ones, but anything that involves calling the PSTN fails miserably. watching the call trace, it looks like it never puts my line uri in the request when I try to make a call. Is that something I might need to have to wait until I setup 2013 to make work?
What if you can't sign in? then you can't get to the options screen to turn on logging.
normal client works fine.
Even if the client is not logged in you can still use the 'Settings' charm to access the Option menu and enable logging as Elan has shown here.
I was able to get the Lync MX client working by entering a CNAME for Lyncdiscover. When we originally signed up for Office365, it was right at release and that CNAME and the sip.{ourdomainname} one were not shown. So, we never entered them. As soon as I entered them, my Lync MX client could connect and it works fine now. A couple of the other guys on the forums said that did not work for them.
HTH,
Lon
Getting below lines in log, seems it is trying to discover sign in server using Internal URL against external URL
<!DOCTYPE ProgressReport>
<root>
<Lync-autodiscovery><![CDATA[GetBestManagedCredentialByType return the cred: 0000000000000000, type:specific, userId:LAD]]><![CDATA[Discovery request sent to URL http://lyncdiscoverinternal.contoso.com?sipuri=Te… txn (00000031BFCA3790)]]><![CDATA[GetBestManagedCredentialByType return the cred: 0000000000000000, type:specific, userId:LAD]]><![CDATA[Discovery request sent to URL https://lyncdiscoverinternal.contoso.com?sipuri=T… txn (00000031BFCA3810)]]><![CDATA[GetBestManagedCredentialByType return the cred: 0000000000000000, type:specific, userId:LAD]]><![CDATA[Discovery request sent to URL https://lyncdiscover.contoso.com?sipuri=Test1@con… txn (00000031BFCA3DB0)]]><![CDATA[GetBestManagedCredentialByType return the cred: 0000000000000000, type:specific, userId:LAD]]><![CDATA[Discovery request sent to URL http://lyncdiscover.contoso.com?sipuri=Test1@cont… txn (00000031BFCA4350)]]><![CDATA[
Starting LogonSession…
Local interfaces: count=1, allExternal=0, someInternal=0, backend=0
Using loaded endpoint config
InitialEndpointConfig calculated…
networksAvailable=1
cacheAvailable=0
takenFromCache =0
Doing logon attempt with data:
currState=10
[email protected]
server=<auto-discovered name>, internal
authModes=0x1000c
with default Cred
proxyAuthModes=0x1f
epFlags=88
withAutoRetrials=0
credsAvailability=valid
redirectedServersList=
newState=14
statusCode=0]]><![CDATA[CLogonCredentialManager::GetProxyCredentials()Credential user 0x00000031BA424900 id=15 asking for credentials with ProxyChallengeDetails[authModes=0, firewallName=, realm=]]]><![CDATA[CLogonCredentialManager::GetProxyCredentials()Credential user 0x00000031BA424900 id=15 asking for credentials with ProxyChallengeDetails[authModes=0, firewallName=, realm=]]]><![CDATA[CLogonCredentialManager::GetProxyCredentials()Credential user 0x00000031BA424900 id=15 asking for credentials with ProxyChallengeDetails[authModes=0, firewallName=, realm=]]]><![CDATA[CLogonCredentialManager::GetProxyCredentials()Credential user 0x00000031BA424900 id=15 asking for credentials with ProxyChallengeDetails[authModes=0, firewallName=, realm=]]]><![CDATA[Lync autodiscovery completed with hr: 0X80004005 sipint: sipext: authint: authext: wts: retry: 0]]><SequenceID>1.1</SequenceID><hr>0x80004005</hr></Lync-autodiscovery><![CDATA[
autoRetryByErrorCode=1
withRescheduleHint=0
withAutoRetrials=0
Login failed with permanent error or no auto-retrials]]></root>
Can we configure Lync RT client manually like Lync 2010 desktop client? I tried via /Shared registry but it doesn't seems to work.
Automatic configuration / Lync autodiscover is working fine in environment {tested with Lync 2010 desktop & mobile client}, but the Lync RT is giving error Lon mentioned "we can't connect to server, please check your sign in info."
Please ignore my post. I forgot that we had edge server still pointing to OCS 2007 R2 and Lync 2010 RT requires Lync Servr 2010 CU5.
Just tested this with my Office 365 Account. I used my [email protected] without any ADFS and things connect right in with Lync RT. If you use my blog and send me the log file, I can try to take a look. Send it to elan at Shudnow dot net. I'll look out for the log file later today as I rarely ever check this e-mail account.
Thanks Elan!
There are a few of us trying to troubleshoot this new Lync client on a Surface RT. Here is the thread: http://community.office365.com/en-us/forums/166/p…
For me, I have finally been able to login using my Admin ID for Office365 but I can't signin using my user email. It won't prompt for a password and when I've been able to get the password field to come up, I enter my user email and password and it says "invalid ID or password". I can successfully login from two other PC's so I know it's working (and it has been for months now…).
Any ideas or direction for us?
Thanks for your help!
Lon