Blog Post

Skype for Business Blog
2 MIN READ

Skype for Business Outdated Client Issue : TurnAuthUnknownUser

Aaron Steele's avatar
Aaron Steele
Former Employee
Jan 18, 2017

We've identified a number of tenants that are using older clients with a bug that's causing media sessions to fail to establish. If you were to diganose these issues, you would see in the logs a possible report of “TurnAuthUnknownUser” . We have created a report you can use by uploading it to https://cqd.lync.com to identifiy the number of different clients in use in your environment.  You can thereby work to update your users to a recent and consistent version.

To see if you are having this issue, download the attachment to this article and upload it into https://cqd.lync.com by entering the detailed reports page and chosing "Import" from the left hand menu.

Once imported, a very important change must be made to ensure only clients in use in your own deployment are being checked and you aren't reporting on federated or meetings being joined from federated partners hosted on your tenant are being shown.

To do that, go to the new report you have just imported. By default it will be all the way to the right, the last one in the list of detailed reports.

On that report, hit the "Edit" link as pictured above.

Once within the Edit interface for the report see the "Filters" section at the bottpom of the left pane.

Within the Filters; select "Second Tenant ID" and paste in your tenanat ID.

 

To retreive your tenant ID, the simplest way is to sign into your Skype for Business Admin portal and see it on the "Dashboard" tab you are on when you first access the portal. To access the portal sign into https://portal.office.com/admin/default.aspx and use the service admin portals section on the bottom left and select "Skype for Business" to be directed to your forest and tenant admin page as pictured. TenantID is shown on the admin portal as "Organization ID". The GUID represented there should be pasted into your CQD report. 

 

Please refer to  Office 365 client update channel releases article to see how latest client version available at https://technet.microsoft.com/en-us/office/mt465751.aspx

 

As additional information, please see the Change Management for Office 365 Clients article below to help understand what the update methodology is and how you can manage and allow for automatic updates while still maintianing a level of control within your organization https://technet.microsoft.com/library/mt584223.

Updated Jan 24, 2017
Version 2.0

6 Comments

  • Hi George, sorry I missed this. So, this isn't as much about that we have a version you should avoid, or a "known gold" version, but about identinting the clients that your users are using that are having problems with this in your set up.

  • George Cabe's avatar
    George Cabe
    Iron Contributor

    Thanks Garry for speaking up and thanks Aaron for the clarification. 

     

    I downloaded and ran the report and had the same thoughts as Garry...I thought I must be missing something basic, but I guess not.

     

    Aaron mentions "a bug":  is there a specific bug and fix that we can look for?  At which level of client was it fixed?

     

    Thanks again 

  • Hi Gary,

    Thanks for the feedback and discussion and I think you are right. I think I mischaracterized the report when I posted this and will work to correct that. However

     

    The report shows a list of all client versions of type OC that are currently in use by the Tenants users. It does not attempt to filter only to bad versions. Reason being is that a report that shows all versions and then providing the tenants with a means to look for the latest versions.  This allows you to review how many and what versions are in use wihtin your tenant.

  • Garry Williams's avatar
    Garry Williams
    Copper Contributor

    Hi Aaron,

    Thanks for this. I just wanted to clarify a couple of points: firstly, your post above says that the attached CQD report to "... identifiy the number of incidences of this error [TurnAuthUnknownUser] within your environment". I don't believe that it does. The report description in the CQDX file says that it ''... summarizes the client versions in use for which it is recommended that the latest update be installed." It does not look at fail-to-establish occurrences at all. Secondly, I take the description in the report itself to mean that it will return a list of all OC versions in use that are specifically susceptible to this issue at hand. But looking at the CQD report (dimensions, measurements, filters) it just returns a list of all OC versions (to be precise - those that have made at least one call over the measured period). So in essence, the script is just returning a list of OC clients in use within the tenant and the guidance behind this is 'stayed patched folks'. If that's the case, I think it's worth clarifying that in your post above as the report does not seem to report on this specific issue.

    Thanks,

    Garry