External chat disabled after s4b onpremise to teams migration

%3CLINGO-SUB%20id%3D%22lingo-sub-2695677%22%20slang%3D%22en-US%22%3EExternal%20chat%20disabled%20after%20s4b%20onpremise%20to%20teams%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2695677%22%20slang%3D%22en-US%22%3E%3CBR%20%2F%3EWe%20have%20shutdown%20skype%20for%20busines%20server%20.%3CBR%20%2F%3EDone%20below%20steps%3CBR%20%2F%3E1.%20changed%20all%20the%20dns%20configuration%3CBR%20%2F%3E2.changed%20coexistence%20mode%20in%20teams%20admin%20center%20to%20teams%20only.%3CBR%20%2F%3E3.%20Enabled%20external%20settings.%3CBR%20%2F%3E%3CBR%20%2F%3ENow%20when%20users%20tries%20to%20chat%20with%20external%20user%20it%20shows%20%22chat%20is%20disabled%20%2C%20This%20user%20is%20currently%20using%20Skype%20for%20Business%22.%3CBR%20%2F%3E%3CBR%20%2F%3Ewhen%20I%20checked%20teams%20admin%20center%20and%20powershell%20command%20I%20got%20following%20results.%3CBR%20%2F%3E%3CBR%20%2F%3ETeams%20admin%20center%20%3A%3CBR%20%2F%3EInterpretedusertype%3A%3CBR%20%2F%3EHybridOnPremEnabledUserWithSfBAnd%20Teams%20License%3CBR%20%2F%3EPowershell%20results%20%3A%3CBR%20%2F%3EHosting%20provider%20%3A%20srv%3A%3CBR%20%2F%3EInterpretedusertype%3A%20hybridonpremteamonlyuser%3CBR%20%2F%3E(Attached)%3CBR%20%2F%3E%3CBR%20%2F%3EOnly%20for%20few%20user%20external%20chat%20is%20working%20and%20the%20configuration%20is%20as%20follows%3CBR%20%2F%3ETeams%20admin%20center%20%3A%3CBR%20%2F%3EInterpretedusertype%3A%3CBR%20%2F%3EHybridOnlineEnabledUserWithSfBAnd%20Teams%20License%3CBR%20%2F%3E%3CBR%20%2F%3EPowershell%20result%3A%3CBR%20%2F%3EHosting%20provider%20%3A%20sipfed.online.lync.com%3CBR%20%2F%3EInterpretedusertype%3A%20AADConnectEnabledonlineteamonlyuser%3CBR%20%2F%3E(Attached).%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EPlease%20advice%20how%20to%20fix%20this%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2695677%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESkype%20for%20Business%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETeams%20Upgrade%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETeams%20Upgrade%20Guidance%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2695724%22%20slang%3D%22en-US%22%3ERe%3A%20External%20chat%20disabled%20after%20s4b%20onpremise%20to%20teams%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2695724%22%20slang%3D%22en-US%22%3EWhen%20did%20you%20do%20the%20change%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2695730%22%20slang%3D%22en-US%22%3ERe%3A%20External%20chat%20disabled%20after%20s4b%20onpremise%20to%20teams%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2695730%22%20slang%3D%22en-US%22%3E%3CP%3E26-Aug%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2695773%22%20slang%3D%22en-US%22%3ERe%3A%20External%20chat%20disabled%20after%20s4b%20onpremise%20to%20teams%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2695773%22%20slang%3D%22en-US%22%3EHi%2C%20what%20have%20you%20done%20after%20the%20migration%20from%20Skype%20onPrem%20to%20Teams.%3CBR%20%2F%3EIf%20your%20Hosting%20provider%20ist%20still%20srv%3A%20%2C%20this%20means%20your%20user%20is%20still%20on%20the%20SFB%20onPrem%20server.%3CBR%20%2F%3EThe%20msRTCsip-Deploymentlocator%20should%20be%20sipfed.online.lync.com%20for%20all%20user%20in%20your%20AD%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2695785%22%20slang%3D%22en-US%22%3ERe%3A%20External%20chat%20disabled%20after%20s4b%20onpremise%20to%20teams%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2695785%22%20slang%3D%22en-US%22%3EWe%20didn't%20had%20much%20meeting%20data%20or%20contact%20list%20to%20migrate%20from%20skype%20to%20teams.%3CBR%20%2F%3ESo%20we%20basically%20shutdown%20the%20skype%20server.%3CBR%20%2F%3EChanged%20dns%20entry%20and%20changed%20the%20coexistence%20mode%20to%20teamsonly%20in%20teams%20admin%20center.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2695786%22%20slang%3D%22en-US%22%3ERe%3A%20External%20chat%20disabled%20after%20s4b%20onpremise%20to%20teams%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2695786%22%20slang%3D%22en-US%22%3EHow%20will%20I%20achieve%20it%20.%3CBR%20%2F%3EIs%20there%20any%20powershell%20script%20I%20have%20to%20run%20in%20migration%20task.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2695789%22%20slang%3D%22en-US%22%3ERe%3A%20External%20chat%20disabled%20after%20s4b%20onpremise%20to%20teams%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2695789%22%20slang%3D%22en-US%22%3EI%20tried%20running%20powershell%20command%3CBR%20%2F%3EGrant-CsTeamsUpgradePolicy%20for%20the%20users%20but%20it%20failed%20saying%20I%20have%20to%20run%20Move-CsUser%20first.%3CBR%20%2F%3EBut%20when%20I%20tried%20executing%20Move-CsUser%20command%2C%20I%20get%20error%20saying%20Move-CsUser%20is%20not%20recognised%20.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2695792%22%20slang%3D%22en-US%22%3ERe%3A%20External%20chat%20disabled%20after%20s4b%20onpremise%20to%20teams%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2695792%22%20slang%3D%22en-US%22%3EYou%20can%20test%20with%20one%20user%20to%20change%20the%20msRTCSIP-DeploymentLocator%20from%20SRV%3A%20to%20sipfed.online.lync.com%2C%20wait%20for%20AAD%20Sync%20and%20check%20the%20Interpretedusertype.%20If%20this%20is%20ok%20for%20the%20user%2C%20clear%20the%20msRTCSIP-DeploymentLocator%20and%20check%20the%20Interpretedusertype%20after%20AAD%20Sync.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20is%20for%20all%20users%3A%3CBR%20%2F%3EGet-ADUser%20-Filter%20%7BUserPrincipalName%20-eq%20%22UPN%22%7D%20-Properties%20*%20%7C%20Set-ADUser%20-clear%20msRTCSIP-DeploymentLocator%3CBR%20%2F%3E%3CBR%20%2F%3EHere%20is%20a%20good%20lin%2C%20how%20to%20remove%20the%20SfB%20onPrem%20correct%20with%20all%20steps%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fimkarl.me%2Fskype-for-business-server-decommission-after-migrating-to-microsoft-teams%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fimkarl.me%2Fskype-for-business-server-decommission-after-migrating-to-microsoft-teams%2F%3C%2FA%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Occasional Contributor
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.
12 Replies
When did you do the change?

