Forum Discussion
MS Teams External Chat not working
- Jun 30, 2021
yes in my post above I posted a command to clear all those locators. I think it was this one :
Get-ADUser -Filter {msRTCSIP-DeploymentLocator -like "SRV*"} |
Set-ADUser -Clear msRTCSIP-DeploymentLocator
http://terenceluk.blogspot.com/2020/11/powershell-script-for-clearing-msrtcsip.html
you can always try 1 account with the AD attribute editor and see if it works before dooing the command on all users. ( don't forget to sync to the cloud)Dooing a logout + login cycle for teams on the users computer might be required.
If not you can make a case with O365 support but I solved it myself before they had any decent info
no idea why this happens but in my case the Skype on prem server crashed before we could decommission properly.
yes in my post above I posted a command to clear all those locators. I think it was this one :
Get-ADUser -Filter {msRTCSIP-DeploymentLocator -like "SRV*"} |
Set-ADUser -Clear msRTCSIP-DeploymentLocator
http://terenceluk.blogspot.com/2020/11/powershell-script-for-clearing-msrtcsip.html
you can always try 1 account with the AD attribute editor and see if it works before dooing the command on all users. ( don't forget to sync to the cloud)
Dooing a logout + login cycle for teams on the users computer might be required.
If not you can make a case with O365 support but I solved it myself before they had any decent info
no idea why this happens but in my case the Skype on prem server crashed before we could decommission properly.
Check teams admin center and go to users. Check if there is a difference on the following options:
Directory status
Interpreted user type
Also check msRTCSIP-DeploymentLocator.
There is probably a difference, because the screenshot shows a different hosting provider and an internal S4B server. Looks like some users are moved to S4B Online / Teams, but DNS is pointing to internal S4B server.
- Lucas_ReisJun 30, 2021Copper Contributor