locked
Skype for Business 2016 client rollout, users getting credentials prompt RRS feed

  • Question

  • We are in the process of upgrading the Office suite on our PCs from 2013 ProPlus click to run, to 2016 ProPlus click to run.  We have an on premise Lync 2010 standard server running the latest CU (April 2016).  We only use Lync for IM/presence at this time - no voice, video or meetings.  The Skype for Business 2013 client works well and we don't have any issues.  The SFB 2016 client also works well - it signs in without issues and IM/presence works fine.  However after about a minute of signing in a credentials prompt will appear.  It's a standard windows credentials prompt that says "Skype for Business connection to username@domain.com".  When you mouse over the prompt in the taskbar is says "outlook security" so it appears to be SFB trying to connect to the mailbox.  I've enabled full logging in the Skype client but nothing shows up here.  Does anyone have any tips on what to look for?  I know Lync 2010 is old but I can't find anything that says the SFB 2016 client is incompatible.   We are running Exchange 2016 enterprise on premise.
    Wednesday, August 31, 2016 9:18 PM

Answers

  • It appears the credentials prompts are due to a MAPI connection failure to the Outlook profile. It appears this KB article describes the issue.  https://support.microsoft.com/en-us/kb/3147130 The workaround is way to complicated to implement for our users, we will just wait for a fix.
    • Marked as answer by Ari_P Thursday, September 1, 2016 11:21 PM
    Thursday, September 1, 2016 11:21 PM

All replies

  • lichen8686,

    Check to make sure the HLB in front of the CAS servers is configured correctly. Do you have session affinity enabled on the HLB? What kind of HLB do you have in front of Exchange?

    -Don

    Wednesday, August 31, 2016 11:41 PM
  • Hi Don-

    Thanks for the message but we don't use HLBs for either Lync or Exchange.

    Thursday, September 1, 2016 6:31 PM
  • It appears the credentials prompts are due to a MAPI connection failure to the Outlook profile. It appears this KB article describes the issue.  https://support.microsoft.com/en-us/kb/3147130 The workaround is way to complicated to implement for our users, we will just wait for a fix.
    • Marked as answer by Ari_P Thursday, September 1, 2016 11:21 PM
    Thursday, September 1, 2016 11:21 PM