Thursday , May 14 2020

Some users are not showing in Teams Admin Center

Some users are not showing in Teams Admin Center. Its a night mare to figure out the issue. The issue happened to be some users had lync / skype for business attributes enabled and disabled in the past. Even thought it was decommissioned gracefully one of the attribute was enabled with a value of SRV: was causing the issue.

How to quickly test you are in the same boat . Check for RTC attributes for working and not working user.

Get-ADUser vaishika -Properties * | FL Samaccountname,*rtc*

Please note that i don’t have lync or skype for business deployment in the environment so i cleared all the attribute for the not working users.

Never run this on a Lync or skype for business working user. It will screw their lync or skype for business credentials

Just took a backup of the values am going to clear.

Get-ADUser -Filter * -Properties * -SearchBase "OU=01 Users,DC=azure365pro,DC=com" | Select-Object Samaccountname,msRTCSIP-DeploymentLocator | Export-Csv BackupAttribute.csv

Clear the attribute for all users –

Get-ADUser -Filter * -Properties * | Set-ADUser -Clear msRTCSIP-DeploymentLocator

Specific Organizational Unit –

Get-ADUser -Filter * -Properties * -SearchBase "OU=01 Users,DC=azure365pro,DC=com" | Set-ADUser  -Clear msRTCSIP-DeploymentLocator

or

Take the CSV Filter the accounts and Clear the Attribute for specific users –

Import-Csv clear.csv | ForEach-Object{Set-ADUser $_.samaccountname -Clear msRTCSIP-DeploymentLocator

For me msRTCSIP-DeploymentLocator was causing the issue but it could be any of the below attributes causing the issue. Still the lync and skype for busines legacy links is following Teams . Nothing can’t be done.

  • msRTCSIP-DeploymentLocator
  • msRTCSIP-FederationEnabled
  • msRTCSIP-InternetAccessEnabled
  • msRTCSIP-Line
  • msRTCSIP-OptionFlags
  • msRTCSIP-PrimaryHomeServer
  • msRTCSIP-PrimaryUserAddress
  • msRTCSIP-UserEnabled

After 60 minutes

About Satheshwaran Manoharan

Satheshwaran Manoharan is an Microsoft Office Server and Services MVP , Publisher of Azure365pro.com. Specialized in Office365 / Microsoft Exchange / Virtualization , Sathesh is an Messaging Expert supporting/Designing/Deploying many medium size businesses to large enterprises when it comes to Corporate messaging and Virtualization Infrastructure

Check Also

Leaving the Organization as guest in Teams

Leaving the Organization in teams is certainly important . So that you can come out …

2 comments

  1. Hi Satheshwaran,
    You mentioned, but it should be noticeable to all, not to use the script if you have a SfB Hybrid environment. Or nobody will be able to sign-in 🙂

    The most probable situation is the SRV value on the field combined with the fact that your tenant is not configured with a ‘shared address space’

Leave a Reply

Your email address will not be published.