26-Aug

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

We 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.
How will I achieve it .
Is there any powershell script I have to run in migration task.
I 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 .
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/
Only password synchronisation was enabled and Attributes synchronisation was not enabled in AAD synchronisation configuration.
I did following step :
1. cleared msRTCSIP-DeploymentLocator attribute in local AD
2. RECONFIGURED AAD with attribute enabled for lync server
3. Initiatied manual synchronisation .
Still the values remain same in online.
In AAD synchronisation wizard , it shows success delta synchronisation and even I performed a full synchronisation but the values are not synchronising with online user.


@salman asif s 

 

Hello, it could take a couple of days after you make changes to on-premises attributes to reflect Online,

 

A couple of questions,

 

What is the current state of all msRTCSip- attributes?

Where are your DNS SRV records related to Skype/Teams pointing?

What is the value of OnPremHostingProvider/HostingProvider (Online side)?

What is the value of InterpretedUserType for the users?

 

 

@Andres Gorzelany 

1.What is the current state of all msRTCSip- attributes?


msRTCSIP-DeploymentLocator : sipfed.online.lync.com
msRTCSIP-FederationEnabled : True
msRTCSIP-InternetAccessEnabled : True
msRTCSIP-OptionFlags : 257
msRTCSIP-PrimaryHomeServer : CN=Lc Services,CN=Microsoft,CN=1:1,CN=Pools,CN=RTC
Service,CN=Services,CN=Configuration,DC=####,DC=com
msRTCSIP-PrimaryUserAddress : sip:#######
msRTCSIP-UserEnabled : True
msRTCSIP-UserPolicies : {0=1449800187}
msRTCSIP-UserRoutingGroupId : {237, 182, 12, 54...}


