No Skype for Business/Lync Server found
Error Message:
No Skype for Business/Lync Server found
Check whether the username provided in Domain Settings is a member of "RTCUniversalUserAdmins" / "RTCUniversalServerAdmins" / "RTCUniversalReadOnlyAdmins" Group.
Root Cause:
The Service account/Domain Admin account provided within ADManager Plus > Domain Settings does not have enough permission to make these changes.
Resolution:
We need to add the Service Account/Domain Admin Account of ADManager Plus - Domain settings to "RTCUniversalUserAdmins", "RTCUniversalServerAdmins", and "RTCUniversalReadOnlyAdmins". These groups will enable HelpDesk Technicians to add users to Skype/Lync.
Note:
If you are not using Impersonate As Admin, then we will need to add those groups directly to the technician in Native AD.
If you are using Impersonate As Admin, then we need to ensure that those groups are added to the service account updated in Domain settings.
New to ADSelfService Plus?
Related Articles
Error: No Skype for Business/Lync Server found when creating user using Create Single User feature.
Error Message: No Skype for Business/Lync Server found when creating a user using the Create Single User feature. Possible Cause: The technician account or the service account configured in Domain/Tenant Settings might not have necessary rights or ...While configuring the LCS/OCS server in user creation template I get an error: No Live Communication Servers found.
Error Message: While configuring the LCS/OCS server in user creation template I get an error: No Live Communication Servers found. Possible Cause: Lync connectivity issues. Solution: 1. Check whether the user account provided in the Domain/Tenant ...Error: Port 80 already in use. Change WebServer port in <ProductHome>/conf/server.xml
Error Message- Error: Port 80 already in use. Change WebServer port in <ProductHome>/conf/server.xml Possible Root Cause: This error message can be found in ADManager Plus, wrapper log file. This error message shows when ADManager Plus cannot start ...Error Code 35 : Error in Creating Terminal Services Home Directory/ Error in Creating Home Directory. The network path was not found.
Error : Error in Creating Terminal Services Home Directory/ Error in Creating Home Directory. The network path was not found. Possible Cause : The remote server path might not be accessible. Possible Solution : It seems ADManager Plus couldn't ...Can ADManager Plus be installed on Windows Server 2019
Yes. ManageEngine ADManager Plus supports the following Microsoft Windows operating system versions: Windows Server 2022 Windows Server 2019 Windows Server 2016 Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2 Windows Server 2008 ...