Hey everyone! Hope your Monday is going well! I'm trying to set up several on-prem Skype for Business 2019 servers in a lab environment, but I'm stuck on an error when I run 'Setup or Remove SfB Server Components.' The error I get is: 'Error 0x8007054b (The specified domain either does not exist or could not be contacted)' related to DCOM layer settings. I've confirmed that all servers are part of the same domain, and I can access them with a domain account, plus DNS and nltest commands are returning normal results.
I've already tried adjusting the COM Security settings to include both RTCUniversalServerAdmins and my admin account for permissions, setting up a group policy for remote SAM calls (which I reverted as it caused issues), running the installer with and without admin rights, and placing the server in a staging area in AD without policies. The same error appears on all servers, suggesting some underlying policy or permission issue.
Could anyone suggest other troubleshooting steps I could try? Thanks in advance!
P.S. I know Skype 2019 is old and I plan to switch to Skype SE soon after handling this issue.
4 Answers
It feels like you're hitting a wall since you're trying to install something that's already been phased out. Just a thought, but why not consider moving straight to Teams or Slack instead? They offer better functionalities and support.
Honestly, as sysadmins, we should avoid setting up platforms that are already outdated, like Skype 2019. I suggest checking Microsoft's lifecycle documentation; they give a good insight into how long support will last for products like these. Might save you some headaches in the future!
I agree with the others — trying to get this setup working seems like a lot of effort for something that's pretty much obsolete. It might be much more efficient to skip this altogether and look towards more modern solutions.
Just out of curiosity, what’s prompting you to stick with Skype instead of transitioning to newer platforms like Teams? There are definitely better options available now.
Thanks for the insight! I'm aware it's dated, but I'm just wrapping up this project before transitioning to Skype SE.