Forum Discussion
Teams creates new meeting links with old IDs
vikankare, Elle-Es, we found out a file which contains the next meeting id is stored for each user in C:\Users\[username]\AppData\Roaming\Microsoft\Teams\meeting-addin\Cache.
When you create a Teams meeting in Outlook or in Teams this file is renewed and will contain the new Meeting ID.
Problems with the synchronisation of the user profile probably causes issues with the renewal of this file. This could explain why the same meeting id is used in other meetings.
We are currently fixing the synchronisation issues in our company, I will post an update if this fixed the issues with the meeting ID for us.
- Elle-EsJun 25, 2020Copper Contributor
maurice23223 wow that is really interesting. That could definitely be the culprit in our case too the User reporting the issue is know to wander about with a laptop in and out of flakey wifi so profile syncing issues are entirely possibly to blame to lack of refresh in the meeting id
- Jörg von der OheJun 26, 2020Iron Contributor
We have an open case for this issues as well but it's kinda hard to reproduce on our side. Even deleting the meeting id cache file helps only for one or two days.
- PeterAlferinkJul 17, 2020Copper Contributor
Jörg von der Ohe It probably only works until there is an issue with the roaming profile and users get an old version of the profile (with an already used "next meeting-id").
- vikankareJun 25, 2020Copper Contributor
maurice23223that is interesting! I have been providing logs and information to product group through our ticket. I will let them know this too and of course keep this thread updated 🙂
They are currently waiting for more information. At least this seems to be finally going forward.
maurice23223you are saving user profile to network drive?- PeterAlferinkJul 17, 2020Copper Contributor
I am a colleague of maurice23223 , we store the User profile on a network share and the profile is roamed to users PC/laptop.
We disabled roaming for the teams data part. Problems are solved now.
It is not so smart (personal opinion) from the developers to store "the next meeting-id" in the cached file.
You can test the behaviour by editing the meeting ID in that cached file, it will re-use a previous meeting if the ID is already known.