2.Where are your DNS SRV records related to Skype/Teams pointing?

SRV_sipfederationtls._tcp360010015061sipfed.online.lync.com
SRV_sip._tls36001001443sipdir.online.lync.com
CNAMElyncdiscover3600N/AN/AN/Awebdir.online.lync.com
CNAMEsip3600N/AN/AN/Asipdir.online.lync.com


reference: https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/decommission-manage-dns-entries

 

3.What is the value of OnPremHostingProvider/HostingProvider (Online side)?
HostingProvider : SRV:


4.What is the value of InterpretedUserType for the users?

Enabled : False
TeamsUpgradeEffectiveMode : TeamsOnly
InterpretedUserType : HybridOnpremTeamsOnlyUser

I have synchronized msRTCSip with Online.
Following are the Outputs:
HostingProvider : sipfed.online.lync.com
InterpretedUserType : AADConnectEnabledOnlineTeamsOnlyUser

 

Trace:

when i synchronized ,

InterpretedUserType changed to AADConnectEnabledOnlineTeamsOnlyUserNeedsProvisioningToAD

then after some time it got updated to AADConnectEnabledOnlineTeamsOnlyUser

 

But still external chat is not activate in teams.

Finally Teams users with license are able to chat with external users.

Thanks to all @Andres Gorzelany @Holger Bunkradt @adam deltinger @StaleHansen 

 

Issue :

Skype 4 business On premise shutdown and We have few users with teams license.

Those users with teams license were not able to chat with external users and below message was shown :

 "chat is disabled , This user is currently using Skype for Business".

 

 

Steps :

 

 

  1. Updated DNS to Online DNS

https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/decommission-manage-dns-entries

      2. Cleared all msRTCSip- attributes in Local AD

https://www.linkedin.com/pulse/sfb-on-prem-decommission-interpretedusertype-andres-gorzelany/

https://msunified.net/2019/07/11/my-post-migration-from-skype-to-teams-toolbox/

Before clear : 

msRTCSIP-DeploymentLocator: SRV

After Clear :

msRTCSIP-DeploymentLocator: 

 

#select users for clearing attributes  
$users=Get-ADuser 
foreach($user in $users){ 
$u=$user.UserPrincipalName 
#Get All msRTCSIP properties for a user that has a value 
$Properties=Get-ADuser -Filter {UserPrincipalName -eq  $u} -Properties * | Select-Object -Property 'msRTCSIP*' 
if($Properties -match "srv"){ 
    #clear all properties for a user 
     Get-ADuser -Filter {UserPrincipalName -eq  $u} -Properties * |Set-ADUser -Clear ($Properties | Get-Member -MemberType "NoteProperty "| % {$_.Name}) 
 $properties 
}}

 

 

3.Updated Coexistence Mode in Teams Admin Center to TEAMSONLY

https://admin.teams.microsoft.com/company-wide-settings/teams-upgrade

 

4. Used Latest Azure ad connect to Sync users with Online AD

Enabled Attribute synchronization for lync server and followed below article for recommended.

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/reference-connect-sync-attributes-syn...

Shown some errors during sync:

https://www.petenetlive.com/KB/Article/0001638

 

#Manualy Sync AD : 
Start-ADSyncSyncCycle -PolicyType delta 

 

 

5.Check Online user attribute 

 

#If MicrosoftTeams Module is Not installed
Install-Module MicrosoftTeams

#Import Microsoft teams
Import-Module MicrosoftTeams 

$userCredential = Get-Credential 
Connect-MicrosoftTeams -Credential $userCredential 

