Forum Discussion
External chat disabled after s4b onpremise to teams migration
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.
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?
- salman asif sAug 30, 2021Copper Contributor
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._tcp 3600 100 1 5061 sipfed.online.lync.com SRV _sip._tls 3600 100 1 443 sipdir.online.lync.com CNAME lyncdiscover 3600 N/A N/A N/A webdir.online.lync.com CNAME sip 3600 N/A N/A N/A sipdir.online.lync.com
reference: https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/decommission-manage-dns-entries3.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- salman asif sAug 31, 2021Copper Contributor
I have synchronized msRTCSip with Online.
Following are the Outputs:
HostingProvider : sipfed.online.lync.com
InterpretedUserType : AADConnectEnabledOnlineTeamsOnlyUserTrace:
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.
- salman asif sSep 01, 2021Copper Contributor
Finally Teams users with license are able to chat with external users.
Thanks to all AndresGorzelany 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 :
- 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-synchronized
Shown some errors during sync:
https://www.petenetlive.com/KB/Article/0001638
#Manualy Sync AD : Start-ADSyncSyncCycle -PolicyType delta5.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, CountryOrRegionDisplayName6. InterpretedUserType and HostingProvider are the main properties
Before sync:
Enabled : FalseTeamsUpgradeEffectiveMode : TeamsOnlyHostingProvider : SRV:InterpretedUserType : HybridOnpremTeamsOnlyUserAfter Sync
Enabled : TrueTeamsUpgradeEffectiveMode : TeamsOnlyHostingProvider : sipfed.online.lync.comInterpretedUserType : AADConnectEnabledOnlineTeamsOnlyUserIn teams admin center -> Users -> Add column "Interpreted User Type "After Sync below are the different user type shown for licensed usersInterpreted User Type : HybridOnlineEnabledUserWithSfBAndTeamsLicenseInterpreted User Type : HybridOnlineEnabledUserWithTeamsLicense7. 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 domainhttps://danielchronlund.com/2021/02/22/manage-teams-external-access-for-allowed-domains-using-powershell-and-teams-approvals/# 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-CsTenantFederationConfiguration9. 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-CsTenantFederationConfigurationNow External chat is working !!!!!
Please do comment to add more into this thread.