SOLVED

Issue with New Teams not showing our own Organization and only Guests Organizations

Copper Contributor

Having a issue with New Teams not showing my primary organization and only showing my guest organizations. After a fresh installation of Teams I was able to see my own organization until I did a restart of Teams. Once it was restarted I can only see the organizations that i've been invited to.

 

If I change back to classic teams I can see my own organizations and also the guest organizations.

 

I've tried reinstalling and clearing %appdata% from Teams. Anyone else that are having this issue? It's only on 1 computer everyone else in the organization are able to use the New Teams and see our own organization aswell as the guests ones.

5 Replies

Hi @FROST374,

can you try to completely sign-out and then sign-in in the new Microsoft Teams client and check if the issue is still there?


Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.


If the post was useful in other ways, please consider giving it Like.


Kindest regards,


Leon Pavesic
(LinkedIn)
(Twitter)

@LeonPavesic 


Hi Leon, 

Yes the issue is still there even after you sign in and sign out.

We've tried a reinstall and it works after the reinstall until you restart the computer or sign out.

best response confirmed by FROST374 (Copper Contributor)
Solution
Hi,

I'm using my personal account here, as I am not allowed to use my organization's for this kind of actions.

I had this problem on a company I work with (roughly 200 employees) who had this problem. After extensive trial and error I managed to find a way to make all organizations appear proerly on Teams - and apparently it might have to do with the current early access content (I may be wrong on that). This is what I did, in this order:

1) Closed all instances of Teams (both classic and new) and uninstall both via control panel and/or Apps&Features;

2) Deleted folder %AppData%\Microsoft\Teams. This will remove stored content related to the current user's Teams account (Classic).

3) Deleted folder %LocalAppData%\Microsoft\Teams. This will remove local Teams (classic) user's information on Windows (I believe).

4) Deleted Folder %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe. This will remove all information regarding your user on Teams (new). They are usually migrated from the previous folders when you upgrade from Teams classic to the new Teams;

5) Disconnected the user's Work/School account through Access Work or School;

6) Deleted Folders %LocalAppData%\Microsoft\OneAuth, %LocalAppData%\Microsoft\TokenBroker and %LocalAppData%\Microsoft\IdentityCache. This removes, as far as I know, all user Login information and Tokens, and might include credentials to other services. I am not certain this step is relevant, but it seemed to do the job on my end (it was safe for me to do so as this organization's employees are not supposed to store any kind of passwords) - do so at own risk!

7) Reinstalled Teams (I used the latest exe for the classic teams and upgraded to the new one, but it seems to work on the teamsbootstrapper.exe with argument "-p" for the new one as well - I could not verify through the .msix as this organization's Laptops have the microsoft Store disabled).

This also seemed to remove the Early Access versions across all clients I tested this procedure with (which aren't many, admittedly).
Also note that I am in no way any Microsoft MVP, so do not take it as a fix or a solution for all. This worked on my scenarios and hasn't been tested properly on other environments. Take it with a grain of salt.

Best Regards,
Seth Dakam
Worked fine for me as well! Thanks for sharing this.
Just one remark for step 4: The folder was called MicrosoftTeams_8w... in my case not MSTeams_8w..
1 best response

Accepted Solutions
best response confirmed by FROST374 (Copper Contributor)
Solution
Hi,

I'm using my personal account here, as I am not allowed to use my organization's for this kind of actions.

I had this problem on a company I work with (roughly 200 employees) who had this problem. After extensive trial and error I managed to find a way to make all organizations appear proerly on Teams - and apparently it might have to do with the current early access content (I may be wrong on that). This is what I did, in this order:

1) Closed all instances of Teams (both classic and new) and uninstall both via control panel and/or Apps&Features;

2) Deleted folder %AppData%\Microsoft\Teams. This will remove stored content related to the current user's Teams account (Classic).

3) Deleted folder %LocalAppData%\Microsoft\Teams. This will remove local Teams (classic) user's information on Windows (I believe).

4) Deleted Folder %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe. This will remove all information regarding your user on Teams (new). They are usually migrated from the previous folders when you upgrade from Teams classic to the new Teams;

5) Disconnected the user's Work/School account through Access Work or School;

6) Deleted Folders %LocalAppData%\Microsoft\OneAuth, %LocalAppData%\Microsoft\TokenBroker and %LocalAppData%\Microsoft\IdentityCache. This removes, as far as I know, all user Login information and Tokens, and might include credentials to other services. I am not certain this step is relevant, but it seemed to do the job on my end (it was safe for me to do so as this organization's employees are not supposed to store any kind of passwords) - do so at own risk!

7) Reinstalled Teams (I used the latest exe for the classic teams and upgraded to the new one, but it seems to work on the teamsbootstrapper.exe with argument "-p" for the new one as well - I could not verify through the .msix as this organization's Laptops have the microsoft Store disabled).

This also seemed to remove the Early Access versions across all clients I tested this procedure with (which aren't many, admittedly).
Also note that I am in no way any Microsoft MVP, so do not take it as a fix or a solution for all. This worked on my scenarios and hasn't been tested properly on other environments. Take it with a grain of salt.

Best Regards,
Seth Dakam

View solution in original post