Lync 2013 client: Onenote links not working after installing KB2910927
Hi, we have an issue with opening Onenote links from IM conversation with the Lync 2013 client. If you try to open a link you get an error "The web page onenote:https://... was not loaded in repsonse to you clicking the link because it is either invalid or restricted for security reasons". I noticed this issue appears only after installing KB2910927 (Lync 2013 December 2014 updates).

Does somebody else experience this? Is there any place we can set to trust links starting with onenote:... ?
January 6th, 2015 12:40pm

Hi,

Is it an OneDrive link that you tried to open? Does this issue happen to all hyperlinks or just OneNote links?

I have KB2910927 installed and tested with an OneNote link, but I cannot reproduce the issue. Maybe the KB2910927 is not the root cause.

If this issue happens to multiple users, we may try to run the following cmdlet on the Lync Server side to see the result:

Set-CsClientPolicy EnableURL $True

For more detailed information, please refer:

http://technet.microsoft.com/en-us/library/gg398300.aspx

Please let me know the result.

Regards,

Steve Fan

Forum Support

Free Windows Admin Tool Kit Click here and download it now
January 7th, 2015 2:28am

Hi Steve,

We don't user URL filtering. It used to work, but after installing the latest updates, all our users are getting this popup when they click a OneNote link.

OneNote links in this format are working fine: onenote:file.one

OneNote links in this format give the error: onenote:https://intranetpath/file.one

Other hyperlinks are working fine... (intranet and internet)

Regards,

Vincent



January 9th, 2015 11:55am

Hi Steve,

We don't user URL filtering. It used to work, but after installing the latest updates, all our users are getting this popup when they click a OneNote link.

OneNote links in this format are working fine: onenote:file.one

OneNote links in this format give the error: onenote:https://intranetpath/file.one

Other hyperlinks are working fine... (intranet and internet)

Regards,

Vincent



Free Windows Admin Tool Kit Click here and download it now
January 9th, 2015 11:55am

I'm pretty convinced KB2910927 (Lync 2013 December 2014 updates) is the cause.

What I tested:

Login to Lync 2013 client without KB2910927 -> no issue

Install KB2910927 and restart Lync client -> error is there

Remove KB2910927 again and restart Lync client -> no issue

January 9th, 2015 12:09pm

Hi,

Thanks for the update.

Now I found that I tested with a general notebook hyperlinks before. When I tested with onenote:file.one and onenote:https://intranetpath/file.one, I can reproduce this issue. Then, I tried uninstalling KB2910927, and found that the issue was gone.

I've submitted a feedback to our product team through internal way on this issue.

Since the KB applies to Lync 2013, we may also post a question in the Lync forum to see if we can get any suggestion on this issue. For your convenience:

https://social.technet.microsoft.com/Forums/lync/en-US/home?forum=lyncinterop

Regards,

Steve Fan

Forum Support

Free Windows Admin Tool Kit Click here and download it now
January 12th, 2015 7:50am

Hi Steve, thanks for the effort. Please keep us updated if you have some feedback from the product team.

January 12th, 2015 10:43am

Hi,

I'll let you know if I get any update on this issue. Please also keep your Office up-to-date and pay attention to our update release and blog articles.

Thanks for your understanding and support.

Regards,

Steve Fan

Forum Support

Free Windows Admin Tool Kit Click here and download it now
January 13th, 2015 2:19pm

Hello,

I also confirm that KB2910927 breaks the simple embedded urls on IM conversations.

January 29th, 2015 10:39pm
Users here experiencing the same issue.  The latest update that changed Lync into Skype For Business does not fix the issue.
Free Windows Admin Tool Kit Click here and download it now
April 24th, 2015 4:01pm
Has op or anybody else opened a bug on Connect?  I'm not having any luck searching for one.
April 27th, 2015 4:39pm

I'm seeing the same behavior using the Skype for Business that's part of Office 2016 as well.  We're using Lync as part of Office365.

The powershell to change the policy isn't accessible to us, and looking through the Office365 Admin Center hasn't come up with anything.  I'm curious if it's a policy setting server side to effect the change or if there's a client issue interpreting the policy incorrectly.  I wonder if there's something client side that can be changed.

Free Windows Admin Tool Kit Click here and download it now
April 30th, 2015 8:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics