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.
Elan Shudnow :: Oct.28.2012 :: Lync ::