![]() ![]() For information about ADSIEdit, go to the following Microsoft website. Open Active Directory Service Interfaces Edit (ADSIEdit) from the on-premises domain controller. If you previously had an Office Communications Server (OCS) or Lync deployment that's no longer being used, you may have to manually edit the user's msRTCSIP attributes to fix the issue. You can also follow the next steps to manually fix the issue. Deleting the user and not just disabling them, from Lync will remove the values in** msRTCSIP** attributes for the user. ![]() If you aren't in a Lync hybrid environment, but still have an on-premises Lync Server, delete the user from the Lync Control Panel or Lync Management Shell. If you're in a Lync hybrid environment and still running Lync Server on-premises, enable the user for Lync through the Lync Control Panel or Lync Management Shell, and then move them to Skype for Business Online. Force a directory synchronization, and then wait 30 minutes. If you're synchronizing your on-premises Active Directory with Microsoft 365 and the user is already licensed for Skype for Business Online but still can't sign in, make sure that the value of msRTCSIP-UserEnabled is TRUE in the on-premises Active Directory schema. After the user is licensed, the user will be displayed in the Lync Admin Center. To resolve this issue, first make sure that the user is licensed for Skype for Business Online in the Microsoft 365 portal. If the problem continues, please contact your support team. Verify the sign-in address and try again. When you try to sign in to Skype for Business Online (formerly Lync Online), you receive the following error message:Ĭannot sign in to Lync because this sign-in address was not found. ![]()
0 Comments
Leave a Reply. |