Forum Discussion
salman asif s
Aug 28, 2021Copper Contributor
External chat disabled after s4b onpremise to teams migration
We have shutdown skype for busines server .
Done below steps
1. changed all the dns configuration
2.changed coexistence mode in teams admin center to teams only.
3. Enabled external chat settings in teams admin center.
Now when users tries to chat with external user it shows "chat is disabled , This user is currently using Skype for Business".
when I checked teams admin center and powershell command I got following results.
Teams admin center :
Interpretedusertype:
HybridOnPremEnabledUserWithSfBAnd Teams License
Powershell results :
Hosting provider : srv:
Interpretedusertype: hybridonpremteamonlyuser
(Attached)
Only for few user external chat is working and the configuration is as follows
Teams admin center :
Interpretedusertype:
HybridOnlineEnabledUserWithSfBAnd Teams License
Powershell result:
Hosting provider : sipfed.online.lync.com
Interpretedusertype: AADConnectEnabledonlineteamonlyuser
(Attached).
Please advice how to fix this issue.
Done below steps
1. changed all the dns configuration
2.changed coexistence mode in teams admin center to teams only.
3. Enabled external chat settings in teams admin center.
Now when users tries to chat with external user it shows "chat is disabled , This user is currently using Skype for Business".
when I checked teams admin center and powershell command I got following results.
Teams admin center :
Interpretedusertype:
HybridOnPremEnabledUserWithSfBAnd Teams License
Powershell results :
Hosting provider : srv:
Interpretedusertype: hybridonpremteamonlyuser
(Attached)
Only for few user external chat is working and the configuration is as follows
Teams admin center :
Interpretedusertype:
HybridOnlineEnabledUserWithSfBAnd Teams License
Powershell result:
Hosting provider : sipfed.online.lync.com
Interpretedusertype: AADConnectEnabledonlineteamonlyuser
(Attached).
Please advice how to fix this issue.
12 Replies
- Hi, what have you done after the migration from Skype onPrem to Teams.
If your Hosting provider ist still srv: , this means your user is still on the SFB onPrem server.
The msRTCsip-Deploymentlocator should be sipfed.online.lync.com for all user in your AD- salman asif sCopper ContributorI tried running powershell command
Grant-CsTeamsUpgradePolicy for the users but it failed saying I have to run Move-CsUser first.
But when I tried executing Move-CsUser command, I get error saying Move-CsUser is not recognised . - salman asif sCopper ContributorHow will I achieve it .
Is there any powershell script I have to run in migration task.- You can test with one user to change the msRTCSIP-DeploymentLocator from SRV: to sipfed.online.lync.com, wait for AAD Sync and check the Interpretedusertype. If this is ok for the user, clear the msRTCSIP-DeploymentLocator and check the Interpretedusertype after AAD Sync.
This is for all users:
Get-ADUser -Filter {UserPrincipalName -eq "UPN"} -Properties * | Set-ADUser -clear msRTCSIP-DeploymentLocator
Here is a good lin, how to remove the SfB onPrem correct with all steps
https://imkarl.me/skype-for-business-server-decommission-after-migrating-to-microsoft-teams/
- salman asif sCopper ContributorWe didn't had much meeting data or contact list to migrate from skype to teams.
So we basically shutdown the skype server.
Changed dns entry and changed the coexistence mode to teamsonly in teams admin center.
- When did you do the change?
- salman asif sCopper Contributor
26-Aug