Troubleshooting Lync Sign-in Errors

I have users who can not sign in to lync after recreating their user name on AD error is as below.what do i need to do so that when i delete an account and recreate it afresh with the similar name they will be able to login to Lync

"You didn't get signed in.it might be your sign-in address or logon credentials so try those again.If that doesn't work.contact your support team


March 12th, 2015 8:38am

Hello Fridah!

As the user being enabled in Lync is not directly tied to their AD account, you need to remove the previous logon from Lync via the Lync Server Control Panel or Lync Management Shell, and then once they have been recreated in AD, you can re-add them and enable them in Lync. Unfortunately, Lync does not have the sort of integration with AD that will simply remove users and re-add them when their AD accounts are deleted or re-created.

I hope this helps clear it up

Free Windows Admin Tool Kit Click here and download it now
March 12th, 2015 10:07am

Thank you Josh, let me try that

Regards

Fridah

March 15th, 2015 7:42am

Hi

I have another issue, we have users from another domain not able to sign into Lync, we belong to the same forest and we are using lync 2013 located at our site and domain,What could be the problem?

NB we are in different countries.

Regards

Fridah

Free Windows Admin Tool Kit Click here and download it now
March 15th, 2015 7:57am

Hello Fridah,

Well, the quick answer is that if you have users within your Forest, but from another domain, that means that their sign-in name probably has a different domain than the users in your Lync 2013 domain. For example, if the domain that your Lync 2013 deployment is in is called domainA.com, then likely the users in this domain sign in to Lync with an address like user1@domainA.com. Further, the Lync 2013 deployment was probably only setup with 1 SIP domain: domainA.com. Now, if a user from the other domain, lets call it domainB.com, has an address of user2@domainB.com, and they try to sign into Lync (assuming their client is even finding the Lync server to begin with), they will not likely be able to log in because domainB.com is not setup as a SIP domain within Lync 2013. 

Obviously I am making a lot of assumptions above about what your setup might look like, but other things come into play like if you have all the proper DNS records setup for an assumed second domain address to login. This could actually be quite a number of things, and is very difficult to narrow down without many more details about your deployment, and if you deployed the Lync 2013 installation with multiple SIP domains in mind or not. However, if this brief bit of information does not really point you in a direction that gets you working, I would suggest opening a new thread with full details about how you designed the installation with this second SIP domain in mind, and what the environment looks like (as it is not really related to the question that this thread was opened for).

March 16th, 2015 10:01am

Hi Josh,

I removed the users from Lync via the Lync Server Control Panel and re-added, and enabled them but i did not succeed error is:You did not get signed in.it might be your sign-in address or logon credentials, so try those again

Any other suggestion?

thank you

Regards

Fridah


Free Windows Admin Tool Kit Click here and download it now
April 1st, 2015 1:17pm

But did you address the situation I discussed above, about having two domains, and whether or not Lync was set up with a SIP domain for each of those domains, or only for a SIP domain for the domain that your Lync deployment is located in? It does not matter whether you disable a user for Lync and then re-enable them. If they sign in with "user1@domainB.com", but your Lync deployment is only set up for a SIP domain of "domainA.com", then they simply will not be able to log in under the current configuration.

April 9th, 2015 1:37pm

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

Other recent topics Other recent topics