#Gets all users 
#Get-CsOnlineUser 

#Gets all Properties for Single user 
$user='abc@domain.com'

#Get-CsOnlineUser $user

#Gets all Properties related to Teams
Get-CsOnlineUser $user | Format-List UserPrincipalName, DisplayName, SipAddress, Enabled, TeamsUpgradeEffectiveMode, EnterpriseVoiceEnabled, HostedVoiceMail, City, UsageLocation, DialPlan, 
TenantDialPlan, OnlineVoiceRoutingPolicy,LineURI, OnPremLineURI, OnlineDialinConferencingPolicy, TeamsVideoInteropServicePolicy, TeamsCallingPolicy, HostingProvider,
InterpretedUserType, VoicePolicy, CountryOrRegionDisplayName

 

 

6. InterpretedUserType and HostingProvider are the main properties

Before sync:

Enabled                        : False
TeamsUpgradeEffectiveMode      : TeamsOnly
HostingProvider                : SRV:
InterpretedUserType            : HybridOnpremTeamsOnlyUser
 

After Sync

Enabled                        : True
TeamsUpgradeEffectiveMode      : TeamsOnly
HostingProvider                : sipfed.online.lync.com
InterpretedUserType            : AADConnectEnabledOnlineTeamsOnlyUser
 
In teams admin center -> Users -> Add column "Interpreted User Type " 
After Sync below are the different user type shown for licensed users
Interpreted User Type : HybridOnlineEnabledUserWithSfBAndTeamsLicense
Interpreted User Type : HybridOnlineEnabledUserWithTeamsLicense
    
7. Skype to teams Migration is complete.
 
8. But my external User chats not enabled Yet .Below message was showing
"We can't setup the conversation because your organizations are not set up to talk to each other".
  I checked the domains i have added for external sharing in Teams Admin center.
I used below powershell script to add multipel domain 

 

# Get current Teams federation settings before change. 
Write-Verbose -Verbose -Message "Before change:" 
Get-CsTenantFederationConfiguration 

# Disable communication with accounts on public IM and presence providers such as Windows Live, Yahoo, and AOL. 
Set-CsTenantFederationConfiguration -AllowPublicUsers $false 

# Enable Teams federation. 
Set-CsTenantFederationConfiguration -AllowFederatedUsers $true 

  
# Run for Add Multiple domain 
# Function to add allowed domain for Teams federation. 

function Enable-TeamsFederationForAllowedDomainsOnly { 
param ( 
 [parameter(Mandatory = $true)] 
 [string[]]$AllowedDomains, 
[parameter(Mandatory = $false)] 
 [switch]$RemoveExistingDomains 
 ) 
  # Remove existing domains (if requested). 
 if ($RemoveExistingDomains) { 
   Write-Verbose -Verbose -Message "Removing existing domains..." 
  Set-CsTenantFederationConfiguration -AllowedDomainsAsAList $null 
 } 
 # Add each domain to the list of allowed domains. 
 foreach ($Domain in $AllowedDomains) { 
 Write-Verbose -Verbose -Message "Adding $Domain..." 
Set-CsTenantFederationConfiguration -AllowedDomainsAsAList @{Add=$Domain} 
 } 
} 

# List of domain to allow. 
$AllowedDomains = "domain1.com", 
"domain2.com", 
"domain3.com" 

# Set Teams federation settings to allowed domains only. 
Enable-TeamsFederationForAllowedDomainsOnly -AllowedDomains $AllowedDomains -RemoveExistingDomains 

# Get current Teams federation settings after change. 
Write-Verbose -Verbose -Message "After change:" 
Get-CsTenantFederationConfiguration

 

 

9. Still it was not working , so i tried removing all the domains fom external sharing but it didnt allow me to clear everything from UI in teams admin center.
 
Used Below Powershell script

 

$x = New-CsEdgeAllowAllKnownDomains 
Set-CsTenantFederationConfiguration -AllowedDomainsAsAList $x 
Get-CsTenantFederationConfiguration 

 

 

Now External chat is working !!!!!

Please do comment to add more into this thread.

www.000webhost.com